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

城市(city): unknown

省份(region): unknown

国家(country): United States of America (the)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;149.26.50.170.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 03 16:36:27 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 170.50.26.149.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 170.50.26.149.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
162.200.232.63 attack
Feb  9 08:56:48 ns382633 sshd\[5088\]: Invalid user zme from 162.200.232.63 port 40828
Feb  9 08:56:48 ns382633 sshd\[5088\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.200.232.63
Feb  9 08:56:50 ns382633 sshd\[5088\]: Failed password for invalid user zme from 162.200.232.63 port 40828 ssh2
Feb  9 09:32:07 ns382633 sshd\[10956\]: Invalid user blh from 162.200.232.63 port 42174
Feb  9 09:32:07 ns382633 sshd\[10956\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.200.232.63
2020-02-09 17:16:50
119.42.74.247 attackspambots
Automatic report - Port Scan Attack
2020-02-09 17:39:12
192.3.67.107 attack
Feb  9 09:01:18 serwer sshd\[2830\]: Invalid user pus from 192.3.67.107 port 37980
Feb  9 09:01:18 serwer sshd\[2830\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.67.107
Feb  9 09:01:20 serwer sshd\[2830\]: Failed password for invalid user pus from 192.3.67.107 port 37980 ssh2
...
2020-02-09 17:26:06
96.9.152.95 attack
$f2bV_matches
2020-02-09 17:39:37
122.51.89.18 attackbotsspam
Feb  9 11:43:14 server sshd\[10397\]: Invalid user fvu from 122.51.89.18
Feb  9 11:43:14 server sshd\[10397\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.89.18 
Feb  9 11:43:16 server sshd\[10397\]: Failed password for invalid user fvu from 122.51.89.18 port 39340 ssh2
Feb  9 11:59:52 server sshd\[12842\]: Invalid user wbk from 122.51.89.18
Feb  9 11:59:52 server sshd\[12842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.89.18 
...
2020-02-09 17:37:44
103.59.132.202 attack
Feb  9 07:53:48 markkoudstaal sshd[26491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.59.132.202
Feb  9 07:53:50 markkoudstaal sshd[26491]: Failed password for invalid user eas from 103.59.132.202 port 37530 ssh2
Feb  9 07:55:36 markkoudstaal sshd[26797]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.59.132.202
2020-02-09 17:32:34
117.199.136.149 attackbotsspam
SS5,WP GET /wp-login.php
2020-02-09 17:32:15
171.228.10.21 attackspam
" "
2020-02-09 17:16:18
118.126.95.101 attackbotsspam
Feb  8 21:39:05 hpm sshd\[4879\]: Invalid user jsq from 118.126.95.101
Feb  8 21:39:05 hpm sshd\[4879\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.126.95.101
Feb  8 21:39:07 hpm sshd\[4879\]: Failed password for invalid user jsq from 118.126.95.101 port 57436 ssh2
Feb  8 21:49:01 hpm sshd\[6174\]: Invalid user tij from 118.126.95.101
Feb  8 21:49:01 hpm sshd\[6174\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.126.95.101
2020-02-09 17:26:53
190.96.172.101 attackspam
Automatic report - SSH Brute-Force Attack
2020-02-09 17:22:01
52.231.72.147 attack
Automatic report - SSH Brute-Force Attack
2020-02-09 17:29:21
62.171.131.123 attack
Feb  7 19:51:54 ovpn sshd[12956]: Did not receive identification string from 62.171.131.123
Feb  7 19:53:08 ovpn sshd[13245]: Invalid user postgres from 62.171.131.123
Feb  7 19:53:08 ovpn sshd[13245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.171.131.123
Feb  7 19:53:11 ovpn sshd[13245]: Failed password for invalid user postgres from 62.171.131.123 port 39736 ssh2
Feb  7 19:53:11 ovpn sshd[13245]: Received disconnect from 62.171.131.123 port 39736:11: Normal Shutdown, Thank you for playing [preauth]
Feb  7 19:53:11 ovpn sshd[13245]: Disconnected from 62.171.131.123 port 39736 [preauth]
Feb  7 19:53:25 ovpn sshd[13315]: Invalid user oracle from 62.171.131.123
Feb  7 19:53:25 ovpn sshd[13315]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.171.131.123
Feb  7 19:53:27 ovpn sshd[13315]: Failed password for invalid user oracle from 62.171.131.123 port 48394 ssh2

........
-----------------------------------------------
ht
2020-02-09 17:19:24
87.98.237.99 attack
Feb  9 09:48:53 amit sshd\[10411\]: Invalid user bck from 87.98.237.99
Feb  9 09:48:53 amit sshd\[10411\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.98.237.99
Feb  9 09:48:55 amit sshd\[10411\]: Failed password for invalid user bck from 87.98.237.99 port 50731 ssh2
...
2020-02-09 17:52:47
222.186.30.187 attack
Feb  9 10:11:14 MK-Soft-VM4 sshd[12985]: Failed password for root from 222.186.30.187 port 44972 ssh2
Feb  9 10:11:17 MK-Soft-VM4 sshd[12985]: Failed password for root from 222.186.30.187 port 44972 ssh2
...
2020-02-09 17:14:41
123.143.203.67 attackspam
ssh failed login
2020-02-09 17:41:58

最近上报的IP列表

9.136.160.251 195.151.229.233 7.178.15.130 6.168.96.185
84.66.54.31 161.68.23.200 95.54.204.130 228.254.177.230
53.206.190.8 125.218.13.211 174.159.40.2 127.29.255.152
181.141.25.74 171.214.73.249 63.72.54.35 213.13.188.197
196.186.35.138 108.20.200.144 51.25.233.195 13.203.135.167