Drupal on Fastly: readiness playbook

Readiness by lane

The Drupal on Fastly playbook

Gaps ordered by impact, with the platform-specific step where one exists.

1. HSTS kept for at least a year

   44% 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 Fastly: Add the header in VCL or a header rule as described in Fastly's HSTS guide.

   Guide: HTTPS and TLS Guide for Website Owners

2. security.txt published

   2.1% 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.

   Guide: A Practical Website Health Check for Owners

3. HTTP/3 advertised

   7% observed · all sites 36%

   Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   Guide: CDN Guide for Website Owners

4. No render-blocking scripts in <head>

   26% observed · all sites 44%

   Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   Guide: Control Third-Party Scripts Before They Control Your Page

5. CAA records limit who can issue certificates

   11% 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.

   Guide: HTTPS and TLS Guide for Website Owners

6. 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

7. Content Security Policy present

   31% observed · all sites 31%

   Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Drupal: The Security Kit module includes CSP settings.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

8. DNSSEC signed

   8.7% 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

Where Drupal on Fastly sites lead

• X-Content-Type-Options: nosniff98% observedall sites 48%
• Framing restricted96% observedall sites 49%
• Static files cached for 30 days or more90% observedall sites 50%
• Reachable over IPv678% observedall sites 44%

All 31 checks on Drupal on Fastly

High-readiness Drupal on Fastly sites

• yourtango.com77
• ufc.com61

Related