maturesaged.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200Family DNS blockedSSL: 84 days left18 years oldTranco #852491

One re-check per domain each UTC day.

50

maturesaged.com was registered on 28 May 2008 via NameSilo, LLC and the registry expiry is 28 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/maturesaged.com.

maturesaged.com publishes 2 nameservers. DNSSEC is not signed.

maturesaged.com has 1 IPv4 address (192.133.138.49). The geolocation database places 192.133.138.49 in Sunnyvale, United States.

The TLS certificate from YR2 is valid and has 84 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Nginx. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

maturesaged.com was registered on 28 May 2008 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/maturesaged.com.

Registeredsince 28 May 2008
Created28 May 2008
Updated27 March 2026
Expires28 May 2027
RegistrarNameSilo, LLC
Statusclient transfer prohibited
Nameserversns1.wifewoman.com, ns2.wifewoman.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/maturesaged.com

maturesaged.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.wifewoman.com is published for maturesaged.com in the registration record from https://rdap.verisign.com/com/v1/domain/maturesaged.com.

Nameserver ns2.wifewoman.com is published for maturesaged.com in the registration record from https://rdap.verisign.com/com/v1/domain/maturesaged.com.

DNS

maturesaged.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A192.133.138.49
AAAA—
NSns1.wifewoman.com, ns2.wifewoman.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 192.133.138.49 answers for maturesaged.com at resolver 1.1.1.1:53.

Hosting and geo

maturesaged.com is placed in Sunnyvale, United States by the local geolocation database (db-ip).

Address192.133.138.49
CountryUnited States
CitySunnyvale
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for maturesaged.com is valid, with 84 days left and 2 subject alternative names. Source: tls:443.

IssuerYR2
Subjectmaturesaged.com
Valid from25 October 2026
Valid until23 January 2027
Days left84
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: maturesaged.com, www.maturesaged.com.

Tech stack

Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.

  • Nginx · Web servers, Reverse proxies

Nginx is filed under Web servers, Reverse proxies.

On-page checks

The homepage returned HTTP 200 in 155 ms. The target title is 77 characters and the page has 0 H1 headings.

Status200
TTFB155 ms
Title length77 no
Quoted title"Nude Aged Women Pics | Horny Mature XXX Photos & Mature Older Women Galleries"
Meta description"Discover the best collection of nude aged women pics and horny mature XXX photos. Explore stunning galleries of mature older women in high-quality porn pics." yes
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Languageen
Links354
Images290
Faviconyes

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 maturesaged.com is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for maturesaged.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 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 Sunnyvale.
  • October 2026: geo country changed from empty to United States.

Questions

Is maturesaged.com safe?

Cloudflare family DNS returned a block for maturesaged.com. That resolver covers adult and malware names.

Who hosts maturesaged.com?

maturesaged.com is placed in Sunnyvale, United States.

When does maturesaged.com expire?

maturesaged.com expires on 28 May 2027 according to https://rdap.verisign.com/com/v1/domain/maturesaged.com.

Who owns maturesaged.com?

The registry did not return a person or a company for maturesaged.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/maturesaged.com at 2026-10-30T14:03:35Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:03:35Z
  • TLS source tls:443 at 2026-10-30T14:03:35Z
  • HTTP source https://maturesaged.com/ at 2026-10-30T14:03:35Z
  • Tech source wappalyzergo at 2026-10-30T14:03:35Z
  • Geo source db-ip at 2026-10-30T14:03:35Z
  • Safety source family DNS and local lists at 2026-10-30T14:03:35Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com NameSilo, LLC

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.

Removal policy

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.