城市(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 '116.128.0.0 - 116.191.255.255'
% Abuse contact for '116.128.0.0 - 116.191.255.255' is 'zhaoyz3@chinaunicom.cn'
inetnum: 116.128.0.0 - 116.191.255.255
netname: UNICOM
descr: China United Network Communications Corporation Limited
descr: No.21 Financial Street,Xicheng District, Beijing 100140 ,P.R.China
country: CN
admin-c: XZ67-AP
tech-c: XZ67-AP
abuse-c: AC1601-AP
status: ALLOCATED PORTABLE
mnt-by: MAINT-CNNIC-AP
mnt-lower: MAINT-CNNIC-AP
mnt-routes: MAINT-CNNIC-AP
mnt-irt: IRT-UNICOM-CN
last-modified: 2021-11-02T07:48:23Z
source: APNIC
irt: IRT-UNICOM-CN
address: No.21 Financial Street,Xicheng District,
address: Beijing 100140 ,P.R.China
e-mail: zhaoyz3@chinaunicom.cn
abuse-mailbox: zhaoyz3@chinaunicom.cn
admin-c: YW6851-AP
tech-c: YW6851-AP
auth: # Filtered
remarks: zhaoyz3@chinaunicom.cn is invalid
mnt-by: MAINT-CNNIC-AP
last-modified: 2025-09-10T13:07:04Z
source: APNIC
role: ABUSE CNNICCN
country: ZZ
address: Beijing, China
phone: +000000000
e-mail: ipas@cnnic.cn
admin-c: IP50-AP
tech-c: IP50-AP
nic-hdl: AC1601-AP
remarks: Generated from irt object IRT-CNNIC-CN
remarks: ipas@cnnic.cn is invalid
abuse-mailbox: ipas@cnnic.cn
mnt-by: APNIC-ABUSE
last-modified: 2025-09-19T17:20:32Z
source: APNIC
person: Xiaomin Zhou
address: No.21 Financial Street,Xicheng District, Beijing 100140 ,P.R.China
country: CN
phone: +86-10-66259626
fax-no: +86-10-66259626
e-mail: zhouxm@chinaunicom.cn
nic-hdl: XZ67-AP
mnt-by: MAINT-CNNIC-AP
last-modified: 2009-06-17T02:45:23Z
source: APNIC
% Information related to '116.128.0.0/10AS4837'
route: 116.128.0.0/10
descr: China Unicom CHINA169 Network
country: CN
origin: AS4837
mnt-by: MAINT-CNCGROUP-RR
last-modified: 2017-10-20T06:12:02Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.34 (WHOIS-AU4)
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 116.133.79.121
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19072
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;116.133.79.121. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025100702 1800 900 604800 86400
;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 08 09:05:10 CST 2025
;; MSG SIZE rcvd: 107
Host 121.79.133.116.in-addr.arpa not found: 2(SERVFAIL)
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server: 183.60.82.98
Address: 183.60.82.98#53
** server can't find 121.79.133.116.in-addr.arpa: SERVFAIL
IP | 类型 | 评论内容 | 时间 |
---|---|---|---|
210.112.232.6 | attackbots | Jun 14 03:17:57 web9 sshd\[11228\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.112.232.6 user=root Jun 14 03:17:58 web9 sshd\[11228\]: Failed password for root from 210.112.232.6 port 42793 ssh2 Jun 14 03:22:22 web9 sshd\[11780\]: Invalid user ubnt from 210.112.232.6 Jun 14 03:22:22 web9 sshd\[11780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.112.232.6 Jun 14 03:22:25 web9 sshd\[11780\]: Failed password for invalid user ubnt from 210.112.232.6 port 38824 ssh2 |
2020-06-15 03:58:47 |
110.54.157.2 | attackspambots | AbusiveCrawling |
2020-06-15 04:00:48 |
93.72.159.251 | attackbots | bruteforce detected |
2020-06-15 03:44:54 |
175.24.46.107 | attack | 2020-06-14T20:52:54.816710struts4.enskede.local sshd\[9958\]: Invalid user zhiying from 175.24.46.107 port 39608 2020-06-14T20:52:54.821208struts4.enskede.local sshd\[9958\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.46.107 2020-06-14T20:52:58.519179struts4.enskede.local sshd\[9958\]: Failed password for invalid user zhiying from 175.24.46.107 port 39608 ssh2 2020-06-14T21:01:10.412355struts4.enskede.local sshd\[10092\]: Invalid user postgres from 175.24.46.107 port 35674 2020-06-14T21:01:10.419009struts4.enskede.local sshd\[10092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.46.107 ... |
2020-06-15 03:34:55 |
206.81.12.209 | attackspam | 2020-06-14T10:47:00.190556morrigan.ad5gb.com sshd[16527]: Invalid user fpt from 206.81.12.209 port 48816 2020-06-14T10:47:02.074031morrigan.ad5gb.com sshd[16527]: Failed password for invalid user fpt from 206.81.12.209 port 48816 ssh2 2020-06-14T10:47:02.884453morrigan.ad5gb.com sshd[16527]: Disconnected from invalid user fpt 206.81.12.209 port 48816 [preauth] |
2020-06-15 03:37:02 |
159.65.219.210 | attack | Jun 14 20:46:48 pve1 sshd[17311]: Failed password for root from 159.65.219.210 port 32884 ssh2 ... |
2020-06-15 03:42:18 |
126.147.180.39 | spambotsattackproxynormal | 123456789 |
2020-06-15 03:47:51 |
134.122.72.221 | attack | Jun 14 16:55:55 localhost sshd\[8506\]: Invalid user terror from 134.122.72.221 Jun 14 16:55:55 localhost sshd\[8506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.72.221 Jun 14 16:55:57 localhost sshd\[8506\]: Failed password for invalid user terror from 134.122.72.221 port 59726 ssh2 Jun 14 16:59:20 localhost sshd\[8579\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.72.221 user=root Jun 14 16:59:22 localhost sshd\[8579\]: Failed password for root from 134.122.72.221 port 32812 ssh2 ... |
2020-06-15 03:35:53 |
175.161.26.16 | attackbots | reported through recidive - multiple failed attempts(SSH) |
2020-06-15 03:49:40 |
122.146.196.217 | attackspambots | Jun 14 14:44:03 sip sshd[646702]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.146.196.217 Jun 14 14:44:03 sip sshd[646702]: Invalid user abbery from 122.146.196.217 port 51550 Jun 14 14:44:05 sip sshd[646702]: Failed password for invalid user abbery from 122.146.196.217 port 51550 ssh2 ... |
2020-06-15 03:46:55 |
110.78.21.254 | attackspambots | bruteforce detected |
2020-06-15 04:04:42 |
113.255.76.253 | attackspambots | Jun 14 19:48:12 sip sshd[648721]: Failed password for invalid user mqm from 113.255.76.253 port 37258 ssh2 Jun 14 19:51:05 sip sshd[648780]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.255.76.253 user=root Jun 14 19:51:07 sip sshd[648780]: Failed password for root from 113.255.76.253 port 50292 ssh2 ... |
2020-06-15 04:13:31 |
222.186.175.202 | attackbotsspam | Jun 14 16:25:56 firewall sshd[6681]: Failed password for root from 222.186.175.202 port 61050 ssh2 Jun 14 16:25:59 firewall sshd[6681]: Failed password for root from 222.186.175.202 port 61050 ssh2 Jun 14 16:26:03 firewall sshd[6681]: Failed password for root from 222.186.175.202 port 61050 ssh2 ... |
2020-06-15 03:34:28 |
144.172.79.5 | attack | SSH Brute-Forcing (server1) |
2020-06-15 03:37:16 |
185.176.27.42 | attack | Jun 14 21:52:56 debian-2gb-nbg1-2 kernel: \[14423087.173188\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.42 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=14985 PROTO=TCP SPT=58546 DPT=10666 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-06-15 03:59:58 |