City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# 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.195.0 - 66.132.195.255
CIDR: 66.132.195.0/24
NetName: CENSY
NetHandle: NET-66-132-195-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.195.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.io
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 9.10.3-P4-Ubuntu <<>> 66.132.195.36
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45185
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;66.132.195.36. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026043000 1800 900 604800 86400
;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 30 19:00:31 CST 2026
;; MSG SIZE rcvd: 10636.195.132.66.in-addr.arpa domain name pointer 36.195.132.66.censys-scanner.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
36.195.132.66.in-addr.arpa name = 36.195.132.66.censys-scanner.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 1.52.60.124 | attack | Honeypot attack, port: 445, PTR: PTR record not found |
2020-02-10 21:58:18 |
| 222.186.30.167 | attackbots | Feb 10 14:28:15 marvibiene sshd[12409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.167 user=root Feb 10 14:28:17 marvibiene sshd[12409]: Failed password for root from 222.186.30.167 port 38347 ssh2 Feb 10 14:28:19 marvibiene sshd[12409]: Failed password for root from 222.186.30.167 port 38347 ssh2 Feb 10 14:28:15 marvibiene sshd[12409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.167 user=root Feb 10 14:28:17 marvibiene sshd[12409]: Failed password for root from 222.186.30.167 port 38347 ssh2 Feb 10 14:28:19 marvibiene sshd[12409]: Failed password for root from 222.186.30.167 port 38347 ssh2 ... |
2020-02-10 22:36:04 |
| 117.218.41.27 | attackbots | Unauthorized connection attempt detected from IP address 117.218.41.27 to port 445 |
2020-02-10 22:28:30 |
| 192.163.207.48 | attackbotsspam | Feb 10 04:08:19 auw2 sshd\[22959\]: Invalid user lbo from 192.163.207.48 Feb 10 04:08:19 auw2 sshd\[22959\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.coachquoter.co.uk Feb 10 04:08:20 auw2 sshd\[22959\]: Failed password for invalid user lbo from 192.163.207.48 port 44088 ssh2 Feb 10 04:11:14 auw2 sshd\[23343\]: Invalid user kyj from 192.163.207.48 Feb 10 04:11:14 auw2 sshd\[23343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.coachquoter.co.uk |
2020-02-10 22:11:28 |
| 190.147.159.34 | attackspam | Feb 10 14:41:12 MK-Soft-Root2 sshd[9299]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.147.159.34 Feb 10 14:41:15 MK-Soft-Root2 sshd[9299]: Failed password for invalid user cxc from 190.147.159.34 port 45669 ssh2 ... |
2020-02-10 22:22:52 |
| 220.170.52.133 | attackbots | ICMP MH Probe, Scan /Distributed - |
2020-02-10 22:07:18 |
| 206.189.139.17 | attackspam | $f2bV_matches |
2020-02-10 22:04:08 |
| 95.108.181.123 | attackspambots | [Mon Feb 10 20:41:27.163428 2020] [:error] [pid 26763:tid 139998917191424] [client 95.108.181.123:50201] [client 95.108.181.123] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XkFdh-a54sPagQy5v9zFVgAAAAI"] ... |
2020-02-10 22:34:34 |
| 191.193.236.108 | attackspambots | Feb 10 14:46:18 dedicated sshd[20073]: Invalid user ekn from 191.193.236.108 port 57250 |
2020-02-10 21:59:41 |
| 118.161.170.160 | attackbots | 20/2/10@08:41:51: FAIL: IoT-Telnet address from=118.161.170.160 ... |
2020-02-10 21:57:13 |
| 212.73.68.142 | attack | Unauthorised access (Feb 10) SRC=212.73.68.142 LEN=40 TTL=248 ID=37890 TCP DPT=445 WINDOW=1024 SYN |
2020-02-10 21:56:12 |
| 217.128.165.168 | attackspam | Currently 25 failed/unauthorized logins attempts via SMTP/IMAP whostnameh 1 different usernames and wrong password: 2020-02-10T14:40:19+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:09:26+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:09:21+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:09:12+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:09:06+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:08:57+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:08:52+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:08:44+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-02-10T14:08:38+01:00 Access from 217.128.165.168 whostnameh username "1" (Unknown account) 2020-........ ------------------------------ |
2020-02-10 22:10:18 |
| 170.210.136.56 | attack | $f2bV_matches |
2020-02-10 22:24:18 |
| 118.169.247.230 | attackspambots | Port probing on unauthorized port 23 |
2020-02-10 22:34:15 |
| 27.78.14.83 | attack | SSH brute-force: detected 10 distinct usernames within a 24-hour window. |
2020-02-10 22:25:15 |