66.132.172.185

Basic Info

City: unknown

Region: unknown

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

No discussion about this subnet yet..

Whois info:

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       66.132.172.0 - 66.132.172.255
CIDR:           66.132.172.0/24
NetName:        CENSY
NetHandle:      NET-66-132-172-0-1
Parent:         NET66 (NET-66-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Censys, Inc. (CENSY)
RegDate:        2024-05-14
Updated:        2024-05-14
Ref:            https://rdap.arin.net/registry/ip/66.132.172.0


OrgName:        Censys, Inc.
OrgId:          CENSY
Address:        116 1/2 S Main Street
City:           Ann Arbor
StateProv:      MI
PostalCode:     48104
Country:        US
RegDate:        2018-08-06
Updated:        2019-08-03
Comment:        https://censys.io
Ref:            https://rdap.arin.net/registry/entity/CENSY


OrgAbuseHandle: CAT20-ARIN
OrgAbuseName:   Censys Abuse Team
OrgAbusePhone:  +1-248-629-0125 
OrgAbuseEmail:  scan-abuse@censys.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/CAT20-ARIN

OrgTechHandle: COT12-ARIN
OrgTechName:   Censys Operations Team
OrgTechPhone:  +1-248-629-0125 
OrgTechEmail:  ops@censys.io
OrgTechRef:    https://rdap.arin.net/registry/entity/COT12-ARIN

OrgNOCHandle: COT12-ARIN
OrgNOCName:   Censys Operations Team
OrgNOCPhone:  +1-248-629-0125 
OrgNOCEmail:  ops@censys.io
OrgNOCRef:    https://rdap.arin.net/registry/entity/COT12-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#

Dig info:

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

;; QUESTION SECTION:
;66.132.172.185.			IN	A

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

;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 08 02:30:05 CST 2026
;; MSG SIZE  rcvd: 107

Host info

185.172.132.66.in-addr.arpa domain name pointer 185.172.132.66.censys-scanner.com.

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
185.172.132.66.in-addr.arpa	name = 185.172.132.66.censys-scanner.com.

Authoritative answers can be found from:

Related IP info:

Related comments:

IP	Type	Details	Datetime
171.236.178.229	attack	SSH bruteforce	2019-12-06 05:48:53
103.75.103.211	attackspambots	$f2bV_matches	2019-12-06 05:37:59
106.54.25.86	attackbots	Dec 5 11:33:57 wbs sshd\[4901\]: Invalid user info from 106.54.25.86 Dec 5 11:33:57 wbs sshd\[4901\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.25.86 Dec 5 11:34:00 wbs sshd\[4901\]: Failed password for invalid user info from 106.54.25.86 port 37158 ssh2 Dec 5 11:40:05 wbs sshd\[5867\]: Invalid user wwwadmin from 106.54.25.86 Dec 5 11:40:05 wbs sshd\[5867\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.25.86	2019-12-06 05:51:45
80.66.146.84	attackspam	Dec 5 21:58:00 tux-35-217 sshd\[24554\]: Invalid user tg from 80.66.146.84 port 60338 Dec 5 21:58:00 tux-35-217 sshd\[24554\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.66.146.84 Dec 5 21:58:02 tux-35-217 sshd\[24554\]: Failed password for invalid user tg from 80.66.146.84 port 60338 ssh2 Dec 5 22:03:52 tux-35-217 sshd\[24601\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.66.146.84 user=root ...	2019-12-06 05:42:33
222.186.180.9	attack	$f2bV_matches	2019-12-06 05:43:49
14.63.223.226	attackspambots	ssh failed login	2019-12-06 05:58:14
59.145.221.103	attack	2019-12-05T21:46:53.104537abusebot-5.cloudsearch.cf sshd\[17566\]: Invalid user hello from 59.145.221.103 port 44235	2019-12-06 05:55:34
180.250.115.98	attackspam	Dec 5 22:54:02 sd-53420 sshd\[13212\]: Invalid user fronczak from 180.250.115.98 Dec 5 22:54:02 sd-53420 sshd\[13212\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.115.98 Dec 5 22:54:05 sd-53420 sshd\[13212\]: Failed password for invalid user fronczak from 180.250.115.98 port 60906 ssh2 Dec 5 23:00:13 sd-53420 sshd\[14565\]: User root from 180.250.115.98 not allowed because none of user's groups are listed in AllowGroups Dec 5 23:00:13 sd-53420 sshd\[14565\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.115.98 user=root ...	2019-12-06 06:07:40
119.29.12.122	attack	2019-12-05T21:51:11.547105shield sshd\[27823\]: Invalid user rprasad from 119.29.12.122 port 59336 2019-12-05T21:51:11.551285shield sshd\[27823\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.12.122 2019-12-05T21:51:13.208424shield sshd\[27823\]: Failed password for invalid user rprasad from 119.29.12.122 port 59336 ssh2 2019-12-05T21:57:19.525689shield sshd\[29168\]: Invalid user eoff from 119.29.12.122 port 39014 2019-12-05T21:57:19.530271shield sshd\[29168\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.12.122	2019-12-06 06:05:06
107.170.227.141	attackspambots	Dec 5 22:04:00 vpn01 sshd[9029]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.227.141 Dec 5 22:04:01 vpn01 sshd[9029]: Failed password for invalid user voetsch from 107.170.227.141 port 37826 ssh2 ...	2019-12-06 05:28:43
192.162.108.32	attack	Dec 6 07:21:37 our-server-hostname postfix/smtpd[13653]: connect from unknown[192.162.108.32] Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x Dec x@x ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=192.162.108.32	2019-12-06 05:42:58
139.155.86.144	attackspam	Dec 5 22:03:57 herz-der-gamer sshd[19015]: Invalid user iceman from 139.155.86.144 port 48990 ...	2019-12-06 05:37:33
192.241.183.220	attackbots	Dec 5 22:48:30 localhost sshd\[21051\]: Invalid user duncan from 192.241.183.220 port 38651 Dec 5 22:48:30 localhost sshd\[21051\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.183.220 Dec 5 22:48:31 localhost sshd\[21051\]: Failed password for invalid user duncan from 192.241.183.220 port 38651 ssh2	2019-12-06 06:06:55
69.94.158.99	attackbots	Dec 5 22:09:29 smtp postfix/smtpd[3746]: NOQUEUE: reject: RCPT from tailor.swingthelamp.com[69.94.158.99]: 554 5.7.1 Service unavailable; Client host [69.94.158.99] blocked using cbl.abuseat.org; Blocked - see http://www.abuseat.org/lookup.cgi?ip=69.94.158.99; from= to= proto=ESMTP helo= ...	2019-12-06 05:27:18
61.133.232.248	attack	2019-12-05T21:56:17.952614abusebot-5.cloudsearch.cf sshd\[17660\]: Invalid user cip from 61.133.232.248 port 9045	2019-12-06 06:02:45

Recently Reported IPs

2606:4700:10::ac43:1192	220.120.247.246	82.43.219.254	239.16.246.42
196.39.13.210	168.144.92.151	122.193.247.121	2606:4700:10::ac43:1269
2606:4700:10::6814:9281	2606:4700:10::6814:6382	2606:4700:10::6816:1305	2606:4700:10::6816:305
2606:4700:10::6816:4675	121.230.89.144	2606:4700:10::ac43:2137	2606:4700:10::6814:6483
2606:4700:10::6814:9301	62.60.130.227	2606:4700:10::ac43:948	2606:4700:10::ac43:1190