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 '120.0.0.0 - 120.15.255.255'

% Abuse contact for '120.0.0.0 - 120.15.255.255' is 'zhaoyz3@chinaunicom.cn'

inetnum:        120.0.0.0 - 120.15.255.255
netname:        UNICOM-HE
descr:          China Unicom Heibei Province Network
descr:          China Unicom
country:        CN
admin-c:        CH1302-AP
tech-c:         KL984-AP
abuse-c:        AC1718-AP
status:         ALLOCATED PORTABLE
remarks:        service provider
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:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-CNCGROUP-HE
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2025-01-22T13:07:17Z
source:         APNIC

irt:            IRT-CU-CN
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
e-mail:         zhaoyz3@chinaunicom.cn
abuse-mailbox:  zhaoyz3@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
auth:           # Filtered
remarks:        zhaoyz3@chinaunicom.cn was validated on 2025-10-17
mnt-by:         MAINT-CNCGROUP
last-modified:  2025-11-18T00:26:20Z
source:         APNIC

role:           ABUSE CUCN
country:        ZZ
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
phone:          +000000000
e-mail:         zhaoyz3@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
nic-hdl:        AC1718-AP
remarks:        Generated from irt object IRT-CU-CN
remarks:        zhaoyz3@chinaunicom.cn was validated on 2025-10-17
abuse-mailbox:  zhaoyz3@chinaunicom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2025-10-17T02:26:56Z
source:         APNIC

person:         ChinaUnicom Hostmaster
nic-hdl:        CH1302-AP
e-mail:         hqs-ipabuse@chinaunicom.cn
address:        No.21,Jin-Rong Street
address:        Beijing,100033
address:        P.R.China
phone:          +86-10-66259764
fax-no:         +86-10-66259764
country:        CN
mnt-by:         MAINT-CNCGROUP
last-modified:  2017-08-17T06:13:16Z
source:         APNIC

person:         Kong Lingfei
nic-hdl:        KL984-AP
e-mail:         konglf5@chinaunicom.cn
address:        45, Guang An Street, Shi Jiazhuang City, HeBei Province,050011,CN
phone:          +86-311-86681601
fax-no:         +86-311-86689210
country:        cn
mnt-by:         MAINT-CNCGROUP-HE
last-modified:  2009-02-06T02:31:32Z
source:         APNIC

% Information related to '120.0.0.0/12AS4837'

route:          120.0.0.0/12
descr:          China Unicom China169 Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2017-05-05T06:28:01Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.36-SNAPSHOT (WHOIS-AU5)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 120.9.189.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 65299
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;120.9.189.180.			IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 06 04:30:41 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 180.189.9.120.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 180.189.9.120.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.54.114.248 attackbots
$f2bV_matches
2020-02-07 01:57:26
36.153.0.229 attack
$f2bV_matches
2020-02-07 02:09:04
113.162.184.93 attackspam
Feb  6 14:29:47 server2 sshd[4803]: Address 113.162.184.93 maps to static.vnpt.vn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Feb  6 14:29:47 server2 sshd[4803]: Invalid user admin from 113.162.184.93
Feb  6 14:29:47 server2 sshd[4803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.162.184.93 
Feb  6 14:29:49 server2 sshd[4803]: Failed password for invalid user admin from 113.162.184.93 port 58015 ssh2
Feb  6 14:29:49 server2 sshd[4803]: Connection closed by 113.162.184.93 [preauth]
Feb  6 14:29:54 server2 sshd[4813]: Address 113.162.184.93 maps to static.vnpt.vn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Feb  6 14:29:54 server2 sshd[4813]: Invalid user admin from 113.162.184.93
Feb  6 14:29:54 server2 sshd[4813]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.162.184.93 


........
-----------------------------------------------
https://www.blocklist.de/en/view.h
2020-02-07 02:30:04
41.42.177.50 attackspam
SMTP-sasl brute force
...
2020-02-07 01:53:35
222.186.175.23 attackbots
2020-02-06T18:53:05.880208scmdmz1 sshd[15235]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.23  user=root
2020-02-06T18:53:07.874842scmdmz1 sshd[15235]: Failed password for root from 222.186.175.23 port 59448 ssh2
2020-02-06T18:53:10.196695scmdmz1 sshd[15235]: Failed password for root from 222.186.175.23 port 59448 ssh2
2020-02-06T18:53:05.880208scmdmz1 sshd[15235]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.23  user=root
2020-02-06T18:53:07.874842scmdmz1 sshd[15235]: Failed password for root from 222.186.175.23 port 59448 ssh2
2020-02-06T18:53:10.196695scmdmz1 sshd[15235]: Failed password for root from 222.186.175.23 port 59448 ssh2
2020-02-06T18:53:05.880208scmdmz1 sshd[15235]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.23  user=root
2020-02-06T18:53:07.874842scmdmz1 sshd[15235]: Failed password for root from 222.186.175.23 port 59448 ssh2
2
2020-02-07 01:54:46
101.51.104.13 attack
Lines containing failures of 101.51.104.13
auth.log:Feb  6 14:27:14 omfg sshd[31415]: Connection from 101.51.104.13 port 50811 on 78.46.60.41 port 22
auth.log:Feb  6 14:27:16 omfg sshd[31416]: Connection from 101.51.104.13 port 50838 on 78.46.60.42 port 22
auth.log:Feb  6 14:27:16 omfg sshd[31417]: Connection from 101.51.104.13 port 50531 on 78.46.60.16 port 22
auth.log:Feb  6 14:27:16 omfg sshd[31418]: Connection from 101.51.104.13 port 50880 on 78.46.60.53 port 22
auth.log:Feb  6 14:27:16 omfg sshd[31419]: Connection from 101.51.104.13 port 51638 on 78.46.60.42 port 22
auth.log:Feb  6 14:27:16 omfg sshd[31420]: Connection from 101.51.104.13 port 51637 on 78.46.60.41 port 22
auth.log:Feb  6 14:27:17 omfg sshd[31423]: Connection from 101.51.104.13 port 51645 on 78.46.60.16 port 22
auth.log:Feb  6 14:27:18 omfg sshd[31425]: Connection from 101.51.104.13 port 51910 on 78.46.60.53 port 22
auth.log:Feb  6 14:27:19 omfg sshd[31423]: Invalid user admin from 101.51.104.13
auth.........
------------------------------
2020-02-07 02:18:56
222.186.180.142 attackbots
02/06/2020-13:20:17.367818 222.186.180.142 Protocol: 6 ET SCAN Potential SSH Scan
2020-02-07 02:30:43
112.85.42.176 attack
Feb  6 19:20:34 nextcloud sshd\[11163\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.176  user=root
Feb  6 19:20:35 nextcloud sshd\[11163\]: Failed password for root from 112.85.42.176 port 46025 ssh2
Feb  6 19:20:55 nextcloud sshd\[11529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.176  user=root
2020-02-07 02:25:58
86.208.0.45 attackbotsspam
Fail2Ban Ban Triggered
2020-02-07 02:17:47
111.22.56.58 attackbotsspam
02/06/2020-08:41:38.416170 111.22.56.58 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-02-07 02:32:01
171.100.25.136 attackspam
Feb  6 16:27:01 server sshd\[1324\]: Invalid user admin from 171.100.25.136
Feb  6 16:27:01 server sshd\[1324\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=cm-171-100-25-136.revip10.asianet.co.th 
Feb  6 16:27:04 server sshd\[1324\]: Failed password for invalid user admin from 171.100.25.136 port 56492 ssh2
Feb  6 18:16:22 server sshd\[19367\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=cm-171-100-25-136.revip10.asianet.co.th  user=root
Feb  6 18:16:24 server sshd\[19367\]: Failed password for root from 171.100.25.136 port 57551 ssh2
...
2020-02-07 02:15:53
45.177.255.123 attackspam
Email rejected due to spam filtering
2020-02-07 02:28:07
23.129.64.157 attack
Unauthorized SSH login attempts
2020-02-07 02:16:53
206.72.194.222 attackbotsspam
Feb  6 17:22:02 silence02 sshd[3099]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.72.194.222
Feb  6 17:22:04 silence02 sshd[3099]: Failed password for invalid user xlq from 206.72.194.222 port 33592 ssh2
Feb  6 17:25:19 silence02 sshd[3324]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.72.194.222
2020-02-07 01:49:08
180.76.246.38 attack
$f2bV_matches
2020-02-07 02:17:16

Recently Reported IPs

20.163.13.196 10.212.177.214 10.212.177.224 47.32.133.153
113.215.188.193 39.64.208.185 27.40.78.29 27.39.205.120
27.38.206.90 183.251.240.111 123.5.215.28 115.63.124.220
115.60.128.187 111.208.78.229 110.18.12.103 101.28.195.235
54.144.193.250 61.224.89.26 117.44.229.17 171.35.100.71