HideMyAss.com

Thursday, 16 March 2017

[Fail2Ban] SSH: banned 91.79.249.255 from herbalyzer.com

Hi,

The IP 91.79.249.255 has just been banned by Fail2Ban after
5 attempts against SSH.


Here is more information about 91.79.249.255:

[Querying whois.ripe.net]
[whois.ripe.net]
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.

% Information related to '91.78.0.0 - 91.79.255.255'

% Abuse contact for '91.78.0.0 - 91.79.255.255' is 'abuse@mtu.ru'

inetnum: 91.78.0.0 - 91.79.255.255
netname: MTU-PPPOE
descr: Comstar-Direct CJSC
descr: Mamonovskij pereulok d.5
descr: P.O. BOX 38 123001
descr: Moscow, Russia
country: RU
admin-c: MTU1-RIPE
tech-c: MTU1-RIPE
status: ASSIGNED PA
mnt-by: MTU-NOC
created: 2009-06-22T12:41:30Z
last-modified: 2009-06-22T12:41:30Z
source: RIPE

role: MTU-Intel NOC
address: PJSC MTS / former CJSC Comstar-Direct
address: Petrovsky blvd 12, bldg 3
address: P.O. BOX 4711 127051
address: Moscow, Russia
remarks: **************************************
remarks: Contact addresses:
remarks: routing & peering noc@mtu.ru
remarks: spam & security abuse@mtu.ru
remarks: mail postmaster@mtu.ru
remarks: ddos reports ddos-reports@mtu.ru
remarks: **************************************
phone: +7 495 721-34-99
fax-no: +7 495 956-07-07
admin-c: EDA-RIPE
admin-c: RPS-RIPE
tech-c: EDA-RIPE
tech-c: SAAP-RIPE
nic-hdl: MTU1-RIPE
mnt-by: MTU-NOC
created: 2002-10-18T13:29:19Z
last-modified: 2015-12-28T13:23:12Z
source: RIPE # Filtered

% Information related to '91.76.0.0/14AS8359'

route: 91.76.0.0/14
descr: ZAO MTU-Intel's Moscow Region Network
descr: ZAO MTU-Intel
descr: Moscow, Russia
origin: AS8359
mnt-by: MTU-NOC
created: 2006-09-13T10:51:37Z
last-modified: 2006-09-13T10:51:37Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.88 (ANGUS)

Regards,

Fail2Ban

No comments:

Post a Comment