必须是合法有效的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 <<>> 219.213.198.140
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44883
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;219.213.198.140.		IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 10:14:25 CST 2025
;; MSG SIZE  rcvd: 108
HOST信息:
140.198.213.219.in-addr.arpa domain name pointer softbank219213198140.bbtec.net.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
140.198.213.219.in-addr.arpa	name = softbank219213198140.bbtec.net.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
119.10.58.58 attackbotsspam
May 19 22:09:48 server sshd\[233516\]: Invalid user hy from 119.10.58.58
May 19 22:09:48 server sshd\[233516\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.10.58.58
May 19 22:09:50 server sshd\[233516\]: Failed password for invalid user hy from 119.10.58.58 port 54091 ssh2
...
2019-07-17 09:17:56
119.130.105.124 attack
May 17 00:50:14 server sshd\[94798\]: Invalid user admin from 119.130.105.124
May 17 00:50:14 server sshd\[94798\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.130.105.124
May 17 00:50:16 server sshd\[94798\]: Failed password for invalid user admin from 119.130.105.124 port 41764 ssh2
...
2019-07-17 09:15:15
119.254.94.73 attackbots
May  6 15:35:10 server sshd\[159419\]: Invalid user admin from 119.254.94.73
May  6 15:35:10 server sshd\[159419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.254.94.73
May  6 15:35:12 server sshd\[159419\]: Failed password for invalid user admin from 119.254.94.73 port 34568 ssh2
...
2019-07-17 08:56:49
46.40.220.225 attack
Automatic report - Port Scan Attack
2019-07-17 08:50:21
213.183.101.89 attackbots
Jul 17 02:57:53 giegler sshd[13591]: Invalid user sav from 213.183.101.89 port 45494
2019-07-17 09:04:20
119.226.21.114 attackbotsspam
fraudulent SSH attempt
2019-07-17 09:00:09
189.34.32.234 attack
Jul 16 22:56:22 mxgate1 postfix/postscreen[26624]: CONNECT from [189.34.32.234]:36870 to [176.31.12.44]:25
Jul 16 22:56:22 mxgate1 postfix/dnsblog[26762]: addr 189.34.32.234 listed by domain zen.spamhaus.org as 127.0.0.4
Jul 16 22:56:22 mxgate1 postfix/dnsblog[26762]: addr 189.34.32.234 listed by domain zen.spamhaus.org as 127.0.0.11
Jul 16 22:56:22 mxgate1 postfix/dnsblog[26763]: addr 189.34.32.234 listed by domain cbl.abuseat.org as 127.0.0.2
Jul 16 22:56:22 mxgate1 postfix/dnsblog[26759]: addr 189.34.32.234 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul 16 22:56:22 mxgate1 postfix/dnsblog[26760]: addr 189.34.32.234 listed by domain b.barracudacentral.org as 127.0.0.2
Jul 16 22:56:23 mxgate1 postfix/dnsblog[26761]: addr 189.34.32.234 listed by domain bl.spamcop.net as 127.0.0.2
Jul 16 22:56:28 mxgate1 postfix/postscreen[26624]: DNSBL rank 6 for [189.34.32.234]:36870
Jul x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=189.34.32.234
2019-07-17 09:23:44
153.36.236.234 attackbotsspam
Jul 17 03:22:15 minden010 sshd[8935]: Failed password for root from 153.36.236.234 port 14294 ssh2
Jul 17 03:22:17 minden010 sshd[8935]: Failed password for root from 153.36.236.234 port 14294 ssh2
Jul 17 03:22:19 minden010 sshd[8935]: Failed password for root from 153.36.236.234 port 14294 ssh2
...
2019-07-17 09:28:26
174.103.158.175 attackbots
The only information I have is the user BKANE was attempting to brute force into one of my SQL servers to attempt to steal a database. When this attempt did not work, he resorted to a lowly DDOS attempt.
2019-07-17 08:58:43
119.165.53.234 attack
Apr 11 14:25:27 server sshd\[118629\]: Invalid user admin from 119.165.53.234
Apr 11 14:25:27 server sshd\[118629\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.165.53.234
Apr 11 14:25:29 server sshd\[118629\]: Failed password for invalid user admin from 119.165.53.234 port 37843 ssh2
...
2019-07-17 09:12:53
119.254.100.209 attack
Apr 29 23:20:32 server sshd\[127912\]: Invalid user internet from 119.254.100.209
Apr 29 23:20:32 server sshd\[127912\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.254.100.209
Apr 29 23:20:35 server sshd\[127912\]: Failed password for invalid user internet from 119.254.100.209 port 58804 ssh2
...
2019-07-17 08:59:16
119.123.242.250 attackspambots
Jul 12 23:52:55 server sshd\[203791\]: Invalid user osm from 119.123.242.250
Jul 12 23:52:55 server sshd\[203791\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.242.250
Jul 12 23:52:57 server sshd\[203791\]: Failed password for invalid user osm from 119.123.242.250 port 46208 ssh2
...
2019-07-17 09:15:44
119.201.109.155 attackspambots
Jun 24 07:31:25 server sshd\[65593\]: Invalid user bolognesi from 119.201.109.155
Jun 24 07:31:25 server sshd\[65593\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.201.109.155
Jun 24 07:31:27 server sshd\[65593\]: Failed password for invalid user bolognesi from 119.201.109.155 port 54674 ssh2
...
2019-07-17 09:06:25
104.37.216.112 attackbots
Jul 17 00:06:36 server2 sshd\[29214\]: User root from 104.37.216.112 not allowed because not listed in AllowUsers
Jul 17 00:06:37 server2 sshd\[29216\]: Invalid user DUP from 104.37.216.112
Jul 17 00:06:38 server2 sshd\[29218\]: User root from 104.37.216.112 not allowed because not listed in AllowUsers
Jul 17 00:06:39 server2 sshd\[29221\]: User root from 104.37.216.112 not allowed because not listed in AllowUsers
Jul 17 00:06:40 server2 sshd\[29223\]: User root from 104.37.216.112 not allowed because not listed in AllowUsers
Jul 17 00:06:41 server2 sshd\[29227\]: User root from 104.37.216.112 not allowed because not listed in AllowUsers
2019-07-17 09:35:19
200.71.55.143 attackbots
Jul 17 02:34:40 legacy sshd[8842]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.71.55.143
Jul 17 02:34:42 legacy sshd[8842]: Failed password for invalid user ops from 200.71.55.143 port 60315 ssh2
Jul 17 02:40:10 legacy sshd[8977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.71.55.143
...
2019-07-17 08:55:56

最近上报的IP列表

223.94.3.255 176.89.130.3 90.34.5.171 205.104.130.198
22.72.212.37 206.188.115.119 29.206.175.206 249.189.202.240
116.161.74.106 240.116.8.0 119.0.141.161 46.44.185.113
117.19.226.245 214.9.225.116 201.74.62.21 149.66.237.79
52.175.168.219 52.80.238.252 175.194.45.217 175.171.25.164