milfxteen.com

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

Online · 200Family DNS blockedSSL: 45 days left3 years old

One re-check per domain each UTC day.

55

milfxteen.com was registered on 5 May 2023 via TurnCommerce, Inc. DBA NameBright.com and the registry expiry is 5 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/milfxteen.com.

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

milfxteen.com has 2 IPv4 addresses (13.223.25.84, 54.243.117.197) and 2 IPv6 addresses (2600:1f18:4ae:c605:dd5d:b838:5816:d7fb, 2600:1f18:4ae:c606:78d4:4260:db4e:aeee). The geolocation database places 13.223.25.84 in Ashburn, United States.

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

Tech detection named Adobe Fonts, Cloudflare, CookieYes, Google Analytics, Microsoft ASP.NET, Typekit, YouTube, jQuery and reCAPTCHA. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

milfxteen.com was registered on 5 May 2023 via TurnCommerce, Inc. DBA NameBright.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/milfxteen.com.

Registeredsince 5 May 2023
Created5 May 2023
Updated15 June 2026
Expires5 May 2027
RegistrarTurnCommerce, Inc. DBA NameBright.com
Statusclient transfer prohibited
Nameserversnsg1.namebrightdns.com, nsg2.namebrightdns.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/milfxteen.com

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

Nameserver nsg2.namebrightdns.com is published for milfxteen.com in the registration record from https://rdap.verisign.com/com/v1/domain/milfxteen.com.

DNS

milfxteen.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A13.223.25.84, 54.243.117.197
AAAA2600:1f18:4ae:c605:dd5d:b838:5816:d7fb, 2600:1f18:4ae:c606:78d4:4260:db4e:aeee
NSnsg1.namebrightdns.com, nsg2.namebrightdns.com
MX—
SPFpresent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at milfxteen.com is "v=spf1 -all".

IPv4 address 13.223.25.84 answers for milfxteen.com at resolver 1.1.1.1:53.

IPv4 address 54.243.117.197 answers for milfxteen.com at resolver 1.1.1.1:53.

IPv6 address 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb answers for milfxteen.com at resolver 1.1.1.1:53.

IPv6 address 2600:1f18:4ae:c606:78d4:4260:db4e:aeee answers for milfxteen.com at resolver 1.1.1.1:53.

A random label under milfxteen.com also resolved, which means wildcard DNS is on.

Hosting and geo

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

Address13.223.25.84
CountryUnited States
CityAshburn
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerYE1
Subjectmilfxteen.com
Valid from16 September 2026
Valid until15 December 2026
Days left45
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.milfxteen.com, milfxteen.com.

Tech stack

Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.

  • Adobe Fonts · Font scripts
  • Cloudflare · CDN
  • CookieYes · Cookie compliance
  • Google Analytics · Analytics
  • Microsoft ASP.NET · Web frameworks
  • Typekit · Font scripts
  • YouTube · Video players
  • jQuery · JavaScript libraries
  • reCAPTCHA · Security

Adobe Fonts is filed under Font scripts.

Cloudflare is filed under CDN.

CookieYes is filed under Cookie compliance.

Google Analytics is filed under Analytics.

Microsoft ASP.NET is filed under Web frameworks.

Typekit is filed under Font scripts.

YouTube is filed under Video players.

jQuery is filed under JavaScript libraries.

reCAPTCHA is filed under Security.

On-page checks

The homepage returned HTTP 200 in 98 ms. The target title is 39 characters and the page has 1 H1 heading.

Status200
TTFB98 ms
Title length39 yes
Quoted title"MilfxTeen.com is for sale | HugeDomains"
Meta description"Easy, affordable options for you to obtain the domain you want. Safe and secure shopping." yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonicalhttps://www.hugeDomains.com/domain_profile.cfm?d=MilfxTeen.com
Languageen
Links63
Images17
Faviconno

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 milfxteen.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 milfxteen.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 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: tls issuer changed from empty to YE1.
  • October 2026: tls not_after changed from empty to 2026-12-15T08:18:21Z.
  • October 2026: tls protocol changed from empty to TLS 1.3.
  • October 2026: tls valid changed from false to true.
  • October 2026: http status_class changed from empty to 2xx.
  • October 2026: tech added Adobe Fonts.
  • October 2026: tech added Cloudflare.
  • October 2026: tech added CookieYes.
  • October 2026: tech added Google Analytics.
  • October 2026: tech added Microsoft ASP.NET.
  • October 2026: tech added Typekit.
  • October 2026: tech added YouTube.
  • October 2026: tech added jQuery.
  • October 2026: tech added reCAPTCHA.
  • October 2026: geo city changed from empty to Ashburn.
  • October 2026: geo country changed from empty to United States.

Questions

Is milfxteen.com safe?

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

Who hosts milfxteen.com?

milfxteen.com is placed in Ashburn, United States.

When does milfxteen.com expire?

milfxteen.com expires on 5 May 2027 according to https://rdap.verisign.com/com/v1/domain/milfxteen.com.

Who owns milfxteen.com?

The registry did not return a person or a company for milfxteen.com. RDAP often redacts the registrant. The registrar on file is TurnCommerce, Inc. DBA NameBright.com.

Sources

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

Methodology

Related reports

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

.com TurnCommerce, Inc. DBA NameBright.com

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.