HideMyAss.com

Friday, 12 May 2017

[Fail2Ban] SSH: banned 85.244.194.63 from herbalyzer.com

Hi,

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


Here is more information about 85.244.194.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 '85.244.16.0 - 85.245.99.255'

% Abuse contact for '85.244.16.0 - 85.245.99.255' is 'abuse@mail.telepac.pt'

inetnum: 85.244.16.0 - 85.245.99.255
netname: MEO-BROADBAND
descr: PT Comunicacoes S.A.
descr: Dynamic Address Range
country: PT
remarks: NCC #2009021074
admin-c: TP3302-RIPE
tech-c: TP3302-RIPE
status: ASSIGNED PA
mnt-by: TELEPAC-MNT
mnt-routes: TELEPAC-MNT
created: 2009-02-16T16:21:54Z
last-modified: 2016-02-05T17:37:07Z
source: RIPE

role: MEO-RESIDENCIAL
org: ORG-TCIS1-RIPE
address: Local Internet Registry Management
address: MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA S.A.
address: Av. Fontes Pereira de Melo, 40 - 3 Bl A
address: Forum Picoas - 1069-300 Lisboa
address: Portugal
phone: +351-215000000
admin-c: NPM17-RIPE
admin-c: DPM37-RIPE
admin-c: LAS102-RIPE
admin-c: TPM7-RIPE
tech-c: RTM15-RIPE
tech-c: FSG53-RIPE
tech-c: JCO39-RIPE
tech-c: PPB29-RIPE
tech-c: HAC24-RIPE
tech-c: HCO6-RIPE
tech-c: AA2895-RIPE
tech-c: PG259-RIPE
tech-c: PC14515-RIPE
nic-hdl: TP3302-RIPE
abuse-mailbox: abuse@mail.telepac.pt
mnt-by: TELEPAC-MNT
created: 2002-08-12T09:57:20Z
last-modified: 2016-09-13T15:47:46Z
source: RIPE # Filtered

% Information related to '85.240.0.0/13AS3243'

route: 85.240.0.0/13
descr: PT Comunicacoes S.A.
origin: AS3243
mnt-by: TELEPAC-MNT
created: 2005-01-04T19:15:12Z
last-modified: 2014-01-31T16:22:08Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.88.1 (BLAARKOP)

Regards,

Fail2Ban

No comments:

Post a Comment