Hi,
The IP 212.86.37.55 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 212.86.37.55:
[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.86.37.0 - 212.86.37.127'
% Abuse contact for '212.86.37.0 - 212.86.37.127' is 'abuse@dns-net.de'
inetnum: 212.86.37.0 - 212.86.37.127
netname: MARTENSNET
descr: Martens Cluster 302 Barnerstrasse
country: DE
admin-c: MA7584-RIPE
tech-c: SN1014-RIPE
status: ASSIGNED PA
mnt-by: SMARTNET-MNT
mnt-lower: SMARTNET-MNT
mnt-routes: SMARTNET-MNT
created: 2013-06-28T11:44:56Z
last-modified: 2013-06-28T11:44:56Z
source: RIPE
role: Martens Admin
address: Martens Antennen und Kabelanlagen GmbH
address: Papenreye 31
address: D-22453 Hamburg
phone: +49 40 55 421 20
fax-no: +49 40 55 421 240
abuse-mailbox: info@martens.tv
admin-c: NA2181-RIPE
tech-c: SN1014-RIPE
nic-hdl: MA7584-RIPE
mnt-by: SMARTNET-MNT
created: 2007-07-12T12:00:26Z
last-modified: 2007-07-12T12:00:26Z
source: RIPE # Filtered
role: smartnet NOC
address: smartnet Online Service GmbH
address: Schnackenburgallee 177
address: D-22525 Hamburg
phone: +49 40 55 400
fax-no: +49 40 55 40 1040
abuse-mailbox: abuse@smartnet.de
admin-c: JT1831-RIPE
tech-c: SN1014-RIPE
tech-c: CM-RIPE
tech-c: OT408-RIPE
tech-c: JT1831-RIPE
nic-hdl: SN1014-RIPE
mnt-by: SMARTNET-MNT
created: 2002-05-29T12:23:18Z
last-modified: 2012-07-10T08:15:54Z
source: RIPE # Filtered
% Information related to '212.86.32.0/19AS15366'
route: 212.86.32.0/19
descr: DE-1STCOM-20140806
origin: AS15366
mnt-by: DNSNET-MNT
mnt-lower: DNSNET-MNT
created: 2014-08-06T10:06:11Z
last-modified: 2014-08-06T10:06:11Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.93.2 (ANGUS)
Regards,
Fail2Ban
No comments:
Post a Comment