城市(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.160.0 - 175.44.191.255'
% Abuse contact for '175.44.160.0 - 175.44.191.255' is 'hqs-ipabuse@chinaunicom.cn'
inetnum: 175.44.160.0 - 175.44.191.255
netname: UNICOM-FJ-SANMING-MAN
descr: Sanming city, fujian provincial network of UNICOM
country: CN
admin-c: SM746-AP
tech-c: SM746-AP
abuse-c: AC1718-AP
status: ALLOCATED NON-PORTABLE
mnt-by: MAINT-CNCGROUP-FJ
mnt-lower: MAINT-CN-SM28
mnt-irt: IRT-CU-CN
last-modified: 2025-01-22T13:18:54Z
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: SAN MING
nic-hdl: SM746-AP
e-mail: fj-xiaosl@chinaunicom.cn
address: Sanming city, Fujian province, China
phone: +86-598-5106174
fax-no: +86-598-5109998
country: CN
mnt-by: MAINT-CNCGROUP-FJ
last-modified: 2013-03-25T00:52:02Z
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-US2); <<>> DiG 9.10.3-P4-Ubuntu <<>> 175.44.171.248
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20999
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;175.44.171.248. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026090200 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 02 18:02:28 CST 2026
;; MSG SIZE rcvd: 107Host 248.171.44.175.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 248.171.44.175.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 133.130.109.152 | attackbotsspam | Jul 29 14:54:11 vps200512 sshd\[9406\]: Invalid user lifengying from 133.130.109.152 Jul 29 14:54:11 vps200512 sshd\[9406\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.130.109.152 Jul 29 14:54:13 vps200512 sshd\[9406\]: Failed password for invalid user lifengying from 133.130.109.152 port 48602 ssh2 Jul 29 14:58:47 vps200512 sshd\[9497\]: Invalid user 110382 from 133.130.109.152 Jul 29 14:58:47 vps200512 sshd\[9497\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.130.109.152 |
2019-07-30 03:00:25 |
| 185.10.68.228 | attackbotsspam | Honeypot attack, port: 23, PTR: 228.68.10.185.ro.ovo.sc. |
2019-07-30 02:53:57 |
| 125.88.177.12 | attack | Jul 29 19:01:20 MK-Soft-VM7 sshd\[13159\]: Invalid user buzhidaog from 125.88.177.12 port 18880 Jul 29 19:01:20 MK-Soft-VM7 sshd\[13159\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.88.177.12 Jul 29 19:01:22 MK-Soft-VM7 sshd\[13159\]: Failed password for invalid user buzhidaog from 125.88.177.12 port 18880 ssh2 ... |
2019-07-30 03:04:17 |
| 153.36.232.49 | attackbotsspam | Jul 29 20:22:09 dev0-dcfr-rnet sshd[5607]: Failed password for root from 153.36.232.49 port 35397 ssh2 Jul 29 20:22:18 dev0-dcfr-rnet sshd[5609]: Failed password for root from 153.36.232.49 port 11334 ssh2 |
2019-07-30 03:01:46 |
| 125.22.76.76 | attackspam | 2019-07-29T18:49:30.293180abusebot-3.cloudsearch.cf sshd\[20458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.22.76.76 user=root |
2019-07-30 03:16:20 |
| 91.34.234.109 | attackspam | Jul 29 19:25:06 h2027339 sshd[8981]: Invalid user pi from 91.34.234.109 Jul 29 19:25:15 h2027339 sshd[8983]: Invalid user pi from 91.34.234.109 Jul 29 19:25:18 h2027339 sshd[8985]: Invalid user pi from 91.34.234.109 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=91.34.234.109 |
2019-07-30 02:41:39 |
| 157.230.32.127 | attackbotsspam | Attempt to log in with non-existing username: [login] |
2019-07-30 02:57:42 |
| 104.131.189.116 | attackbotsspam | Jul 29 13:35:32 aat-srv002 sshd[18062]: Failed password for root from 104.131.189.116 port 52088 ssh2 Jul 29 13:42:04 aat-srv002 sshd[18239]: Failed password for root from 104.131.189.116 port 48142 ssh2 Jul 29 13:48:34 aat-srv002 sshd[18397]: Failed password for root from 104.131.189.116 port 44354 ssh2 ... |
2019-07-30 02:55:57 |
| 178.128.65.72 | attackspambots | Honeypot attack, port: 23, PTR: PTR record not found |
2019-07-30 02:35:51 |
| 37.49.230.216 | attack | Honeypot attack, port: 81, PTR: PTR record not found |
2019-07-30 03:04:33 |
| 221.165.126.138 | attack | Honeypot attack, port: 23, PTR: PTR record not found |
2019-07-30 03:16:45 |
| 168.232.71.77 | attackbotsspam | Jul 29 20:57:30 SilenceServices sshd[30007]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.71.77 Jul 29 20:57:32 SilenceServices sshd[30007]: Failed password for invalid user btsync from 168.232.71.77 port 32234 ssh2 Jul 29 21:02:52 SilenceServices sshd[697]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.71.77 |
2019-07-30 03:04:59 |
| 185.234.219.57 | attack | Jul 29 20:20:42 relay postfix/smtpd\[18667\]: warning: unknown\[185.234.219.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 29 20:22:50 relay postfix/smtpd\[27545\]: warning: unknown\[185.234.219.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 29 20:24:56 relay postfix/smtpd\[27545\]: warning: unknown\[185.234.219.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 29 20:27:08 relay postfix/smtpd\[12682\]: warning: unknown\[185.234.219.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 29 20:29:17 relay postfix/smtpd\[12682\]: warning: unknown\[185.234.219.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-07-30 02:51:55 |
| 185.240.188.34 | attackbotsspam | Jul 30 01:14:36 our-server-hostname postfix/smtpd[12023]: connect from unknown[185.240.188.34] Jul x@x Jul 30 01:14:37 our-server-hostname postfix/smtpd[12023]: lost connection after DATA from unknown[185.240.188.34] Jul 30 01:14:37 our-server-hostname postfix/smtpd[12023]: disconnect from unknown[185.240.188.34] Jul 30 01:14:39 our-server-hostname postfix/smtpd[15832]: connect from unknown[185.240.188.34] Jul x@x Jul x@x Jul 30 01:14:40 our-server-hostname postfix/smtpd[15832]: lost connection after DATA from unknown[185.240.188.34] Jul 30 01:14:40 our-server-hostname postfix/smtpd[15832]: disconnect from unknown[185.240.188.34] Jul 30 03:00:21 our-server-hostname postfix/smtpd[5224]: connect from unknown[185.240.188.34] Jul x@x Jul x@x Jul 30 03:00:22 our-server-hostname postfix/smtpd[5224]: lost connection after DATA from unknown[185.240.188.34] Jul 30 03:00:22 our-server-hostname postfix/smtpd[5224]: disconnect from unknown[185.240.188.34] Jul 30 03:00:27 our-server........ ------------------------------- |
2019-07-30 03:19:12 |
| 190.197.122.110 | attack | Jul 26 15:11:04 mercury auth[5965]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=info@lukegirvin.co.uk rhost=190.197.122.110 ... |
2019-07-30 03:14:26 |