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

城市(city): unknown

省份(region): unknown

国家(country): Japan

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;180.50.121.145.			IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 23:40:01 CST 2025
;; MSG SIZE  rcvd: 107
HOST信息:
Host 145.121.50.180.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 145.121.50.180.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
51.158.167.187 attack
51.158.167.187 - - [03/Nov/2019:06:52:44 +0100] "POST /wp-login.php HTTP/1.1" 200 2112 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
51.158.167.187 - - [03/Nov/2019:06:52:44 +0100] "POST /wp-login.php HTTP/1.1" 200 2093 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-11-03 16:34:28
36.73.109.46 attackbots
445/tcp 445/tcp
[2019-11-01]2pkt
2019-11-03 16:48:54
139.198.5.79 attack
Nov  2 22:10:23 web1 sshd\[6812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79  user=root
Nov  2 22:10:25 web1 sshd\[6812\]: Failed password for root from 139.198.5.79 port 39794 ssh2
Nov  2 22:15:00 web1 sshd\[7208\]: Invalid user zenoss from 139.198.5.79
Nov  2 22:15:00 web1 sshd\[7208\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79
Nov  2 22:15:01 web1 sshd\[7208\]: Failed password for invalid user zenoss from 139.198.5.79 port 45170 ssh2
2019-11-03 16:34:57
159.224.158.39 attack
445/tcp 445/tcp
[2019-10-29/11-03]2pkt
2019-11-03 16:31:07
202.182.97.158 attack
Nov  2 15:52:45 nandi sshd[1174]: reveeclipse mapping checking getaddrinfo for 202.182.97.158.vultr.com [202.182.97.158] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov  2 15:52:45 nandi sshd[1174]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.182.97.158  user=r.r
Nov  2 15:52:47 nandi sshd[1174]: Failed password for r.r from 202.182.97.158 port 56082 ssh2
Nov  2 15:52:47 nandi sshd[1174]: Received disconnect from 202.182.97.158: 11: Bye Bye [preauth]
Nov  2 15:59:29 nandi sshd[6828]: reveeclipse mapping checking getaddrinfo for 202.182.97.158.vultr.com [202.182.97.158] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov  2 15:59:29 nandi sshd[6828]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.182.97.158  user=r.r
Nov  2 15:59:31 nandi sshd[6828]: Failed password for r.r from 202.182.97.158 port 48356 ssh2
Nov  2 15:59:31 nandi sshd[6828]: Received disconnect from 202.182.97.158: 11: Bye Bye [pre........
-------------------------------
2019-11-03 16:38:50
144.217.79.233 attackbots
SSH Brute-Force reported by Fail2Ban
2019-11-03 17:02:25
219.92.166.80 attackspambots
60001/tcp 60001/tcp
[2019-11-01/03]2pkt
2019-11-03 16:35:40
82.64.129.178 attackbots
Nov  3 08:38:22 server sshd\[26049\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82-64-129-178.subs.proxad.net  user=root
Nov  3 08:38:24 server sshd\[26049\]: Failed password for root from 82.64.129.178 port 42260 ssh2
Nov  3 08:51:36 server sshd\[29896\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82-64-129-178.subs.proxad.net  user=root
Nov  3 08:51:38 server sshd\[29896\]: Failed password for root from 82.64.129.178 port 47674 ssh2
Nov  3 08:55:22 server sshd\[31090\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82-64-129-178.subs.proxad.net  user=root
...
2019-11-03 16:55:34
118.24.28.39 attack
Nov  3 08:09:23 localhost sshd\[4945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.28.39  user=root
Nov  3 08:09:25 localhost sshd\[4945\]: Failed password for root from 118.24.28.39 port 40090 ssh2
Nov  3 08:15:10 localhost sshd\[5325\]: Invalid user jubar from 118.24.28.39
Nov  3 08:15:10 localhost sshd\[5325\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.28.39
Nov  3 08:15:12 localhost sshd\[5325\]: Failed password for invalid user jubar from 118.24.28.39 port 47844 ssh2
...
2019-11-03 16:58:43
134.209.17.42 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2019-11-03 16:54:53
46.38.144.17 attack
2019-11-03T09:34:44.181793mail01 postfix/smtpd[7533]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-03T09:34:51.149493mail01 postfix/smtpd[13046]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-03T09:35:08.056619mail01 postfix/smtpd[7533]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-03 16:36:45
103.55.91.51 attackspambots
Nov  3 06:52:12 lnxded63 sshd[31701]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.55.91.51
2019-11-03 17:00:13
106.51.33.29 attack
Invalid user bbaintelkam from 106.51.33.29 port 47188
2019-11-03 17:02:37
45.55.38.39 attackspam
Nov  3 06:52:54 dedicated sshd[7705]: Invalid user cn from 45.55.38.39 port 52965
2019-11-03 16:26:35
71.6.233.38 attack
4343/tcp 2004/tcp 4786/tcp...
[2019-09-04/11-03]4pkt,4pt.(tcp)
2019-11-03 16:29:46

最近上报的IP列表

93.44.242.15 122.81.182.209 58.77.225.12 67.86.2.25
233.20.118.15 67.222.222.56 62.202.139.85 63.46.134.100
65.131.1.166 60.116.71.204 154.1.38.131 212.72.117.137
34.49.1.249 139.159.176.35 206.186.145.56 171.134.209.127
141.150.59.186 205.85.246.177 104.118.254.43 173.178.72.145