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.235.47.193 attackbotsspam
Unauthorized connection attempt detected from IP address 42.235.47.193 to port 23 [T]
2020-05-06 08:31:37
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 2025-10-17
mnt-by:         MAINT-CNCGROUP
last-modified:  2025-10-17T02:26:26Z
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:         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.36-SNAPSHOT (WHOIS-AU5)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 42.235.47.161
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2500
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;42.235.47.161.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 06 13:00:51 CST 2025
;; MSG SIZE  rcvd: 106
Host info
161.47.235.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:
161.47.235.42.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
183.111.227.5 attackbots
detected by Fail2Ban
2019-11-09 21:54:02
104.244.72.98 attack
2019-11-09T10:51:07.970181abusebot-3.cloudsearch.cf sshd\[14105\]: Invalid user fake from 104.244.72.98 port 40710
2019-11-09 22:16:06
150.95.186.200 attackbots
Nov  9 11:28:35 XXX sshd[21600]: Invalid user deploy from 150.95.186.200 port 37738
2019-11-09 21:54:50
110.49.70.241 attack
Automatic report - Banned IP Access
2019-11-09 22:16:53
180.76.176.174 attackspam
Nov  9 14:08:05 tux-35-217 sshd\[20591\]: Invalid user solrs from 180.76.176.174 port 35528
Nov  9 14:08:05 tux-35-217 sshd\[20591\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.176.174
Nov  9 14:08:08 tux-35-217 sshd\[20591\]: Failed password for invalid user solrs from 180.76.176.174 port 35528 ssh2
Nov  9 14:13:23 tux-35-217 sshd\[20619\]: Invalid user mysql from 180.76.176.174 port 40758
Nov  9 14:13:23 tux-35-217 sshd\[20619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.176.174
...
2019-11-09 21:42:12
211.252.19.254 attackspam
Nov  9 12:17:14 XXX sshd[56872]: Invalid user ofsaa from 211.252.19.254 port 56486
2019-11-09 22:06:17
91.121.103.175 attackbots
$f2bV_matches
2019-11-09 22:12:42
76.11.0.63 attackbots
Hits on port : 2323
2019-11-09 21:47:13
185.156.177.171 attackspambots
rdp brute-force attack
2019-11-09 22:09:38
45.136.110.40 attackbotsspam
Nov  9 13:47:05 h2177944 kernel: \[6179212.628904\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.40 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=2398 PROTO=TCP SPT=48096 DPT=3900 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  9 13:47:15 h2177944 kernel: \[6179222.418701\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.40 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=39562 PROTO=TCP SPT=48096 DPT=7391 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  9 13:57:42 h2177944 kernel: \[6179849.370567\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.40 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=17421 PROTO=TCP SPT=48096 DPT=5553 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  9 14:06:07 h2177944 kernel: \[6180354.254241\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.40 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=22109 PROTO=TCP SPT=48096 DPT=40300 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  9 14:35:44 h2177944 kernel: \[6182130.690960\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.40 DST=85.214.117.9
2019-11-09 21:52:44
45.136.110.47 attack
Nov  9 14:50:41 mc1 kernel: \[4593730.471126\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=9898 PROTO=TCP SPT=50544 DPT=8095 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  9 14:52:49 mc1 kernel: \[4593857.941345\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=51260 PROTO=TCP SPT=50544 DPT=6677 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  9 14:57:30 mc1 kernel: \[4594139.323677\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=5317 PROTO=TCP SPT=50544 DPT=8268 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-09 22:04:29
45.136.108.68 attack
Connection by 45.136.108.68 on port: 3872 got caught by honeypot at 11/9/2019 10:07:39 AM
2019-11-09 21:56:58
118.174.215.121 attackspambots
DATE:2019-11-09 07:18:07, IP:118.174.215.121, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2019-11-09 22:22:02
218.92.0.198 attack
Nov  9 11:17:54 legacy sshd[11703]: Failed password for root from 218.92.0.198 port 10751 ssh2
Nov  9 11:21:28 legacy sshd[11814]: Failed password for root from 218.92.0.198 port 60004 ssh2
Nov  9 11:21:31 legacy sshd[11814]: Failed password for root from 218.92.0.198 port 60004 ssh2
...
2019-11-09 22:21:18
37.187.122.195 attack
Nov  9 10:10:55 [host] sshd[10799]: Invalid user arojas from 37.187.122.195
Nov  9 10:10:55 [host] sshd[10799]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.122.195
Nov  9 10:10:57 [host] sshd[10799]: Failed password for invalid user arojas from 37.187.122.195 port 52074 ssh2
2019-11-09 22:18:14

Recently Reported IPs

42.230.241.105 42.229.128.13 39.190.84.28 36.143.157.251
27.213.53.19 27.14.204.84 183.198.45.155 182.126.107.118
182.116.127.103 120.9.206.163 120.239.155.216 119.178.160.74
112.51.197.81 112.246.225.39 110.254.214.255 209.76.93.14
103.163.46.125 192.34.61.122 173.88.106.36 45.144.53.78