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

城市(city): unknown

省份(region): unknown

国家(country): unknown

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;138.122.120.241.		IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:23:30 CST 2022
;; MSG SIZE  rcvd: 108
HOST信息:
Host 241.120.122.138.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 241.120.122.138.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
187.174.169.110 attack
Dec  1 07:30:32 vmd17057 sshd\[4911\]: Invalid user burlon from 187.174.169.110 port 56098
Dec  1 07:30:32 vmd17057 sshd\[4911\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.174.169.110
Dec  1 07:30:34 vmd17057 sshd\[4911\]: Failed password for invalid user burlon from 187.174.169.110 port 56098 ssh2
...
2019-12-01 15:15:56
218.92.0.133 attack
2019-12-01T08:02:11.1519531240 sshd\[8865\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.133  user=root
2019-12-01T08:02:13.2947431240 sshd\[8865\]: Failed password for root from 218.92.0.133 port 40933 ssh2
2019-12-01T08:02:16.4462251240 sshd\[8865\]: Failed password for root from 218.92.0.133 port 40933 ssh2
...
2019-12-01 15:12:33
154.221.24.135 attackspambots
Nov 30 20:56:25 php1 sshd\[20716\]: Invalid user nexus from 154.221.24.135
Nov 30 20:56:25 php1 sshd\[20716\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.221.24.135
Nov 30 20:56:27 php1 sshd\[20716\]: Failed password for invalid user nexus from 154.221.24.135 port 56976 ssh2
Nov 30 20:59:29 php1 sshd\[20958\]: Invalid user pizza from 154.221.24.135
Nov 30 20:59:29 php1 sshd\[20958\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.221.24.135
2019-12-01 15:06:14
218.92.0.170 attackbots
Dec  1 10:00:09 server sshd\[746\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.170  user=root
Dec  1 10:00:09 server sshd\[615\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.170  user=root
Dec  1 10:00:10 server sshd\[709\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.170  user=root
Dec  1 10:00:11 server sshd\[746\]: Failed password for root from 218.92.0.170 port 56128 ssh2
Dec  1 10:00:11 server sshd\[615\]: Failed password for root from 218.92.0.170 port 4102 ssh2
...
2019-12-01 15:01:07
198.12.149.7 attackbots
Looking for resource vulnerabilities
2019-12-01 15:13:52
164.132.80.137 attack
2019-12-01T07:27:28.395976vps751288.ovh.net sshd\[19049\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137  user=root
2019-12-01T07:27:29.912009vps751288.ovh.net sshd\[19049\]: Failed password for root from 164.132.80.137 port 36804 ssh2
2019-12-01T07:30:09.069957vps751288.ovh.net sshd\[19057\]: Invalid user ethereal from 164.132.80.137 port 43384
2019-12-01T07:30:09.077325vps751288.ovh.net sshd\[19057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
2019-12-01T07:30:11.029688vps751288.ovh.net sshd\[19057\]: Failed password for invalid user ethereal from 164.132.80.137 port 43384 ssh2
2019-12-01 15:18:17
112.85.42.173 attackbotsspam
Dec  1 08:05:54 dcd-gentoo sshd[30193]: User root from 112.85.42.173 not allowed because none of user's groups are listed in AllowGroups
Dec  1 08:05:57 dcd-gentoo sshd[30193]: error: PAM: Authentication failure for illegal user root from 112.85.42.173
Dec  1 08:05:54 dcd-gentoo sshd[30193]: User root from 112.85.42.173 not allowed because none of user's groups are listed in AllowGroups
Dec  1 08:05:57 dcd-gentoo sshd[30193]: error: PAM: Authentication failure for illegal user root from 112.85.42.173
Dec  1 08:05:54 dcd-gentoo sshd[30193]: User root from 112.85.42.173 not allowed because none of user's groups are listed in AllowGroups
Dec  1 08:05:57 dcd-gentoo sshd[30193]: error: PAM: Authentication failure for illegal user root from 112.85.42.173
Dec  1 08:05:57 dcd-gentoo sshd[30193]: Failed keyboard-interactive/pam for invalid user root from 112.85.42.173 port 59052 ssh2
...
2019-12-01 15:07:41
171.212.109.159 attackspam
[portscan] Port scan
2019-12-01 15:35:31
14.232.78.123 attack
Dec  1 07:18:06 xeon postfix/smtpd[58143]: warning: unknown[14.232.78.123]: SASL PLAIN authentication failed: authentication failure
2019-12-01 15:34:33
91.11.70.81 attack
MYH,DEF GET /phpmyadmin/
2019-12-01 15:24:12
175.158.209.154 attackbotsspam
badbot
2019-12-01 15:04:13
201.99.120.13 attack
Automatic report - SSH Brute-Force Attack
2019-12-01 15:13:26
222.186.169.194 attackbots
Dec  1 08:08:03 vmanager6029 sshd\[12292\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194  user=root
Dec  1 08:08:05 vmanager6029 sshd\[12292\]: Failed password for root from 222.186.169.194 port 36644 ssh2
Dec  1 08:08:08 vmanager6029 sshd\[12292\]: Failed password for root from 222.186.169.194 port 36644 ssh2
2019-12-01 15:11:44
179.107.131.0 attackspambots
SpamReport
2019-12-01 15:17:48
159.203.111.100 attackspambots
Dec  1 08:04:51 dedicated sshd[18783]: Invalid user totoidc from 159.203.111.100 port 43131
2019-12-01 15:19:07

最近上报的IP列表

138.122.120.237 138.122.120.213 138.122.120.146 138.122.121.150
138.122.120.143 138.122.120.244 118.174.70.144 138.122.120.99
138.122.121.70 138.122.121.159 138.122.121.47 138.122.121.36
138.122.123.138 138.122.123.186 138.122.123.196 138.122.123.198
138.122.123.194 138.122.123.10 138.122.123.20 138.122.123.157