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

城市(city): unknown

省份(region): unknown

国家(country): United States of America (the)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;52.244.238.21.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 06:36:36 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 21.238.244.52.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 21.238.244.52.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
180.250.140.74 attack
Nov 26 06:57:19 ovpn sshd\[18856\]: Invalid user ayfer from 180.250.140.74
Nov 26 06:57:19 ovpn sshd\[18856\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.140.74
Nov 26 06:57:22 ovpn sshd\[18856\]: Failed password for invalid user ayfer from 180.250.140.74 port 51818 ssh2
Nov 26 07:23:26 ovpn sshd\[25354\]: Invalid user steam from 180.250.140.74
Nov 26 07:23:26 ovpn sshd\[25354\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.140.74
2019-11-26 19:44:21
106.12.152.194 attackspam
11/26/2019-06:34:08.197189 106.12.152.194 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-26 19:46:18
195.175.202.110 attackspambots
Port 1433 Scan
2019-11-26 19:24:23
92.50.249.92 attack
2019-11-26 05:18:28,193 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 92.50.249.92
2019-11-26 05:49:35,251 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 92.50.249.92
2019-11-26 06:20:01,756 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 92.50.249.92
2019-11-26 06:53:32,056 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 92.50.249.92
2019-11-26 07:23:46,366 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 92.50.249.92
...
2019-11-26 19:32:02
167.250.44.156 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/167.250.44.156/ 
 
 IN - 1H : (24)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : IN 
 NAME ASN : ASN5 
 
 IP : 167.250.44.156 
 
 CIDR : 167.250.44.0/24 
 
 PREFIX COUNT : 9 
 
 UNIQUE IP COUNT : 3840 
 
 
 ATTACKS DETECTED ASN5 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-26 08:27:27 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-26 19:18:16
182.180.173.249 attackbotsspam
Automatic report - Banned IP Access
2019-11-26 19:47:11
223.71.167.61 attackbots
firewall-block, port(s): 79/tcp, 4567/tcp
2019-11-26 19:51:08
5.196.143.9 attackspambots
Nov 26 07:06:10 mxgate1 postfix/postscreen[19964]: CONNECT from [5.196.143.9]:34321 to [176.31.12.44]:25
Nov 26 07:06:10 mxgate1 postfix/dnsblog[19969]: addr 5.196.143.9 listed by domain zen.spamhaus.org as 127.0.0.4
Nov 26 07:06:10 mxgate1 postfix/dnsblog[19969]: addr 5.196.143.9 listed by domain zen.spamhaus.org as 127.0.0.3
Nov 26 07:06:10 mxgate1 postfix/dnsblog[19966]: addr 5.196.143.9 listed by domain cbl.abuseat.org as 127.0.0.2
Nov 26 07:06:10 mxgate1 postfix/dnsblog[19967]: addr 5.196.143.9 listed by domain b.barracudacentral.org as 127.0.0.2
Nov 26 07:06:16 mxgate1 postfix/postscreen[19964]: DNSBL rank 4 for [5.196.143.9]:34321
Nov 26 07:06:16 mxgate1 postfix/tlsproxy[20026]: CONNECT from [5.196.143.9]:34321
Nov 26 07:06:16 mxgate1 postfix/postscreen[19964]: DISCONNECT [5.196.143.9]:34321
Nov 26 07:06:16 mxgate1 postfix/tlsproxy[20026]: DISCONNECT [5.196.143.9]:34321
Nov 26 07:06:43 mxgate1 postfix/postscreen[19964]: CONNECT from [5.196.143.9]:51031 to [176.31........
-------------------------------
2019-11-26 19:33:55
23.254.229.232 attackspam
SSH brute-force: detected 30 distinct usernames within a 24-hour window.
2019-11-26 19:23:21
51.79.65.158 attackspam
Nov 26 10:35:39 web8 sshd\[13206\]: Invalid user genshiro from 51.79.65.158
Nov 26 10:35:39 web8 sshd\[13206\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.65.158
Nov 26 10:35:41 web8 sshd\[13206\]: Failed password for invalid user genshiro from 51.79.65.158 port 35188 ssh2
Nov 26 10:41:56 web8 sshd\[16107\]: Invalid user compston from 51.79.65.158
Nov 26 10:41:56 web8 sshd\[16107\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.65.158
2019-11-26 19:37:31
115.111.89.66 attackbots
Nov 26 10:03:44 server sshd\[2022\]: Invalid user test from 115.111.89.66
Nov 26 10:03:44 server sshd\[2022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.111.89.66 
Nov 26 10:03:46 server sshd\[2022\]: Failed password for invalid user test from 115.111.89.66 port 54081 ssh2
Nov 26 10:15:23 server sshd\[5064\]: Invalid user sule from 115.111.89.66
Nov 26 10:15:23 server sshd\[5064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.111.89.66 
...
2019-11-26 19:29:39
112.85.42.182 attack
Nov 26 08:14:08 firewall sshd[15752]: Failed password for root from 112.85.42.182 port 50469 ssh2
Nov 26 08:14:11 firewall sshd[15752]: Failed password for root from 112.85.42.182 port 50469 ssh2
Nov 26 08:14:15 firewall sshd[15752]: Failed password for root from 112.85.42.182 port 50469 ssh2
...
2019-11-26 19:21:21
119.29.128.126 attackbots
Nov 26 16:30:37 gw1 sshd[16633]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.128.126
Nov 26 16:30:38 gw1 sshd[16633]: Failed password for invalid user ftp from 119.29.128.126 port 42424 ssh2
...
2019-11-26 19:42:47
2a01:7e00::f03c:92ff:fe69:e899 attackspam
Lines containing failures of 2a01:7e00::f03c:92ff:fe69:e899
Nov 26 07:05:16 web02 sshd[17799]: refused connect from 2a01:7e00::f03c:92ff:fe69:e899 (2a01:7e00::f03c:92ff:fe69:e899)
Nov 26 07:05:16 web02 sshd[17800]: refused connect from 2a01:7e00::f03c:92ff:fe69:e899 (2a01:7e00::f03c:92ff:fe69:e899)
Nov 26 07:05:16 web02 sshd[17798]: refused connect from 2a01:7e00::f03c:92ff:fe69:e899 (2a01:7e00::f03c:92ff:fe69:e899)
Nov 26 07:05:16 web02 sshd[17797]: refused connect from 2a01:7e00::f03c:92ff:fe69:e899 (2a01:7e00::f03c:92ff:fe69:e899)


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=2a01:7e00::f03c:92ff:fe69:e899
2019-11-26 19:28:24
106.240.86.211 attack
Unauthorized connection attempt from IP address 106.240.86.211 on Port 25(SMTP)
2019-11-26 19:48:07

最近上报的IP列表

15.128.208.30 154.108.208.58 75.189.50.253 180.68.249.192
135.221.101.42 123.39.216.237 172.147.162.63 188.40.69.147
200.54.162.65 125.218.196.166 99.219.234.230 142.63.177.246
213.32.138.55 104.162.98.166 104.143.113.119 242.89.155.215
90.129.159.216 195.62.238.12 40.184.67.175 43.86.40.138