3xxhamsters.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 63 days left10 years old
35
3xxhamsters.com was registered on 13 Apr 2016 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 13 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/3xxhamsters.com.
3xxhamsters.com publishes 4 nameservers. DNSSEC is not signed.
3xxhamsters.com has 1 IPv4 address (185.149.133.12). The geolocation database places 185.149.133.12 in Amsterdam, The Netherlands.
The TLS certificate from YR1 is valid and has 63 days left (TLS 1.3).
Domain · RDAP/WHOIS
3xxhamsters.com was registered on 13 Apr 2016 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/3xxhamsters.com.
| Registered | since 13 Apr 2016 |
|---|---|
| Created | 13 April 2016 |
| Updated | 8 April 2026 |
| Expires | 13 April 2027 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | dns1.regway.com, dns2.regway.com, dns3.regway.com, dns4.regway.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/3xxhamsters.com |
3xxhamsters.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 dns1.regway.com is published for 3xxhamsters.com in the registration record from https://rdap.verisign.com/com/v1/domain/3xxhamsters.com.
Nameserver dns2.regway.com is published for 3xxhamsters.com in the registration record from https://rdap.verisign.com/com/v1/domain/3xxhamsters.com.
Nameserver dns3.regway.com is published for 3xxhamsters.com in the registration record from https://rdap.verisign.com/com/v1/domain/3xxhamsters.com.
Nameserver dns4.regway.com is published for 3xxhamsters.com in the registration record from https://rdap.verisign.com/com/v1/domain/3xxhamsters.com.
DNS
3xxhamsters.com has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 185.149.133.12 |
|---|---|
| AAAA | — |
| NS | dns1.regway.com, dns2.regway.com, dns3.regway.com, dns4.regway.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.149.133.12 answers for 3xxhamsters.com at resolver 1.1.1.1:53.
Hosting and geo
3xxhamsters.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 185.149.133.12 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for 3xxhamsters.com is valid, with 63 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | 3xxhamsters.com |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 63 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: 3xxhamsters.com, www.3xxhamsters.com.
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 |
|---|
Get "https://3xxhamsters.com/": stream error: stream ID 1; PROTOCOL_ERROR; received from peer
Security
Family DNS for 3xxhamsters.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 3xxhamsters.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 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 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 Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is 3xxhamsters.com safe?
Cloudflare family DNS returned a block for 3xxhamsters.com. That resolver covers adult and malware names.
Who hosts 3xxhamsters.com?
3xxhamsters.com is placed in Amsterdam, The Netherlands.
When does 3xxhamsters.com expire?
3xxhamsters.com expires on 13 April 2027 according to https://rdap.verisign.com/com/v1/domain/3xxhamsters.com.
Who owns 3xxhamsters.com?
The registry did not return a person or a company for 3xxhamsters.com. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/3xxhamsters.com at 2026-10-30T13:41:29Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:41:29Z
- TLS source tls:443 at 2026-10-30T13:41:29Z
- HTTP source https://3xxhamsters.com/ at 2026-10-30T13:41:29Z
- Tech source not available at 2026-10-30T13:41:29Z
- Geo source db-ip at 2026-10-30T13:41:29Z
- Safety source family DNS and local lists at 2026-10-30T13:41:29Z
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.