Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /*/media
Disallow: /*/photos
Disallow: /*/videos
Disallow: /*/audios
Disallow: /*/likes
Disallow: /*/streams
Disallow: /*/upcoming-streams
BTLS Certificate Expiry & Recommendations63 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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
ADNS Records2 A records, 1030 ms lookupPASS
| A | 172.66.0.144, 162.159.140.146 |
| AAAA | — |
| CNAME | — |
| NS | ns-1697.awsdns-20.co.uk, ns-713.awsdns-25.net, ns-1381.awsdns-44.org, ns-158.awsdns-19.com |
| MX | 10 inbound-smtp.us-east-1.amazonaws.com |
| TXT | google-site-verification=cCYazcwl39IyKOjENTcydGP_hx-QM0IRj7jTEx5ZZls h1-domain-verification=gMHMAJkqUQ5736hpkAUd7ZwP4z1g1HLivwwjL9RWbF8jy6YM dlyyb13d2kwy4tc0qq56mfgdjpt7mlzw facebook-domain-verification=t4v612fq7qxhqypi627dn5zumlwag2 SPF v=spf1 +a +mx ip4:3.226.227.91 ip4:54.175.88.73 ip4:18.232.46.215 include:amazon... google-site-verification=pe0Tbj-4J9WcdPWMmKN9A23JBxS7Q_v0yNXs26GQ2Lk atlassian-domain-verification=puayH7wgeQrYnWGVFbP9PHjbcqrPuVh2JmVvjT7a4pgg9wKALo... MS=A1ABFEB5CA2E639421538B196FFF5EB1DBAE0FB7 google-site-verification=vwksrAgGYSO0CRDHi-GL5zUbuXYl63RrHh6lQTCX0FA _globalsign-domain-verification=eemA9F_UsK0bGrGGm2wfKCLw_pen3ByIq06fk2SjZe facebook-domain-verification=7jovorxjgyt0xc5dbw5rjxyrogoglu docusign=282ecea0-1005-448e-98dc-b73eeb8ea750 google-site-verification=2sM2u2738SgRyoEv08B_k1c1Hdy6NEP6kgZbqW8L8DI" ": ca3-de336f9c3eea41d182c58a0e383506c2 MS=ms58770879 google-site-verification=YdGOLeW5196Q7EO8CSEFulXKVsJOGCz5wtgCUJdC6qU |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Redirect ChainNo redirects — direct accessPASS
https://onlyfans.com
166 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://onlyfans.com | 200 | 166 ms | HTTP/1.1 | cloudflare |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceonlyfans.com — via GoDaddy Corporate Domains, LLC, 13 years, 4 months old, hosted on CloudflarePASS
3122 days
January 29, 2035
63 days
Issued by Let's Encrypt
13 years, 4 months
Registered January 29, 2013
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
162.159.140.146
GoDaddy Corporate Domains, 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