ourhotwives.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
ourhotwives.org was registered on 28 Aug 2005 via eNom, LLC and the registry expiry is 28 Aug 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
ourhotwives.org publishes 5 nameservers. DNSSEC is not signed.
ourhotwives.org has 1 IPv4 address (198.49.71.166). The geolocation database places 198.49.71.166 in Orlando, United States.
The TLS certificate from YR1 is valid and has 32 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Nginx and Ubuntu. The fingerprints ran on the homepage that was already downloaded.
ourhotwives.org was registered on 28 Aug 2005 via eNom, LLC. The registry returned 1 status value and 5 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
| Registered | since 28 Aug 2005 |
|---|---|
| Created | 28 August 2005 |
| Updated | 12 August 2026 |
| Expires | 28 August 2027 |
| Registrar | eNom, LLC |
| Status | client transfer prohibited |
| Nameservers | dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org |
ourhotwives.org 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.name-services.com is published for ourhotwives.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
Nameserver dns2.name-services.com is published for ourhotwives.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
Nameserver dns3.name-services.com is published for ourhotwives.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
Nameserver dns4.name-services.com is published for ourhotwives.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
Nameserver dns5.name-services.com is published for ourhotwives.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
ourhotwives.org has 1 address record, 1 mail exchanger and 5 nameservers, measured at 1.1.1.1:53.
| A | 198.49.71.166 |
|---|---|
| AAAA | — |
| NS | dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com |
| MX | ourhotwives.org (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at ourhotwives.org is "v=spf1 a mx ip4:198.49.71.166 ~all".
The DMARC text record at _dmarc.ourhotwives.org is "v=DMARC1; p=reject".
IPv4 address 198.49.71.166 answers for ourhotwives.org at resolver 1.1.1.1:53.
Mail exchanger ourhotwives.org has preference 10.
ourhotwives.org is placed in Orlando, United States by the local geolocation database (db-ip).
| Address | 198.49.71.166 |
|---|---|
| Country | United States |
| City | Orlando |
| Source | db-ip |
The certificate for ourhotwives.org is valid, with 32 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | ourhotwives.org |
| Valid from | 3 September 2026 |
| Valid until | 2 December 2026 |
| Days left | 32 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: ourhotwives.org, www.ourhotwives.org.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Nginx is filed under Web servers, Reverse proxies.
Ubuntu is filed under Operating systems.
The homepage returned HTTP 200 in 116 ms. The target title is 20 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 116 ms |
| Title length | 20 yes |
| Quoted title | "Your Hot Wives Forum" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 1 |
| Images | 1 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for ourhotwives.org 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 ourhotwives.org. 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.
Availability 25 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 10 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.
Cloudflare family DNS returned a block for ourhotwives.org. That resolver covers adult and malware names.
ourhotwives.org is placed in Orlando, United States.
ourhotwives.org expires on 28 August 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/ourhotwives.org.
The registry did not return a person or a company for ourhotwives.org. RDAP often redacts the registrant. The registrar on file is eNom, LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.