Stack playbook · Snapshot 23 October 2026
Nuxt on Amazon CloudFront: readiness playbook
What 117 measured sites on this stack get right, where they fall short, and the Nuxt on Amazon CloudFront-specific steps that close each gap.
- Sites measured
- 117
- Median readiness index
- 73/100
- Profiles on this stack
- 87
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
84/100
All sites 77
Harden
60/100
All sites 56
Accelerate
77/100
All sites 64
Recover
22/100
All sites 10
The Nuxt on Amazon CloudFront playbook
Gaps ordered by impact, with the platform-specific step where one exists.
CAA records limit who can issue certificates
8.5% 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.
HSTS kept for at least a year
51% 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.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
security.txt published
20% 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.
DMARC policy enforces quarantine or reject
51% 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.
Certificate lifetime of 100 days or less
9.4% observed · all sites 67%
Move to automated issuance and renewal now, while you still have time to test it.
Content Security Policy present
32% 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
DNSSEC signed
11% observed · all sites 8%
Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
HTTP/3 advertised
45% observed · all sites 37%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.
Where Nuxt on Amazon CloudFront sites lead
- Modern image formats in use68% observedall sites 40%
- No render-blocking scripts in <head>67% observedall sites 48%
- Offscreen images lazy-loaded81% observedall sites 62%
- HSTS kept for at least a year51% observedall sites 34%