HTTP Header Checker

Enter a URL to see every redirect, the status code of each step and the headers the server sends back, with a check of the security headers that matter.

What are HTTP headers?

Every time a browser loads a page, the server sends a short block of headers before the content. They set the status code (200, 301, 404), caching, compression and cookies, and they tell the browser which security rules to apply. They aren’t visible on the page, so problems in them are easy to miss.

What this checker shows

  • Redirect chain: each hop with its status code and target, so you can spot loops, mixed HTTP/HTTPS hops and chains that are longer than they need to be.
  • All response headers from the final page.
  • Security check of the headers browsers act on: Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy.
  • Version leaks in Server and X-Powered-By, and whether compression is on.

Security headers in short

  • Strict-Transport-Security makes browsers use HTTPS only. Use max-age=31536000; includeSubDomains.
  • Content-Security-Policy lists where scripts, styles and images may load from. It is the strongest defence against cross-site scripting.
  • X-Content-Type-Options: nosniff stops browsers from guessing file types.
  • X-Frame-Options or CSP frame-ancestors stops other sites from embedding your pages (clickjacking).
  • Referrer-Policy controls how much of your URL is passed on to other sites.

Pages that collect email addresses, such as sign-up and contact forms, are common targets. Check those pages and their certificate with the SSL checker, then check the mail side with our SMTP test.

Frequently asked questions

Enter the URL above. The checker requests the page, follows each redirect one at a time and shows the headers of every response. From a terminal you can run curl -I https://example.com.

A 301 is permanent: browsers and search engines remember it and pass ranking to the new URL. A 302 (or 307) is temporary. Use 301 for HTTP to HTTPS and for moved pages.

At minimum: Strict-Transport-Security, X-Content-Type-Options: nosniff, a clickjacking defence (X-Frame-Options or CSP frame-ancestors) and a Referrer-Policy. Add a Content-Security-Policy once you know which sources your pages load from.

Servers and CDNs can vary headers by location, cookies, user agent and cache state. The checker sends a plain request with no cookies from our server, which is what a first-time visitor or search engine sees.