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:
IP Type Details Datetime
42.234.176.217 attackbots
port 23 attempt blocked
2019-11-19 07:32:14
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 'hqs-ipabuse@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:         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 '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.234.17.226
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9768
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;42.234.17.226.			IN	A

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

;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Aug 20 19:31:30 CST 2026
;; MSG SIZE  rcvd: 106
Host info
226.17.234.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:
226.17.234.42.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.55.182.232 attackbots
May  1 14:57:55 ip-172-31-61-156 sshd[27611]: Invalid user software from 45.55.182.232
May  1 14:57:57 ip-172-31-61-156 sshd[27611]: Failed password for invalid user software from 45.55.182.232 port 40514 ssh2
May  1 14:57:55 ip-172-31-61-156 sshd[27611]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.182.232
May  1 14:57:55 ip-172-31-61-156 sshd[27611]: Invalid user software from 45.55.182.232
May  1 14:57:57 ip-172-31-61-156 sshd[27611]: Failed password for invalid user software from 45.55.182.232 port 40514 ssh2
...
2020-05-01 23:58:07
66.70.130.153 attackbotsspam
May  1 17:38:35 gw1 sshd[6194]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.130.153
May  1 17:38:37 gw1 sshd[6194]: Failed password for invalid user gn from 66.70.130.153 port 47402 ssh2
...
2020-05-02 00:16:50
121.154.209.29 attackspambots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-05-01 23:59:35
222.186.175.183 attackbotsspam
May  1 17:47:27 legacy sshd[12947]: Failed password for root from 222.186.175.183 port 2014 ssh2
May  1 17:47:39 legacy sshd[12947]: error: maximum authentication attempts exceeded for root from 222.186.175.183 port 2014 ssh2 [preauth]
May  1 17:47:45 legacy sshd[12953]: Failed password for root from 222.186.175.183 port 17200 ssh2
...
2020-05-02 00:03:18
162.243.142.72 attackspam
2323/tcp 2323/tcp 9200/tcp
[2020-04-29/05-01]3pkt
2020-05-01 23:44:23
162.243.136.231 attackbotsspam
465/tcp 8087/tcp
[2020-04-29/30]2pkt
2020-05-01 23:53:49
116.98.54.4 attack
Someone from this IP address keep trying to get into my email. I have double security but they keep trying. 
Are you trying to sign in?
If so, use this code to finish signing in.
chrome, windows nt
When

April 26, 2020 6:18:51 PM PDT
Where*
Vietnam
116.98.54.41
2020-05-01 23:45:44
173.18.35.132 attack
Unauthorized connection attempt detected from IP address 173.18.35.132 to port 23
2020-05-02 00:05:55
45.227.253.146 attack
Magento 1.9 Admin Login Brute-Force
2020-05-01 23:52:43
162.243.142.176 attack
firewall-block, port(s): 1433/tcp
2020-05-01 23:55:44
51.68.142.141 spamattack
Wtf
2020-05-01 23:41:16
156.218.184.37 attack
May 1 13:48:15 *host* postfix/smtps/smtpd\[10937\]: warning: unknown\[156.218.184.37\]: SASL PLAIN authentication failed:
2020-05-02 00:12:25
93.185.192.92 attackspam
445/tcp 445/tcp 445/tcp...
[2020-04-27/05-01]4pkt,1pt.(tcp)
2020-05-01 23:45:23
118.89.25.35 attack
Brute-force attempt banned
2020-05-01 23:57:29
49.235.240.105 attack
(sshd) Failed SSH login from 49.235.240.105 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May  1 14:34:51 s1 sshd[19808]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.240.105  user=root
May  1 14:34:53 s1 sshd[19808]: Failed password for root from 49.235.240.105 port 39290 ssh2
May  1 14:57:59 s1 sshd[20582]: Invalid user postgres from 49.235.240.105 port 48738
May  1 14:58:02 s1 sshd[20582]: Failed password for invalid user postgres from 49.235.240.105 port 48738 ssh2
May  1 15:03:38 s1 sshd[21176]: Invalid user oracle from 49.235.240.105 port 49486
2020-05-01 23:38:06

Recently Reported IPs

78.225.248.37 107.150.98.237 44.220.185.107 95.181.232.51
39.154.23.58 39.154.12.48 223.88.145.57 183.208.135.199
72.10.192.69 72.131.142.100 60.5.26.148 39.78.96.198
223.90.32.63 1.61.63.98 123.12.30.43 120.82.87.159
117.188.27.99 112.49.113.92 112.238.178.200 2606:4700:10::ac43:2334