voyeurzz.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked5 years old
20
voyeurzz.com was registered on 7 Jun 2021 via eNom, LLC and the registry expiry is 7 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
voyeurzz.com publishes 6 nameservers. DNSSEC is not signed.
voyeurzz.com has 1 IPv4 address (162.216.242.208) and 1 IPv6 address (2602:ff23:0:8888::208). The geolocation database places 162.216.242.208 in Phoenix, United States.
Domain · RDAP/WHOIS
voyeurzz.com was registered on 7 Jun 2021 via eNom, LLC. The registry returned 1 status value and 5 nameservers from https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
| Registered | since 7 Jun 2021 |
|---|---|
| Created | 7 June 2021 |
| Updated | 16 May 2026 |
| Expires | 7 June 2027 |
| Registrar | eNom, LLC |
| Status | client transfer prohibited |
| Nameservers | ns1.dynu.com, ns2.dynu.com, ns3.dynu.com, ns4.dynu.com, ns5.dynu.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/voyeurzz.com |
voyeurzz.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver ns1.dynu.com is published for voyeurzz.com in the registration record from https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
Nameserver ns2.dynu.com is published for voyeurzz.com in the registration record from https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
Nameserver ns3.dynu.com is published for voyeurzz.com in the registration record from https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
Nameserver ns4.dynu.com is published for voyeurzz.com in the registration record from https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
Nameserver ns5.dynu.com is published for voyeurzz.com in the registration record from https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
DNS
voyeurzz.com has 2 address records, 1 mail exchanger and 6 nameservers, measured at 1.1.1.1:53.
| A | 162.216.242.208 |
|---|---|
| AAAA | 2602:ff23:0:8888::208 |
| NS | ns1.dynu.com, ns2.dynu.com, ns3.dynu.com, ns4.dynu.com, ns5.dynu.com, ns6.dynu.com |
| MX | mail.voyeurzz.com (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at voyeurzz.com is "v=spf1 a mx ip4:162.248.227.241 -all".
IPv4 address 162.216.242.208 answers for voyeurzz.com at resolver 1.1.1.1:53.
IPv6 address 2602:ff23:0:8888::208 answers for voyeurzz.com at resolver 1.1.1.1:53.
Mail exchanger mail.voyeurzz.com has preference 0.
A random label under voyeurzz.com also resolved, which means wildcard DNS is on.
Hosting and geo
voyeurzz.com is placed in Phoenix, United States by the local geolocation database (db-ip).
| Address | 162.216.242.208 |
|---|---|
| Country | United States |
| City | Phoenix |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for voyeurzz.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 162.216.242.208:443: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for voyeurzz.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for voyeurzz.com. That resolver covers adult and malware names.
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Phoenix.
- October 2026: geo country changed from empty to United States.
Questions
Is voyeurzz.com safe?
Cloudflare family DNS returned a block for voyeurzz.com. That resolver covers adult and malware names.
Who hosts voyeurzz.com?
voyeurzz.com is placed in Phoenix, United States.
When does voyeurzz.com expire?
voyeurzz.com expires on 7 June 2027 according to https://rdap.verisign.com/com/v1/domain/voyeurzz.com.
Who owns voyeurzz.com?
The registry did not return a person or a company for voyeurzz.com. RDAP often redacts the registrant. The registrar on file is eNom, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/voyeurzz.com at 2026-10-30T14:19:24Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:19:24Z
- TLS source tls:443 at 2026-10-30T14:19:24Z
- HTTP source https://voyeurzz.com/ at 2026-10-30T14:19:24Z
- Tech source not available at 2026-10-30T14:19:24Z
- Geo source db-ip at 2026-10-30T14:19:24Z
- Safety source family DNS and local lists at 2026-10-30T14:19:24Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.