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

城市(city): Heiwajima

省份(region): Tokyo

国家(country): Japan

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;139.180.207.160.		IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:13:44 CST 2022
;; MSG SIZE  rcvd: 108
HOST信息:
160.207.180.139.in-addr.arpa domain name pointer 139.180.207.160.vultr.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
160.207.180.139.in-addr.arpa	name = 139.180.207.160.vultr.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
36.255.87.152 attackspam
Attempts against non-existent wp-login
2020-07-23 21:18:31
51.79.82.137 attackbots
51.79.82.137 - - [23/Jul/2020:14:03:01 +0200] "GET /wp-login.php HTTP/1.1" 200 5738 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
51.79.82.137 - - [23/Jul/2020:14:03:02 +0200] "POST /wp-login.php HTTP/1.1" 200 5989 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
51.79.82.137 - - [23/Jul/2020:14:03:03 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-07-23 21:15:14
85.14.242.76 attack
RDP brute forcing (r)
2020-07-23 21:20:12
181.129.14.218 attackspambots
Jul 23 12:43:42 vps-51d81928 sshd[61450]: Invalid user sysop from 181.129.14.218 port 5819
Jul 23 12:43:42 vps-51d81928 sshd[61450]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.129.14.218 
Jul 23 12:43:42 vps-51d81928 sshd[61450]: Invalid user sysop from 181.129.14.218 port 5819
Jul 23 12:43:44 vps-51d81928 sshd[61450]: Failed password for invalid user sysop from 181.129.14.218 port 5819 ssh2
Jul 23 12:48:02 vps-51d81928 sshd[61571]: Invalid user puja from 181.129.14.218 port 37220
...
2020-07-23 21:00:15
93.115.1.195 attack
Jul 23 17:30:23 gw1 sshd[7855]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.115.1.195
Jul 23 17:30:25 gw1 sshd[7855]: Failed password for invalid user git from 93.115.1.195 port 57810 ssh2
...
2020-07-23 20:40:41
180.126.228.63 attackspam
20 attempts against mh-ssh on seed
2020-07-23 21:19:16
206.189.138.99 attackspambots
Jul 23 12:45:27 vlre-nyc-1 sshd\[29858\]: Invalid user line from 206.189.138.99
Jul 23 12:45:27 vlre-nyc-1 sshd\[29858\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.138.99
Jul 23 12:45:29 vlre-nyc-1 sshd\[29858\]: Failed password for invalid user line from 206.189.138.99 port 40110 ssh2
Jul 23 12:50:06 vlre-nyc-1 sshd\[29979\]: Invalid user gitblit from 206.189.138.99
Jul 23 12:50:06 vlre-nyc-1 sshd\[29979\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.138.99
...
2020-07-23 21:10:03
134.122.96.20 attackspambots
2020-07-23T12:59:37.753645shield sshd\[12774\]: Invalid user postgres from 134.122.96.20 port 51346
2020-07-23T12:59:37.761576shield sshd\[12774\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.96.20
2020-07-23T12:59:39.636770shield sshd\[12774\]: Failed password for invalid user postgres from 134.122.96.20 port 51346 ssh2
2020-07-23T13:03:36.819503shield sshd\[13647\]: Invalid user testuser from 134.122.96.20 port 59350
2020-07-23T13:03:36.828014shield sshd\[13647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.96.20
2020-07-23 21:10:24
192.35.168.201 attack
Unauthorized connection attempt detected from IP address 192.35.168.201 to port 9132
2020-07-23 20:56:08
222.186.180.223 attackspam
Jul 23 15:09:56 vps sshd[226394]: Failed password for root from 222.186.180.223 port 7250 ssh2
Jul 23 15:09:59 vps sshd[226394]: Failed password for root from 222.186.180.223 port 7250 ssh2
Jul 23 15:10:03 vps sshd[226394]: Failed password for root from 222.186.180.223 port 7250 ssh2
Jul 23 15:10:06 vps sshd[226394]: Failed password for root from 222.186.180.223 port 7250 ssh2
Jul 23 15:10:09 vps sshd[226394]: Failed password for root from 222.186.180.223 port 7250 ssh2
...
2020-07-23 21:13:25
139.59.58.155 attackspambots
Jul 23 12:32:28 rush sshd[12842]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.58.155
Jul 23 12:32:29 rush sshd[12842]: Failed password for invalid user laurie from 139.59.58.155 port 47078 ssh2
Jul 23 12:39:59 rush sshd[12977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.58.155
...
2020-07-23 20:59:44
49.235.196.250 attackspam
Jul 23 14:34:16 ns381471 sshd[3415]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.196.250
Jul 23 14:34:18 ns381471 sshd[3415]: Failed password for invalid user qcluster from 49.235.196.250 port 61038 ssh2
2020-07-23 21:13:37
190.145.254.138 attackspam
20 attempts against mh-ssh on echoip
2020-07-23 21:11:13
198.98.59.29 attackbotsspam
Jul 23 14:03:03 host sshd[27583]: Invalid user username from 198.98.59.29 port 55871
...
2020-07-23 21:13:52
185.153.196.2 attackbots
Port scan: Attack repeated for 24 hours
2020-07-23 20:59:30

最近上报的IP列表

139.180.205.210 139.180.206.122 118.238.236.43 139.180.207.9
139.180.207.63 139.180.207.80 139.180.206.110 139.180.208.122
139.180.207.53 139.180.205.182 139.180.207.225 139.180.205.35
118.238.236.56 139.180.208.158 139.180.208.173 139.180.208.240
139.180.208.58 139.180.208.68 139.180.208.32 139.180.208.55