Security Headers Checker

Grade any website’s HTTP security headers from A+ to F, see which ones are missing or weak, and get the exact header to add for each.

Checked from our serverOnly what you enter is sentNo sign-up

What the Security Headers Checker does

The Security Headers Checker loads a page and reads the HTTP headers that tell browsers how to protect its visitors. Strict-Transport-Security keeps them on https, Content-Security-Policy limits where scripts may load from, X-Frame-Options stops other sites showing the page in a hidden frame, X-Content-Type-Options stops browsers guessing file types, and Referrer-Policy and Permissions-Policy keep addresses and device features private. Each header earns points, out of 100 in all, and the total becomes a grade from A+ to F. For every missing or weak header, the tool says what it protects against and the exact value to add. It also flags headers that give away the web server’s software and version.

How to use it

  1. Type the address of a page, such as your home page. If you leave out https://, it is added for you.
  2. Press Check. Redirects are followed, and the final page is graded.
  3. Read the grade, then the findings: what each header does and what to change.
  4. Open All response headers to see everything the page sent.

Example

Checking github.com gives an A+ with 90 of 100 points: a year-long HSTS with includeSubDomains and preload, a strict Content-Security-Policy that also sets frame-ancestors, nosniff and a referrer policy. The only header missing is Permissions-Policy. A site with none of these headers scores 0 and gets an F.

Where to add the headers

Security headers are set in the web server or the hosting platform, not in the page. On Apache they go in the site’s configuration with Header always set; on nginx with add_header … always; and on hosting services such as Netlify, Vercel or Cloudflare in a headers file or a rules page. Add one header at a time and test the site after each.

Content-Security-Policy needs the most care, because a strict policy can block scripts the site really needs, such as analytics or ads. Start with Content-Security-Policy-Report-Only, read the reports for a week, then switch to the real header. The other headers are safe to add straight away.

Questions people ask

What is sent to your server, and is it kept?

Only the address you type is sent, so the Kitlantis server can load the page and read its headers. It is not saved with anything about you; the admin only sees that the tool was used.

Does a good grade mean the site is secure?

No. Headers are one layer of protection. A site still needs up-to-date software, safe code and good passwords; the headers make many common attacks harder.

Why is a big site graded low?

The grade reflects the headers that page sends, nothing else. Some large sites rely on other protections, or send different headers on different pages, so check the page you care about.

Should I hide the Server header?

Hiding the version is worth doing, because it tells attackers which known weaknesses to try. On Apache, ServerTokens Prod does this; on nginx, server_tokens off.

Related tools