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

Region: Beijing

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 '42.224.0.0 - 42.239.255.255'

% Abuse contact for '42.224.0.0 - 42.239.255.255' is 'zhaoyz3@chinaunicom.cn'

inetnum:        42.224.0.0 - 42.239.255.255
netname:        UNICOM-HA
descr:          China Unicom Henan province network
descr:          China Unicom
descr:          No.21,JiN-Rong Street,
descr:          Beijing 100033
country:        CN
admin-c:        CH1302-AP
tech-c:         WW444-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-HA
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2025-01-22T13:12:22Z
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 2026-05-08
mnt-by:         MAINT-CNCGROUP
last-modified:  2026-05-09T04:50:16Z
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 2026-05-08
abuse-mailbox:  zhaoyz3@chinaunicom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2026-05-08T01:31:32Z
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 '42.224.0.0/12AS4837'

route:          42.224.0.0/12
descr:          China Unicom Henan Province Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2011-03-02T05:24:03Z
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 <<>> 42.236.19.16
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59778
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;42.236.19.16.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jul 18 14:09:46 CST 2026
;; MSG SIZE  rcvd: 105
Host info
16.19.236.42.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:
16.19.236.42.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
195.154.223.226 attackbots
2019-12-10T08:40:29.370463abusebot-4.cloudsearch.cf sshd\[32462\]: Invalid user admin from 195.154.223.226 port 42112
2019-12-10 17:01:47
156.213.72.205 attack
Host Scan
2019-12-10 17:13:35
37.49.225.166 attack
37.49.225.166 was recorded 11 times by 10 hosts attempting to connect to the following ports: 17185,3283. Incident counter (4h, 24h, all-time): 11, 33, 1018
2019-12-10 17:11:52
109.94.69.124 attack
[portscan] Port scan
2019-12-10 17:17:11
144.217.84.164 attackbotsspam
Dec 10 10:02:39 vps691689 sshd[24574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.84.164
Dec 10 10:02:41 vps691689 sshd[24574]: Failed password for invalid user guest333 from 144.217.84.164 port 43104 ssh2
...
2019-12-10 17:14:06
159.138.151.224 attackbotsspam
badbot
2019-12-10 16:56:42
163.172.251.80 attackbotsspam
2019-12-10T09:21:06.141625vps751288.ovh.net sshd\[9395\]: Invalid user www from 163.172.251.80 port 54216
2019-12-10T09:21:06.153709vps751288.ovh.net sshd\[9395\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.251.80
2019-12-10T09:21:08.601708vps751288.ovh.net sshd\[9395\]: Failed password for invalid user www from 163.172.251.80 port 54216 ssh2
2019-12-10T09:26:55.927579vps751288.ovh.net sshd\[9453\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.251.80  user=root
2019-12-10T09:26:57.618231vps751288.ovh.net sshd\[9453\]: Failed password for root from 163.172.251.80 port 36442 ssh2
2019-12-10 16:47:36
119.29.152.172 attackspam
Dec 10 08:43:18 sd-53420 sshd\[30931\]: Invalid user pizza from 119.29.152.172
Dec 10 08:43:18 sd-53420 sshd\[30931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.152.172
Dec 10 08:43:20 sd-53420 sshd\[30931\]: Failed password for invalid user pizza from 119.29.152.172 port 37606 ssh2
Dec 10 08:49:52 sd-53420 sshd\[32025\]: Invalid user server from 119.29.152.172
Dec 10 08:49:52 sd-53420 sshd\[32025\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.152.172
...
2019-12-10 17:20:14
54.39.196.199 attackspam
Dec 10 05:41:16 firewall sshd[25236]: Invalid user mozee from 54.39.196.199
Dec 10 05:41:18 firewall sshd[25236]: Failed password for invalid user mozee from 54.39.196.199 port 43862 ssh2
Dec 10 05:46:52 firewall sshd[25416]: Invalid user ursala from 54.39.196.199
...
2019-12-10 16:57:13
185.175.93.107 attackspambots
12/10/2019-09:46:18.221288 185.175.93.107 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-12-10 17:09:21
46.238.53.245 attackspambots
2019-12-10T08:36:23.444317shield sshd\[17242\]: Invalid user 1qazxcvghjklp0 from 46.238.53.245 port 50592
2019-12-10T08:36:23.449856shield sshd\[17242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.238.53.245
2019-12-10T08:36:25.119841shield sshd\[17242\]: Failed password for invalid user 1qazxcvghjklp0 from 46.238.53.245 port 50592 ssh2
2019-12-10T08:42:43.768828shield sshd\[18533\]: Invalid user abcd1234!@\# from 46.238.53.245 port 59338
2019-12-10T08:42:43.774808shield sshd\[18533\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.238.53.245
2019-12-10 17:15:04
52.73.169.169 attackbots
52.73.169.169 was recorded 12 times by 12 hosts attempting to connect to the following ports: 123. Incident counter (4h, 24h, all-time): 12, 45, 665
2019-12-10 17:12:45
96.64.7.59 attack
Dec 10 03:49:56 linuxvps sshd\[12745\]: Invalid user trashcan from 96.64.7.59
Dec 10 03:49:56 linuxvps sshd\[12745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.64.7.59
Dec 10 03:49:58 linuxvps sshd\[12745\]: Failed password for invalid user trashcan from 96.64.7.59 port 34546 ssh2
Dec 10 03:55:25 linuxvps sshd\[16416\]: Invalid user danielb from 96.64.7.59
Dec 10 03:55:25 linuxvps sshd\[16416\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.64.7.59
2019-12-10 17:00:10
183.134.212.18 attackbotsspam
Dec  9 22:26:00 hanapaa sshd\[26680\]: Invalid user clemence from 183.134.212.18
Dec  9 22:26:00 hanapaa sshd\[26680\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.134.212.18
Dec  9 22:26:01 hanapaa sshd\[26680\]: Failed password for invalid user clemence from 183.134.212.18 port 2122 ssh2
Dec  9 22:31:34 hanapaa sshd\[27329\]: Invalid user admin from 183.134.212.18
Dec  9 22:31:34 hanapaa sshd\[27329\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.134.212.18
2019-12-10 17:00:42
54.36.180.236 attackspam
2019-12-10T09:35:32.536809scmdmz1 sshd\[29417\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=236.ip-54-36-180.eu  user=root
2019-12-10T09:35:34.579325scmdmz1 sshd\[29417\]: Failed password for root from 54.36.180.236 port 59192 ssh2
2019-12-10T09:41:47.075863scmdmz1 sshd\[29721\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=236.ip-54-36-180.eu  user=named
...
2019-12-10 17:14:35

Recently Reported IPs

38.76.168.213 2606:4700:10::ac43:2744 2606:4700:10::6814:5803 2606:4700:10::6816:3548
2606:4700:10::6814:8980 161.35.84.208 121.199.34.107 2606:4700:10::6816:3098
2606:4700:10::6816:910 185.242.3.233 34.77.232.84 170.205.31.154
2606:4700:10::6816:3797 2606:4700:10::6816:4559 2606:4700:10::6816:3328 109.162.246.154
2606:4700:10::6816:1302 192.168.2.53 190.2.150.133 27.154.89.190