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

城市(city): unknown

省份(region): unknown

国家(country): Indonesia

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;202.80.125.54.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 23:10:49 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 54.125.80.202.in-addr.arpa not found: 2(SERVFAIL)
NSLOOKUP信息:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 54.125.80.202.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
200.11.219.206 attackspam
SSH brutforce
2019-10-10 04:34:23
120.203.5.92 attackspambots
Honeypot attack, port: 23, PTR: PTR record not found
2019-10-10 04:36:06
42.247.30.132 attackspam
Oct  9 18:11:19 plesk sshd[11921]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.247.30.132  user=r.r
Oct  9 18:11:22 plesk sshd[11921]: Failed password for r.r from 42.247.30.132 port 57098 ssh2
Oct  9 18:11:22 plesk sshd[11921]: Received disconnect from 42.247.30.132: 11: Bye Bye [preauth]
Oct  9 18:24:18 plesk sshd[12354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.247.30.132  user=r.r
Oct  9 18:24:21 plesk sshd[12354]: Failed password for r.r from 42.247.30.132 port 37578 ssh2
Oct  9 18:24:21 plesk sshd[12354]: Received disconnect from 42.247.30.132: 11: Bye Bye [preauth]
Oct  9 18:29:15 plesk sshd[12549]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.247.30.132  user=r.r
Oct  9 18:29:18 plesk sshd[12549]: Failed password for r.r from 42.247.30.132 port 48206 ssh2
Oct  9 18:29:18 plesk sshd[12549]: Received disconnect from 42.247.........
-------------------------------
2019-10-10 04:43:54
14.162.183.197 attackbotsspam
Oct  9 10:03:13 php1 sshd\[976\]: Invalid user PassW0rd2017 from 14.162.183.197
Oct  9 10:03:13 php1 sshd\[976\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.162.183.197
Oct  9 10:03:14 php1 sshd\[976\]: Failed password for invalid user PassW0rd2017 from 14.162.183.197 port 52820 ssh2
Oct  9 10:11:37 php1 sshd\[1768\]: Invalid user 123Canon from 14.162.183.197
Oct  9 10:11:37 php1 sshd\[1768\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.162.183.197
2019-10-10 04:39:15
193.32.163.182 attackspambots
SSH Server BruteForce Attack
2019-10-10 04:22:58
103.80.117.214 attackspambots
Oct  9 22:56:50 microserver sshd[24087]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.80.117.214  user=root
Oct  9 22:56:52 microserver sshd[24087]: Failed password for root from 103.80.117.214 port 52568 ssh2
Oct  9 23:00:59 microserver sshd[24794]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.80.117.214  user=root
Oct  9 23:01:01 microserver sshd[24794]: Failed password for root from 103.80.117.214 port 36100 ssh2
Oct  9 23:05:02 microserver sshd[25018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.80.117.214  user=root
Oct  9 23:17:21 microserver sshd[26820]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.80.117.214  user=root
Oct  9 23:17:23 microserver sshd[26820]: Failed password for root from 103.80.117.214 port 54938 ssh2
Oct  9 23:21:29 microserver sshd[27410]: pam_unix(sshd:auth): authentication failure; logname= uid
2019-10-10 04:46:27
115.70.184.65 attackbots
Tried sshing with brute force.
2019-10-10 05:00:23
186.10.17.84 attack
Oct  9 23:28:35 pkdns2 sshd\[54866\]: Invalid user Qwerty1@3 from 186.10.17.84Oct  9 23:28:37 pkdns2 sshd\[54866\]: Failed password for invalid user Qwerty1@3 from 186.10.17.84 port 49692 ssh2Oct  9 23:32:50 pkdns2 sshd\[55075\]: Invalid user 6tfc5rdx from 186.10.17.84Oct  9 23:32:53 pkdns2 sshd\[55075\]: Failed password for invalid user 6tfc5rdx from 186.10.17.84 port 60506 ssh2Oct  9 23:37:06 pkdns2 sshd\[55284\]: Invalid user Partial@123 from 186.10.17.84Oct  9 23:37:08 pkdns2 sshd\[55284\]: Failed password for invalid user Partial@123 from 186.10.17.84 port 43104 ssh2
...
2019-10-10 04:58:31
46.38.144.202 attack
Oct  9 21:59:11 webserver postfix/smtpd\[5392\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  9 22:01:40 webserver postfix/smtpd\[5843\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  9 22:04:10 webserver postfix/smtpd\[5392\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  9 22:06:39 webserver postfix/smtpd\[5392\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  9 22:09:07 webserver postfix/smtpd\[5392\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-10-10 04:20:29
130.198.67.114 attackbotsspam
Oct  9 22:31:21 mail kernel: [366328.724130] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3c:05:0d:89:f8:66:f2:68:66:ff:08:00 SRC=130.198.67.114 DST=77.73.69.240 LEN=40 TOS=0x08 PREC=0x20 TTL=63 ID=11572 DF PROTO=TCP SPT=50819 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  9 22:31:21 mail kernel: [366328.733582] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3c:05:0d:89:f8:66:f2:68:66:ff:08:00 SRC=130.198.67.114 DST=77.73.69.240 LEN=40 TOS=0x08 PREC=0x20 TTL=57 ID=34779 DF PROTO=TCP SPT=49583 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  9 22:31:22 mail kernel: [366328.855581] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3c:05:0d:89:f8:66:f2:68:66:ff:08:00 SRC=130.198.67.114 DST=77.73.69.240 LEN=40 TOS=0x08 PREC=0x20 TTL=64 ID=25623 DF PROTO=TCP SPT=52939 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  9 22:31:22 mail kernel: [366328.885170] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3c:05:0d:89:f8:66:f2:68:66:ff:08:00 SRC=130.198.67.114 DST=77.73.69.240 LEN=40 TOS=0x08 PREC=0x20 TTL=56 ID=25689 DF PROTO=TCP SPT=51607 DPT=22 WINDOW=29200 RES=0x00 SY
2019-10-10 04:41:20
49.88.112.90 attack
2019-10-09T19:55:19.201079abusebot-2.cloudsearch.cf sshd\[9034\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.90  user=root
2019-10-10 04:19:35
218.187.101.200 attackspambots
Honeypot attack, port: 5555, PTR: NK218-187-101-200.adsl.dynamic.apol.com.tw.
2019-10-10 04:44:14
189.69.44.56 attackspam
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/189.69.44.56/ 
 BR - 1H : (264)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BR 
 NAME ASN : ASN27699 
 
 IP : 189.69.44.56 
 
 CIDR : 189.69.0.0/16 
 
 PREFIX COUNT : 267 
 
 UNIQUE IP COUNT : 6569728 
 
 
 WYKRYTE ATAKI Z ASN27699 :  
  1H - 5 
  3H - 16 
  6H - 27 
 12H - 61 
 24H - 113 
 
 DateTime : 2019-10-09 21:46:28 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-10 04:25:42
46.101.11.213 attack
2019-10-09T20:16:47.697670abusebot-2.cloudsearch.cf sshd\[9124\]: Invalid user Windows@2012 from 46.101.11.213 port 59634
2019-10-10 04:23:18
117.254.80.66 attackbots
$f2bV_matches
2019-10-10 04:49:01

最近上报的IP列表

200.97.198.206 137.235.175.131 52.122.238.8 23.68.212.207
107.201.190.121 126.197.81.230 72.126.221.81 208.231.158.92
42.102.233.2 7.232.30.247 30.52.87.13 180.224.189.248
176.76.211.60 95.238.165.58 189.79.5.186 86.23.38.120
193.111.33.176 44.189.169.40 236.127.107.96 13.143.141.119