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

城市(city): unknown

省份(region): unknown

国家(country): Korea Republic of

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;166.125.64.45.			IN	A

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

;; Query time: 85 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 28 00:32:13 CST 2020
;; MSG SIZE  rcvd: 117
HOST信息:
Host 45.64.125.166.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.64.125.166.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
45.226.81.197 attackbots
$f2bV_matches
2019-11-04 02:42:17
190.25.232.2 attack
Oct 20 11:45:04 vtv3 sshd\[6888\]: Invalid user cloud from 190.25.232.2 port 59521
Oct 20 11:45:04 vtv3 sshd\[6888\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.25.232.2
Oct 20 11:45:06 vtv3 sshd\[6888\]: Failed password for invalid user cloud from 190.25.232.2 port 59521 ssh2
Oct 20 11:49:28 vtv3 sshd\[9236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.25.232.2  user=root
Oct 20 11:49:30 vtv3 sshd\[9236\]: Failed password for root from 190.25.232.2 port 51237 ssh2
Oct 20 12:02:36 vtv3 sshd\[16194\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.25.232.2  user=root
Oct 20 12:02:38 vtv3 sshd\[16194\]: Failed password for root from 190.25.232.2 port 54629 ssh2
Oct 20 12:07:12 vtv3 sshd\[18586\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.25.232.2  user=root
Oct 20 12:07:14 vtv3 sshd\[18586\]: Failed password f
2019-11-04 02:04:56
123.21.94.145 attack
$f2bV_matches
2019-11-04 02:47:07
54.37.139.235 attack
Nov  3 17:46:09 meumeu sshd[17869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.139.235 
Nov  3 17:46:11 meumeu sshd[17869]: Failed password for invalid user bandit123 from 54.37.139.235 port 57290 ssh2
Nov  3 17:50:30 meumeu sshd[18454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.139.235 
...
2019-11-04 02:09:25
46.101.43.224 attackbots
Nov  3 17:39:16 bouncer sshd\[27244\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.43.224  user=root
Nov  3 17:39:18 bouncer sshd\[27244\]: Failed password for root from 46.101.43.224 port 54162 ssh2
Nov  3 17:43:31 bouncer sshd\[27270\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.43.224  user=root
...
2019-11-04 02:21:48
59.42.192.217 attackspam
Brute forcing RDP port 3389
2019-11-04 02:24:10
154.118.141.90 attack
Too many connections or unauthorized access detected from Arctic banned ip
2019-11-04 02:33:10
129.211.108.202 attack
Nov  3 16:36:51 root sshd[17396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.108.202 
Nov  3 16:36:53 root sshd[17396]: Failed password for invalid user user from 129.211.108.202 port 53265 ssh2
Nov  3 16:42:00 root sshd[17497]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.108.202 
...
2019-11-04 02:06:50
123.207.233.79 attackspambots
$f2bV_matches
2019-11-04 02:12:48
8.2.215.75 attackbots
port scan and connect, tcp 23 (telnet)
2019-11-04 02:22:50
178.128.112.98 attack
Nov  3 07:49:35 php1 sshd\[7117\]: Invalid user hassan from 178.128.112.98
Nov  3 07:49:35 php1 sshd\[7117\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.112.98
Nov  3 07:49:37 php1 sshd\[7117\]: Failed password for invalid user hassan from 178.128.112.98 port 55597 ssh2
Nov  3 07:56:22 php1 sshd\[7652\]: Invalid user kaysha from 178.128.112.98
Nov  3 07:56:22 php1 sshd\[7652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.112.98
2019-11-04 02:22:07
193.32.160.146 attack
Nov  3 19:27:33 mailserver postfix/smtpd[34994]: NOQUEUE: reject: RCPT from unknown[193.32.160.146]: 450 4.7.1 Client host rejected: cannot find your hostname, [193.32.160.146]; from= to=<[hidden]> proto=ESMTP helo=<[193.32.160.153]>
Nov  3 19:27:33 mailserver postfix/smtpd[34994]: NOQUEUE: reject: RCPT from unknown[193.32.160.146]: 450 4.7.1 Client host rejected: cannot find your hostname, [193.32.160.146]; from= to=<[hidden]> proto=ESMTP helo=<[193.32.160.153]>
Nov  3 19:27:33 mailserver postfix/smtpd[34994]: NOQUEUE: reject: RCPT from unknown[193.32.160.146]: 450 4.7.1 Client host rejected: cannot find your hostname, [193.32.160.146]; from= to=<[hidden]> proto=ESMTP helo=<[193.32.160.153]>
Nov  3 19:27:33 mailserver postfix/smtpd[34994]: NOQUEUE: reject: RCPT from unknown[193.32.160.146]: 450 4.7.1 Client host rejected: cannot find your hostname, [193.32.160.146]; from= to=<[hidden]> proto=ESMTP helo=<[193.32.160.153]>
2019-11-04 02:39:59
201.26.191.101 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/201.26.191.101/ 
 
 BR - 1H : (315)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BR 
 NAME ASN : ASN27699 
 
 IP : 201.26.191.101 
 
 CIDR : 201.26.128.0/17 
 
 PREFIX COUNT : 267 
 
 UNIQUE IP COUNT : 6569728 
 
 
 ATTACKS DETECTED ASN27699 :  
  1H - 6 
  3H - 13 
  6H - 37 
 12H - 67 
 24H - 150 
 
 DateTime : 2019-11-03 15:33:41 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-04 02:10:14
51.75.51.32 attackbotsspam
SSHScan
2019-11-04 02:44:44
95.213.244.42 attack
95.213.244.42 was recorded 5 times by 1 hosts attempting to connect to the following ports: 3128. Incident counter (4h, 24h, all-time): 5, 54, 152
2019-11-04 02:48:57

最近上报的IP列表

185.107.29.135 94.113.241.246 14.29.215.69 51.75.66.89
85.97.117.53 71.6.233.61 13.232.248.185 180.242.75.111
136.233.15.42 170.80.63.196 66.74.30.16 177.55.165.60
94.191.62.172 210.153.220.72 91.165.129.186 213.183.48.96
79.148.232.33 88.250.50.20 104.129.72.66 118.25.51.181