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

城市(city): unknown

省份(region): unknown

国家(country): IANA Special-Purpose Address

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;245.85.99.140.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 08:16:22 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 140.99.85.245.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 140.99.85.245.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
121.206.49.9 attack
Jul  2 09:24:42 eola postfix/smtpd[20657]: warning: hostname 9.49.206.121.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 121.206.49.9: Name or service not known
Jul  2 09:24:42 eola postfix/smtpd[20657]: connect from unknown[121.206.49.9]
Jul  2 09:24:42 eola postfix/smtpd[20659]: warning: hostname 9.49.206.121.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 121.206.49.9: Name or service not known
Jul  2 09:24:42 eola postfix/smtpd[20659]: connect from unknown[121.206.49.9]
Jul  2 09:24:45 eola postfix/smtpd[20659]: lost connection after AUTH from unknown[121.206.49.9]
Jul  2 09:24:45 eola postfix/smtpd[20659]: disconnect from unknown[121.206.49.9] ehlo=1 auth=0/1 commands=1/2
Jul  2 09:24:46 eola postfix/smtpd[20659]: warning: hostname 9.49.206.121.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 121.206.49.9: Name or service not known
Jul  2 09:24:46 eola postfix/smtpd[20659]: connect from unknown[121.206.49.9]
Jul  2 09:24........
-------------------------------
2019-07-03 03:47:32
189.161.156.173 attack
Jan 12 09:31:12 motanud sshd\[11725\]: Invalid user minecraft from 189.161.156.173 port 44786
Jan 12 09:31:12 motanud sshd\[11725\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.161.156.173
Jan 12 09:31:14 motanud sshd\[11725\]: Failed password for invalid user minecraft from 189.161.156.173 port 44786 ssh2
2019-07-03 03:02:20
189.135.164.174 attackbots
Jan 19 01:03:31 motanud sshd\[30270\]: Invalid user police from 189.135.164.174 port 50534
Jan 19 01:03:31 motanud sshd\[30270\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.135.164.174
Jan 19 01:03:34 motanud sshd\[30270\]: Failed password for invalid user police from 189.135.164.174 port 50534 ssh2
2019-07-03 03:16:30
125.64.94.211 attackbotsspam
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-07-03 03:46:57
47.52.93.9 attackspam
port scan and connect, tcp 80 (http)
2019-07-03 03:46:28
189.155.247.162 attackbotsspam
Jan  5 10:44:49 motanud sshd\[5601\]: Invalid user elastic from 189.155.247.162 port 37302
Jan  5 10:44:49 motanud sshd\[5601\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.155.247.162
Jan  5 10:44:51 motanud sshd\[5601\]: Failed password for invalid user elastic from 189.155.247.162 port 37302 ssh2
2019-07-03 03:06:09
128.199.212.232 attackspambots
Automatic report - Web App Attack
2019-07-03 03:22:16
194.50.254.227 attackspambots
1562075002 - 07/02/2019 20:43:22 Host: 194.50.254.227/194.50.254.227 Port: 23 TCP Blocked
...
2019-07-03 03:02:38
87.66.95.135 attackbotsspam
DATE:2019-07-02 19:48:28, IP:87.66.95.135, PORT:ssh SSH brute force auth (ermes)
2019-07-03 03:41:06
34.77.51.253 attack
Automatic report - Web App Attack
2019-07-03 03:34:17
85.84.209.164 attack
Hit on /wp-login.php
2019-07-03 03:17:28
209.250.237.72 attack
Jul  2 13:40:24 xxxxxxx7446550 sshd[896]: Did not receive identification string from 209.250.237.72
Jul  2 13:42:36 xxxxxxx7446550 sshd[1366]: reveeclipse mapping checking getaddrinfo for 209.250.237.72.vultr.com [209.250.237.72] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul  2 13:42:36 xxxxxxx7446550 sshd[1366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.250.237.72  user=r.r
Jul  2 13:42:38 xxxxxxx7446550 sshd[1366]: Failed password for r.r from 209.250.237.72 port 39347 ssh2
Jul  2 13:42:38 xxxxxxx7446550 sshd[1367]: Received disconnect from 209.250.237.72: 11: Bye Bye
Jul  2 13:43:29 xxxxxxx7446550 sshd[1689]: reveeclipse mapping checking getaddrinfo for 209.250.237.72.vultr.com [209.250.237.72] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul  2 13:43:29 xxxxxxx7446550 sshd[1689]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.250.237.72  user=r.r
Jul  2 13:43:32 xxxxxxx7446550 sshd[1689]........
-------------------------------
2019-07-03 03:45:12
113.204.16.94 attackbotsspam
Jul  2 20:26:22 tux-35-217 sshd\[28109\]: Invalid user kuai from 113.204.16.94 port 42783
Jul  2 20:26:22 tux-35-217 sshd\[28109\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.204.16.94
Jul  2 20:26:25 tux-35-217 sshd\[28109\]: Failed password for invalid user kuai from 113.204.16.94 port 42783 ssh2
Jul  2 20:29:04 tux-35-217 sshd\[28117\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.204.16.94  user=mail
...
2019-07-03 03:40:12
171.243.34.221 attack
445/tcp
[2019-07-02]1pkt
2019-07-03 03:32:20
78.167.155.4 attack
37215/tcp
[2019-07-02]1pkt
2019-07-03 03:14:31

最近上报的IP列表

24.116.61.123 146.89.41.2 170.96.76.118 88.123.86.19
40.236.146.88 185.172.176.216 81.0.243.12 185.160.185.50
247.179.152.82 92.189.234.51 47.109.135.177 209.76.142.89
22.175.207.61 77.122.133.212 225.212.114.134 92.240.68.136
217.201.191.87 245.170.142.34 132.32.145.241 56.19.196.108