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

;; QUESTION SECTION:
;220.29.21.42.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 05:39:32 CST 2025
;; MSG SIZE  rcvd: 105
HOST信息:
42.21.29.220.in-addr.arpa domain name pointer softbank220029021042.bbtec.net.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.21.29.220.in-addr.arpa	name = softbank220029021042.bbtec.net.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
54.39.22.191 attackbots
2020-04-08T07:13:06.805971struts4.enskede.local sshd\[23132\]: Invalid user lia from 54.39.22.191 port 33744
2020-04-08T07:13:06.813492struts4.enskede.local sshd\[23132\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.22.191
2020-04-08T07:13:09.395019struts4.enskede.local sshd\[23132\]: Failed password for invalid user lia from 54.39.22.191 port 33744 ssh2
2020-04-08T07:18:29.220631struts4.enskede.local sshd\[23286\]: Invalid user user from 54.39.22.191 port 57608
2020-04-08T07:18:29.227274struts4.enskede.local sshd\[23286\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.22.191
...
2020-04-08 14:35:09
124.228.54.216 attack
Apr805:31:38server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:33:35server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:58:13server6pure-ftpd:\(\?@124.228.54.216\)[WARNING]Authenticationfailedforuser[www]Apr805:32:55server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:33:43server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:33:56server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:32:15server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:34:40server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:33:49server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]Apr805:34:33server6pure-ftpd:\(\?@36.153.224.74\)[WARNING]Authenticationfailedforuser[www]IPAddressesBlocked:36.153.224.74\(CN/China/-\)
2020-04-08 14:19:32
46.38.145.6 attack
Apr  8 07:41:09 mail postfix/smtpd\[15308\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Apr  8 07:42:18 mail postfix/smtpd\[15308\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Apr  8 08:12:41 mail postfix/smtpd\[15803\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Apr  8 08:13:54 mail postfix/smtpd\[15803\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2020-04-08 14:25:41
92.118.38.82 attack
Apr  8 08:30:04 srv01 postfix/smtpd\[31992\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr  8 08:30:14 srv01 postfix/smtpd\[24419\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr  8 08:30:22 srv01 postfix/smtpd\[719\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr  8 08:30:24 srv01 postfix/smtpd\[31992\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr  8 08:30:38 srv01 postfix/smtpd\[24419\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-04-08 14:42:16
37.49.226.104 attackspambots
Automatic report - Port Scan Attack
2020-04-08 14:52:28
112.85.42.89 attackbots
k+ssh-bruteforce
2020-04-08 14:53:19
177.53.52.37 attack
Scanning an empty webserver with deny all robots.txt
2020-04-08 14:29:15
193.187.116.140 attackbotsspam
2020-04-08T04:26:53.702308shield sshd\[10561\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.187.116.140  user=mail
2020-04-08T04:26:56.075597shield sshd\[10561\]: Failed password for mail from 193.187.116.140 port 44456 ssh2
2020-04-08T04:31:05.684790shield sshd\[11362\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.187.116.140  user=root
2020-04-08T04:31:07.651855shield sshd\[11362\]: Failed password for root from 193.187.116.140 port 55496 ssh2
2020-04-08T04:35:22.678940shield sshd\[12041\]: Invalid user lee from 193.187.116.140 port 38310
2020-04-08 14:44:58
49.88.112.65 attackbotsspam
Apr  8 04:57:37 pi sshd[24588]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.65  user=root
Apr  8 04:57:39 pi sshd[24588]: Failed password for invalid user root from 49.88.112.65 port 34977 ssh2
2020-04-08 14:51:59
178.128.121.180 attackbots
SSH auth scanning - multiple failed logins
2020-04-08 14:11:02
140.143.127.179 attackbotsspam
Apr  7 22:38:07 server1 sshd\[31408\]: Failed password for invalid user update from 140.143.127.179 port 60952 ssh2
Apr  7 22:42:10 server1 sshd\[32602\]: Invalid user testftp from 140.143.127.179
Apr  7 22:42:10 server1 sshd\[32602\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.127.179 
Apr  7 22:42:11 server1 sshd\[32602\]: Failed password for invalid user testftp from 140.143.127.179 port 60272 ssh2
Apr  7 22:46:08 server1 sshd\[1288\]: Invalid user marcela from 140.143.127.179
...
2020-04-08 14:53:51
218.92.0.171 attackspam
Apr  7 21:30:09 server sshd\[19891\]: Failed password for root from 218.92.0.171 port 5515 ssh2
Apr  7 21:30:10 server sshd\[19949\]: Failed password for root from 218.92.0.171 port 35051 ssh2
Apr  7 21:30:11 server sshd\[19955\]: Failed password for root from 218.92.0.171 port 8227 ssh2
Apr  7 21:30:11 server sshd\[19945\]: Failed password for root from 218.92.0.171 port 50794 ssh2
Apr  8 09:12:48 server sshd\[14460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.171  user=root
...
2020-04-08 14:15:27
120.71.145.209 attack
2020-04-08T05:56:39.633810v22018076590370373 sshd[12458]: Invalid user jeffrey from 120.71.145.209 port 36363
2020-04-08T05:56:39.639259v22018076590370373 sshd[12458]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.71.145.209
2020-04-08T05:56:39.633810v22018076590370373 sshd[12458]: Invalid user jeffrey from 120.71.145.209 port 36363
2020-04-08T05:56:41.647930v22018076590370373 sshd[12458]: Failed password for invalid user jeffrey from 120.71.145.209 port 36363 ssh2
2020-04-08T05:58:29.179622v22018076590370373 sshd[23789]: Invalid user swg from 120.71.145.209 port 47999
...
2020-04-08 14:13:16
49.235.158.195 attack
Wordpress malicious attack:[sshd]
2020-04-08 14:59:43
77.42.87.213 attackbotsspam
Automatic report - Port Scan Attack
2020-04-08 14:58:58

最近上报的IP列表

202.248.83.158 176.126.98.224 7.36.81.230 58.235.26.40
253.61.178.113 16.110.241.161 20.21.91.220 241.71.25.239
210.46.111.148 227.221.40.182 66.47.192.67 95.41.167.129
30.47.159.236 136.103.162.97 180.63.125.86 123.33.135.211
221.192.193.102 29.182.73.206 47.217.183.238 12.23.78.204