Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DHTTP Probe TimingActionTotal 2175 ms — DNS, TCP, TLS, TTFB, content transfer breakdownFIX
Connection waterfall
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BTLS Certificate Expiry & Recommendations74 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 19 ms lookupPASS
| A | 104.21.23.31, 172.67.208.120 |
| AAAA | 2606:4700:3030::6815:171f, 2606:4700:3030::ac43:d078 |
| CNAME | — |
| NS | carter.ns.cloudflare.com, rafe.ns.cloudflare.com |
| MX | — |
| TXT | ahrefs-site-verification_da8c986399a76ae49857083416a506dfba01f8ce451349aac534002... SPF v=spf1 +a +mx +a:thepornguy.org -all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
ACAA Recordsissue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.comPASS
A+Multi-Resolver DNS SpeedMean 5ms across 3 resolvers (spread 5ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://thepornguy.org
2060 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://thepornguy.org | 200 | 2060 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 10 URLsPASS
User-agent: *
Allow: /
Disallow: *?utm_medium=*
Disallow: *?utm_content=*
Disallow: *?utm_source=*
Disallow: *?replytocom*
Disallow: *?s=*
Disallow: /search/*
Disallow: *?p=*
Disallow: *?q=*
Disallow: *?k=*
Disallow: *?l=*
Disallow: *?lang=*
Disallow: *?page_id=*
Disallow: *?*.xml
Disallow: *?hl=*
Disallow: *?in=*
Disallow: *?with=*
Disallow: *?channel=*
Disallow: *?1$
Disallow: */page/*?s$
Disallow: /*/*_gp*
Disallow: *?unapproved=*
Disallow: *?from=*
Disallow: *?by=*
Disallow: *?redirect_to=*
Disallow: /*/feed/*
Disallow: /cdn-cgi*
Disallow: /wp-json
Disallow: /author/*
Disallow: /tag/*
Disallow: /category/*
Disallow: /pornstar/*
Disallow: /studio/*
Disallow: /dvd/*
Disallow: /video/*
Disallow: *?swcfpc=*
Disallow: *?attachment_id*
Disallow: /.well-known/*
User-agent: *
Disallow: /da/
Disallow: /fi/
Disallow: /ar/
Disallow: /nb/
User-agent: AhrefsBot
Allow: /
User-agent: AhrefsSiteAudit
Allow: /
User-agent: AnthropicBot
Disallow: /
User-agent: Claude
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-Agent: FacebookBot
Disallow: /
Sitemap: https://thepornguy.org/sitemap_index.xml
Sitemap: https://thepornguy.org/priority-pages.php
- https://thepornguy.org/post-sitemap.xml
- https://thepornguy.org/page-sitemap.xml
- https://thepornguy.org/page-sitemap2.xml
- https://thepornguy.org/page-sitemap3.xml
- https://thepornguy.org/page-sitemap4.xml
- https://thepornguy.org/page-sitemap5.xml
- https://thepornguy.org/page-sitemap6.xml
- https://thepornguy.org/page-sitemap7.xml
- https://thepornguy.org/page-sitemap8.xml
- https://thepornguy.org/page-sitemap9.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencethepornguy.org — via GoDaddy.com, LLC, 7 years, 5 months oldPASS
963 days
March 11, 2029
74 days
Issued by Google Trust Services
7 years, 5 months
Registered March 11, 2019
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3030::6815:171f
GoDaddy.com, LLC
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