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

;; QUESTION SECTION:
;66.94.64.42.			IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 18:31:11 CST 2025
;; MSG SIZE  rcvd: 104
HOST信息:
42.64.94.66.in-addr.arpa domain name pointer 42.nat1.kth.clev.oh.fidelityaccess.net.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.64.94.66.in-addr.arpa	name = 42.nat1.kth.clev.oh.fidelityaccess.net.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
87.156.132.86 attack
$f2bV_matches
2020-04-16 21:22:45
47.190.3.185 attack
Apr 16 16:22:10 www5 sshd\[15279\]: Invalid user admin from 47.190.3.185
Apr 16 16:22:10 www5 sshd\[15279\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.190.3.185
Apr 16 16:22:12 www5 sshd\[15279\]: Failed password for invalid user admin from 47.190.3.185 port 55560 ssh2
...
2020-04-16 21:33:30
80.211.164.5 attackbotsspam
Apr 16 15:18:15 * sshd[4479]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.164.5
Apr 16 15:18:17 * sshd[4479]: Failed password for invalid user couchdb from 80.211.164.5 port 53762 ssh2
2020-04-16 21:56:56
125.124.254.31 attackbotsspam
Apr 16 14:27:30 srv01 sshd[32128]: Invalid user test2 from 125.124.254.31 port 40456
Apr 16 14:27:30 srv01 sshd[32128]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.124.254.31
Apr 16 14:27:30 srv01 sshd[32128]: Invalid user test2 from 125.124.254.31 port 40456
Apr 16 14:27:31 srv01 sshd[32128]: Failed password for invalid user test2 from 125.124.254.31 port 40456 ssh2
Apr 16 14:31:52 srv01 sshd[32376]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.124.254.31  user=root
Apr 16 14:31:54 srv01 sshd[32376]: Failed password for root from 125.124.254.31 port 35120 ssh2
...
2020-04-16 21:29:48
198.199.103.92 attackspam
Apr 16 14:01:44 ns382633 sshd\[26144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.103.92  user=root
Apr 16 14:01:46 ns382633 sshd\[26144\]: Failed password for root from 198.199.103.92 port 43779 ssh2
Apr 16 14:14:37 ns382633 sshd\[28654\]: Invalid user oracle from 198.199.103.92 port 42118
Apr 16 14:14:37 ns382633 sshd\[28654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.103.92
Apr 16 14:14:39 ns382633 sshd\[28654\]: Failed password for invalid user oracle from 198.199.103.92 port 42118 ssh2
2020-04-16 21:54:41
223.74.105.122 attackbots
spam
2020-04-16 21:49:13
159.203.190.189 attack
Bruteforce detected by fail2ban
2020-04-16 21:29:04
218.92.0.199 attack
Apr 16 15:42:11 server sshd[16101]: Failed password for root from 218.92.0.199 port 36402 ssh2
Apr 16 15:42:13 server sshd[16101]: Failed password for root from 218.92.0.199 port 36402 ssh2
Apr 16 15:42:16 server sshd[16101]: Failed password for root from 218.92.0.199 port 36402 ssh2
2020-04-16 21:50:34
45.152.34.24 attack
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with plinkechiropractic.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture
2020-04-16 21:53:05
200.219.229.57 attack
port 5901
2020-04-16 21:14:42
138.94.134.17 attackbotsspam
1587039277 - 04/16/2020 14:14:37 Host: 138.94.134.17/138.94.134.17 Port: 445 TCP Blocked
2020-04-16 21:57:58
218.29.200.172 attackbotsspam
Apr 16 15:06:17 pkdns2 sshd\[36838\]: Invalid user upload from 218.29.200.172Apr 16 15:06:19 pkdns2 sshd\[36838\]: Failed password for invalid user upload from 218.29.200.172 port 27760 ssh2Apr 16 15:10:30 pkdns2 sshd\[37038\]: Invalid user judy from 218.29.200.172Apr 16 15:10:32 pkdns2 sshd\[37038\]: Failed password for invalid user judy from 218.29.200.172 port 40611 ssh2Apr 16 15:14:52 pkdns2 sshd\[37187\]: Invalid user eliuth from 218.29.200.172Apr 16 15:14:54 pkdns2 sshd\[37187\]: Failed password for invalid user eliuth from 218.29.200.172 port 53467 ssh2
...
2020-04-16 21:37:13
5.196.63.250 attackspambots
2020-04-16T12:27:53.817871abusebot.cloudsearch.cf sshd[25764]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip250.ip-5-196-63.eu  user=root
2020-04-16T12:27:55.890278abusebot.cloudsearch.cf sshd[25764]: Failed password for root from 5.196.63.250 port 41960 ssh2
2020-04-16T12:32:12.262710abusebot.cloudsearch.cf sshd[26067]: Invalid user lr from 5.196.63.250 port 54874
2020-04-16T12:32:12.272467abusebot.cloudsearch.cf sshd[26067]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip250.ip-5-196-63.eu
2020-04-16T12:32:12.262710abusebot.cloudsearch.cf sshd[26067]: Invalid user lr from 5.196.63.250 port 54874
2020-04-16T12:32:13.903316abusebot.cloudsearch.cf sshd[26067]: Failed password for invalid user lr from 5.196.63.250 port 54874 ssh2
2020-04-16T12:35:26.544695abusebot.cloudsearch.cf sshd[26393]: Invalid user tj from 5.196.63.250 port 45625
...
2020-04-16 21:40:13
114.142.171.22 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 16-04-2020 13:15:15.
2020-04-16 21:14:10
222.186.42.136 attackspam
Apr 16 15:34:49 plex sshd[26338]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.136  user=root
Apr 16 15:34:51 plex sshd[26338]: Failed password for root from 222.186.42.136 port 25806 ssh2
2020-04-16 21:43:52

最近上报的IP列表

124.132.119.187 171.236.26.86 48.6.44.77 230.32.102.5
66.115.132.15 123.25.180.66 88.205.118.62 205.181.213.225
148.60.43.28 5.110.76.239 154.10.90.220 148.94.148.102
101.181.34.98 9.100.57.177 230.68.92.170 244.117.212.128
19.191.95.142 107.218.191.219 51.148.135.172 197.144.218.103