Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/6 IPs match cert SANREVIEW
BTLS Certificate Expiry & Recommendations34 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Enable DNSSEC on your domain for DNS spoofing protection
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
ADNS Records3 A records, 16 ms lookupPASS
| A | 172.67.74.52, 104.26.15.207, 104.26.14.207 |
| AAAA | 2606:4700:20::681a:ecf, 2606:4700:20::681a:fcf, 2606:4700:20::ac43:4a34 |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 11ms across 3 resolvers (spread 14ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://www.thepornblender.com
146 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.thepornblender.com | 200 | 146 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 14 URLsPASS
User-agent: *
Disallow: */feed/
Disallow: /wp-content/uploads/wpo-plugins-tables-list.json
Disallow: */wp-content/themes/maddos_new_design_pstars/
Disallow: */wp-content/themes/
Disallow: /public/video/
Disallow: /wp-admin/
Disallow: /*/wp-admin/
Disallow: /cdn-cgi/
Disallow: /*/cdn-cgi/
Disallow: /feed/
Disallow: /feed/$
Disallow: /comments/feed
Disallow: /trackback/
Disallow: */?author=*
Disallow: */author/*
Disallow: /author*
Disallow: /author/
Disallow: */comments$
Disallow: */feed
Disallow: */feed$
Disallow: */trackback
Disallow: */trackback$
Disallow: /?feed=
Disallow: /wp-comments
Disallow: /wp-comments/
Disallow: /wp-feed
Disallow: /wp-trackback
Disallow: */replytocom=
Disallow: */search/*
Disallow: */livecams/*
Disallow: */discounts/*
Disallow: */amp/
Disallow: */amp/*
Disallow: */go/*
Disallow: /*?utm_
Disallow: */?s=*
Disallow: */gcnamealg.php
Disallow: /pornstarprofile/
Disallow: /*/pornstarprofile/
Allow: /wp-admin/admin-ajax.php
User-agent: ia_archiver
Disallow: /
Sitemap: https://www.thepornblender.com/sitemap_index.xml
Sitemap: https://www.thepornblender.com/post-sitemap.xml
Sitemap: https://www.thepornblender.com/post-sitemap2.xml
Sitemap: https://www.thepornblender.com/page-sitemap.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap2.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap3.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap4.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap5.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap6.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap7.xml
Sitemap: https://www.thepornblender.com/pornstar-sitemap8.xml
Sitemap: https://www.thepornblender.com/sale-sitemap.xml
Sitemap: https://www.thepornblender.com/category-sitemap.xml
- https://www.thepornblender.com/post-site...
- https://www.thepornblender.com/post-site...
- https://www.thepornblender.com/post-site...
- https://www.thepornblender.com/page-site...
- https://www.thepornblender.com/page-site...
- https://www.thepornblender.com/pornstar-...
- https://www.thepornblender.com/pornstar-...
- https://www.thepornblender.com/pornstar-...
- https://www.thepornblender.com/pornstar-...
- https://www.thepornblender.com/pornstar-...
- https://www.thepornblender.com/pornstar-...
- https://www.thepornblender.com/pornstar-...
- https://www.thepornblender.com/sale-site...
- https://www.thepornblender.com/category-...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencethepornblender.com — via Amazon Registrar, Inc., 7 years, 5 months old, hosted on CloudflarePASS
238 days
April 12, 2027
34 days
Issued by Google Trust Services
7 years, 5 months
Registered April 12, 2019
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.26.14.207
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice