42.228.123.172

Basic Info

City: unknown

Region: unknown

Country: China

Internet Service Provider: China Unicom

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

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 '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-AU4)

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 42.228.123.172
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16576
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;42.228.123.172.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 13 20:32:10 CST 2026
;; MSG SIZE  rcvd: 107

Host info

172.123.228.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:
172.123.228.42.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:

Related IP info:

Related comments:

IP	Type	Details	Datetime
111.177.32.83	attackbots	Sep 6 06:50:07 intra sshd\[35940\]: Invalid user ansible from 111.177.32.83Sep 6 06:50:10 intra sshd\[35940\]: Failed password for invalid user ansible from 111.177.32.83 port 34308 ssh2Sep 6 06:55:00 intra sshd\[36029\]: Invalid user demo from 111.177.32.83Sep 6 06:55:02 intra sshd\[36029\]: Failed password for invalid user demo from 111.177.32.83 port 49618 ssh2Sep 6 06:59:52 intra sshd\[36081\]: Invalid user nagios from 111.177.32.83Sep 6 06:59:54 intra sshd\[36081\]: Failed password for invalid user nagios from 111.177.32.83 port 36676 ssh2 ...	2019-09-06 12:10:07
60.165.53.185	attackspambots	19/9/5@23:58:57: FAIL: Alarm-Intrusion address from=60.165.53.185 ...	2019-09-06 12:49:00
95.58.194.141	attackbotsspam	Automatic report - Banned IP Access	2019-09-06 12:05:12
185.53.88.66	attackspambots	\[2019-09-06 00:14:20\] NOTICE\[1829\] chan_sip.c: Registration from '"7458" \' failed for '185.53.88.66:5333' - Wrong password \[2019-09-06 00:14:20\] SECURITY\[1837\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-09-06T00:14:20.111-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="7458",SessionID="0x7f7b30be0af8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.53.88.66/5333",Challenge="4e449fb6",ReceivedChallenge="4e449fb6",ReceivedHash="2700993449a2671f69437e0cc38a1d91" \[2019-09-06 00:14:20\] NOTICE\[1829\] chan_sip.c: Registration from '"7458" \' failed for '185.53.88.66:5333' - Wrong password \[2019-09-06 00:14:20\] SECURITY\[1837\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-09-06T00:14:20.225-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="7458",SessionID="0x7f7b306fb678",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/1	2019-09-06 12:34:57
118.152.164.59	attackbotsspam	2019-09-05T23:20:28.957396WS-Zach sshd[9615]: Invalid user bcd from 118.152.164.59 port 57408 2019-09-05T23:20:28.961454WS-Zach sshd[9615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.152.164.59 2019-09-05T23:20:28.957396WS-Zach sshd[9615]: Invalid user bcd from 118.152.164.59 port 57408 2019-09-05T23:20:30.992386WS-Zach sshd[9615]: Failed password for invalid user bcd from 118.152.164.59 port 57408 ssh2 2019-09-06T00:06:52.462705WS-Zach sshd[1116]: Invalid user asd from 118.152.164.59 port 58236 ...	2019-09-06 12:40:11
43.226.69.133	attackspam	Sep 5 18:41:30 wbs sshd\[25747\]: Invalid user admin from 43.226.69.133 Sep 5 18:41:30 wbs sshd\[25747\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.69.133 Sep 5 18:41:32 wbs sshd\[25747\]: Failed password for invalid user admin from 43.226.69.133 port 60510 ssh2 Sep 5 18:43:55 wbs sshd\[26011\]: Invalid user oracle from 43.226.69.133 Sep 5 18:43:55 wbs sshd\[26011\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.69.133	2019-09-06 12:49:21
68.183.236.92	attackbotsspam	Sep 6 04:24:47 web8 sshd\[25881\]: Invalid user postgres from 68.183.236.92 Sep 6 04:24:47 web8 sshd\[25881\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.236.92 Sep 6 04:24:48 web8 sshd\[25881\]: Failed password for invalid user postgres from 68.183.236.92 port 44756 ssh2 Sep 6 04:29:57 web8 sshd\[28580\]: Invalid user jenkins from 68.183.236.92 Sep 6 04:29:57 web8 sshd\[28580\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.236.92	2019-09-06 12:34:00
92.82.36.130	attackbots	Jun 25 02:03:50 Server10 sshd[16012]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.82.36.130 Jun 25 02:03:52 Server10 sshd[16012]: Failed password for invalid user ts3server from 92.82.36.130 port 54367 ssh2 Jun 25 02:06:03 Server10 sshd[17238]: Invalid user bobby from 92.82.36.130 port 38597 Jun 25 02:06:03 Server10 sshd[17238]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.82.36.130 Jun 25 02:06:05 Server10 sshd[17238]: Failed password for invalid user bobby from 92.82.36.130 port 38597 ssh2	2019-09-06 12:45:09
222.186.42.241	attackspam	Sep 6 03:59:56 unicornsoft sshd\[22241\]: User root from 222.186.42.241 not allowed because not listed in AllowUsers Sep 6 03:59:56 unicornsoft sshd\[22241\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.241 user=root Sep 6 03:59:58 unicornsoft sshd\[22241\]: Failed password for invalid user root from 222.186.42.241 port 64964 ssh2	2019-09-06 12:06:28
178.128.158.199	attack	Sep 5 11:23:15 lcdev sshd\[8507\]: Invalid user admin from 178.128.158.199 Sep 5 11:23:15 lcdev sshd\[8507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=instock.mx Sep 5 11:23:16 lcdev sshd\[8507\]: Failed password for invalid user admin from 178.128.158.199 port 56438 ssh2 Sep 5 11:27:24 lcdev sshd\[8817\]: Invalid user vagrant from 178.128.158.199 Sep 5 11:27:24 lcdev sshd\[8817\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=instock.mx	2019-09-06 12:02:14
119.29.53.107	attack	Sep 6 07:26:04 yabzik sshd[29616]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.53.107 Sep 6 07:26:06 yabzik sshd[29616]: Failed password for invalid user sail_ftp from 119.29.53.107 port 35597 ssh2 Sep 6 07:31:20 yabzik sshd[31340]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.53.107	2019-09-06 12:31:47
51.79.73.206	attackspambots	Sep 5 23:59:28 TORMINT sshd\[23687\]: Invalid user demo from 51.79.73.206 Sep 5 23:59:28 TORMINT sshd\[23687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.73.206 Sep 5 23:59:30 TORMINT sshd\[23687\]: Failed password for invalid user demo from 51.79.73.206 port 40826 ssh2 ...	2019-09-06 12:14:14
14.232.122.247	attack	Unauthorised access (Sep 6) SRC=14.232.122.247 LEN=52 TTL=116 ID=30127 DF TCP DPT=445 WINDOW=8192 SYN	2019-09-06 12:26:56
201.48.233.196	attackbots	Sep 5 23:17:33 aat-srv002 sshd[7277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.48.233.196 Sep 5 23:17:34 aat-srv002 sshd[7277]: Failed password for invalid user user from 201.48.233.196 port 37960 ssh2 Sep 5 23:22:06 aat-srv002 sshd[7424]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.48.233.196 Sep 5 23:22:08 aat-srv002 sshd[7424]: Failed password for invalid user mysql from 201.48.233.196 port 34885 ssh2 ...	2019-09-06 12:26:37
118.24.95.31	attackbots	Sep 6 06:52:03 site1 sshd\[46497\]: Invalid user deploy from 118.24.95.31Sep 6 06:52:04 site1 sshd\[46497\]: Failed password for invalid user deploy from 118.24.95.31 port 47835 ssh2Sep 6 06:55:57 site1 sshd\[46638\]: Invalid user musikbot from 118.24.95.31Sep 6 06:55:59 site1 sshd\[46638\]: Failed password for invalid user musikbot from 118.24.95.31 port 36163 ssh2Sep 6 06:59:41 site1 sshd\[46802\]: Invalid user ftpadmin from 118.24.95.31Sep 6 06:59:43 site1 sshd\[46802\]: Failed password for invalid user ftpadmin from 118.24.95.31 port 52720 ssh2 ...	2019-09-06 12:17:13

Recently Reported IPs

64.205.72.104	39.154.11.79	36.148.43.140	2.57.17.158
223.66.42.224	200.138.46.51	200.138.46.44	200.138.46.119
183.198.161.146	182.127.12.115	120.239.27.182	120.229.151.53
119.181.17.101	117.10.138.244	112.50.143.233	112.22.80.136
37.255.206.81	34.240.45.137	104.243.31.175	23.224.194.122