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

城市(city): unknown

省份(region): unknown

国家(country): United States

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;54.107.220.31.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 12:59:47 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 31.220.107.54.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 31.220.107.54.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
222.186.175.212 attackspambots
detected by Fail2Ban
2019-10-14 04:32:07
103.60.126.80 attackbotsspam
2019-10-13T20:48:35.050086abusebot-5.cloudsearch.cf sshd\[11705\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.60.126.80  user=root
2019-10-14 04:51:38
106.13.49.233 attackspam
2019-10-13T20:28:32.190372shield sshd\[22374\]: Invalid user \#EDC\$RFV from 106.13.49.233 port 46662
2019-10-13T20:28:32.194433shield sshd\[22374\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.49.233
2019-10-13T20:28:34.328109shield sshd\[22374\]: Failed password for invalid user \#EDC\$RFV from 106.13.49.233 port 46662 ssh2
2019-10-13T20:32:31.378467shield sshd\[24379\]: Invalid user P4SSword2017 from 106.13.49.233 port 55212
2019-10-13T20:32:31.382725shield sshd\[24379\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.49.233
2019-10-14 04:35:05
168.195.176.105 attackspambots
Apr 16 23:44:32 yesfletchmain sshd\[29064\]: Invalid user Else from 168.195.176.105 port 47809
Apr 16 23:44:32 yesfletchmain sshd\[29064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.195.176.105
Apr 16 23:44:34 yesfletchmain sshd\[29064\]: Failed password for invalid user Else from 168.195.176.105 port 47809 ssh2
Apr 16 23:47:44 yesfletchmain sshd\[29144\]: Invalid user pk from 168.195.176.105 port 59713
Apr 16 23:47:44 yesfletchmain sshd\[29144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.195.176.105
...
2019-10-14 04:44:15
168.90.125.130 attack
Mar 12 22:26:38 yesfletchmain sshd\[32728\]: Invalid user newuser from 168.90.125.130 port 50888
Mar 12 22:26:38 yesfletchmain sshd\[32728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.90.125.130
Mar 12 22:26:41 yesfletchmain sshd\[32728\]: Failed password for invalid user newuser from 168.90.125.130 port 50888 ssh2
Mar 12 22:34:14 yesfletchmain sshd\[537\]: Invalid user marvin from 168.90.125.130 port 64139
Mar 12 22:34:14 yesfletchmain sshd\[537\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.90.125.130
...
2019-10-14 04:22:11
185.90.118.18 attack
10/13/2019-16:26:45.998342 185.90.118.18 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 04:32:39
168.63.250.142 attackspam
Aug  4 18:36:05 yesfletchmain sshd\[22109\]: Invalid user daniel from 168.63.250.142 port 52346
Aug  4 18:36:05 yesfletchmain sshd\[22109\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.63.250.142
Aug  4 18:36:08 yesfletchmain sshd\[22109\]: Failed password for invalid user daniel from 168.63.250.142 port 52346 ssh2
Aug  4 18:41:03 yesfletchmain sshd\[22301\]: Invalid user abc123 from 168.63.250.142 port 39486
Aug  4 18:41:03 yesfletchmain sshd\[22301\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.63.250.142
...
2019-10-14 04:25:00
168.62.63.55 attackspam
Mar 17 01:45:39 yesfletchmain sshd\[8507\]: Invalid user pma from 168.62.63.55 port 33258
Mar 17 01:45:39 yesfletchmain sshd\[8507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.63.55
Mar 17 01:45:41 yesfletchmain sshd\[8507\]: Failed password for invalid user pma from 168.62.63.55 port 33258 ssh2
Mar 17 01:51:27 yesfletchmain sshd\[8836\]: Invalid user web2 from 168.62.63.55 port 60556
Mar 17 01:51:27 yesfletchmain sshd\[8836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.63.55
...
2019-10-14 04:26:52
168.194.160.235 attackbotsspam
Mar  9 02:56:44 dillonfme sshd\[10119\]: User root from 168.194.160.235 not allowed because not listed in AllowUsers
Mar  9 02:56:44 dillonfme sshd\[10119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.160.235  user=root
Mar  9 02:56:47 dillonfme sshd\[10119\]: Failed password for invalid user root from 168.194.160.235 port 28286 ssh2
Mar  9 03:04:20 dillonfme sshd\[10294\]: Invalid user musique from 168.194.160.235 port 19050
Mar  9 03:04:20 dillonfme sshd\[10294\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.160.235
...
2019-10-14 04:48:31
168.194.163.138 attack
Mar 13 17:06:41 yesfletchmain sshd\[6015\]: Invalid user ts3 from 168.194.163.138 port 6357
Mar 13 17:06:41 yesfletchmain sshd\[6015\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.163.138
Mar 13 17:06:44 yesfletchmain sshd\[6015\]: Failed password for invalid user ts3 from 168.194.163.138 port 6357 ssh2
Mar 13 17:12:09 yesfletchmain sshd\[6267\]: Invalid user user from 168.194.163.138 port 43284
Mar 13 17:12:09 yesfletchmain sshd\[6267\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.163.138
...
2019-10-14 04:47:43
61.133.232.254 attackbots
2019-10-13T20:16:52.535956abusebot-5.cloudsearch.cf sshd\[11406\]: Invalid user alice from 61.133.232.254 port 4084
2019-10-14 04:19:54
185.90.117.5 attackbots
10/13/2019-16:16:52.943492 185.90.117.5 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 04:19:09
80.82.65.74 attackspam
10/13/2019-16:28:49.726712 80.82.65.74 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-14 04:29:40
213.251.35.49 attackbots
Automatic report - Banned IP Access
2019-10-14 04:24:29
177.136.39.10 attack
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/177.136.39.10/ 
 BR - 1H : (177)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BR 
 NAME ASN : ASN52871 
 
 IP : 177.136.39.10 
 
 CIDR : 177.136.39.0/24 
 
 PREFIX COUNT : 61 
 
 UNIQUE IP COUNT : 41472 
 
 
 WYKRYTE ATAKI Z ASN52871 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-13 22:16:14 
 
 INFO : Port SERVER 80 Scan Detected and Blocked by ADMIN  - data recovery
2019-10-14 04:50:45

最近上报的IP列表

251.16.252.95 51.93.137.214 250.25.94.29 230.254.103.227
152.255.178.24 125.141.192.170 140.172.179.170 21.236.165.10
238.195.233.11 67.109.183.226 229.24.185.174 82.102.118.122
66.1.211.175 148.247.88.86 40.190.60.55 115.235.98.249
232.22.105.195 165.174.131.161 185.247.25.124 140.248.120.134