HideMyAss.com

Wednesday 29 January 2014

[Fail2Ban] SSH: banned 95.167.180.114

Hi,

The IP 95.167.180.114 has just been banned by Fail2Ban after
5 attempts against SSH.


Here are more information about 95.167.180.114:

[Querying whois.arin.net]
[Redirected to whois.ripe.net:43]
[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 '95.167.179.0 - 95.167.180.255'

% Abuse contact for '95.167.179.0 - 95.167.180.255' is 'ripe@rt.ru'

inetnum: 95.167.179.0 - 95.167.180.255
netname: ROSTELECOMNET
descr: JSC Rostelecom P2P client connections for PF
remarks: INFRA-AW
country: RU
admin-c: RTNC-RIPE
tech-c: RTNC-RIPE
status: ASSIGNED PA
mnt-by: ROSTELECOM-MNT
source: RIPE # Filtered

role: JSC Rostelecom Technical Team
address: JSC Rostelecom
address: Russian Federation
abuse-mailbox: ripe@rt.ru
admin-c: DS4715-RIPE
admin-c: ANK2555-RIPE
tech-c: DS4715-RIPE
tech-c: EEA-RIPE
tech-c: EK1142-RIPE
phone: +7 499 9953922
remarks: trouble: ---------------------------------------------------------
remarks: trouble: Rostelecom NOC is available 24 x 7
remarks: trouble: 24x7 phone number: +7 499 9953922
remarks: trouble: e-mail: cuss-ip@rt.ru
remarks: trouble: ---------------------------------------------------------
remarks: -----------------------------------------------------------------------
remarks: peering requests: peering@rt.ru
remarks: -----------------------------------------------------------------------
nic-hdl: RTNC-RIPE
mnt-by: ROSTELECOM-MNT
source: RIPE # Filtered

% Information related to '95.167.0.0/16AS12389'

route: 95.167.0.0/16
descr: ROSTELECOM NETS
origin: AS12389
mnt-by: ROSTELECOM-MNT
source: RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.70.1 (WHOIS4)

Regards,

Fail2Ban

No comments:

Post a Comment