Hi,
The IP 89.237.21.135 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 89.237.21.135:
[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 '89.237.21.0 - 89.237.21.255'
% Abuse contact for '89.237.21.0 - 89.237.21.255' is 'abuse@ttk.ru'
inetnum: 89.237.21.0 - 89.237.21.255
netname: MSS-SUTTK-CLK
descr: Southern Urals TransTelecom MSS DHCP + IPoE
remarks: INFRA-AW
country: RU
admin-c: SUTK-RIPE
tech-c: SUTK-RIPE
status: ASSIGNED PA
mnt-by: SUTTK-MNT
created: 2009-08-28T03:45:50Z
last-modified: 2013-07-12T08:15:50Z
source: RIPE
role: SUTTK NOC
address: Southern Urals TransTelecom
address: 60 Tsvilling Street
address: Chelyabinsk
address: Russia, 454111
phone: +7 351 2111111
remarks: ----------------------------------------------------------
remarks: Points of contact for SUTTK Network Operations
remarks: ----------------------------------------------------------
remarks: Routing and peering issues: ipnoc@suttk.ru
remarks: Network security issues: abuse@suttk.ru
remarks: Mail and SPAM issues: postmaster@suttk.ru
remarks: VoIP issues: voip@suttk.ru
remarks: Customer support: helpdesk@suttk.ru
remarks: ----------------------------------------------------------
tech-c: YIV74-RIPE
tech-c: VB6330-RIPE
tech-c: IB5304-RIPE
nic-hdl: SUTK-RIPE
abuse-mailbox: abuse@suttk.ru
mnt-by: SUTTK-MNT
created: 2006-02-27T06:58:15Z
last-modified: 2018-05-21T04:13:57Z
source: RIPE # Filtered
% Information related to '89.237.16.0/20AS28745'
route: 89.237.16.0/20
descr: SUTTK Chelyabinsk
origin: AS28745
mnt-by: SUTTK-MNT
created: 2006-08-21T04:09:45Z
last-modified: 2006-08-21T04:09:45Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.92.6 (BLAARKOP)
Regards,
Fail2Ban
No comments:
Post a Comment