Skip to main content

Free Security Headers Checker for Websites

Check the HTTP security headers of a public page, or paste headers you copied. Compare each value with the OWASP proposal and copy fixes for Next.js, WordPress or Apache.

Last updated 15 November 2026

Loading tool…

This security headers checker reads the HTTP response headers of one public address and lays them out in a matrix: the value the response sent beside the value the OWASP Secure Headers Project proposes, with a plain-English note on each. It covers Strict-Transport-Security, Content-Security-Policy and its report-only form, X-Frame-Options read against frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and the three cross-origin policies. It then lists the attributes on the cookies the response sets, the headers that name the software behind the site, and the deprecated headers it checks: X-XSS-Protection, Expect-CT, Public-Key-Pins and Feature-Policy. Where a finding has a header fix, the tool writes it for Next.js, WordPress or the Apache HTTP Server, ready to copy, with a retest checklist. Our server makes the request for you, so check only a site you own or have permission to check. To read a signed-in page, paste its headers instead: the paste tab analyses them in your browser.

How to use this tool

  1. 1

    Enter an address, or open the paste tab

    On the Check a site tab, type a site name without http:// or https://, which is checked over HTTPS, or a full address that starts with http:// or https://. To read headers you copied from your browser or from curl -i, open the Paste headers tab, paste up to 200 lines and say whether the response came over HTTPS.

  2. 2

    Run the check

    Press Check headers. Our server looks up the address, requests it once with GET, follows up to 5 redirects and reads only the headers of the final response. On the paste tab, press Analyse headers instead: nothing is sent anywhere.

  3. 3

    Read the matrix and the findings

    Each row shows the value seen, the value the OWASP Secure Headers Project proposes and a result of Fix, Review, Note or Matches. The findings below the matrix explain each row and add notes on cookies, headers that name software and deprecated headers, with the ones to fix first.

  4. 4

    Copy the fixes, then retest

    Pick Next.js, WordPress or Apache HTTP Server, copy the combined block or one fix at a time, and deploy the change. Then work through the retest checklist and run the check again.

What the security headers checker reads, and what it cannot see

When you press Check headers, our server looks up the address you typed in DNS, refuses it if it points to a private or reserved network address, and sends one GET request to it on port 80 or 443. If the answer is a redirect, the next address is checked the same way before it is requested, up to 5 redirects. The server reads the response headers and stops before reading the page itself, and the whole request stops after 10 seconds. Each check also counts against a limit on requests per visitor and in total, so a check can be refused when too many have run recently. What comes back is the final address, its status code, each address in the redirect chain and the headers of the final response. The analysis reads the complete headers our server received. On screen, the raw list shows up to 60 headers and 4,096 characters of each value, and the matrix and findings repeat a shorter part of a value; anything shown cut short is marked as cut. Set-Cookie values are replaced before the answer leaves our server, so only cookie names and attributes reach your browser. The limits matter as much as the results. The check reads one response to one address at one time, from our server's location, without signing in. Another page, a static file, an error page, an API route or a page behind a login can send different headers, and a response can also depend on where the request came from. A missing header is something to look into, and a header that matches the proposal is one setting among many; neither tells you anything about the rest of the site. There is no grade or score. Check only a site you own or have permission to check: running the tool does not establish that permission.

The headers in the matrix, and the values it compares against

Each proposed value in the matrix comes from the configuration proposal on the OWASP Secure Headers Project's best practices page, and the explanations draw on MDN Web Docs. Strict-Transport-Security tells browsers to reach the host only over HTTPS and to upgrade later http:// requests. MDN says browsers ignore it when it arrives over plain HTTP. The tool therefore judges it only on an HTTPS response, and the site check skips it when the address is an IP address, which MDN says cannot be an HSTS host. The paste tab cannot see the address, so it reads the host as a name. MDN also says includeSubDomains applies the policy to every subdomain. The project proposes max-age=63072000; includeSubDomains and leaves preload out of its proposal. X-Frame-Options and the frame-ancestors directive both control which pages may show this one in a frame. MDN says that without either, the browser will allow other sites to embed the page. The project says that when a resource has both, frame-ancestors is enforced and X-Frame-Options ignored. The matrix reads them as one row. MDN calls ALLOW-FROM obsolete and says modern browsers that meet it ignore the whole header. X-Content-Type-Options: nosniff makes the browser use the declared Content-Type instead of examining the content to guess it, and blocks a script or stylesheet whose type does not match. Referrer-Policy controls how much referrer information is sent with requests. MDN says browsers use strict-origin-when-cross-origin when no policy is given, and warns that unsafe-url will leak potentially private information from HTTPS resource addresses to insecure origins. The project proposes no-referrer. Permissions-Policy allows and denies browser features. The project marks it a working draft and says it is supported only by Chromium-based browsers. The tool does not judge each feature. Cross-Origin-Opener-Policy, Cross-Origin-Embedder-Policy and Cross-Origin-Resource-Policy control how a page and its files deal with other origins. Each can stop something a site relies on, such as a reference to a payment or sign-in window it opened, or an image loaded from another site, so a missing one is a note and its fix is marked optional.

Why the policy fix starts in report-only mode

A content security policy can block the scripts, styles and frames a page needs, so this tool never hands you an enforced policy to paste. When no policy is sent, its fix is the OWASP Secure Headers Project's proposed policy sent as Content-Security-Policy-Report-Only, with a Reporting-Endpoints header and a report-to directive. MDN describes the report-only header as monitoring violations without enforcing the policy. It also says the report-to directive must be specified for reports to be sent, and that without one the header has no effect. Replace the example.com report address with an endpoint you control, use the site as visitors do, and adjust the policy until real pages stop reporting violations. Then send the same policy as Content-Security-Policy and run the check again. When a policy is already enforced, the matrix reads three things from the header alone. MDN says inline scripts and eval() are blocked by default when a policy contains default-src or script-src, and that script-src is the fallback for script-src-elem and script-src-attr. The tool reads inline script elements through script-src-elem and inline event handlers through script-src-attr, each with those fallbacks, and eval() through script-src, then default-src. MDN says developers should avoid 'unsafe-inline' and 'unsafe-eval', because each defeats much of the purpose of having a CSP, and that a nonce or hash beside 'unsafe-inline' makes the browser ignore it. Each kind of script that every enforced policy leaves open is marked for review. It also reads form-action, base-uri and frame-ancestors, which the project says do not fall back to default-src and should always be set, form-action and base-uri to at least 'self' and frame-ancestors to at least 'none'. The row is marked Matches only when no kind of script is left open and all three meet those values; anything else is noted. With several enforced policies, MDN says adding policies can only further restrict what the page may do. The tool therefore counts a protection when any enforced policy has it. A report-only policy never counts as enforcement. For a directive-by-directive reading of a policy, use the CSP checker.

Cookies, software names and deprecated headers

Below the matrix, the findings cover three more groups. For each Set-Cookie header, the tool reads the cookie's name and attributes and never its value. It marks a cookie without Secure on an HTTPS response for review: MDN says Secure sends the cookie only on https: requests. It notes a missing HttpOnly, which MDN says forbids JavaScript from accessing the cookie, and leaves that call to you, because some cookies are meant for page scripts. It notes a missing SameSite, which MDN says some browsers default to Lax, and checks the rules MDN gives for SameSite=None, Partitioned and the __Secure-, __Host-, __Http- and __Host-Http- name prefixes. The first 20 cookies are listed and checked. Headers that name software come from the project's list of headers to remove, when possible, so a response does not disclose technical information about the environment: Server, X-Powered-By, X-AspNet-Version and more than eighty others. A value that includes what looks like a version number is marked for review. MDN adds a balance worth keeping. It says it is debatable whether hiding the information in the Server header provides much benefit, because server software can be fingerprinted by other means, and that a more robust approach is to keep software updated or patched against known vulnerabilities. The tool reports X-XSS-Protection, Expect-CT, Public-Key-Pins and Feature-Policy, which the project marks deprecated. For X-XSS-Protection the project recommends sending 0 and using Content-Security-Policy instead, and MDN warns that the header can, in some cases, create cross-site scripting vulnerabilities in otherwise safe websites. MDN says Chromium deprecated Expect-CT from version 107, because Chromium now enforces Certificate Transparency by default. The project also marks Pragma deprecated, but the tool leaves it alone, because the project still shows it beside Cache-Control for HTTP/1.0 caches.

Applying the fixes in Next.js, WordPress and Apache

The fixes are written from the tool's own fixed values, never copied from the response. The combined block holds every fix marked Fix or Review. Every fix also appears on its own below it, and optional fixes, such as the cross-origin policies and Permissions-Policy, appear only there, so you can test each before sending it. For Next.js, the entries go in the headers() function in next.config.js, with the source pattern '/:path*' so they apply to every path. The Next.js documentation says headers are checked before the filesystem, which includes pages and /public files, and that when two entries match the same path and set the same header key, the last one overrides the first. The headers() function sets headers, so a removal becomes poweredByHeader: false for X-Powered-By, which the documentation gives as the way to stop Next.js adding that header, and a comment for any other header. For WordPress, the fix is PHP for the wp_headers filter, which the WordPress code reference describes as filtering the HTTP headers before they are sent to the browser. A removal is left as a comment, because the filter changes only the headers WordPress passes through it. For the Apache HTTP Server, each header is set with Header always set after a Header onsuccess unset for the same name. The mod_headers documentation explains why: headers in the always table are added even on error responses and redirects, and a configuration that ignores the two tables can send the same header twice. Values are double-quoted, with inner quotes escaped as the httpd configuration syntax allows, and comments sit on their own lines, because httpd does not allow a comment on the same line as a directive. Whichever platform you use, the OWASP Clickjacking Defense Cheat Sheet warns that web proxies are notorious for adding and stripping headers. Run the check again after each deployment.

Sources

Worked example

An invented example, not taken from any site: a developer checks a page served over HTTPS before a launch.

Strict-Transport-Security
max-age=31536000
X-Frame-Options
ALLOW-FROM https://partner.example
X-Content-Type-Options
nosniff
Content-Security-Policy
Not sent
Set-Cookie
One session cookie with Path=/ and HttpOnly

Two rows are marked Fix: framing, because the HTML Standard treats an ALLOW-FROM value as if the header were omitted, and the policy, which is not sent. The session cookie is marked Review for its missing Secure attribute. X-Content-Type-Options is marked Matches, and Strict-Transport-Security and the other rows are Notes.

The partner site no longer frames the page, so the developer pastes the combined Apache block, which sets X-Frame-Options: DENY and starts the proposed policy in report-only mode. They add Secure to the session cookie in the application code, deploy, and run the check again before working through the retest checklist.

Who uses this tool

Developers before a launch

Check the production address for missing headers and copy the fixes for Next.js, WordPress or Apache, whichever the site runs on.

Teams moving hosts or adding a proxy

Check the same page before and after the move to see whether a header was dropped or now arrives twice.

Developers working behind a login

Paste the headers of a signed-in page from the browser's developer tools, which the site check cannot reach.

Owners filling in a security questionnaire

See which security headers the home page sends before answering a question about them.

Frequently asked questions

What does the security headers checker send to my site?

Our server looks up the address in DNS, then sends one GET request to it and one more for each redirect it follows, up to 5. It refuses private and reserved network addresses, uses only ports 80 and 443, reads the response headers without reading the page, and stops after 10 seconds. Check only a site you own or have permission to check.

Why does a header show as missing when my site sets it?

The tool reads one response to one address. Your setting may apply only to some paths or some responses, or a cache or proxy may answer differently. Check the final address and status above the matrix. For example, the Apache documentation says that on a non-2xx response the server generates itself, such as a redirect, only headers set with always are used.

Does this checker give my site a grade?

No. There is no letter grade or score. Each row shows the value seen beside the value the OWASP Secure Headers Project proposes, with a result of Fix, Review, Note or Matches and a note explaining it. How much a gap matters depends on the page, such as a sign-in form compared with a brochure page, and the tool does not know which kind it read.

Is the paste mode sent to Clever Ops?

No. The paste tab analyses the headers in your browser and sends nothing. It accepts up to 200 lines and 64,000 characters, and refuses anything longer rather than reading part of it. Set-Cookie values are hidden in what it shows, and only cookie names and attributes are analysed.

Why is the content security policy fix in report-only mode?

An enforced policy can block scripts, styles or frames your pages need. MDN describes Content-Security-Policy-Report-Only as monitoring violations without enforcing the policy, and says reports are sent only when a report-to directive is given. The fix includes one, with an example address for you to replace. Read the reports, adjust the policy, then send it as Content-Security-Policy.

Can the checker read pages behind a login?

No. The site check never signs in, so it sees what a visitor without an account sees at that one address. For a signed-in page, open your browser's developer tools, copy the response headers of the page, and paste them into the Paste headers tab. The same analysis then runs in your browser.

Related tools and services