Skip to content

Free HSTS checker

Check a website's Strict-Transport-Security header and its redirect from HTTP to HTTPS.

Reads the home page as a browser would. No login access needed. What happens to the domain you enter

Example report

example.com
  • 2 Medium
  • 1 Low
  • 1 passed
  • HTTP is not redirected to HTTPSwww.example.comMedium

    http://www.example.com/ answered 200 without redirecting to HTTPS.

    Next step

    Redirect every HTTP request to the same path over HTTPS with a 301 or 308.

    View fix guide

  • HSTS is not enabledwww.example.comMedium

    https://www.example.com/ answered without a Strict-Transport-Security header.

    Next step

    Add Strict-Transport-Security: max-age=31536000; includeSubDomains to HTTPS responses once every subdomain serves HTTPS.

    View fix guide

  • HSTS max-age is shortexample.comLow

    HSTS is on with max-age 604800 (7 days).

    Next step

    Raise max-age to at least one year (31536000 seconds).

    View fix guide

What the HSTS check looks at

  • The header

    Find Strict-Transport-Security on the HTTPS response, redirects included.

  • max-age

    Flag a value under 180 days as short, and zero as none.

  • Directives

    Show includeSubDomains and preload, without judging them.

  • HTTP redirect

    Check that plain HTTP on each name redirects to HTTPS.

The check reads the home page; browsers apply HSTS to the whole host once they have seen it.

Understand the issue and your next step

Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

HSTS is not enabledMedium

HTTPS responses do not include a Strict-Transport-Security header.

Strict-Transport-Security: not present

Common HSTS issues you can put right

  • HSTS is not enabledMedium

    Your site may use HTTPS without telling browsers to keep using it on future visits. Check your HTTPS setup before enabling HSTS.

    Read the fix guide

  • HTTP is not redirected to HTTPSMedium

    A visitor who types the bare name arrives over plain HTTP and stays there. Redirect every HTTP request to the same address over HTTPS.

    Read the fix guide

  • HSTS max-age is shortLow

    The protection lapses for anyone who visits less often than the max-age lasts. Raise it once HTTPS is settled on every name.

    Read the fix guide

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • The Strict-Transport-Security header on any HTTPS response for the home page, including a redirect before the final page, for the domain and its www. name, or the subdomain entered.
  • Its max-age. A missing header, max-age=0 or a value that does not parse counts as no HSTS; under 15,552,000 seconds (180 days) counts as short.
  • Whether includeSubDomains and preload are present. Both are shown; neither is judged.
  • Whether http:// on each name answers with a redirect to HTTPS, following up to three redirects. If port 80 does not answer, there is nothing to redirect and that check does not apply.

Reading a result

HSTS (RFC 6797) tells a browser that, for the next max-age seconds, this host must only be reached over HTTPS. The browser then upgrades http:// links and typed addresses itself, before any request leaves, and does not let the visitor click through a certificate warning.

Browsers ignore the header on plain HTTP responses, which is why the redirect matters. A first-time visitor who types the bare name arrives over HTTP, and the redirect is what brings them to the HTTPS response that carries the header. That first request, and any after max-age runs out, can still be intercepted.

A pass on both checks means plain HTTP redirects to HTTPS and the header asks browsers to remember that for at least 180 days. A short max-age is low severity: the protection works, but lapses for anyone who visits less often than it lasts.

What it does not do

  • Only the domain and its www. name are visited. Other subdomains are not, so the check cannot tell whether includeSubDomains would cut off one that still serves plain HTTP.
  • It does not look up the browsers' preload list. The preload directive asks to be included; whether the domain is on the list is shown at hstspreload.org.
  • The redirect check looks at the home page only. It does not test that every path redirects or that the redirect keeps the path.

What happens to the domain you enter

The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.

Guides

A few things worth knowing

What max-age should HSTS use?
One year (31536000 seconds) is the usual choice, and this check reports anything under 180 days as short. Start lower while you confirm every name serves HTTPS, then raise it.
Should I add includeSubDomains?
Only once every subdomain, including internal and forgotten ones, serves HTTPS with a valid certificate. Browsers will refuse plain HTTP on all of them for the length of max-age.
Does HSTS protect the very first visit?
No. A browser learns the rule from the first HTTPS response it sees, so the first request can still go over HTTP. Preloading the domain into browsers closes that gap, but it is hard to undo.