城市(city): unknown
省份(region): unknown
国家(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 '175.44.96.0 - 175.44.127.255'
% Abuse contact for '175.44.96.0 - 175.44.127.255' is 'hqs-ipabuse@chinaunicom.cn'
inetnum: 175.44.96.0 - 175.44.127.255
netname: UNICOM-FJ-NANPING-MAN
descr: Nanping city, fujian provincial network of UNICOM
country: CN
admin-c: NP118-AP
tech-c: NP118-AP
abuse-c: AC1718-AP
status: ALLOCATED NON-PORTABLE
mnt-by: MAINT-CNCGROUP-FJ
mnt-lower: MAINT-CN-NP28
mnt-irt: IRT-CU-CN
last-modified: 2025-01-22T13:20:58Z
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: NAN PING
nic-hdl: NP118-AP
e-mail: liulei108@chinaunicom.cn
address: Nanping city, Fujian province, China
phone: +86-599-6186941
fax-no: +86-599-6186911
country: cn
mnt-by: MAINT-CNCGROUP-FJ
last-modified: 2009-04-02T02:12:47Z
source: APNIC
% Information related to '175.44.0.0/16AS4837'
route: 175.44.0.0/16
descr: China Unicom Fujian Province Network
country: CN
origin: AS4837
mnt-by: MAINT-CNCGROUP-RR
last-modified: 2009-12-15T05:23:20Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 175.44.116.201
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55276
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;175.44.116.201. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026091001 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 05:02:02 CST 2026
;; MSG SIZE rcvd: 107Host 201.116.44.175.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 201.116.44.175.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 89.28.114.49 | attackbots | 19/7/9@09:29:44: FAIL: Alarm-Intrusion address from=89.28.114.49 ... |
2019-07-10 04:28:08 |
| 91.210.145.25 | attack | Time: Tue Jul 9 10:11:14 2019 -0300 IP: 91.210.145.25 (UA/Ukraine/25.145.dynamic.PPPoE.fregat.ua) Failures: 20 (WordPressBruteForcePOST) Interval: 3600 seconds Blocked: Permanent Block |
2019-07-10 04:16:21 |
| 201.174.182.159 | attack | Jul 9 22:07:44 localhost sshd\[19345\]: Invalid user peter from 201.174.182.159 port 43856 Jul 9 22:07:44 localhost sshd\[19345\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.174.182.159 Jul 9 22:07:45 localhost sshd\[19345\]: Failed password for invalid user peter from 201.174.182.159 port 43856 ssh2 |
2019-07-10 04:37:47 |
| 175.143.5.126 | attackbots | Jul 9 21:22:46 apollo sshd\[24849\]: Invalid user testuser from 175.143.5.126Jul 9 21:22:48 apollo sshd\[24849\]: Failed password for invalid user testuser from 175.143.5.126 port 52368 ssh2Jul 9 21:26:04 apollo sshd\[24878\]: Invalid user temp1 from 175.143.5.126 ... |
2019-07-10 04:18:11 |
| 198.55.121.27 | attack | port scan/probe/communication attempt |
2019-07-10 03:55:47 |
| 113.170.67.116 | attack | Unauthorized connection attempt from IP address 113.170.67.116 on Port 445(SMB) |
2019-07-10 04:13:15 |
| 150.242.140.92 | attackspambots | 150.242.140.92 |
2019-07-10 04:20:59 |
| 1.227.93.172 | attack | scan z |
2019-07-10 03:57:15 |
| 113.160.172.29 | attackbots | Unauthorized connection attempt from IP address 113.160.172.29 on Port 445(SMB) |
2019-07-10 03:55:29 |
| 130.211.246.128 | attackspam | IP attempted unauthorised action |
2019-07-10 04:32:39 |
| 81.21.85.114 | attackspam | Unauthorized connection attempt from IP address 81.21.85.114 on Port 445(SMB) |
2019-07-10 04:02:14 |
| 185.53.88.37 | attackbotsspam | Scanning (more than 2 packets) random ports - tries to find possible vulnerable services |
2019-07-10 04:12:32 |
| 162.247.74.27 | attackbotsspam | 2019-07-09T21:47:32.022614scmdmz1 sshd\[27638\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.74.27 user=root 2019-07-09T21:47:33.978797scmdmz1 sshd\[27638\]: Failed password for root from 162.247.74.27 port 44670 ssh2 2019-07-09T21:47:36.845922scmdmz1 sshd\[27638\]: Failed password for root from 162.247.74.27 port 44670 ssh2 ... |
2019-07-10 04:04:50 |
| 119.194.14.3 | attackbots | SSH bruteforce (Triggered fail2ban) |
2019-07-10 04:27:04 |
| 94.126.40.140 | attack | xmlrpc attack |
2019-07-10 04:24:18 |