City: Zhengzhou
Region: Henan
Country: China
Internet Service Provider: 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 '125.40.0.0 - 125.47.255.255'
% Abuse contact for '125.40.0.0 - 125.47.255.255' is 'zhaoyz3@chinaunicom.cn'
inetnum: 125.40.0.0 - 125.47.255.255
netname: UNICOM-HA
descr: China Unicom Henan province network
descr: China Unicom
country: CN
admin-c: CH1302-AP
tech-c: WW444-AP
abuse-c: AC1718-AP
status: ALLOCATED PORTABLE
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: 2023-10-21T03:35:34Z
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 is invalid
mnt-by: MAINT-CNCGROUP
last-modified: 2025-09-10T13:07:04Z
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 is invalid
abuse-mailbox: zhaoyz3@chinaunicom.cn
mnt-by: APNIC-ABUSE
last-modified: 2025-09-10T13:08:11Z
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 '125.40.0.0/13AS4837'
route: 125.40.0.0/13
descr: CNC Group CHINA169 Henan Province Network
country: CN
origin: AS4837
mnt-by: MAINT-CNCGROUP-RR
last-modified: 2008-09-04T07:54:43Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.36-SNAPSHOT (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 125.42.64.40
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29257
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;125.42.64.40. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025092900 1800 900 604800 86400
;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Sep 29 15:38:41 CST 2025
;; MSG SIZE rcvd: 10540.64.42.125.in-addr.arpa domain name pointer hn.kd.ny.adsl.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
40.64.42.125.in-addr.arpa name = hn.kd.ny.adsl.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 51.254.37.192 | attackbots | 2020-06-14T19:07:48.001581+02:00 |
2020-06-15 04:38:44 |
| 54.38.180.93 | attack | 2020-06-14T19:08:01.892871abusebot-5.cloudsearch.cf sshd[30513]: Invalid user www-data from 54.38.180.93 port 51060 2020-06-14T19:08:01.898255abusebot-5.cloudsearch.cf sshd[30513]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.ip-54-38-180.eu 2020-06-14T19:08:01.892871abusebot-5.cloudsearch.cf sshd[30513]: Invalid user www-data from 54.38.180.93 port 51060 2020-06-14T19:08:03.879265abusebot-5.cloudsearch.cf sshd[30513]: Failed password for invalid user www-data from 54.38.180.93 port 51060 ssh2 2020-06-14T19:11:21.148373abusebot-5.cloudsearch.cf sshd[30554]: Invalid user michael from 54.38.180.93 port 33604 2020-06-14T19:11:21.153585abusebot-5.cloudsearch.cf sshd[30554]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.ip-54-38-180.eu 2020-06-14T19:11:21.148373abusebot-5.cloudsearch.cf sshd[30554]: Invalid user michael from 54.38.180.93 port 33604 2020-06-14T19:11:23.591320abusebot-5.cloudsearch.cf s ... |
2020-06-15 04:41:38 |
| 51.77.140.36 | attackbots | Jun 14 21:36:52 pve1 sshd[6043]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.140.36 Jun 14 21:36:54 pve1 sshd[6043]: Failed password for invalid user alex from 51.77.140.36 port 45216 ssh2 ... |
2020-06-15 04:28:57 |
| 106.12.212.89 | attackbots | Jun 14 00:30:03 garuda sshd[465627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.212.89 user=r.r Jun 14 00:30:04 garuda sshd[465627]: Failed password for r.r from 106.12.212.89 port 45838 ssh2 Jun 14 00:30:05 garuda sshd[465627]: Received disconnect from 106.12.212.89: 11: Bye Bye [preauth] Jun 14 00:39:16 garuda sshd[468333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.212.89 user=r.r Jun 14 00:39:18 garuda sshd[468333]: Failed password for r.r from 106.12.212.89 port 33068 ssh2 Jun 14 00:39:18 garuda sshd[468333]: Received disconnect from 106.12.212.89: 11: Bye Bye [preauth] Jun 14 00:43:12 garuda sshd[469530]: Invalid user prisca from 106.12.212.89 Jun 14 00:43:12 garuda sshd[469530]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.212.89 Jun 14 00:43:14 garuda sshd[469530]: Failed password for invalid user prisca fro........ ------------------------------- |
2020-06-15 04:31:07 |
| 122.51.125.104 | attack | Unauthorised connection attempt detected at AUO NODE 4. System is sshd. Protected by AUO Stack Web Application Firewall (WAF) |
2020-06-15 04:29:25 |
| 106.12.45.32 | attackbots | Jun 14 19:28:52 sip sshd[14111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.45.32 Jun 14 19:28:54 sip sshd[14111]: Failed password for invalid user sed from 106.12.45.32 port 48904 ssh2 Jun 14 19:31:16 sip sshd[15011]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.45.32 |
2020-06-15 04:34:48 |
| 159.89.121.79 | attackbotsspam | Automatic report - XMLRPC Attack |
2020-06-15 04:39:04 |
| 62.1.216.128 | attackspambots | Automatic report - XMLRPC Attack |
2020-06-15 05:02:57 |
| 31.186.81.139 | attack | Attacks websites by trying to access known vulnerables of plugins, brute-force of backends or probing of administrative tools |
2020-06-15 04:32:16 |
| 106.13.120.224 | attack | 2020-06-14T12:28:08.290755randservbullet-proofcloud-66.localdomain sshd[13922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.120.224 user=root 2020-06-14T12:28:10.116700randservbullet-proofcloud-66.localdomain sshd[13922]: Failed password for root from 106.13.120.224 port 47142 ssh2 2020-06-14T12:42:53.391837randservbullet-proofcloud-66.localdomain sshd[13989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.120.224 user=root 2020-06-14T12:42:55.377698randservbullet-proofcloud-66.localdomain sshd[13989]: Failed password for root from 106.13.120.224 port 43848 ssh2 ... |
2020-06-15 04:48:37 |
| 179.61.132.206 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drtomalin.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new software that can |
2020-06-15 04:30:30 |
| 66.96.228.119 | attackspambots | Jun 14 18:40:28 * sshd[24502]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.96.228.119 Jun 14 18:40:30 * sshd[24502]: Failed password for invalid user hjbae from 66.96.228.119 port 34424 ssh2 |
2020-06-15 04:27:24 |
| 62.234.137.128 | attack | Jun 14 13:32:40 onepixel sshd[974705]: Invalid user contact from 62.234.137.128 port 60458 Jun 14 13:32:40 onepixel sshd[974705]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.137.128 Jun 14 13:32:40 onepixel sshd[974705]: Invalid user contact from 62.234.137.128 port 60458 Jun 14 13:32:42 onepixel sshd[974705]: Failed password for invalid user contact from 62.234.137.128 port 60458 ssh2 Jun 14 13:35:24 onepixel sshd[975003]: Invalid user qiusb from 62.234.137.128 port 60518 |
2020-06-15 04:42:59 |
| 122.51.183.135 | attack | Jun 14 15:16:17 vps639187 sshd\[3185\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.183.135 user=root Jun 14 15:16:20 vps639187 sshd\[3185\]: Failed password for root from 122.51.183.135 port 40638 ssh2 Jun 14 15:19:43 vps639187 sshd\[3215\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.183.135 user=root ... |
2020-06-15 04:34:33 |
| 41.80.26.227 | attackbotsspam | Brute forcing RDP port 3389 |
2020-06-15 04:26:18 |