城市(city): unknown
省份(region): unknown
国家(country): China
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 121.234.219.249 | attack | Aug 26 04:38:42 shivevps sshd[21284]: Bad protocol version identification '\024' from 121.234.219.249 port 50172 Aug 26 04:38:49 shivevps sshd[21427]: Bad protocol version identification '\024' from 121.234.219.249 port 50342 Aug 26 04:39:21 shivevps sshd[21974]: Bad protocol version identification '\024' from 121.234.219.249 port 50648 Aug 26 04:39:58 shivevps sshd[23441]: Bad protocol version identification '\024' from 121.234.219.249 port 51424 ... |
2020-08-26 16:24:52 |
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '121.224.0.0 - 121.239.255.255'
% Abuse contact for '121.224.0.0 - 121.239.255.255' is 'anti-spam@chinatelecom.cn'
inetnum: 121.224.0.0 - 121.239.255.255
netname: CHINANET-JS
descr: CHINANET jiangsu province network
descr: China Telecom
descr: A12,Xin-Jie-Kou-Wai Street
descr: Beijing 100088
country: CN
admin-c: CH93-AP
tech-c: CJ186-AP
abuse-c: AC1573-AP
status: ALLOCATED PORTABLE
mnt-by: APNIC-HM
mnt-lower: MAINT-CHINANET-JS
mnt-routes: MAINT-CHINANET-JS
mnt-irt: IRT-CHINANET-CN
last-modified: 2021-06-15T08:05:09Z
source: APNIC
irt: IRT-CHINANET-CN
address: No.31 ,jingrong street,beijing
address: 100032
e-mail: anti-spam@chinatelecom.cn
abuse-mailbox: anti-spam@chinatelecom.cn
admin-c: CH93-AP
tech-c: CH93-AP
auth: # Filtered
remarks: anti-spam@chinatelecom.cn was validated on 2025-11-13
mnt-by: MAINT-CHINANET
last-modified: 2026-03-13T07:12:20Z
source: APNIC
role: ABUSE CHINANETCN
country: ZZ
address: No.31 ,jingrong street,beijing
address: 100032
phone: +000000000
e-mail: anti-spam@chinatelecom.cn
admin-c: CH93-AP
tech-c: CH93-AP
nic-hdl: AC1573-AP
remarks: Generated from irt object IRT-CHINANET-CN
remarks: anti-spam@chinatelecom.cn was validated on 2025-11-13
abuse-mailbox: anti-spam@chinatelecom.cn
mnt-by: APNIC-ABUSE
last-modified: 2025-11-13T14:15:15Z
source: APNIC
role: CHINANET JIANGSU
address: 260 Zhongyang Road,Nanjing 210037
country: CN
phone: +86-25-87799222
e-mail: jsipmanager@163.com
remarks: send anti-spam reports tojsipmanager@163.com
remarks: send abuse reports tojsipmanager@163.com
remarks: times in GMT+8
remarks: www.jsinfo.net
admin-c: CH360-AP
tech-c: CS306-AP
tech-c: CN142-AP
nic-hdl: CJ186-AP
notify: jsipmanager@163.com
mnt-by: MAINT-CHINANET-JS
last-modified: 2022-08-05T15:34:47Z
source: APNIC
person: Chinanet Hostmaster
nic-hdl: CH93-AP
e-mail: anti-spam@chinatelecom.cn
address: No.31 ,jingrong street,beijing
address: 100032
phone: +86-10-58501724
fax-no: +86-10-58501724
country: CN
mnt-by: MAINT-CHINANET
last-modified: 2022-02-28T06:53:44Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5)
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 121.234.219.117
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4503
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;121.234.219.117. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026042301 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 24 12:02:55 CST 2026
;; MSG SIZE rcvd: 108
Host 117.219.234.121.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 117.219.234.121.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 95.85.9.94 | attack | Bruteforce detected by fail2ban |
2020-04-19 19:39:15 |
| 156.54.173.75 | attack | 19.04.2020 11:44:55 - RDP Login Fail Detected by https://www.elinox.de/RDP-Wächter |
2020-04-19 19:36:02 |
| 49.234.6.105 | attack | (sshd) Failed SSH login from 49.234.6.105 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 19 09:50:30 amsweb01 sshd[8817]: Invalid user ko from 49.234.6.105 port 38926 Apr 19 09:50:33 amsweb01 sshd[8817]: Failed password for invalid user ko from 49.234.6.105 port 38926 ssh2 Apr 19 10:00:39 amsweb01 sshd[10254]: Invalid user vj from 49.234.6.105 port 59498 Apr 19 10:00:41 amsweb01 sshd[10254]: Failed password for invalid user vj from 49.234.6.105 port 59498 ssh2 Apr 19 10:05:34 amsweb01 sshd[11342]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.6.105 user=root |
2020-04-19 19:50:30 |
| 68.183.124.53 | attackspambots | 2020-04-19T13:01:40.907490vps751288.ovh.net sshd\[28461\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.124.53 user=root 2020-04-19T13:01:43.458056vps751288.ovh.net sshd\[28461\]: Failed password for root from 68.183.124.53 port 40962 ssh2 2020-04-19T13:05:40.911223vps751288.ovh.net sshd\[28495\]: Invalid user zi from 68.183.124.53 port 59266 2020-04-19T13:05:40.917785vps751288.ovh.net sshd\[28495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.124.53 2020-04-19T13:05:43.086338vps751288.ovh.net sshd\[28495\]: Failed password for invalid user zi from 68.183.124.53 port 59266 ssh2 |
2020-04-19 19:13:57 |
| 139.59.190.55 | attackspam | 2020-04-19T13:05:16.135648vps773228.ovh.net sshd[4872]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.190.55 user=root 2020-04-19T13:05:18.008334vps773228.ovh.net sshd[4872]: Failed password for root from 139.59.190.55 port 36822 ssh2 2020-04-19T13:10:10.151189vps773228.ovh.net sshd[4962]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.190.55 user=postfix 2020-04-19T13:10:12.049422vps773228.ovh.net sshd[4962]: Failed password for postfix from 139.59.190.55 port 56248 ssh2 2020-04-19T13:15:04.069440vps773228.ovh.net sshd[4996]: Invalid user ubuntu from 139.59.190.55 port 47442 ... |
2020-04-19 19:23:31 |
| 202.79.172.29 | attack | invalid user |
2020-04-19 19:34:15 |
| 106.12.197.52 | attack | Triggered by Fail2Ban at Ares web server |
2020-04-19 19:17:11 |
| 113.190.76.37 | attack | 20/4/18@23:48:03: FAIL: Alarm-Network address from=113.190.76.37 20/4/18@23:48:03: FAIL: Alarm-Network address from=113.190.76.37 ... |
2020-04-19 19:13:45 |
| 52.187.25.220 | attack | Apr 19 06:36:08 powerpi2 sshd[19613]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.187.25.220 Apr 19 06:36:08 powerpi2 sshd[19613]: Invalid user admin8 from 52.187.25.220 port 34180 Apr 19 06:36:10 powerpi2 sshd[19613]: Failed password for invalid user admin8 from 52.187.25.220 port 34180 ssh2 ... |
2020-04-19 19:14:25 |
| 210.245.92.228 | attackspam | Apr 19 12:08:14 server sshd[16878]: Failed password for root from 210.245.92.228 port 37738 ssh2 Apr 19 12:12:28 server sshd[17693]: Failed password for invalid user github from 210.245.92.228 port 40801 ssh2 Apr 19 12:16:06 server sshd[18416]: Failed password for invalid user oracle from 210.245.92.228 port 41505 ssh2 |
2020-04-19 19:18:23 |
| 64.31.6.60 | attack | $f2bV_matches |
2020-04-19 19:52:25 |
| 139.59.67.82 | attack | k+ssh-bruteforce |
2020-04-19 19:45:30 |
| 196.194.253.25 | attack | Autoban 196.194.253.25 AUTH/CONNECT |
2020-04-19 19:55:05 |
| 41.221.168.168 | attackspambots | " " |
2020-04-19 19:20:31 |
| 144.217.161.78 | attackspam | 2020-04-19T03:13:22.0108921495-001 sshd[24393]: Invalid user zd from 144.217.161.78 port 49910 2020-04-19T03:13:22.0143561495-001 sshd[24393]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.ip-144-217-161.net 2020-04-19T03:13:22.0108921495-001 sshd[24393]: Invalid user zd from 144.217.161.78 port 49910 2020-04-19T03:13:23.4456931495-001 sshd[24393]: Failed password for invalid user zd from 144.217.161.78 port 49910 ssh2 2020-04-19T03:17:49.5462601495-001 sshd[24652]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.ip-144-217-161.net user=root 2020-04-19T03:17:51.9230251495-001 sshd[24652]: Failed password for root from 144.217.161.78 port 38670 ssh2 ... |
2020-04-19 19:52:57 |