Stack playbook · Snapshot 23 October 2026
Angular on Amazon CloudFront: readiness playbook
What 122 measured sites on this stack get right, where they fall short, and the Angular on Amazon CloudFront-specific steps that close each gap.
- Sites measured
- 122
- Median readiness index
- 72/100
- Profiles on this stack
- 22
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
87/100
All sites 77
Harden
60/100
All sites 55
Accelerate
71/100
All sites 63
Recover
12/100
All sites 11
The Angular on Amazon CloudFront playbook
Gaps ordered by impact, with the platform-specific step where one exists.
security.txt published
4.2% observed · all sites 5.5%
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
9.8% observed · all sites 11%
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
44% 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
DMARC policy enforces quarantine or reject
44% observed · all sites 31%
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.
HTTP/3 advertised
21% observed · all sites 36%
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.
HSTS kept for at least a year
59% observed · all sites 31%
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.
DNSSEC signed
4.9% observed · all sites 8.1%
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
Certificate lifetime of 100 days or less
5.8% observed · all sites 75%
Move to automated issuance and renewal now, while you still have time to test it.
Where Angular on Amazon CloudFront sites lead
- No render-blocking scripts in <head>76% observedall sites 44%
- HSTS kept for at least a year59% observedall sites 31%
- Referrer-Policy set43% observedall sites 23%
- Canonical URL declared88% observedall sites 70%