Hi,
The IP 212.92.112.141 has just been banned by Fail2Ban after
2 attempts against SSH.
Here is more information about 212.92.112.141:
[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.92.112.0 - 212.92.112.255'
% Abuse contact for '212.92.112.0 - 212.92.112.255' is 'abuse@amsterdamresidential.com'
inetnum: 212.92.112.0 - 212.92.112.255
netname: Amsterdam_Residential_Television_and_Internet_Network
country: NL
org: ORG-ARTA4-RIPE
admin-c: ARTA2-RIPE
tech-c: ARTA2-RIPE
status: ASSIGNED PA
mnt-by: MNT-NFORCE
created: 2016-12-19T17:00:23Z
last-modified: 2016-12-19T17:00:23Z
source: RIPE # Filtered
mnt-lower: MNT-NFORCE
mnt-routes: MNT-NFORCE
organisation: ORG-ARTA4-RIPE
org-name: Amsterdam Residential Television and Internet, LLC
org-type: OTHER
descr: Amsterdam Residential Television and Internet
address: 2885 Sanford Ave. SW Suite 20138
address: Grandville, MI 49418
abuse-mailbox: abuse@amsterdamresidential.com
abuse-c: ARTA2-RIPE
mnt-ref: MNT-NFORCE
mnt-by: MNT-NFORCE
created: 2016-12-19T14:54:43Z
last-modified: 2016-12-21T14:45:14Z
source: RIPE # Filtered
role: Amsterdam Residential Television and Internet, LLC
address: 2885 Sanford Ave. SW Suite 20138
address: Grandville, MI 49418
org: ORG-ARTA4-RIPE
nic-hdl: ARTA2-RIPE
abuse-mailbox: abuse@amsterdamresidential.com
mnt-by: MNT-NFORCE
created: 2016-12-19T15:20:10Z
last-modified: 2016-12-21T14:45:59Z
source: RIPE # Filtered
% Information related to '212.92.112.0/21AS43350'
route: 212.92.112.0/21
descr: NFOrce Entertainment BV - route 212.92.112.0/21
origin: AS43350
mnt-by: MNT-NFORCE
created: 2016-12-19T17:04:41Z
last-modified: 2016-12-19T17:04:41Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.89.2 (ANGUS)
Regards,
Fail2Ban
No comments:
Post a Comment