HideMyAss.com

Tuesday, 10 October 2017

[Fail2Ban] SSH: banned 91.75.80.74 from herbalyzer.com

Hi,

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


Here is more information about 91.75.80.74:

[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.75.80.0 - 91.75.87.255'

% Abuse contact for '91.75.80.0 - 91.75.87.255' is 'abuse@du.ae'

inetnum: 91.75.80.0 - 91.75.87.255
netname: IC-Pkg4-POP1-NET
descr: Emirates Integrated Telecommunications Company PJSC (EITC-DU)
country: AE
remarks: *******************************************************************
remarks: * For any kind of illegal activity originating from our network *
remarks: * Please Contact: abuse@du.ae *
remarks: *******************************************************************
admin-c: EITC2-RIPE
tech-c: EITC2-RIPE
status: Assigned PA
mnt-by: DIC-MNT
mnt-lower: DIC-MNT
mnt-routes: DIC-MNT
created: 2007-12-09T15:38:49Z
last-modified: 2011-01-18T12:24:37Z
source: RIPE

role: EITC Contact Role
address: Emirates Integrated Telecommunications
address: P.O.Box:502666
address: Shatha Tower 25th Floor, Dubai, UAE
phone: +97143600000
fax-no: +97143916800
admin-c: CC7854-RIPE
tech-c: CC7854-RIPE
tech-c: CC7854-RIPE
tech-c: CC7854-RIPE
nic-hdl: EITC2-RIPE
abuse-mailbox: abuse@du.ae
mnt-by: DIC-MNT
created: 2006-07-25T04:42:43Z
last-modified: 2017-01-04T11:24:48Z
source: RIPE # Filtered

% Information related to '91.75.64.0/19AS15802'

route: 91.75.64.0/19
descr: Emirates Integrated Telecommunications Company PJSC
origin: AS15802
mnt-by: DIC-MNT
created: 2007-12-05T12:07:34Z
last-modified: 2007-12-05T12:07:34Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.89.2 (WAGYU)

Regards,

Fail2Ban

No comments:

Post a Comment