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: Shenzhen

Region: Guangdong

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 '163.125.0.0 - 163.125.255.255'

% Abuse contact for '163.125.0.0 - 163.125.255.255' is 'hqs-ipabuse@chinaunicom.cn'

inetnum:        163.125.0.0 - 163.125.255.255
netname:        UNICOM-GD
descr:          China Unicom Guangdong province network
descr:          China Unicom
country:        CN
admin-c:        CH1302-AP
tech-c:         RP181-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-GD
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2025-01-22T13:10:14Z
source:         APNIC

irt:            IRT-CU-CN
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
e-mail:         hqs-ipabuse@chinaunicom.cn
abuse-mailbox:  hqs-ipabuse@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
auth:           # Filtered
remarks:        hqs-ipabuse@chinaunicom.cn was validated on 2026-08-19
mnt-by:         MAINT-CNCGROUP
last-modified:  2026-08-19T00:57:22Z
source:         APNIC

role:           ABUSE CUCN
country:        ZZ
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
phone:          +000000000
e-mail:         hqs-ipabuse@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
nic-hdl:        AC1718-AP
remarks:        Generated from irt object IRT-CU-CN
remarks:        hqs-ipabuse@chinaunicom.cn was validated on 2026-08-19
abuse-mailbox:  hqs-ipabuse@chinaunicom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2026-08-20T03:22:23Z
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:         runkeng pan
nic-hdl:        RP181-AP
e-mail:         gdipnoc@chinaunicom.cn
address:        XinShiKong Plaza,No 666 Huangpu Rd. Guangzhou 510627,China
phone:          +86-20-22214174
fax-no:         +86-20-22212266-4174
country:        CN
mnt-by:         MAINT-CNCGROUP-GD
last-modified:  2015-12-16T03:32:02Z
source:         APNIC

% Information related to '163.125.0.0/16AS17623'

route:          163.125.0.0/16
descr:          China Unicom Guangdong Province Network
country:        CN
origin:         AS17623
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2011-04-22T07:04:01Z
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 <<>> 163.125.220.216
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12869
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;163.125.220.216.		IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 02 20:02:33 CST 2026
;; MSG SIZE  rcvd: 108
Host info
Host 216.220.125.163.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 216.220.125.163.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
186.168.115.104 attackspambots
Jun 10 13:33:07 vps sshd[186803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.168.115.104  user=root
Jun 10 13:33:09 vps sshd[186803]: Failed password for root from 186.168.115.104 port 44974 ssh2
Jun 10 13:35:38 vps sshd[199790]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.168.115.104  user=root
Jun 10 13:35:41 vps sshd[199790]: Failed password for root from 186.168.115.104 port 49706 ssh2
Jun 10 13:38:12 vps sshd[208674]: Invalid user optimax from 186.168.115.104 port 54438
...
2020-06-10 19:39:03
68.170.232.231 attackspam
Automatic report - Port Scan Attack
2020-06-10 19:53:12
37.252.187.140 attackbotsspam
Jun 10 07:16:14 NPSTNNYC01T sshd[21640]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.252.187.140
Jun 10 07:16:16 NPSTNNYC01T sshd[21640]: Failed password for invalid user jian from 37.252.187.140 port 59496 ssh2
Jun 10 07:19:27 NPSTNNYC01T sshd[21799]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.252.187.140
...
2020-06-10 19:23:48
94.237.88.96 attackspam
Auto Fail2Ban report, multiple SSH login attempts.
2020-06-10 19:50:43
195.54.166.43 attackspambots
Port-scan: detected 198 distinct ports within a 24-hour window.
2020-06-10 19:32:15
185.176.27.46 attackbots
Port-scan: detected 210 distinct ports within a 24-hour window.
2020-06-10 19:21:34
222.186.180.130 attackbotsspam
Jun 10 12:38:26 rocket sshd[14665]: Failed password for root from 222.186.180.130 port 55306 ssh2
Jun 10 12:38:37 rocket sshd[14667]: Failed password for root from 222.186.180.130 port 10250 ssh2
...
2020-06-10 19:41:31
51.255.173.222 attackspam
Jun 10 20:47:08 web1 sshd[13153]: Invalid user uirc from 51.255.173.222 port 58764
Jun 10 20:47:08 web1 sshd[13153]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.173.222
Jun 10 20:47:08 web1 sshd[13153]: Invalid user uirc from 51.255.173.222 port 58764
Jun 10 20:47:10 web1 sshd[13153]: Failed password for invalid user uirc from 51.255.173.222 port 58764 ssh2
Jun 10 20:59:04 web1 sshd[16098]: Invalid user ubnt from 51.255.173.222 port 38222
Jun 10 20:59:04 web1 sshd[16098]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.173.222
Jun 10 20:59:04 web1 sshd[16098]: Invalid user ubnt from 51.255.173.222 port 38222
Jun 10 20:59:06 web1 sshd[16098]: Failed password for invalid user ubnt from 51.255.173.222 port 38222 ssh2
Jun 10 21:02:47 web1 sshd[17096]: Invalid user renx from 51.255.173.222 port 40736
...
2020-06-10 19:31:19
106.12.174.227 attackbotsspam
Jun 10 01:28:01 web9 sshd\[27985\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.174.227  user=root
Jun 10 01:28:03 web9 sshd\[27985\]: Failed password for root from 106.12.174.227 port 35498 ssh2
Jun 10 01:33:41 web9 sshd\[28836\]: Invalid user monitor from 106.12.174.227
Jun 10 01:33:41 web9 sshd\[28836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.174.227
Jun 10 01:33:43 web9 sshd\[28836\]: Failed password for invalid user monitor from 106.12.174.227 port 58670 ssh2
2020-06-10 19:50:21
167.114.115.201 attackbots
Jun 10 13:17:55 haigwepa sshd[9388]: Failed password for root from 167.114.115.201 port 56072 ssh2
...
2020-06-10 19:57:56
195.54.167.243 attackbots
06/10/2020-07:02:56.489236 195.54.167.243 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-06-10 19:21:15
168.227.200.162 attackspambots
Unauthorized connection attempt from IP address 168.227.200.162 on Port 445(SMB)
2020-06-10 19:38:22
181.134.15.194 attackbotsspam
Jun 10 16:29:40 dhoomketu sshd[627545]: Invalid user bitnami from 181.134.15.194 port 43432
Jun 10 16:29:40 dhoomketu sshd[627545]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.134.15.194 
Jun 10 16:29:40 dhoomketu sshd[627545]: Invalid user bitnami from 181.134.15.194 port 43432
Jun 10 16:29:42 dhoomketu sshd[627545]: Failed password for invalid user bitnami from 181.134.15.194 port 43432 ssh2
Jun 10 16:32:41 dhoomketu sshd[627578]: Invalid user birgit from 181.134.15.194 port 52550
...
2020-06-10 19:37:35
23.129.64.196 attack
2020-06-10T13:02:45.880411vps751288.ovh.net sshd\[27407\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.196  user=root
2020-06-10T13:02:47.880330vps751288.ovh.net sshd\[27407\]: Failed password for root from 23.129.64.196 port 15055 ssh2
2020-06-10T13:02:50.690397vps751288.ovh.net sshd\[27407\]: Failed password for root from 23.129.64.196 port 15055 ssh2
2020-06-10T13:02:52.633723vps751288.ovh.net sshd\[27407\]: Failed password for root from 23.129.64.196 port 15055 ssh2
2020-06-10T13:02:55.306699vps751288.ovh.net sshd\[27407\]: Failed password for root from 23.129.64.196 port 15055 ssh2
2020-06-10 19:23:04
86.57.227.102 attack
Unauthorized connection attempt from IP address 86.57.227.102 on Port 445(SMB)
2020-06-10 19:37:07

Recently Reported IPs

120.219.185.96 120.217.226.143 112.32.241.27 103.78.127.30
159.203.92.47 222.138.43.82 20.65.217.239 182.127.196.187
121.24.28.86 115.60.49.108 112.238.207.148 110.252.106.102
101.26.28.215 2606:4700:10::6816:1498 43.226.40.150 42.51.173.8
34.53.162.97 167.71.213.58 107.170.26.87 172.172.163.244