maturerape.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
maturerape.com was registered on 17 Dec 2015 via NameSilo, LLC and the registry expiry is 17 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/maturerape.com.
maturerape.com publishes 2 nameservers. DNSSEC is not signed.
maturerape.com has 2 IPv4 addresses (104.21.79.54, 172.67.142.99) and 2 IPv6 addresses (2606:4700:3032::6815:4f36, 2606:4700:3037::ac43:8e63). The geolocation database places 104.21.79.54 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 60 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
maturerape.com was registered on 17 Dec 2015 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/maturerape.com.
| Registered | since 17 Dec 2015 |
|---|---|
| Created | 17 December 2015 |
| Updated | 5 November 2025 |
| Expires | 17 December 2026 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | eugene.ns.cloudflare.com, mina.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/maturerape.com |
maturerape.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 eugene.ns.cloudflare.com is published for maturerape.com in the registration record from https://rdap.verisign.com/com/v1/domain/maturerape.com.
Nameserver mina.ns.cloudflare.com is published for maturerape.com in the registration record from https://rdap.verisign.com/com/v1/domain/maturerape.com.
maturerape.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.79.54, 172.67.142.99 |
|---|---|
| AAAA | 2606:4700:3032::6815:4f36, 2606:4700:3037::ac43:8e63 |
| NS | eugene.ns.cloudflare.com, mina.ns.cloudflare.com |
| MX | — |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at maturerape.com is "v=spf1 -all".
The DMARC text record at _dmarc.maturerape.com is "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;".
IPv4 address 104.21.79.54 answers for maturerape.com at resolver 1.1.1.1:53.
IPv4 address 172.67.142.99 answers for maturerape.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::6815:4f36 answers for maturerape.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:8e63 answers for maturerape.com at resolver 1.1.1.1:53.
maturerape.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.79.54 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for maturerape.com is valid, with 60 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | maturerape.com |
| Valid from | 1 October 2026 |
| Valid until | 30 December 2026 |
| Days left | 60 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.maturerape.com, maturerape.com.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 97 ms. The target title is 25 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 97 ms |
| Title length | 25 yes |
| Quoted title | "MATURE RAPE - Porn Videos" |
| Meta description | "Mature women getting raped and tormented on video. Watch helpless sexy moms get kidnapped, restrained and hard fucked." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://maturerape.com/ |
| Language | en-us |
| Links | 77 |
| Images | 59 |
| 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 maturerape.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 maturerape.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.
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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for maturerape.com. That resolver covers adult and malware names.
maturerape.com is placed in Toronto, Canada.
maturerape.com expires on 17 December 2026 according to https://rdap.verisign.com/com/v1/domain/maturerape.com.
The registry did not return a person or a company for maturerape.com. RDAP often redacts the registrant. The registrar on file is NameSilo, 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.