Hi,
The IP 91.143.18.63 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 91.143.18.63:
[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 '91.143.16.0 - 91.143.23.255'
% Abuse contact for '91.143.16.0 - 91.143.23.255' is 'megalog@megalog.ru'
inetnum: 91.143.16.0 - 91.143.23.255
netname: MEGALOG-NET
descr: Megalog-Plus Ltd. Internet Service Provider
country: RU
org: ORG-ML62-RIPE
admin-c: AZ2795-RIPE
tech-c: AZ2795-RIPE
status: ASSIGNED PA
mnt-by: MEGALOG-MNT
mnt-lower: MEGALOG-MNT
mnt-domains: MEGALOG-MNT
mnt-routes: MEGALOG-MNT
created: 2006-10-27T08:37:15Z
last-modified: 2009-04-10T09:42:51Z
source: RIPE # Filtered
organisation: ORG-ML62-RIPE
org-name: Megalog-Plus Ltd
org-type: LIR
address: Megalog-Plus Ltd Murat Abaev Post Box 137 357500 Pyatigorsk RUSSIAN FEDERATION
phone: +7 8793 392919
fax-no: +7 8793 392919
abuse-c: AR16785-RIPE
admin-c: AZ2795-RIPE
admin-c: EVK10-RIPE
admin-c: LY10-RIPE
admin-c: AMT44-RIPE
admin-c: NL799-RIPE
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: MEGALOG-MNT
mnt-by: RIPE-NCC-HM-MNT
created: 2006-10-25T05:11:04Z
last-modified: 2013-12-18T14:36:22Z
source: RIPE # Filtered
person: Akhsarbek Zangiyev
address: Kalinin str, 2/4, Pyatigorsk,
address: 357500, Russia
phone: +7 (8793) 328240
fax-no: +7 (8793) 380926
nic-hdl: AZ2795-RIPE
mnt-by: MEGALOG-MNT
created: 2009-04-10T09:36:48Z
last-modified: 2009-04-10T09:36:48Z
source: RIPE # Filtered
% Information related to '91.143.16.0/20AS41816'
route: 91.143.16.0/20
descr: Megalog-Plus Ltd
origin: AS41816
mnt-by: MEGALOG-MNT
created: 2006-10-30T14:47:14Z
last-modified: 2006-10-30T14:47:14Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.80.1 (DB-1)
Regards,
Fail2Ban
No comments:
Post a Comment