城市(city): Zhengzhou
省份(region): Henan
国家(country): China
运营商(isp): China Unicom
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
% [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 9.10.3-P4-Ubuntu <<>> 42.236.156.49
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42978
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;42.236.156.49. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026091001 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 06:01:14 CST 2026
;; MSG SIZE rcvd: 10649.156.236.42.in-addr.arpa domain name pointer hn.kd.ny.adsl.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
49.156.236.42.in-addr.arpa name = hn.kd.ny.adsl.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 112.85.42.174 | attackbotsspam | Dec 4 06:24:45 ns381471 sshd[4459]: Failed password for root from 112.85.42.174 port 23059 ssh2 Dec 4 06:24:59 ns381471 sshd[4459]: error: maximum authentication attempts exceeded for root from 112.85.42.174 port 23059 ssh2 [preauth] |
2019-12-04 13:27:29 |
| 148.70.116.223 | attackspambots | 2019-12-04T04:57:45.808699abusebot-6.cloudsearch.cf sshd\[16701\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.116.223 user=root |
2019-12-04 13:18:26 |
| 139.199.29.114 | attackspam | 2019-12-04T05:11:05.696420shield sshd\[17728\]: Invalid user eaglesham from 139.199.29.114 port 59666 2019-12-04T05:11:05.700748shield sshd\[17728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.29.114 2019-12-04T05:11:07.365545shield sshd\[17728\]: Failed password for invalid user eaglesham from 139.199.29.114 port 59666 ssh2 2019-12-04T05:17:48.558229shield sshd\[18836\]: Invalid user hanz from 139.199.29.114 port 35344 2019-12-04T05:17:48.563025shield sshd\[18836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.29.114 |
2019-12-04 13:33:41 |
| 159.65.155.227 | attackbots | Dec 4 06:11:52 sd-53420 sshd\[16337\]: User backup from 159.65.155.227 not allowed because none of user's groups are listed in AllowGroups Dec 4 06:11:52 sd-53420 sshd\[16337\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.155.227 user=backup Dec 4 06:11:55 sd-53420 sshd\[16337\]: Failed password for invalid user backup from 159.65.155.227 port 45918 ssh2 Dec 4 06:18:22 sd-53420 sshd\[17458\]: Invalid user stockbridge from 159.65.155.227 Dec 4 06:18:22 sd-53420 sshd\[17458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.155.227 ... |
2019-12-04 13:26:59 |
| 110.43.34.48 | attack | Dec 4 05:50:48 tux-35-217 sshd\[29216\]: Invalid user perl from 110.43.34.48 port 24980 Dec 4 05:50:48 tux-35-217 sshd\[29216\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.43.34.48 Dec 4 05:50:50 tux-35-217 sshd\[29216\]: Failed password for invalid user perl from 110.43.34.48 port 24980 ssh2 Dec 4 05:58:00 tux-35-217 sshd\[29299\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.43.34.48 user=root ... |
2019-12-04 13:06:16 |
| 196.219.173.109 | attackbotsspam | Dec 3 18:58:25 kapalua sshd\[20910\]: Invalid user rajsree from 196.219.173.109 Dec 3 18:58:25 kapalua sshd\[20910\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.219.173.109 Dec 3 18:58:28 kapalua sshd\[20910\]: Failed password for invalid user rajsree from 196.219.173.109 port 51128 ssh2 Dec 3 19:06:46 kapalua sshd\[21687\]: Invalid user elba from 196.219.173.109 Dec 3 19:06:46 kapalua sshd\[21687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.219.173.109 |
2019-12-04 13:19:38 |
| 80.191.185.174 | attackspambots | scan z |
2019-12-04 13:32:15 |
| 31.171.152.107 | attack | (From contactformblastingSaums@gmail.com) What are “contact us” forms? Virtually any website has them, it’s the method any website will use to allow you to contact them. It’s usually a simple form that asks for your name, email address and message and once submitted will result in the person or business receiving your message instantly! Unlike bulk emailing, there are no laws against automated form submission and your message will never get stuck in spam filters. We can’t think of a better way to quickly reach a large volume of people and at such a low cost! https://formblasting.classifiedsubmissions.net http://www.contactformblasting.best |
2019-12-04 13:07:21 |
| 187.16.96.37 | attackspam | Dec 4 05:51:15 minden010 sshd[18166]: Failed password for root from 187.16.96.37 port 36532 ssh2 Dec 4 05:57:56 minden010 sshd[20334]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.16.96.37 Dec 4 05:57:58 minden010 sshd[20334]: Failed password for invalid user motoyoshi from 187.16.96.37 port 47378 ssh2 ... |
2019-12-04 13:07:54 |
| 92.118.38.38 | attackbots | IP: 92.118.38.38 ASN: AS50360 Tamatiya EOOD Port: Message Submission 587 Found in one or more Blacklists Date: 4/12/2019 5:32:25 AM UTC |
2019-12-04 13:36:20 |
| 91.67.43.182 | attackbots | 2019-12-04T05:08:35.622444abusebot-5.cloudsearch.cf sshd\[22629\]: Invalid user robert from 91.67.43.182 port 51882 |
2019-12-04 13:13:52 |
| 212.38.45.66 | attackbotsspam | Dec 4 05:57:27 srv01 sshd[26004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.38.45.66 user=root Dec 4 05:57:29 srv01 sshd[26004]: Failed password for root from 212.38.45.66 port 36009 ssh2 Dec 4 05:57:31 srv01 sshd[26004]: Failed password for root from 212.38.45.66 port 36009 ssh2 Dec 4 05:57:27 srv01 sshd[26004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.38.45.66 user=root Dec 4 05:57:29 srv01 sshd[26004]: Failed password for root from 212.38.45.66 port 36009 ssh2 Dec 4 05:57:31 srv01 sshd[26004]: Failed password for root from 212.38.45.66 port 36009 ssh2 Dec 4 05:57:27 srv01 sshd[26004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.38.45.66 user=root Dec 4 05:57:29 srv01 sshd[26004]: Failed password for root from 212.38.45.66 port 36009 ssh2 Dec 4 05:57:31 srv01 sshd[26004]: Failed password for root from 212.38.45.66 port 36009 ... |
2019-12-04 13:28:03 |
| 54.36.241.186 | attack | 2019-12-04T04:57:42.850402abusebot-2.cloudsearch.cf sshd\[12725\]: Invalid user popovic from 54.36.241.186 port 49156 |
2019-12-04 13:22:36 |
| 119.57.162.18 | attackbots | $f2bV_matches |
2019-12-04 13:36:49 |
| 45.141.86.156 | attack | RDP Bruteforce |
2019-12-04 11:05:18 |