curl -sI your-site

Check your website's security headers — free

Enter an address and in about 20 seconds you get a grade and the three most important problems. No registration.

Check only websites you own or are responsible for. We make a handful of ordinary requests, the same ones a browser makes.

What we check

Six groups of checks, all from the outside

Everything here is visible to any visitor of your site. We only read it and compare it with current good practice.

01 / transport

Transport

Whether the plain http:// address redirects to https://, and whether the browser is told to use HTTPS only from then on.

  • HTTPS redirect
  • HSTS
02 / browser

Browser protections

Headers that tell the browser what the page may load, who may embed it, and what it may pass on to other sites.

  • CSP
  • MIME sniffing
  • clickjacking
  • Referrer-Policy
  • Permissions-Policy
03 / cookies

Cookies

Whether the cookies set on the first response are protected against being read on the network, by scripts, or sent from other sites.

  • Secure
  • HttpOnly
  • SameSite
04 / content

What the page loads

Scripts from other hosts that are loaded without an integrity check, and resources still fetched over unencrypted HTTP.

  • third-party scripts
  • SRI
  • mixed content
05 / edges

Error pages and security.txt

Whether the 404 page keeps the same protections as normal pages, whether headers reveal software versions, and whether researchers know where to report a problem.

  • 404 headers
  • version disclosure
  • security.txt
06 / mail

Mail records of the domain

DNS records that decide who may send email in your name and which authorities may issue certificates for your domain.

  • SPF
  • DMARC
  • CAA
What this is not

A hygiene check, not an audit

This tool is not a penetration test and not a vulnerability scan. It reads only what your site tells every visitor.

  • It does not log in, send attack payloads or guess hidden addresses.
  • A good grade means good hygiene, not a secure application. Flaws in logic, access control and code are invisible from here.
  • TLS configuration details, such as protocol versions and cipher suites, are not checked.

See what a real audit covers.

Next step

Need to know what is behind the headers?

We review code, applications and infrastructure by hand, rank the findings by risk and check the fixes afterwards. Tell us what you run and we will suggest a sensible scope.

Discuss an audit