城市(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.64.0 - 175.44.95.255'
% Abuse contact for '175.44.64.0 - 175.44.95.255' is 'hqs-ipabuse@chinaunicom.cn'
inetnum: 175.44.64.0 - 175.44.95.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:19:52Z
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-AU4); <<>> DiG 9.10.3-P4-Ubuntu <<>> 175.44.80.225
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21681
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;175.44.80.225. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026102400 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 24 19:03:47 CST 2026
;; MSG SIZE rcvd: 106Host 225.80.44.175.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 225.80.44.175.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 175.24.33.60 | attack | Aug 4 13:57:43 pixelmemory sshd[55267]: Failed password for root from 175.24.33.60 port 35546 ssh2 Aug 4 14:02:34 pixelmemory sshd[66351]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.33.60 user=root Aug 4 14:02:36 pixelmemory sshd[66351]: Failed password for root from 175.24.33.60 port 33146 ssh2 Aug 4 14:12:38 pixelmemory sshd[89821]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.33.60 user=root Aug 4 14:12:39 pixelmemory sshd[89821]: Failed password for root from 175.24.33.60 port 56578 ssh2 ... |
2020-08-05 07:59:10 |
| 149.202.59.123 | attack | 149.202.59.123 - - [04/Aug/2020:19:54:14 +0200] "GET /wp-login.php HTTP/1.1" 301 247 "http://[hidden]/wp-login.php" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 149.202.59.123 - - [04/Aug/2020:19:54:14 +0200] "GET /wp-login.php HTTP/1.1" 404 4264 "http://[hidden]/wp-login.php" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2020-08-05 07:34:52 |
| 118.172.186.244 | attack | 20/8/4@13:53:42: FAIL: Alarm-Network address from=118.172.186.244 20/8/4@13:53:43: FAIL: Alarm-Network address from=118.172.186.244 ... |
2020-08-05 08:00:55 |
| 106.13.39.56 | attackbotsspam | Aug 5 01:38:16 srv-ubuntu-dev3 sshd[67629]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.39.56 user=root Aug 5 01:38:18 srv-ubuntu-dev3 sshd[67629]: Failed password for root from 106.13.39.56 port 38424 ssh2 Aug 5 01:40:21 srv-ubuntu-dev3 sshd[67870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.39.56 user=root Aug 5 01:40:23 srv-ubuntu-dev3 sshd[67870]: Failed password for root from 106.13.39.56 port 43894 ssh2 Aug 5 01:42:28 srv-ubuntu-dev3 sshd[68086]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.39.56 user=root Aug 5 01:42:31 srv-ubuntu-dev3 sshd[68086]: Failed password for root from 106.13.39.56 port 49360 ssh2 Aug 5 01:44:37 srv-ubuntu-dev3 sshd[68334]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.39.56 user=root Aug 5 01:44:40 srv-ubuntu-dev3 sshd[68334]: Failed password ... |
2020-08-05 07:48:19 |
| 179.212.136.198 | attackbotsspam | Jul 30 21:28:44 prox sshd[14475]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.212.136.198 Jul 30 21:28:46 prox sshd[14475]: Failed password for invalid user tristos from 179.212.136.198 port 32889 ssh2 |
2020-08-05 07:53:28 |
| 45.145.67.80 | attackspam | Aug 5 01:36:32 debian-2gb-nbg1-2 kernel: \[18842656.094775\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.145.67.80 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=26106 PROTO=TCP SPT=42901 DPT=54154 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-08-05 07:37:04 |
| 185.193.88.4 | attackspam | Brute forcing RDP port 3389 |
2020-08-05 07:27:23 |
| 139.99.238.150 | attackbots | Aug 4 23:03:44 rush sshd[20267]: Failed password for root from 139.99.238.150 port 48902 ssh2 Aug 4 23:08:04 rush sshd[20417]: Failed password for root from 139.99.238.150 port 55658 ssh2 ... |
2020-08-05 07:33:07 |
| 124.105.173.17 | attack | 2020-08-04T23:36:13.697144shield sshd\[22660\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.105.173.17 user=root 2020-08-04T23:36:15.470237shield sshd\[22660\]: Failed password for root from 124.105.173.17 port 37171 ssh2 2020-08-04T23:38:39.305974shield sshd\[23769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.105.173.17 user=root 2020-08-04T23:38:40.789765shield sshd\[23769\]: Failed password for root from 124.105.173.17 port 54719 ssh2 2020-08-04T23:41:00.919518shield sshd\[24710\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.105.173.17 user=root |
2020-08-05 07:55:31 |
| 192.35.169.42 | attackbots |
|
2020-08-05 07:34:39 |
| 109.86.244.225 | attack | Dovecot Invalid User Login Attempt. |
2020-08-05 08:02:08 |
| 222.186.175.148 | attackbotsspam | 2020-08-04T23:25:18.583121server.espacesoutien.com sshd[9010]: Failed password for root from 222.186.175.148 port 19722 ssh2 2020-08-04T23:25:21.846383server.espacesoutien.com sshd[9010]: Failed password for root from 222.186.175.148 port 19722 ssh2 2020-08-04T23:25:24.993098server.espacesoutien.com sshd[9010]: Failed password for root from 222.186.175.148 port 19722 ssh2 2020-08-04T23:25:27.888656server.espacesoutien.com sshd[9010]: Failed password for root from 222.186.175.148 port 19722 ssh2 ... |
2020-08-05 07:29:23 |
| 92.63.196.20 | attackspambots | 3389BruteforceStormFW22 |
2020-08-05 07:49:28 |
| 62.148.226.131 | attackbots | Unauthorised access (Aug 4) SRC=62.148.226.131 LEN=52 PREC=0x20 TTL=114 ID=18357 DF TCP DPT=445 WINDOW=8192 SYN |
2020-08-05 07:42:20 |
| 139.155.74.13 | attackspambots | MLV GET /wp-login.php |
2020-08-05 07:43:38 |