Hi,
The IP 31.216.204.73 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 31.216.204.73:
[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 '31.216.192.0 - 31.216.207.255'
% Abuse contact for '31.216.192.0 - 31.216.207.255' is 'abuse@t.ht.hr'
inetnum: 31.216.192.0 - 31.216.207.255
netname: T-HT
descr: Hrvatski Telekom d.d.
descr: Croatian Telecom Inc.
country: HR
admin-c: THT8-RIPE
tech-c: THT8-RIPE
status: ASSIGNED PA
mnt-by: HPT-MNT
mnt-lower: HPT-MNT
mnt-routes: HPT-MNT
created: 2011-05-19T19:56:38Z
last-modified: 2014-01-22T09:25:33Z
source: RIPE
role: T-HT Contact
address: Hrvatski Telekom d.d.
address: Croatian Telecom Inc.
address: Draskoviceva 26
address: HR-10000 Zagreb
address: Croatia
phone: +385 1 4914 303
fax-no: +385 1 4914 330
admin-c: DS4957-RIPE
admin-c: MR4108-RIPE
tech-c: TA324-RIPE
tech-c: MR4108-RIPE
tech-c: TV650-RIPE
tech-c: LD1640-RIPE
tech-c: BB1217-RIPE
tech-c: GS5517-RIPE
tech-c: GS5730-RIPE
tech-c: MG9409-RIPE
tech-c: IM109-RIPE
tech-c: IT40-RIPE
tech-c: DC9547-RIPE
tech-c: MK12709-RIPE
tech-c: SD7822-RIPE
tech-c: TN1950-RIPE
tech-c: ZH1367-RIPE
tech-c: MC24240-RIPE
tech-c: TV2945-RIPE
nic-hdl: THT8-RIPE
mnt-by: HPT-MNT
created: 2004-12-03T10:09:02Z
last-modified: 2016-02-24T10:01:48Z
source: RIPE # Filtered
abuse-mailbox: abuse@t.ht.hr
% Information related to '31.216.192.0/19AS5391'
route: 31.216.192.0/19
descr: Hrvatski Telekom d.d.
descr: Croatian Telecom Inc.
origin: AS5391
mnt-lower: HPT-MNT
mnt-by: HPT-MNT
created: 2011-05-19T20:13:26Z
last-modified: 2014-01-22T08:53:35Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.88 (WAGYU)
Regards,
Fail2Ban
No comments:
Post a Comment