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

Region: Jiangsu

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 '123.8.0.0 - 123.15.255.255'

% Abuse contact for '123.8.0.0 - 123.15.255.255' is 'hqs-ipabuse@chinaunicom.cn'

inetnum:        123.8.0.0 - 123.15.255.255
netname:        UNICOM-HA
descr:          China Unicom Henan province network
descr:          China Unicom
country:        CN
admin-c:        CH1302-AP
tech-c:         WW444-AP
abuse-c:        AC1718-AP
status:         ALLOCATED PORTABLE
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-HA
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2023-10-21T03:34:47Z
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:         Wei Wang
nic-hdl:        WW444-AP
e-mail:         abuse@public.zz.ha.cn
address:        #55 San Quan Road, Zhengzhou, Henan Provice
phone:          +86-371-65952358
fax-no:         +86-371-65968952
country:        CN
mnt-by:         MAINT-CNCGROUP-HA
last-modified:  2010-03-05T08:20:01Z
source:         APNIC

% Information related to '123.8.0.0/13AS4837'

route:          123.8.0.0/13
descr:          CNC Group CHINA169 Henan Province Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2008-09-04T07:54:53Z
source:         APNIC

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

;; QUESTION SECTION:
;123.12.220.100.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 03:31:24 CST 2026
;; MSG SIZE  rcvd: 107
Host info
100.220.12.123.in-addr.arpa domain name pointer hn.kd.ny.adsl.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
100.220.12.123.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
61.220.207.241 attackbots
Dec 31 00:38:13 vpn sshd[5881]: Failed password for root from 61.220.207.241 port 59458 ssh2
Dec 31 00:38:18 vpn sshd[5883]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.220.207.241
Dec 31 00:38:20 vpn sshd[5883]: Failed password for invalid user webftp from 61.220.207.241 port 49765 ssh2
2020-01-05 20:25:27
61.19.242.140 attackbotsspam
Mar  8 21:00:46 vpn sshd[18913]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.19.242.140
Mar  8 21:00:48 vpn sshd[18913]: Failed password for invalid user cargue from 61.19.242.140 port 54412 ssh2
Mar  8 21:06:03 vpn sshd[18952]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.19.242.140
2020-01-05 20:41:52
61.68.38.74 attackbotsspam
Mar  3 04:27:40 vpn sshd[22888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.68.38.74
Mar  3 04:27:43 vpn sshd[22888]: Failed password for invalid user yq from 61.68.38.74 port 6231 ssh2
Mar  3 04:37:28 vpn sshd[22916]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.68.38.74
2020-01-05 20:14:28
222.186.175.161 attackspambots
Jan  5 13:19:27 srv-ubuntu-dev3 sshd[36493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.161  user=root
Jan  5 13:19:28 srv-ubuntu-dev3 sshd[36493]: Failed password for root from 222.186.175.161 port 2452 ssh2
Jan  5 13:19:37 srv-ubuntu-dev3 sshd[36493]: Failed password for root from 222.186.175.161 port 2452 ssh2
Jan  5 13:19:27 srv-ubuntu-dev3 sshd[36493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.161  user=root
Jan  5 13:19:28 srv-ubuntu-dev3 sshd[36493]: Failed password for root from 222.186.175.161 port 2452 ssh2
Jan  5 13:19:37 srv-ubuntu-dev3 sshd[36493]: Failed password for root from 222.186.175.161 port 2452 ssh2
Jan  5 13:19:27 srv-ubuntu-dev3 sshd[36493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.161  user=root
Jan  5 13:19:28 srv-ubuntu-dev3 sshd[36493]: Failed password for root from 222.186.175.161 port 
...
2020-01-05 20:20:28
61.2.210.154 attackbotsspam
Mar 13 07:27:58 vpn sshd[14188]: Failed password for root from 61.2.210.154 port 47702 ssh2
Mar 13 07:37:19 vpn sshd[14257]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.2.210.154
Mar 13 07:37:21 vpn sshd[14257]: Failed password for invalid user mcserver from 61.2.210.154 port 56864 ssh2
2020-01-05 20:28:39
82.200.226.226 attack
Unauthorized connection attempt detected from IP address 82.200.226.226 to port 2220 [J]
2020-01-05 20:44:06
218.92.0.168 attack
Jan  5 02:31:10 php1 sshd\[395\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.168  user=root
Jan  5 02:31:12 php1 sshd\[395\]: Failed password for root from 218.92.0.168 port 64873 ssh2
Jan  5 02:31:25 php1 sshd\[395\]: Failed password for root from 218.92.0.168 port 64873 ssh2
Jan  5 02:31:28 php1 sshd\[419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.168  user=root
Jan  5 02:31:30 php1 sshd\[419\]: Failed password for root from 218.92.0.168 port 33647 ssh2
2020-01-05 20:36:20
14.63.174.149 attackbotsspam
Jan  5 12:46:01 srv206 sshd[18167]: Invalid user wnak from 14.63.174.149
...
2020-01-05 20:45:50
36.66.149.211 attackbots
Jan  5 13:08:20 srv2 sshd\[10815\]: Invalid user test3 from 36.66.149.211 port 50988
Jan  5 13:10:41 srv2 sshd\[10884\]: Invalid user carlos from 36.66.149.211 port 42752
Jan  5 13:13:16 srv2 sshd\[10971\]: Invalid user test from 36.66.149.211 port 34518
2020-01-05 20:23:18
61.41.159.29 attackbots
Jan  5 06:30:05 lanister sshd[29282]: Invalid user support from 61.41.159.29
Jan  5 06:30:05 lanister sshd[29282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.41.159.29
Jan  5 06:30:05 lanister sshd[29282]: Invalid user support from 61.41.159.29
Jan  5 06:30:07 lanister sshd[29282]: Failed password for invalid user support from 61.41.159.29 port 55954 ssh2
...
2020-01-05 20:46:32
193.105.134.45 attack
Jan  5 13:33:26 debian64 sshd\[17727\]: Invalid user anonymous from 193.105.134.45 port 7556
Jan  5 13:33:26 debian64 sshd\[17727\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.105.134.45
Jan  5 13:33:27 debian64 sshd\[17727\]: Failed password for invalid user anonymous from 193.105.134.45 port 7556 ssh2
...
2020-01-05 20:47:25
205.185.119.77 attackspam
20/1/4@23:52:27: FAIL: Alarm-Network address from=205.185.119.77
...
2020-01-05 20:43:39
61.37.82.220 attack
Feb 25 06:37:54 vpn sshd[5966]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.37.82.220
Feb 25 06:37:56 vpn sshd[5966]: Failed password for invalid user test from 61.37.82.220 port 40822 ssh2
Feb 25 06:45:08 vpn sshd[6059]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.37.82.220
2020-01-05 20:17:24
196.192.110.100 attackbots
Jan  5 09:24:53 vps46666688 sshd[28625]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.192.110.100
Jan  5 09:24:56 vps46666688 sshd[28625]: Failed password for invalid user qcr from 196.192.110.100 port 49656 ssh2
...
2020-01-05 20:26:58
61.222.168.37 attack
Mar  2 12:32:44 vpn sshd[18803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.222.168.37
Mar  2 12:32:46 vpn sshd[18803]: Failed password for invalid user gi from 61.222.168.37 port 36402 ssh2
Mar  2 12:39:52 vpn sshd[18822]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.222.168.37
2020-01-05 20:22:37

Recently Reported IPs

123.15.184.118 120.208.18.141 119.134.4.206 117.147.28.187
115.60.160.169 112.38.52.220 66.249.73.205 60.7.179.62
60.5.185.12 42.235.41.133 40.124.112.239 39.189.36.119
39.188.164.48 39.162.75.32 39.154.8.24 36.159.129.56
36.148.43.2 36.143.147.22 27.222.100.246 223.91.40.165