City: Jiaxing
Region: Zhejiang
Country: China
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '110.80.0.0 - 110.87.255.255'
% Abuse contact for '110.80.0.0 - 110.87.255.255' is 'anti-spam@chinatelecom.cn'
inetnum: 110.80.0.0 - 110.87.255.255
netname: CHINANET-FJ
descr: CHINANET FUJIAN PROVINCE NETWORK
descr: China Telecom
descr: No.31,jingrong street
descr: Beijing 100032
country: CN
admin-c: CH93-AP
tech-c: CA67-AP
abuse-c: AC1573-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-CHINANET-FJ
mnt-irt: IRT-CHINANET-CN
last-modified: 2021-06-15T08:06:20Z
source: APNIC
irt: IRT-CHINANET-CN
address: No.31 ,jingrong street,beijing
address: 100032
e-mail: anti-spam@chinatelecom.cn
abuse-mailbox: anti-spam@chinatelecom.cn
admin-c: CH93-AP
tech-c: CH93-AP
auth: # Filtered
remarks: anti-spam@chinatelecom.cn was validated on 2025-11-13
mnt-by: MAINT-CHINANET
last-modified: 2026-03-13T07:12:20Z
source: APNIC
role: ABUSE CHINANETCN
country: ZZ
address: No.31 ,jingrong street,beijing
address: 100032
phone: +000000000
e-mail: anti-spam@chinatelecom.cn
admin-c: CH93-AP
tech-c: CH93-AP
nic-hdl: AC1573-AP
remarks: Generated from irt object IRT-CHINANET-CN
remarks: anti-spam@chinatelecom.cn was validated on 2025-11-13
abuse-mailbox: anti-spam@chinatelecom.cn
mnt-by: APNIC-ABUSE
last-modified: 2025-11-13T14:15:15Z
source: APNIC
role: CHINANETFJ IP ADMIN
address: 7,East Street,Fuzhou,Fujian,PRC
country: CN
phone: +86-591-83309761
fax-no: +86-591-83371954
e-mail: fjnic@fjdcb.fz.fj.cn
remarks: send spam reports and abuse reports
remarks: to abuse@fjdcb.fz.fj.cn
remarks: Please include detailed information and
remarks: times in UTC
admin-c: FH71-AP
tech-c: FH71-AP
nic-hdl: CA67-AP
remarks: www.fjtelecom.com
notify: fjnic@fjdcb.fz.fj.cn
mnt-by: MAINT-CHINANET-FJ
last-modified: 2011-12-06T00:10:50Z
source: APNIC
person: Chinanet Hostmaster
nic-hdl: CH93-AP
e-mail: anti-spam@chinatelecom.cn
address: No.31 ,jingrong street,beijing
address: 100032
phone: +86-10-58501724
fax-no: +86-10-58501724
country: CN
mnt-by: MAINT-CHINANET
last-modified: 2022-02-28T06:53:44Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.36-SNAPSHOT (WHOIS-AU5)
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 110.82.104.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27331
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;110.82.104.164. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026032400 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 24 19:37:43 CST 2026
;; MSG SIZE rcvd: 107
Host 164.104.82.110.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 164.104.82.110.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 119.96.227.19 | attackbotsspam | Oct 31 16:56:24 [host] sshd[13751]: Invalid user health from 119.96.227.19 Oct 31 16:56:24 [host] sshd[13751]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.96.227.19 Oct 31 16:56:26 [host] sshd[13751]: Failed password for invalid user health from 119.96.227.19 port 60284 ssh2 |
2019-11-01 00:35:39 |
| 64.201.57.114 | attackbotsspam | Unauthorized connection attempt from IP address 64.201.57.114 on Port 445(SMB) |
2019-11-01 00:06:18 |
| 199.249.230.68 | attackspam | Automatic report - XMLRPC Attack |
2019-11-01 00:19:17 |
| 190.22.167.251 | attackspam | kp-nj1-01 recorded 6 login violations from 190.22.167.251 and was blocked at 2019-10-31 12:02:54. 190.22.167.251 has been blocked on 0 previous occasions. 190.22.167.251's first attempt was recorded at 2019-10-31 12:02:54 |
2019-11-01 00:21:00 |
| 118.173.136.177 | attackbotsspam | Unauthorized connection attempt from IP address 118.173.136.177 on Port 445(SMB) |
2019-11-01 00:08:08 |
| 110.137.176.133 | attackspam | Unauthorized connection attempt from IP address 110.137.176.133 on Port 445(SMB) |
2019-11-01 00:31:03 |
| 52.172.217.146 | attack | 2019-10-30 18:36:14,645 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 18:54:46,231 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 19:13:49,017 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 19:32:50,300 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 19:56:24,685 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 18:36:14,645 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 18:54:46,231 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 19:13:49,017 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 19:32:50,300 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 19:56:24,685 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2019-10-30 18:36:14,645 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 52.172.217.146 2 |
2019-11-01 00:13:26 |
| 220.191.239.4 | attackbots | Unauthorized connection attempt from IP address 220.191.239.4 on Port 445(SMB) |
2019-11-01 00:35:04 |
| 196.189.24.121 | attackbots | Port 1433 Scan |
2019-11-01 00:31:29 |
| 78.187.239.88 | attackbots | Unauthorized connection attempt from IP address 78.187.239.88 on Port 445(SMB) |
2019-11-01 00:20:32 |
| 205.233.73.62 | attack | HTTP 503 XSS Attempt |
2019-11-01 00:25:26 |
| 92.154.31.65 | attackspambots | Unauthorized connection attempt from IP address 92.154.31.65 on Port 445(SMB) |
2019-11-01 00:25:54 |
| 67.22.49.255 | attackbotsspam | HTTP 503 XSS Attempt |
2019-11-01 00:41:43 |
| 167.172.82.230 | attackbotsspam | Lines containing failures of 167.172.82.230 Oct 31 06:46:45 zabbix sshd[79640]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.82.230 user=r.r Oct 31 06:46:47 zabbix sshd[79640]: Failed password for r.r from 167.172.82.230 port 47148 ssh2 Oct 31 06:46:47 zabbix sshd[79640]: Received disconnect from 167.172.82.230 port 47148:11: Bye Bye [preauth] Oct 31 06:46:47 zabbix sshd[79640]: Disconnected from authenticating user r.r 167.172.82.230 port 47148 [preauth] Oct 31 07:04:24 zabbix sshd[81004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.82.230 user=r.r Oct 31 07:04:26 zabbix sshd[81004]: Failed password for r.r from 167.172.82.230 port 42114 ssh2 Oct 31 07:04:27 zabbix sshd[81004]: Received disconnect from 167.172.82.230 port 42114:11: Bye Bye [preauth] Oct 31 07:04:27 zabbix sshd[81004]: Disconnected from authenticating user r.r 167.172.82.230 port 42114 [preauth] Oct 3........ ------------------------------ |
2019-11-01 00:37:30 |
| 51.77.133.61 | attackspambots | WordPress login Brute force / Web App Attack on client site. |
2019-11-01 00:24:22 |