Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
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 & Recommendations169 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
A+DNS Records1 A records, 52 ms lookupPASS
| A | 34.85.147.204 |
| AAAA | — |
| CNAME | — |
| NS | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | varnish-group=2 MS=ms87800513 3600 _5u97qc6xguz881jz4fscoj5t8yc4ztw _6n18c3tu5kctyxvhaf5wgs3fgpoyt9h ZOOM_verify_c_5ZM5v4SF-7g3M1mbSgfQ adobe-sign-verification=d42aacceb0cdcd44286532fa2d19780 knowbe4-site-verification=d6e44116a749b1f61f1d7bc9f3e4b677 google-site-verification=Hdn7mz4jHIwDNtSlWjOSE7pVr3EVG76SHGwujsg9Npo google-site-verification=Pfe4ATKIkMdXrGKHYCfJPW6ict-JPocai106LCiMEOw google-site-verification=aPjHVom3SlYMdPTCZVW1zhRHm1cdwcvMUpVZcEt2Lj8 google-site-verification=yef8pCp2q_gzGbxXwOphufhfx1DMzlbTZntd5Py-0Jo adobe-idp-site-verification=23a64011527341e7a0b4471230e84b44977294637c642b8b2348... tollbit-domain-verification=61aeca7ae41010315ba7998cce3a58f5b9b0203b64375282e9ad... SPF v=spf1 include:_spf.mcclatchy.com include:cust-spf.osgbilling.com ip4:205.234.4.... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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), 46 ms totalPASS
https://sacbee.com
46 ms · HTTP/1.0 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sacbee.com | 301 | 46 ms | HTTP/1.0 | BigIP |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencesacbee.com — via GoDaddy Corporate Domains, LLC, 31 years, 5 months old, hosted on Google CloudPASS
268 days
April 12, 2027
169 days
Issued by DigiCert Inc
31 years, 5 months
Registered April 11, 1995
Enabled
Protects against DNS spoofing
Google Cloud
ASN AS396982
34.85.147.204
GoDaddy Corporate Domains, 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