Security

Free tool · Runs in your browser

Grade pasted headers. Nothing leaves your browser.

Updated 16 November 2026

Paste the response headers of a page and get the same A to F headers grade as the live check, without the page being reachable from the internet. Made for staging, intranet and pre-launch sites.

Your headers stay in your browser. Nothing you paste is uploaded, logged or stored; this page has no way to send it anywhere. Paste the output of curl -I, or Response Headers copied from devtools. Up to 64 KB.

What it checks
9 header rows: HTTPS, HSTS, CSP, clickjacking, nosniff, Referrer-Policy, Permissions-Policy, software version leaks and cookie flags. SPF and DMARC are DNS, not headers, so they are not here.
Where it runs, limits
In your browser, as plain JavaScript on this page. Up to 64 KB of text. No request is made to anyone.
What happens to your input
Nothing. It is not uploaded, logged or stored, and it is shown back as plain text only. Free, no sign-up.
Sample resultillustrative values, not a real scan

Sample

  • fail

    Content-Security-Policy

    Missing

    Add a policy so injected scripts cannot run. Start with Report-Only.

  • warn

    Permissions-Policy

    Missing

    Switch off browser features you do not use.

  • pass

    Strict-Transport-Security

    max-age=31536000; includeSubDomains

A static example. Paste your own headers above to see the records for your site.

How do I use it?

Copy the response headers from curl -sI or your browser's developer tools, paste them into the box and press Analyze headers. You get the same A to F grade and fix snippets as the live check, but nothing leaves your browser, so it works for staging, intranet and pre-launch sites.

  1. Get the headers: run curl -sI https://your-site in a terminal, or copy Response Headers from your browser's devtools, Network tab.

  2. Paste them into the box. Untick the HTTPS box only if the response came over plain http://.

  3. Press Analyze headers. The grade and the records appear below, failures first.

  4. Copy the snippet for your host, deploy it to staging, copy the headers again and re-run.

When to use the paste analyzer

The live headers check loads a public page for you. Paste the headers instead when it cannot reach the site.

Sites the live check can't reach

  • Staging and pre-launch sites
  • Intranet and VPN-only apps
  • Pages behind a login or an IP allow-list

Where to get the headers

  • Terminal: curl -sI https://your-site
  • Follow redirects: curl -sIL https://your-site
  • Browser: devtools, Network tab, first request, Response Headers

What it does not cover

Your headers stay in your browser. Parsing and grading are plain JavaScript on this page. The page's Content-Security-Policy allows no connections except Google Analytics page views, so pasted text cannot be sent out. Pasted text is shown as plain text only.

Frequently asked questions

Are the headers I paste sent anywhere?

No. The analysis runs in your browser. This page's Content-Security-Policy allows no connections except the Google Analytics page-view hosts, so the page could not send your text to a server even by mistake.

How do I get the headers?

Run curl -sI https://your-site (add -L to follow redirects), or open your browser's developer tools, go to the Network tab, click the first request and copy the Response Headers. Both formats work.

What if I paste a redirect chain?

If the paste holds several responses, for example curl -sIL output, the last one is analysed, because it is the page the visitor ends up on. The page tells you when it does this.

Is the grade the same as the live headers check?

The 9 header rules are ported from the live check: same checks, same weights, same A to F cutoffs. The live check also grades SPF, DMARC and other DNS records, which a paste cannot contain, so a letter can differ between the two.

What are the limits?

Up to 64 KB of pasted text, which is far more than any set of response headers needs. Paste only the headers, not the page body.

Why can't it see my HTTPS status?

A header paste does not say whether the response came over HTTPS, so there is a checkbox for it. Untick it for an http:// response and HTTPS and HSTS fail, as they would in the live check.

More free tools

Read the guides · All free tools