amateurwifeshared.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: -643 days left7 years old
15
amateurwifeshared.com was registered on 12 Sep 2019 via NameSilo, LLC and the registry expiry is 12 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/amateurwifeshared.com.
amateurwifeshared.com publishes 2 nameservers. DNSSEC is not signed.
amateurwifeshared.com has 1 IPv4 address (162.254.191.223). The geolocation database places 162.254.191.223 in Phoenix (Southbank), United States.
The TLS certificate from R11 is not valid (TLS 1.3).
Domain · RDAP/WHOIS
amateurwifeshared.com was registered on 12 Sep 2019 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/amateurwifeshared.com.
| Registered | since 12 Sep 2019 |
|---|---|
| Created | 12 September 2019 |
| Updated | 11 September 2026 |
| Expires | 12 September 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | ns1.hostiservices.com, ns2.hostiservices.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/amateurwifeshared.com |
amateurwifeshared.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.hostiservices.com is published for amateurwifeshared.com in the registration record from https://rdap.verisign.com/com/v1/domain/amateurwifeshared.com.
Nameserver ns2.hostiservices.com is published for amateurwifeshared.com in the registration record from https://rdap.verisign.com/com/v1/domain/amateurwifeshared.com.
DNS
amateurwifeshared.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.254.191.223 |
|---|---|
| AAAA | — |
| NS | ns1.hostiservices.com, ns2.hostiservices.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 162.254.191.223 answers for amateurwifeshared.com at resolver 1.1.1.1:53.
Hosting and geo
amateurwifeshared.com is placed in Phoenix (Southbank), United States by the local geolocation database (db-ip).
| Address | 162.254.191.223 |
|---|---|
| Country | United States |
| City | Phoenix (Southbank) |
| Source | db-ip |
SSL/TLS
The certificate for amateurwifeshared.com is not valid, with -643 days left and 2 subject alternative names. Source: tls:443.
| Issuer | R11 |
|---|---|
| Subject | wivesthatfuck.com |
| Valid from | 27 October 2024 |
| Valid until | 25 January 2025 |
| Days left | -643 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: wivesthatfuck.com, www.wivesthatfuck.com.
Validation result: certificate did not validate
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://amateurwifeshared.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T13:44:10Z is after 2025-01-25T20:19:30Z
Security
Family DNS for amateurwifeshared.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 amateurwifeshared.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 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 Phoenix (Southbank).
- October 2026: geo country changed from empty to United States.
Questions
Is amateurwifeshared.com safe?
Cloudflare family DNS returned a block for amateurwifeshared.com. That resolver covers adult and malware names.
Who hosts amateurwifeshared.com?
amateurwifeshared.com is placed in Phoenix (Southbank), United States.
When does amateurwifeshared.com expire?
amateurwifeshared.com expires on 12 September 2027 according to https://rdap.verisign.com/com/v1/domain/amateurwifeshared.com.
Who owns amateurwifeshared.com?
The registry did not return a person or a company for amateurwifeshared.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/amateurwifeshared.com at 2026-10-30T13:44:10Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:44:10Z
- TLS source tls:443 at 2026-10-30T13:44:10Z
- HTTP source https://amateurwifeshared.com/ at 2026-10-30T13:44:10Z
- Tech source not available at 2026-10-30T13:44:10Z
- Geo source db-ip at 2026-10-30T13:44:10Z
- Safety source family DNS and local lists at 2026-10-30T13:44:10Z
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.