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

城市(city): unknown

省份(region): unknown

国家(country): None

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;116.126.106.2.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 04:49:13 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
Host 2.106.126.116.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 2.106.126.116.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
84.17.46.246 attack
"GET /wp-includes/wlwmanifest.xml HTTP/1.1" 404
"GET /xmlrpc.php?rsd HTTP/1.1" 403
"GET /blog/wp-includes/wlwmanifest.xml HTTP/1.1" 404
"GET /wordpress/wp-includes/wlwmanifest.xml HTTP/1.1" 404
"GET /wp/wp-includes/wlwmanifest.xml HTTP/1.1" 404
"GET /site/wp-includes/wlwmanifest.xml HTTP/1.1" 404
"GET /cms/wp-includes/wlwmanifest.xml HTTP/1.1" 404
2020-04-16 06:06:59
182.242.143.78 attackbotsspam
Apr 16 00:01:04 ns382633 sshd\[21561\]: Invalid user gmodserver from 182.242.143.78 port 41206
Apr 16 00:01:04 ns382633 sshd\[21561\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.242.143.78
Apr 16 00:01:05 ns382633 sshd\[21561\]: Failed password for invalid user gmodserver from 182.242.143.78 port 41206 ssh2
Apr 16 00:22:30 ns382633 sshd\[25222\]: Invalid user es from 182.242.143.78 port 40376
Apr 16 00:22:30 ns382633 sshd\[25222\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.242.143.78
2020-04-16 06:23:11
191.8.91.89 attack
SSH Invalid Login
2020-04-16 06:26:31
51.91.140.218 attackbots
Apr 16 00:58:20 ift sshd\[58597\]: Failed password for root from 51.91.140.218 port 35760 ssh2Apr 16 00:58:58 ift sshd\[58625\]: Failed password for root from 51.91.140.218 port 40560 ssh2Apr 16 00:59:36 ift sshd\[58632\]: Failed password for root from 51.91.140.218 port 45424 ssh2Apr 16 01:00:13 ift sshd\[58951\]: Failed password for root from 51.91.140.218 port 50334 ssh2Apr 16 01:00:48 ift sshd\[59067\]: Failed password for root from 51.91.140.218 port 55030 ssh2
...
2020-04-16 06:04:26
87.236.212.42 attackspambots
(sshd) Failed SSH login from 87.236.212.42 (GB/United Kingdom/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 15 22:20:27 amsweb01 sshd[17937]: Invalid user postgres from 87.236.212.42 port 45104
Apr 15 22:20:29 amsweb01 sshd[17937]: Failed password for invalid user postgres from 87.236.212.42 port 45104 ssh2
Apr 15 22:50:20 amsweb01 sshd[21701]: Invalid user postgresql from 87.236.212.42 port 42612
Apr 15 22:50:21 amsweb01 sshd[21701]: Failed password for invalid user postgresql from 87.236.212.42 port 42612 ssh2
Apr 15 23:06:54 amsweb01 sshd[23728]: Invalid user rust from 87.236.212.42 port 50462
2020-04-16 06:16:01
185.151.242.186 attack
Port Scan: Events[4] countPorts[4]: 10000 33389 50001 33899 ..
2020-04-16 05:56:55
217.182.71.54 attackbotsspam
Invalid user asterisk from 217.182.71.54 port 58306
2020-04-16 06:11:07
119.96.208.40 attackbotsspam
Apr 15 23:47:38 vpn01 sshd[9651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.96.208.40
Apr 15 23:47:40 vpn01 sshd[9651]: Failed password for invalid user leon from 119.96.208.40 port 33058 ssh2
...
2020-04-16 06:19:21
128.199.169.102 attackspambots
2020-04-15T21:54:43.846449shield sshd\[8146\]: Invalid user ftpuser from 128.199.169.102 port 57974
2020-04-15T21:54:43.849730shield sshd\[8146\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.169.102
2020-04-15T21:54:45.684632shield sshd\[8146\]: Failed password for invalid user ftpuser from 128.199.169.102 port 57974 ssh2
2020-04-15T21:58:40.568824shield sshd\[9339\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.169.102  user=root
2020-04-15T21:58:42.604701shield sshd\[9339\]: Failed password for root from 128.199.169.102 port 56807 ssh2
2020-04-16 06:29:05
183.89.211.57 attack
IMAP brute force
...
2020-04-16 06:26:17
124.156.214.11 attack
SSH bruteforce
2020-04-16 06:01:18
14.161.36.150 attackbots
Invalid user firefart from 14.161.36.150 port 50784
2020-04-16 06:13:22
218.92.0.212 attackbotsspam
Apr 15 23:56:54 legacy sshd[14701]: Failed password for root from 218.92.0.212 port 60779 ssh2
Apr 15 23:57:07 legacy sshd[14701]: error: maximum authentication attempts exceeded for root from 218.92.0.212 port 60779 ssh2 [preauth]
Apr 15 23:57:18 legacy sshd[14707]: Failed password for root from 218.92.0.212 port 34869 ssh2
...
2020-04-16 06:22:13
93.171.5.244 attackspambots
Port Scan: Events[1] countPorts[1]: 8182 ..
2020-04-16 06:21:32
61.133.232.250 attack
Apr 15 22:45:54 srv01 sshd[22877]: Invalid user ultimate from 61.133.232.250 port 17029
Apr 15 22:45:54 srv01 sshd[22877]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.232.250
Apr 15 22:45:54 srv01 sshd[22877]: Invalid user ultimate from 61.133.232.250 port 17029
Apr 15 22:45:56 srv01 sshd[22877]: Failed password for invalid user ultimate from 61.133.232.250 port 17029 ssh2
Apr 15 22:48:40 srv01 sshd[23007]: Invalid user nagios from 61.133.232.250 port 40702
...
2020-04-16 06:32:19

最近上报的IP列表

116.62.191.162 116.140.13.129 116.125.140.18 116.62.191.186
116.62.193.16 116.62.193.62 116.62.194.248 116.62.195.142
116.62.196.146 116.62.198.43 116.62.199.207 116.62.199.223
116.17.102.112 116.17.100.79 116.169.3.28 116.17.102.104
116.168.75.34 116.163.52.249 116.17.102.116 116.17.185.100