Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations75 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryCloudflareREVIEW
A+DNS Records3 A records, 5 ms lookupPASS
| A | 172.67.97.131, 104.25.118.19, 104.25.119.19 |
| AAAA | 2606:4700:20::6819:7613, 2606:4700:20::6819:7713, 2606:4700:20::ac43:6183 |
| CNAME | — |
| NS | liv.ns.cloudflare.com, joel.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | facebook-domain-verification=92cs1l5ybjhtc56h3ro4tkvygq56qy google-site-verification=bki4cRjobXU4jBc936x6zLnL5Y9Tan2ioW8f0QXULZE google-site-verification=eZlXaNBHj61LxRj-aMHALRIXut8Fdy3wrJNsDP_mLwA google-site-verification=fNliJRKj6pIsMzFztkh3OYxVsU2kcjrp3m-Q6NFixNg google-site-verification=qksbCaau2ZN99mrILdCqYoUnHHdW8VjWVtTDv32kvY8 google-site-verification=sfFRFysAKnYyOdDzA-pnQukdWyvEs2eLIBbq3r8Smxo SPF v=spf1 ip4:208.117.50.171 ip4:74.63.247.110 ip4:50.31.44.75 ip4:192.254.123.144 ... |
| 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.
A+Redirect Chain0 redirect(s), 21 ms totalPASS
https://commonsensemedia.org
21 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://commonsensemedia.org | 403 | 21 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecommonsensemedia.org — via GoDaddy.com, LLC, 23 years, 5 months oldPASS
1685 days
February 27, 2031
75 days
Issued by Let's Encrypt
23 years, 5 months
Registered February 27, 2003
Enabled
Protects against DNS spoofing
Unknown
2606:4700:20::6819:7713
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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