Stack playbook · Snapshot 23 October 2026
Blogger: readiness playbook
What 164 measured sites on this hosted platform get right, where they fall short, and the Blogger-specific steps that close each gap.
- Sites measured
- 164
- Median readiness index
- 64/100
- Profiles on this stack
- 83
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
83/100
All sites 77
Harden
49/100
All sites 56
Accelerate
62/100
All sites 64
Recover
6/100
All sites 10
The Blogger playbook
Gaps ordered by impact, with the platform-specific step where one exists.
HSTS kept for at least a year
8.5% observed · all sites 34%
Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.
DMARC policy enforces quarantine or reject
21% observed · all sites 39%
Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
security.txt published
1.3% observed · all sites 7.1%
Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
CAA records limit who can issue certificates
3.7% observed · all sites 13%
Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
Modern image formats in use
40% observed · all sites 40%
Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Framing restricted
15% observed · all sites 51%
Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
Static files cached for 30 days or more
43% observed · all sites 51%
Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
Content Security Policy present
15% observed · all sites 32%
Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Where Blogger sites lead
- Reachable over IPv667% observedall sites 48%
- Certificate lifetime of 100 days or less85% observedall sites 67%
- Canonical URL declared84% observedall sites 68%
- XML sitemap discoverable85% observedall sites 70%
A note on hosted platforms
On Blogger, the platform controls much of the TLS, header and caching configuration. Owners mostly influence content-level checks such as images, structured data, social previews and the sitemap. Header-level gaps are worth raising with the platform.