Hi,
The IP 185.134.28.206 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 185.134.28.206:
[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 '185.134.28.0 - 185.134.28.255'
% Abuse contact for '185.134.28.0 - 185.134.28.255' is 'abuse@zitcom.dk'
inetnum: 185.134.28.0 - 185.134.28.255
netname: CloudCustomers
country: DK
admin-c: CA7013-RIPE
tech-c: CT6203-RIPE
status: ASSIGNED PA
mnt-by: dk-meebox-1-mnt
mnt-by: CLOUDDK-MNT
created: 2017-11-17T12:58:43Z
last-modified: 2017-11-17T12:58:43Z
source: RIPE
role: CLOUDDK ADMINS
address: Robert Jacobsens vej 76A
nic-hdl: CA7013-RIPE
admin-c: JK10827-RIPE
admin-c: AE4667-RIPE
tech-c: JK10827-RIPE
tech-c: AE4667-RIPE
abuse-mailbox: abuse@cloud.dk
mnt-by: dk-meebox-1-mnt
mnt-by: CLOUDDK-MNT
created: 2016-04-27T07:28:27Z
last-modified: 2016-09-12T07:37:38Z
source: RIPE # Filtered
role: CLOUDDK TECH
address: Robert Jacobsens Vej 76A
nic-hdl: CT6203-RIPE
admin-c: JK10827-RIPE
admin-c: AE4667-RIPE
tech-c: JK10827-RIPE
tech-c: AE4667-RIPE
mnt-by: dk-meebox-1-mnt
mnt-by: CLOUDDK-MNT
created: 2016-04-27T07:32:18Z
last-modified: 2016-09-12T07:44:32Z
source: RIPE # Filtered
% Information related to '185.134.28.0/22AS203453'
route: 185.134.28.0/22
origin: AS203453
mnt-by: dk-meebox-1-mnt
mnt-by: CLOUDDK-MNT
created: 2016-04-27T07:17:44Z
last-modified: 2016-04-27T07:19:23Z
source: RIPE
% Information related to '185.134.28.0/22AS48854'
route: 185.134.28.0/22
origin: AS48854
mnt-by: ZITCOM-MNT
mnt-by: CLOUDDK-MNT
created: 2018-01-11T13:17:54Z
last-modified: 2018-01-11T13:17:54Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.92.6 (HEREFORD)
Regards,
Fail2Ban
No comments:
Post a Comment