Skip to content
FixSecurityHeadersScan a site

How to add Strict-Transport-Security on Next.js

Last updated · Reviewed by a CISSP-certified security practitioner

To add Strict-Transport-Security on Next.js, set the header in next.config.js with the value max-age=63072000; includeSubDomains; preload. Forces browsers to only use HTTPS for your domain. Restart dev server or redeploy. Then confirm it with curl -I or a free FixSecurityHeaders scan.

What does Strict-Transport-Security do?

HSTS tells the browser to always connect over HTTPS for a set time, even if someone types http:// or clicks an old link.

Risk if missing: Without it, the first request can be downgraded to plain HTTP, letting attackers on public Wi‑Fi intercept or rewrite traffic (SSL stripping).

What is the Next.js configuration?

Add this to next.config.js:

next.config.js
// next.config.js
module.exports = {
  poweredByHeader: false,
  async headers() {
    return [
      {
        source: "/(.*)",
        headers: [
          { key: "Strict-Transport-Security", value: "max-age=63072000; includeSubDomains; preload" },
        ],
      },
    ];
  },
};

How do I add it step by step?

  1. Open next.config.js.
  2. Paste the Strict-Transport-Security configuration shown below.
  3. Restart dev server or redeploy.
  4. Run curl -I https://yourdomain.com and look for the strict-transport-security line.
  5. Scan your site on FixSecurityHeaders to confirm the grade improved.

How do I verify it worked?

terminal
curl -sI https://yourdomain.com | grep -i "strict-transport-security"
# expected:
# strict-transport-security: max-age=63072000; includeSubDomains; preload

Check your site now

Free scan, instant grade, exact fixes for your stack.

What are the common mistakes?

  • The preload directive is hard to undo: removal from browser preload lists takes months.
  • includeSubDomains breaks any subdomain that still serves plain HTTP. Audit subdomains first.
  • Start with a short max-age (e.g. 300) and ramp up to 1–2 years once verified.
  • Browsers ignore HSTS sent over plain HTTP; it must be sent on the HTTPS response.
  • For nonce-based CSP use middleware.ts instead of static headers.
  • poweredByHeader: false removes X-Powered-By.

Quick reference

HeaderStrict-Transport-Security
Recommended valuemax-age=63072000; includeSubDomains; preload
StackNext.js
Wherenext.config.js
CompliancePCI DSS 4.0 4.2.1, NIST 800-171 3.13.8, CMMC SC.L2-3.13.8, OWASP ASVS V14.4.5, SOC 2 CC6.7

FAQ

What value should I use for Strict-Transport-Security?

A safe default is max-age=63072000; includeSubDomains; preload. The preload directive is hard to undo: removal from browser preload lists takes months.

Why isn't Strict-Transport-Security showing up on Next.js?

For nonce-based CSP use middleware.ts instead of static headers. Also clear any CDN or page cache, and check you edited the config that actually serves your domain.

Does Strict-Transport-Security affect SEO or performance?

No measurable performance cost — it's a few bytes per response. It doesn't affect rankings directly, but a misconfigured policy can break page resources, so test before enforcing.

Which compliance frameworks reference Strict-Transport-Security?

PCI DSS 4.0 4.2.1, NIST 800-171 3.13.8, CMMC SC.L2-3.13.8, OWASP ASVS V14.4.5, SOC 2 CC6.7.

Related guides