必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): unknown

省份(region): unknown

国家(country): China

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 116.134.208.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20384
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;116.134.208.14.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025022802 1800 900 604800 86400

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 01 12:31:40 CST 2025
;; MSG SIZE  rcvd: 107
HOST信息:
Host 14.208.134.116.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 14.208.134.116.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
58.239.125.14 attackbots
Jun 18 13:05:55 vz239 sshd[19537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.239.125.14  user=r.r
Jun 18 13:05:57 vz239 sshd[19537]: Failed password for r.r from 58.239.125.14 port 33917 ssh2
Jun 18 13:05:59 vz239 sshd[19537]: Failed password for r.r from 58.239.125.14 port 33917 ssh2
Jun 18 13:06:02 vz239 sshd[19537]: Failed password for r.r from 58.239.125.14 port 33917 ssh2
Jun 18 13:06:04 vz239 sshd[19537]: Failed password for r.r from 58.239.125.14 port 33917 ssh2
Jun 18 13:06:07 vz239 sshd[19537]: Failed password for r.r from 58.239.125.14 port 33917 ssh2
Jun 18 13:06:09 vz239 sshd[19537]: Failed password for r.r from 58.239.125.14 port 33917 ssh2
Jun 18 13:06:09 vz239 sshd[19537]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.239.125.14  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=58.239.125.14
2019-06-21 21:44:58
218.22.186.115 attack
'IP reached maximum auth failures for a one day block'
2019-06-21 22:09:45
162.144.153.143 attackbotsspam
Jun 18 16:55:17 h2421860 postfix/postscreen[30929]: CONNECT from [162.144.153.143]:58182 to [85.214.119.52]:25
Jun 18 16:55:17 h2421860 postfix/dnsblog[30938]: addr 162.144.153.143 listed by domain dnsbl.sorbs.net as 127.0.0.6
Jun 18 16:55:17 h2421860 postfix/dnsblog[30931]: addr 162.144.153.143 listed by domain zen.spamhaus.org as 127.0.0.3
Jun 18 16:55:17 h2421860 postfix/dnsblog[30935]: addr 162.144.153.143 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jun 18 16:55:17 h2421860 postfix/dnsblog[30933]: addr 162.144.153.143 listed by domain bl.blocklist.de as 127.0.0.9
Jun 18 16:55:17 h2421860 postfix/dnsblog[30930]: addr 162.144.153.143 listed by domain Unknown.trblspam.com as 185.53.179.7
Jun 18 16:55:18 h2421860 postfix/dnsblog[30936]: addr 162.144.153.143 listed by domain b.barracudacentral.org as 127.0.0.2
Jun 18 16:55:23 h2421860 postfix/postscreen[30929]: DNSBL rank 9 for [162.144.153.143]:58182
Jun 18 16:55:23 h2421860 postfix/tlsproxy[30939]: CONNECT from [........
-------------------------------
2019-06-21 21:16:55
178.137.80.111 attackbotsspam
PHI,WP GET /wp-includes/wlwmanifest.xml
GET /blog/wp-includes/wlwmanifest.xml
GET /web/wp-includes/wlwmanifest.xml
GET /wordpress/wp-includes/wlwmanifest.xml
GET /website/wp-includes/wlwmanifest.xml
GET /wp/wp-includes/wlwmanifest.xml
GET /news/wp-includes/wlwmanifest.xml
GET /2015/wp-includes/wlwmanifest.xml
GET /2016/wp-includes/wlwmanifest.xml
GET /2017/wp-includes/wlwmanifest.xml
GET /2018/wp-includes/wlwmanifest.xml
GET /shop/wp-includes/wlwmanifest.xml
GET /wp1/wp-includes/wlwmanifest.xml
GET /test/wp-includes/wlwmanifest.xml
GET /media/wp-includes/wlwmanifest.xml
GET /wp2/wp-includes/wlwmanifest.xml
2019-06-21 21:13:44
210.212.210.83 attackspambots
Unauthorised access (Jun 21) SRC=210.212.210.83 LEN=52 TTL=116 ID=26615 DF TCP DPT=445 WINDOW=8192 SYN
2019-06-21 21:23:06
178.128.119.134 attackspambots
Jun 19 14:21:37 pi01 sshd[29930]: Connection from 178.128.119.134 port 54806 on 192.168.1.10 port 22
Jun 19 14:21:39 pi01 sshd[29930]: Invalid user discord from 178.128.119.134 port 54806
Jun 19 14:21:39 pi01 sshd[29930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.119.134
Jun 19 14:21:41 pi01 sshd[29930]: Failed password for invalid user discord from 178.128.119.134 port 54806 ssh2
Jun 19 14:21:41 pi01 sshd[29930]: Received disconnect from 178.128.119.134 port 54806:11: Bye Bye [preauth]
Jun 19 14:21:41 pi01 sshd[29930]: Disconnected from 178.128.119.134 port 54806 [preauth]
Jun 19 14:25:58 pi01 sshd[30027]: Connection from 178.128.119.134 port 41658 on 192.168.1.10 port 22
Jun 19 14:25:59 pi01 sshd[30027]: Invalid user kong from 178.128.119.134 port 41658
Jun 19 14:25:59 pi01 sshd[30027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.119.134
Jun 19 14:26:01 pi01 sshd[........
-------------------------------
2019-06-21 21:09:58
183.83.42.182 attack
445/tcp
[2019-06-21]1pkt
2019-06-21 21:16:20
162.243.133.126 attackspambots
21.06.2019 09:14:15 Connection to port 161 blocked by firewall
2019-06-21 22:03:18
220.118.124.195 attackbotsspam
Jun 21 12:36:21 ns3042688 proftpd\[6077\]: 127.0.0.1 \(220.118.124.195\[220.118.124.195\]\) - USER anonymous: no such user found from 220.118.124.195 \[220.118.124.195\] to 51.254.197.112:21
Jun 21 12:36:25 ns3042688 proftpd\[6118\]: 127.0.0.1 \(220.118.124.195\[220.118.124.195\]\) - USER www: no such user found from 220.118.124.195 \[220.118.124.195\] to 51.254.197.112:21
Jun 21 12:36:27 ns3042688 proftpd\[6135\]: 127.0.0.1 \(220.118.124.195\[220.118.124.195\]\) - USER www: no such user found from 220.118.124.195 \[220.118.124.195\] to 51.254.197.112:21
Jun 21 12:36:31 ns3042688 proftpd\[6157\]: 127.0.0.1 \(220.118.124.195\[220.118.124.195\]\) - USER cesumin \(Login failed\): Incorrect password
Jun 21 12:36:36 ns3042688 proftpd\[6207\]: 127.0.0.1 \(220.118.124.195\[220.118.124.195\]\) - USER cesumin \(Login failed\): Incorrect password
...
2019-06-21 21:48:32
221.203.125.212 attack
5500/tcp
[2019-06-21]1pkt
2019-06-21 22:04:29
182.254.230.122 attack
19/6/21@05:13:59: FAIL: Alarm-Intrusion address from=182.254.230.122
...
2019-06-21 21:31:13
106.12.205.48 attack
Jun 21 12:36:35 yabzik sshd[19362]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.205.48
Jun 21 12:36:36 yabzik sshd[19362]: Failed password for invalid user jenkins from 106.12.205.48 port 56084 ssh2
Jun 21 12:38:07 yabzik sshd[19932]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.205.48
2019-06-21 21:44:16
112.112.7.202 attackspambots
Jun 21 09:14:07 Tower sshd[41138]: Connection from 112.112.7.202 port 49940 on 192.168.10.220 port 22
Jun 21 09:14:09 Tower sshd[41138]: Invalid user sang from 112.112.7.202 port 49940
Jun 21 09:14:09 Tower sshd[41138]: error: Could not get shadow information for NOUSER
Jun 21 09:14:09 Tower sshd[41138]: Failed password for invalid user sang from 112.112.7.202 port 49940 ssh2
Jun 21 09:14:09 Tower sshd[41138]: Received disconnect from 112.112.7.202 port 49940:11: Bye Bye [preauth]
Jun 21 09:14:09 Tower sshd[41138]: Disconnected from invalid user sang 112.112.7.202 port 49940 [preauth]
2019-06-21 22:17:31
123.16.140.255 attackspam
445/tcp
[2019-06-21]1pkt
2019-06-21 21:10:29
36.72.218.97 attackspambots
8080/tcp
[2019-06-21]1pkt
2019-06-21 21:27:44

最近上报的IP列表

59.179.28.203 226.64.236.75 82.42.68.123 72.182.69.176
170.113.155.247 225.165.157.90 243.64.124.108 175.232.132.200
87.33.26.207 26.40.51.73 160.70.4.131 88.225.174.65
91.127.255.97 29.127.21.165 37.122.83.191 62.20.143.88
126.210.116.155 122.22.249.168 207.12.42.219 59.20.100.186