Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: China

Internet Service Provider: China Unicom

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
% [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 info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 220.194.144.140
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25401
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;220.194.144.140.		IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026103001 1800 900 604800 86400

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 31 08:30:26 CST 2026
;; MSG SIZE  rcvd: 108
Host info
b'Host 140.144.194.220.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
;; 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 140.144.194.220.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
222.186.30.57 attack
SSH bruteforce
2020-04-11 03:59:28
162.210.70.52 attack
Phishing mail send: We recently experience service disruption with our home bank on international transactions ever since the Convid 19 situation started affecting bank operation hours.
Please process payment to our below offshore Sweden bank account. Please confirm when payment will be expected and also share the transfer copy once processed for follow up.

Received: from us2-ob1-1.mailhostbox.com (162.210.70.52) by
 AM5EUR03FT041.mail.protection.outlook.com (10.152.17.186) with Microsoft SMTP
 Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.20.2856.17
 via Frontend Transport; Sat, 28 Mar 2020 14:21:49 +0000
2020-04-11 04:10:45
106.12.208.31 attackspam
$f2bV_matches
2020-04-11 04:02:29
103.140.83.20 attack
Apr 10 20:10:25 server sshd[45735]: User postgres from 103.140.83.20 not allowed because not listed in AllowUsers
Apr 10 20:10:28 server sshd[45735]: Failed password for invalid user postgres from 103.140.83.20 port 45092 ssh2
Apr 10 20:14:53 server sshd[46999]: Failed password for invalid user mongo from 103.140.83.20 port 54364 ssh2
2020-04-11 03:52:06
37.187.60.182 attackbots
Apr 10 21:01:56 host5 sshd[30757]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.ip-37-187-60.eu  user=root
Apr 10 21:01:58 host5 sshd[30757]: Failed password for root from 37.187.60.182 port 34532 ssh2
...
2020-04-11 04:02:57
2a01:cb08:864d:7d00:4c04:f4e0:360a:d220 attackbots
CMS brute force
...
2020-04-11 03:46:10
106.13.45.243 attackbotsspam
2020-04-10T10:29:15.921256linuxbox-skyline sshd[27092]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.243  user=root
2020-04-10T10:29:18.493795linuxbox-skyline sshd[27092]: Failed password for root from 106.13.45.243 port 36576 ssh2
...
2020-04-11 04:14:30
49.235.76.154 attack
Apr 10 19:35:01 ip-172-31-62-245 sshd\[7769\]: Invalid user miteq from 49.235.76.154\
Apr 10 19:35:03 ip-172-31-62-245 sshd\[7769\]: Failed password for invalid user miteq from 49.235.76.154 port 45140 ssh2\
Apr 10 19:38:46 ip-172-31-62-245 sshd\[7809\]: Failed password for root from 49.235.76.154 port 42556 ssh2\
Apr 10 19:42:43 ip-172-31-62-245 sshd\[7934\]: Invalid user rfmngr from 49.235.76.154\
Apr 10 19:42:46 ip-172-31-62-245 sshd\[7934\]: Failed password for invalid user rfmngr from 49.235.76.154 port 39974 ssh2\
2020-04-11 04:00:23
175.36.162.112 attackspambots
Invalid user whoopsie from 175.36.162.112 port 33050
2020-04-11 03:47:38
113.125.159.5 attack
SSH brute force attempt
2020-04-11 04:04:43
116.196.79.253 attackspambots
2020-04-10T17:54:17.022092librenms sshd[23840]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.196.79.253
2020-04-10T17:54:17.019037librenms sshd[23840]: Invalid user test from 116.196.79.253 port 37496
2020-04-10T17:54:19.239081librenms sshd[23840]: Failed password for invalid user test from 116.196.79.253 port 37496 ssh2
...
2020-04-11 03:50:46
42.100.228.204 attack
42.100.228.204 - - \[10/Apr/2020:14:03:31 +0200\] "GET http://api.gxout.com/proxy/check.aspx HTTP/1.1" 400 666 "http://api.gxout.com/proxy/check.aspx" "Mozilla/4.0 \(compatible\; MSIE 6.0\; Windows NT 5.1\)"
...
2020-04-11 04:23:28
182.61.108.64 attackbots
Apr 10 14:14:57 XXX sshd[15628]: Invalid user nagios from 182.61.108.64 port 44842
2020-04-11 03:52:23
49.233.192.22 attack
Repeated brute force against a port
2020-04-11 03:48:04
190.158.201.33 attack
Apr 10 18:18:14 vlre-nyc-1 sshd\[1930\]: Invalid user host from 190.158.201.33
Apr 10 18:18:14 vlre-nyc-1 sshd\[1930\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.158.201.33
Apr 10 18:18:17 vlre-nyc-1 sshd\[1930\]: Failed password for invalid user host from 190.158.201.33 port 34146 ssh2
Apr 10 18:23:07 vlre-nyc-1 sshd\[2019\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.158.201.33  user=root
Apr 10 18:23:09 vlre-nyc-1 sshd\[2019\]: Failed password for root from 190.158.201.33 port 10383 ssh2
...
2020-04-11 03:48:23

Recently Reported IPs

183.185.182.105 113.132.41.224 117.28.11.226 43.156.132.199
40.124.85.0 188.166.93.193 89.167.32.97 178.156.146.23
4.150.187.62 20.119.97.217 172.234.83.205 172.232.111.191
35.206.146.145 43.106.108.249 27.128.163.28 43.106.106.7
154.80.128.173 137.184.52.43 165.154.36.79 165.232.97.244