城市(city): unknown
省份(region): unknown
国家(country): China
运营商(isp): China Unicom
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '220.192.0.0 - 220.207.255.255'
% Abuse contact for '220.192.0.0 - 220.207.255.255' is 'zhaoyz3@chinaunicom.cn'
inetnum: 220.192.0.0 - 220.207.255.255
netname: UNICOM
descr: China Unicom
descr: No.21 Financial Street,Xicheng District,
descr: Beijing 100140 ,P.R.China
country: CN
admin-c: YW6851-AP
tech-c: YW6851-AP
abuse-c: AC1601-AP
status: ALLOCATED PORTABLE
mnt-by: MAINT-CNNIC-AP
mnt-irt: IRT-UNICOM-CN
mnt-lower: MAINT-CNNIC-AP
mnt-routes: MAINT-CNCGROUP-RR
last-modified: 2023-11-28T00:57:29Z
source: APNIC
irt: IRT-UNICOM-CN
address: No.21 Financial Street,Xicheng District,
address: Beijing 100140 ,P.R.China
e-mail: zhaoyz3@chinaunicom.cn
abuse-mailbox: zhaoyz3@chinaunicom.cn
admin-c: YW6851-AP
tech-c: YW6851-AP
auth: # Filtered
remarks: zhaoyz3@chinaunicom.cn was validated on 2026-05-08
mnt-by: MAINT-CNNIC-AP
last-modified: 2026-05-08T01:30:43Z
source: APNIC
role: ABUSE CNNICCN
country: ZZ
address: Beijing, China
phone: +000000000
e-mail: ipas@cnnic.cn
admin-c: IP50-AP
tech-c: IP50-AP
nic-hdl: AC1601-AP
remarks: Generated from irt object IRT-CNNIC-CN
remarks: ipas@cnnic.cn is invalid
abuse-mailbox: ipas@cnnic.cn
mnt-by: APNIC-ABUSE
last-modified: 2025-09-19T17:20:32Z
source: APNIC
person: Yuzhen Zhao
address: No.21 Financial Street,Xicheng District,
address: Beijing 100140 ,P.R.China
country: CN
phone: +86-10-66258500
fax-no: +86-10-66259626
e-mail: zhaoyz3@chinaunicom.cn
e-mail: hqs-ipabuse@chinaunicom.cn
nic-hdl: YW6851-AP
mnt-by: MAINT-CNNIC-AP
last-modified: 2017-09-21T03:48:02Z
source: APNIC
% Information related to '220.192.0.0/12AS4837'
route: 220.192.0.0/12
descr: China Unicom Network
country: CN
origin: AS4837
mnt-by: MAINT-CNCGROUP-RR
last-modified: 2011-12-13T01:08:02Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4); <<>> DiG 9.10.3-P4-Ubuntu <<>> 220.194.144.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40342
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;220.194.144.139. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026102200 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Oct 22 19:30:29 CST 2026
;; MSG SIZE rcvd: 108Host 139.144.194.220.in-addr.arpa not found: 2(SERVFAIL)
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server: 183.60.82.98
Address: 183.60.82.98#53
** server can't find 139.144.194.220.in-addr.arpa: SERVFAIL| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 134.209.236.223 | attackbots | Jun 26 00:05:54 lnxweb61 sshd[32293]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.236.223 Jun 26 00:05:54 lnxweb61 sshd[32293]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.236.223 |
2019-06-26 06:34:17 |
| 157.230.122.181 | attackspam | Jun 26 00:06:27 vtv3 sshd\[18861\]: Invalid user nec from 157.230.122.181 port 60474 Jun 26 00:06:27 vtv3 sshd\[18861\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.122.181 Jun 26 00:06:29 vtv3 sshd\[18861\]: Failed password for invalid user nec from 157.230.122.181 port 60474 ssh2 Jun 26 00:07:54 vtv3 sshd\[19391\]: Invalid user wanda from 157.230.122.181 port 41197 Jun 26 00:07:54 vtv3 sshd\[19391\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.122.181 Jun 26 00:19:12 vtv3 sshd\[24603\]: Invalid user tester from 157.230.122.181 port 53445 Jun 26 00:19:12 vtv3 sshd\[24603\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.122.181 Jun 26 00:19:14 vtv3 sshd\[24603\]: Failed password for invalid user tester from 157.230.122.181 port 53445 ssh2 Jun 26 00:20:37 vtv3 sshd\[25601\]: Invalid user ts from 157.230.122.181 port 33803 Jun 26 00:20:37 vtv3 sshd\[2 |
2019-06-26 06:07:25 |
| 80.216.149.30 | attack | 37215/tcp 37215/tcp 37215/tcp... [2019-06-06/25]8pkt,1pt.(tcp) |
2019-06-26 06:30:35 |
| 92.126.192.75 | attack | Unauthorized connection attempt from IP address 92.126.192.75 on Port 445(SMB) |
2019-06-26 06:21:02 |
| 168.121.238.43 | attack | 23/tcp 23/tcp 23/tcp... [2019-05-04/06-25]5pkt,1pt.(tcp) |
2019-06-26 06:04:42 |
| 88.99.145.83 | attack | Only those who intend to destroy a site makes "all day" attempts like this below, so if this ip appears on your website block immediately 88.99.0.0/16 is high risk: 88.99.145.83/25/06/2019 02:10/error 403/GET/HTTP/1.1/9/ 88.99.145.83/25/06/2019 12:21/9/error 403/GET/HTTP/1.1/ |
2019-06-26 06:13:01 |
| 114.232.250.53 | attackspam | 2019-06-25T16:55:45.227778 X postfix/smtpd[29166]: warning: unknown[114.232.250.53]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 2019-06-25T19:10:53.125278 X postfix/smtpd[48229]: warning: unknown[114.232.250.53]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 2019-06-25T19:13:36.396290 X postfix/smtpd[48229]: warning: unknown[114.232.250.53]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 |
2019-06-26 06:36:23 |
| 218.248.28.146 | attackbots | 445/tcp 445/tcp 445/tcp [2019-05-09/06-25]3pkt |
2019-06-26 06:28:18 |
| 45.32.174.210 | attackspam | 20 attempts against mh-ssh on pluto.magehost.pro |
2019-06-26 06:06:01 |
| 195.176.3.19 | attack | Malicious Traffic/Form Submission |
2019-06-26 06:12:28 |
| 104.236.94.202 | attackspambots | Jun 25 19:11:20 h2177944 sshd\[19420\]: Invalid user shuan from 104.236.94.202 port 40148 Jun 25 19:11:20 h2177944 sshd\[19420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.94.202 Jun 25 19:11:22 h2177944 sshd\[19420\]: Failed password for invalid user shuan from 104.236.94.202 port 40148 ssh2 Jun 25 19:14:19 h2177944 sshd\[19462\]: Invalid user vagrant from 104.236.94.202 port 39852 ... |
2019-06-26 06:20:09 |
| 175.183.87.97 | attackbots | Telnet Server BruteForce Attack |
2019-06-26 06:31:13 |
| 64.32.10.29 | attackspam | 445/tcp 445/tcp 445/tcp... [2019-05-03/06-25]8pkt,1pt.(tcp) |
2019-06-26 06:06:21 |
| 143.255.109.34 | attackbots | C1,WP GET /wp-login.php |
2019-06-26 06:04:19 |
| 204.48.19.178 | attackbotsspam | Jun 25 23:41:20 nextcloud sshd\[28943\]: Invalid user left4dead2 from 204.48.19.178 Jun 25 23:41:20 nextcloud sshd\[28943\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=204.48.19.178 Jun 25 23:41:23 nextcloud sshd\[28943\]: Failed password for invalid user left4dead2 from 204.48.19.178 port 41638 ssh2 ... |
2019-06-26 06:38:37 |