172.66.45.200 - IPInfo

基本信息:

城市(city): unknown

省份(region): unknown

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

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:

点此参与IP信息讨论

暂无关于此IP的讨论, 沙发请点上方按钮

相同子网IP讨论:

暂无关于此IP所属子网相关IP的讨论.

WHOIS信息:

DIG信息:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 172.66.45.200
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44596
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;172.66.45.200.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 29 18:56:26 CST 2025
;; MSG SIZE  rcvd: 106

HOST信息:

Host 200.45.66.172.in-addr.arpa. not found: 3(NXDOMAIN)

NSLOOKUP信息:

Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 200.45.66.172.in-addr.arpa: NXDOMAIN

最新评论:

IP	类型	评论内容	时间
84.101.59.202	attack	Nov 8 16:21:20 master sshd[23013]: Failed password for invalid user pi from 84.101.59.202 port 53662 ssh2 Nov 8 16:21:20 master sshd[23011]: Failed password for invalid user pi from 84.101.59.202 port 53656 ssh2	2019-11-09 02:10:31
222.110.158.109	attackspambots	IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/222.110.158.109/ KR - 1H : (32) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : KR NAME ASN : ASN4766 IP : 222.110.158.109 CIDR : 222.110.152.0/21 PREFIX COUNT : 8136 UNIQUE IP COUNT : 44725248 ATTACKS DETECTED ASN4766 : 1H - 2 3H - 2 6H - 3 12H - 6 24H - 11 DateTime : 2019-11-08 15:35:58 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN - data recovery	2019-11-09 02:39:06
39.135.32.57	attackspam	39.135.32.57 was recorded 5 times by 1 hosts attempting to connect to the following ports: 7002,9200,1433,6379,6380. Incident counter (4h, 24h, all-time): 5, 15, 67	2019-11-09 02:38:01
212.237.33.48	attack	Nov 8 20:59:20 server sshd\[26484\]: Invalid user marketing from 212.237.33.48 Nov 8 20:59:20 server sshd\[26484\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.33.48 Nov 8 20:59:22 server sshd\[26484\]: Failed password for invalid user marketing from 212.237.33.48 port 54178 ssh2 Nov 8 21:10:48 server sshd\[29823\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.33.48 user=root Nov 8 21:10:50 server sshd\[29823\]: Failed password for root from 212.237.33.48 port 48582 ssh2 ...	2019-11-09 02:35:12
58.52.132.201	attack	Nov 8 05:46:13 server sshd\[12172\]: Failed password for invalid user admin from 58.52.132.201 port 4106 ssh2 Nov 8 14:45:12 server sshd\[25188\]: Invalid user admin from 58.52.132.201 Nov 8 14:45:12 server sshd\[25188\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.52.132.201 Nov 8 14:45:14 server sshd\[25188\]: Failed password for invalid user admin from 58.52.132.201 port 13065 ssh2 Nov 8 18:48:49 server sshd\[25431\]: Invalid user admin from 58.52.132.201 Nov 8 18:48:49 server sshd\[25431\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.52.132.201 ...	2019-11-09 02:23:40
62.210.31.99	attack	ssh failed login	2019-11-09 02:14:51
58.248.254.124	attackbots	Nov 8 18:54:21 nextcloud sshd\[13327\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.248.254.124 user=root Nov 8 18:54:23 nextcloud sshd\[13327\]: Failed password for root from 58.248.254.124 port 57421 ssh2 Nov 8 19:04:15 nextcloud sshd\[27608\]: Invalid user yg from 58.248.254.124 Nov 8 19:04:15 nextcloud sshd\[27608\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.248.254.124 ...	2019-11-09 02:18:19
85.185.18.70	attack	pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.185.18.70 Failed password for invalid user sodapop from 85.185.18.70 port 48372 ssh2 Invalid user 123456 from 85.185.18.70 port 46920 pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.185.18.70 Failed password for invalid user 123456 from 85.185.18.70 port 46920 ssh2	2019-11-09 02:10:43
3.86.204.193	attack	2019-11-08 08:37:01 H=ec2-3-86-204-193.compute-1.amazonaws.com (phylobago.mysecuritycamera.org) [3.86.204.193]:43430 I=[192.147.25.65]:25 sender verify fail for : Unrouteable address 2019-11-08 08:37:01 H=ec2-3-86-204-193.compute-1.amazonaws.com (phylobago.mysecuritycamera.org) [3.86.204.193]:43430 I=[192.147.25.65]:25 F= rejected RCPT : Sender verify failed 2019-11-08 08:37:05 H=ec2-3-86-204-193.compute-1.amazonaws.com (phylobago.mysecuritycamera.org) [3.86.204.193]:35616 I=[192.147.25.65]:25 sender verify fail for : Unrouteable address 2019-11-08 08:37:05 H=ec2-3-86-204-193.compute-1.amazonaws.com (phylobago.mysecuritycamera.org) [3.86.204.193]:35616 I=[192.147.25.65]:25 F= rejected RCPT : Sender verify failed ...	2019-11-09 02:05:48
34.95.156.134	attack	Nov 8 18:43:40 vmanager6029 sshd\[18200\]: Invalid user drunk from 34.95.156.134 port 39464 Nov 8 18:43:40 vmanager6029 sshd\[18200\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.95.156.134 Nov 8 18:43:42 vmanager6029 sshd\[18200\]: Failed password for invalid user drunk from 34.95.156.134 port 39464 ssh2	2019-11-09 02:13:07
109.94.82.149	attack	2019-10-11 22:40:08,916 fail2ban.actions [843]: NOTICE [sshd] Ban 109.94.82.149 2019-10-12 01:48:57,349 fail2ban.actions [843]: NOTICE [sshd] Ban 109.94.82.149 2019-10-12 04:55:50,548 fail2ban.actions [843]: NOTICE [sshd] Ban 109.94.82.149 ...	2019-11-09 02:09:18
220.128.139.29	attackbots	$f2bV_matches	2019-11-09 02:09:59
116.31.105.198	attack	Nov 8 16:22:31 vps666546 sshd\[15280\]: Invalid user rr@123 from 116.31.105.198 port 51830 Nov 8 16:22:31 vps666546 sshd\[15280\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.31.105.198 Nov 8 16:22:33 vps666546 sshd\[15280\]: Failed password for invalid user rr@123 from 116.31.105.198 port 51830 ssh2 Nov 8 16:29:04 vps666546 sshd\[15528\]: Invalid user changeme from 116.31.105.198 port 32830 Nov 8 16:29:04 vps666546 sshd\[15528\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.31.105.198 ...	2019-11-09 02:11:59
181.48.225.126	attack	Lines containing failures of 181.48.225.126 Nov 8 10:46:10 jarvis sshd[9548]: Invalid user spark from 181.48.225.126 port 43860 Nov 8 10:46:10 jarvis sshd[9548]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.225.126 Nov 8 10:46:12 jarvis sshd[9548]: Failed password for invalid user spark from 181.48.225.126 port 43860 ssh2 Nov 8 10:46:14 jarvis sshd[9548]: Received disconnect from 181.48.225.126 port 43860:11: Bye Bye [preauth] Nov 8 10:46:14 jarvis sshd[9548]: Disconnected from invalid user spark 181.48.225.126 port 43860 [preauth] Nov 8 11:07:01 jarvis sshd[13815]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.225.126 user=r.r Nov 8 11:07:03 jarvis sshd[13815]: Failed password for r.r from 181.48.225.126 port 53654 ssh2 Nov 8 11:07:05 jarvis sshd[13815]: Received disconnect from 181.48.225.126 port 53654:11: Bye Bye [preauth] Nov 8 11:07:05 jarvis sshd[13815]: D........ ------------------------------	2019-11-09 02:42:31
116.196.109.197	attackspam	2019-11-08T18:20:39.791799abusebot-5.cloudsearch.cf sshd\[2676\]: Invalid user waggoner from 116.196.109.197 port 43502	2019-11-09 02:32:50

最近上报的IP列表

45.90.30.191	111.50.60.4	47.84.99.250	0.213.236.139
0.213.236.143	84.252.73.89	208.69.36.154	209.38.201.154
101.132.129.206	43.166.242.189	23.95.35.114	245.210.216.13
20.29.21.208	180.252.142.236	80.178.190.234	10.232.81.73
80.178.190.47	80.178.190.245	95.165.93.211	91.204.110.216