Security Headers Checker

Grade a website’s HTTP security headers and cookie flags.

Website security Live check from this server, against public hosts only.

About the Security Headers Checker

HTTP response headers can switch on strong browser protections: HTTPS-only access (HSTS), a Content Security Policy against cross-site scripting, protection against clickjacking and MIME sniffing, and control over referrer and browser features.

The checker requests the page like a browser, follows up to five redirects and grades each header. It also checks cookies for the Secure, HttpOnly and SameSite flags and points out headers that reveal server software versions.

How to use it

  1. Enter the full address of the page, e.g. https://example.com.
  2. Run the check.
  3. Review the grade, each header’s result and the suggested fixes.

Frequently asked questions

Which security headers matter most?

Strict-Transport-Security and a Content-Security-Policy give the most protection. X-Content-Type-Options: nosniff, a Referrer-Policy and clickjacking protection (frame-ancestors in CSP, or X-Frame-Options) are easy additions.

Is X-XSS-Protection still needed?

No. Modern browsers removed the XSS auditor, and the header can even create problems. Use a Content-Security-Policy instead and set X-XSS-Protection to 0 or omit it.

Do security headers matter for PCI DSS?

PCI DSS 4.0 requirement 6.4.3 requires controlling and authorising scripts on payment pages, which a strict Content-Security-Policy supports, and requirement 11.6.1 requires detecting unauthorised changes to security-relevant headers on those pages.

All free tools