Hi,
The IP 91.225.120.202 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 91.225.120.202:
[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.225.120.0 - 91.225.123.255'
% Abuse contact for '91.225.120.0 - 91.225.123.255' is 'alexnvis@gmail.com'
inetnum: 91.225.120.0 - 91.225.123.255
netname: MEDIANA-NET
country: UA
org: ORG-MEDI1-RIPE
admin-c: KRYL1-RIPE
tech-c: KRYL1-RIPE
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-by: MEDIANASERV-MNT
mnt-routes: MEDIANASERV-MNT
mnt-domains: MEDIANASERV-MNT
created: 2011-02-09T12:51:03Z
last-modified: 2016-04-14T09:30:30Z
source: RIPE # Filtered
sponsoring-org: ORG-Vs35-RIPE
organisation: ORG-MEDI1-RIPE
org-name: CHP "Mediana-Servis"
org-type: OTHER
address: 02099, Ukraine, Kiev, Rossiyskaya 58-a,31
abuse-c: AR30607-RIPE
mnt-ref: MEDIANASERV-MNT
mnt-by: MEDIANASERV-MNT
created: 2011-02-04T11:17:28Z
last-modified: 2014-11-17T22:48:55Z
source: RIPE # Filtered
person: Yuri Krylach
address: of. 31, Rossiyska str. 58-a, 02099, Kyiv, Ukraine
phone: +380444558215
nic-hdl: KRYL1-RIPE
mnt-by: MEDIANASERV-MNT
created: 2011-02-04T11:16:01Z
last-modified: 2011-02-04T11:16:01Z
source: RIPE
% Information related to '91.225.120.0/22AS15929'
route: 91.225.120.0/22
descr: CHP "Mediana-Servis"
origin: AS15929
mnt-by: MEDIANASERV-MNT
mnt-by: EMPLOT-MNT
created: 2011-02-23T14:23:30Z
last-modified: 2011-02-23T14:23:30Z
source: RIPE
% Information related to '91.225.120.0/22AS197575'
route: 91.225.120.0/22
descr: CHP "Mediana-Servis"
origin: AS197575
mnt-by: MEDIANASERV-MNT
created: 2011-02-15T12:02:51Z
last-modified: 2011-02-15T12:02:51Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.92.6 (BLAARKOP)
Regards,
Fail2Ban
No comments:
Post a Comment