xnxxmommy.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 28 days left6 years old
60
xnxxmommy.com was registered on 29 Jul 2020 via Dynadot Inc and the registry expiry is 29 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/xnxxmommy.com.
xnxxmommy.com publishes 2 nameservers. DNSSEC is not signed.
xnxxmommy.com has 2 IPv4 addresses (92.113.16.51, 92.113.23.14) and 2 IPv6 addresses (2a02:4780:84:156:ab6f:e47f:51bf:b866, 2a02:4780:84:caf6:b598:ff42:345f:f1b8). The geolocation database places 92.113.16.51 in Frankfurt am Main, Germany.
The TLS certificate from YE1 is valid and has 28 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named HTTP/3, Hostinger, Hostinger CDN, LiteSpeed, LiteSpeed Cache, Litespeed Cache, MySQL, PHP, Site Kit and WordPress. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
xnxxmommy.com was registered on 29 Jul 2020 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/xnxxmommy.com.
| Registered | since 29 Jul 2020 |
|---|---|
| Created | 29 July 2020 |
| Updated | 17 September 2026 |
| Expires | 29 July 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | ns1.dns-parking.com, ns2.dns-parking.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/xnxxmommy.com |
xnxxmommy.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.dns-parking.com is published for xnxxmommy.com in the registration record from https://rdap.verisign.com/com/v1/domain/xnxxmommy.com.
Nameserver ns2.dns-parking.com is published for xnxxmommy.com in the registration record from https://rdap.verisign.com/com/v1/domain/xnxxmommy.com.
DNS
xnxxmommy.com has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 92.113.16.51, 92.113.23.14 |
|---|---|
| AAAA | 2a02:4780:84:156:ab6f:e47f:51bf:b866, 2a02:4780:84:caf6:b598:ff42:345f:f1b8 |
| NS | ns1.dns-parking.com, ns2.dns-parking.com |
| MX | mx1.hostinger.in (5), mx2.hostinger.in (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at xnxxmommy.com is "v=spf1 include:_spf.mail.hostinger.com ~all".
IPv4 address 92.113.16.51 answers for xnxxmommy.com at resolver 1.1.1.1:53.
IPv4 address 92.113.23.14 answers for xnxxmommy.com at resolver 1.1.1.1:53.
IPv6 address 2a02:4780:84:156:ab6f:e47f:51bf:b866 answers for xnxxmommy.com at resolver 1.1.1.1:53.
IPv6 address 2a02:4780:84:caf6:b598:ff42:345f:f1b8 answers for xnxxmommy.com at resolver 1.1.1.1:53.
Mail exchanger mx1.hostinger.in has preference 5.
Mail exchanger mx2.hostinger.in has preference 10.
Hosting and geo
xnxxmommy.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 92.113.16.51 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for xnxxmommy.com is valid, with 28 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | xnxxmommy.com |
| Valid from | 31 August 2026 |
| Valid until | 29 November 2026 |
| Days left | 28 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: www.xnxxmommy.com, xnxxmommy.com.
Tech stack
Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.
- HTTP/3 · Miscellaneous
- Hostinger · Hosting
- Hostinger CDN · CDN
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- MySQL · Databases
- PHP · Programming languages
- Site Kit · Analytics, WordPress plugins
- WordPress · CMS, Blogs
HTTP/3 is filed under Miscellaneous.
Hostinger is filed under Hosting.
Hostinger CDN is filed under CDN.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Site Kit is filed under Analytics, WordPress plugins.
WordPress is filed under CMS, Blogs.
On-page checks
The homepage returned HTTP 200 in 4 ms. The target title is 25 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 4 ms |
| Title length | 25 yes |
| Quoted title | "XNXX MOMMY HOT SEX VIDEOS" |
| Meta description | "XNXX MOMMY is the mature tube on XNXXMOM HOT SEX VIDEOS, mom son porn, mom and son porn . Best free porn tube for you with romantic porn" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | — |
| Robots meta | follow, index |
| Canonical | https://xnxxmommy.com/ |
| Language | en-US |
| Links | 59 |
| Images | 30 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for xnxxmommy.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 | yes |
Cloudflare family DNS returned a block for xnxxmommy.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 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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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: dns a changed from 92.113.16.27,92.113.23.25 to 92.113.16.51,92.113.23.14.
- October 2026: dns aaaa changed from 2a02:4780:84:91f8:4ed6:c75b:5b78:37c1,2a02:4780:84:cc14:ab85:c400:e135:a7db to 2a02:4780:84:156:ab6f:e47f:51bf:b866,2a02:4780:84:caf6:b598:ff42:345f:f1b8.
- October 2026: geo city changed from empty to Frankfurt am Main.
- October 2026: geo country changed from empty to Germany.
Questions
Is xnxxmommy.com safe?
Cloudflare family DNS returned a block for xnxxmommy.com. That resolver covers adult and malware names.
Who hosts xnxxmommy.com?
xnxxmommy.com is placed in Frankfurt am Main, Germany.
When does xnxxmommy.com expire?
xnxxmommy.com expires on 29 July 2027 according to https://rdap.verisign.com/com/v1/domain/xnxxmommy.com.
Who owns xnxxmommy.com?
The registry did not return a person or a company for xnxxmommy.com. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/xnxxmommy.com at 2026-10-30T14:20:50Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:20:50Z
- TLS source tls:443 at 2026-10-30T14:20:50Z
- HTTP source https://xnxxmommy.com/ at 2026-10-30T14:20:50Z
- Tech source wappalyzergo at 2026-10-30T14:20:50Z
- Geo source db-ip at 2026-10-30T14:20:50Z
- Safety source family DNS and local lists at 2026-10-30T14:20:50Z
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.