Hi,
The IP 212.170.50.203 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 212.170.50.203:
[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 '212.170.48.0 - 212.170.63.255'
% Abuse contact for '212.170.48.0 - 212.170.63.255' is 'nemesys@telefonica.es'
inetnum: 212.170.48.0 - 212.170.63.255
netname: RIMA
descr: Telefonica de Espana SAU (NCC # 2008052974)
descr: Red de servicios IP
descr: Spain
country: ES
admin-c: ATdE1-RIPE
tech-c: TTdE1-RIPE
status: ASSIGNED PA
mnt-by: MAINT-AS3352
mnt-lower: MAINT-AS3352
mnt-routes: MAINT-AS3352
created: 2014-05-29T16:34:23Z
last-modified: 2014-05-29T16:34:23Z
source: RIPE
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.es
created: 2006-01-18T12:24:41Z
last-modified: 2018-09-18T10:36:42Z
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.es
created: 2006-01-18T12:39:59Z
last-modified: 2018-09-18T12:08:51Z
source: RIPE # Filtered
% Information related to '212.170.0.0/16AS3352'
route: 212.170.0.0/16
descr: TDENET (Red de servicios IP)
origin: AS3352
mnt-by: MAINT-AS3352
mnt-routes: MAINT-AS3352
mnt-lower: MAINT-AS3352
created: 2002-03-13T15:00:02Z
last-modified: 2006-06-22T09:44:31Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.92.6 (WAGYU)
Regards,
Fail2Ban
No comments:
Post a Comment