Hi,
The IP 139.162.122.110 has just been banned by Fail2Ban after
2 attempts against SSH.
Here is more information about 139.162.122.110:
[Querying whois.arin.net]
[Redirected to whois.ripe.net]
[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 '139.162.0.0 - 139.162.255.255'
% Abuse contact for '139.162.0.0 - 139.162.255.255' is 'abuse@linode.com'
inetnum: 139.162.0.0 - 139.162.255.255
netname: EU-LINODE-20141229
descr: 139.162.0.0/16
org: ORG-LL198-RIPE
country: US
admin-c: TA2589-RIPE
tech-c: TA2589-RIPE
tech-c: LA538-RIPE
status: LEGACY
remarks: For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources
remarks: Please send abuse reports to abuse@linode.com
mnt-by: linode-leg-mnt
created: 2004-02-02T16:20:09Z
last-modified: 2015-05-05T01:52:02Z
source: RIPE
organisation: ORG-LL198-RIPE
org-name: Linode, LLC
org-type: OTHER
address: 329 E. Jimmie Leeds Road, Suite A, Galloway, NJ 08205
abuse-c: AR31889-RIPE
abuse-mailbox: abuse@linode.com
mnt-ref: linode-leg-mnt
mnt-by: linode-leg-mnt
created: 2015-04-20T03:09:43Z
last-modified: 2015-04-20T03:18:36Z
source: RIPE # Filtered
person: Linode Abuse Support
address: 329 E. Jimmie Leeds Road, Suite A, Galloway, NJ 08205, USA
phone: +16093807100
abuse-mailbox: abuse@linode.com
nic-hdl: LA538-RIPE
mnt-by: Linode-mnt
created: 2009-11-11T15:16:50Z
last-modified: 2015-08-13T19:55:05Z
source: RIPE
person: Thomas Asaro
address: 329 E. Jimmie Leeds Road, Suite A, Galloway, NJ 08205, USA
phone: +16093807504
nic-hdl: TA2589-RIPE
mnt-by: Linode-mnt
created: 2009-11-02T17:17:56Z
last-modified: 2014-11-20T18:51:15Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.90 (ANGUS)
Regards,
Fail2Ban
No comments:
Post a Comment