HSTS Checker: Is HSTS Enabled on This Website?

Enter a site address to see whether it sends the HSTS header and how it is configured. Free, instant, no signup.

FreeNo signupNo account or emailLast checked November 2026

A free HSTS checker. Enter a URL and it reads the Strict-Transport-Security response header, then shows whether HSTS is enabled, its max-age lifetime and whether includeSubDomains and preload are set. No signup, no email.

What it checks

  • Whether the Strict-Transport-Security header is present
  • The max-age value and whether it is at least one year
  • includeSubDomains and preload
  • Whether the page is served over HTTPS at all

What you get

  • Enabled or not enabled
  • The header exactly as sent
  • A plain-language reading of each directive

Limits

  • One request to the page you enter, after redirects
  • Whether a domain is on the browser preload list is not checked
  • Other security headers are covered by the Security Headers Checker

HSTS directives

DirectiveWhat it doesRecommended
max-ageHow long, in seconds, browsers must use HTTPS only31536000 (one year) or more
includeSubDomainsApplies the rule to every subdomainOnly when all subdomains support HTTPS
preloadAsks browsers to build the rule in before the first visitOnly when ready to commit; hard to undo
What HSTS does

HSTS (HTTP Strict Transport Security) is a response header that tells a browser to use only HTTPS for a site for a set time. After one visit, the browser upgrades every later request itself, so an attacker cannot downgrade the connection to HTTP.

The header only counts when it is sent over HTTPS. For the other headers that protect a site, such as Content-Security-Policy and X-Frame-Options, use the Security Headers Checker.

Frequently asked questions

How do I check if HSTS is enabled on a website?

Enter the address above. The tool requests the page and reads the Strict-Transport-Security header. By hand, open the browser's developer tools, look at the response headers of the page and find Strict-Transport-Security.

What max-age should HSTS use?

At least one year (31,536,000 seconds) for any site that wants to join the preload list. Start with a short value while testing, then raise it once HTTPS works everywhere on the site.

Should I add includeSubDomains and preload?

Only when every subdomain works over HTTPS. includeSubDomains applies the rule to all of them, and preload asks browsers to build the rule in, which is slow and hard to undo.

Related tools

We use cookies to analyze site usage and improve your experience. You can decline non-essential cookies. Privacy Policy