Hi,
The IP 222.220.98.67 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 222.220.98.67:
[Querying whois.apnic.net]
[whois.apnic.net]
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '222.219.0.0 - 222.221.255.255'
% Abuse contact for '222.219.0.0 - 222.221.255.255' is 'anti-spam@ns.chinanet.cn.net'
inetnum: 222.219.0.0 - 222.221.255.255
netname: CHINANET-YN
descr: CHINANET yunnan province network
descr: China Telecom
descr: A12,Xin-Jie-Kou-Wai Street
descr: Beijing 100088
country: CN
admin-c: CH93-AP
tech-c: ZL48-AP
mnt-by: APNIC-HM
mnt-lower: MAINT-CHINANET-YN
mnt-routes: MAINT-CHINANET-YN
status: ALLOCATED PORTABLE
remarks: --------------------------------------------------------
remarks: To report network abuse, please contact mnt-irt
remarks: For troubleshooting, please contact tech-c and admin-c
remarks: Report invalid contact via www.apnic.net/invalidcontact
remarks: --------------------------------------------------------
source: APNIC
mnt-irt: IRT-CHINANET-CN
changed: hm-changed@apnic.net 20040621
irt: IRT-CHINANET-CN
address: No.31 ,jingrong street,beijing
address: 100032
e-mail: anti-spam@ns.chinanet.cn.net
abuse-mailbox: anti-spam@ns.chinanet.cn.net
admin-c: CH93-AP
tech-c: CH93-AP
auth: # Filtered
mnt-by: MAINT-CHINANET
changed: anti-spam@ns.chinanet.cn.net 20101115
source: APNIC
person: Chinanet Hostmaster
nic-hdl: CH93-AP
e-mail: anti-spam@ns.chinanet.cn.net
address: No.31 ,jingrong street,beijing
address: 100032
phone: +86-10-58501724
fax-no: +86-10-58501724
country: CN
changed: dingsy@cndata.com 20070416
changed: zhengzm@gsta.com 20140227
mnt-by: MAINT-CHINANET
source: APNIC
person: zhiyong liu
nic-hdl: ZL48-AP
e-mail: ynipm@126.com
address: 136 beijin roadkunmingchina
phone: +86-871-8223073
fax-no: +86-871-8221536
country: CN
changed: ynipm@126.com 20070813
mnt-by: MAINT-CHINANET-YN
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.15-35 (WHOIS-US3)
Regards,
Fail2Ban
No comments:
Post a Comment