HideMyAss.com

Sunday, 17 June 2018

[Fail2Ban] SSH: banned 80.26.116.5 from natural-breast-active.com

Hi,

The IP 80.26.116.5 has just been banned by Fail2Ban after
2 attempts against SSH.


Here is more information about 80.26.116.5:

[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 '80.26.0.0 - 80.26.127.255'

% Abuse contact for '80.26.0.0 - 80.26.127.255' is 'nemesys@telefonica.com'

inetnum: 80.26.0.0 - 80.26.127.255
netname: RIMA
descr: Red de servicios IP
country: ES
admin-c: ATdE1-RIPE
tech-c: TTdE1-RIPE
status: ASSIGNED PA
mnt-by: MAINT-AS3352
created: 2003-09-23T12:38:29Z
last-modified: 2016-04-22T09:32:08Z
source: RIPE # Filtered

role: Administradores Telefonica de Espana
address: Ronda de la Comunicacion s/n
address: Edificio Norte 1, planta 6
address: 28050 Madrid
address: SPAIN
org: ORG-TDE1-RIPE
admin-c: KIX1-RIPE
tech-c: TTDE1-RIPE
nic-hdl: ATDE1-RIPE
mnt-by: MAINT-AS3352
abuse-mailbox: nemesys@telefonica.com
created: 2006-01-18T12:24:41Z
last-modified: 2018-06-05T08:57:59Z
source: RIPE # Filtered

role: Tecnicos Telefonica de Espana
address: Ronda de la Comunicacion S/N
address: 28050-MADRID
address: SPAIN
org: ORG-TDE1-RIPE
admin-c: TTE2-RIPE
tech-c: TTE2-RIPE
nic-hdl: TTdE1-RIPE
mnt-by: MAINT-AS3352
abuse-mailbox: nemesys@telefonica.com
created: 2006-01-18T12:39:59Z
last-modified: 2018-04-09T09:43:13Z
source: RIPE # Filtered

% Information related to '80.26.0.0/16AS3352'

route: 80.26.0.0/16
descr: TDENET (Red de servicios IP)
origin: AS3352
mnt-by: MAINT-AS3352
mnt-routes: MAINT-AS3352
mnt-lower: MAINT-AS3352
created: 2011-03-10T10:22:10Z
last-modified: 2011-03-10T10:22:10Z
source: RIPE

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

Regards,

Fail2Ban

No comments:

Post a Comment