Which page should I audit?
Your main HTML pages, ideally one anonymous and one logged-in page. Headers such as CSP and framing protection matter most on documents, less on images or scripts.
Paste the response headers from your site and get an A to F grade with a finding and a fix for every check. It works offline on pasted text, so it can grade staging and internal sites that an online scanner cannot reach.
Loading the workbench.
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.
Each check carries a weight from 1 to 5. A pass earns the full weight, a header that is present but weak earns half, and a missing or failing one earns nothing. The score is the share of available weight earned, and the grade follows the original thresholds:
Five fixes make the grade honest. A header that is present but weak is now reported as weak, not missing. The deprecated Expect-CT is no longer scored, only noted. A Server header fails only when it reveals a version number, so nginx passes while nginx/1.18.0 does not. The cache advice no longer recommends no-store everywhere: caching is scored only on responses that set a cookie, where a shared cache could leak a session.
The CSP check now parses the policy. script-src falls back to default-src, and 'unsafe-inline' is not held against a policy that also uses a nonce, a hash, or 'strict-dynamic', because modern browsers ignore it then.
An online scanner has to fetch your site from its own servers, so it cannot see staging hosts, intranet apps, or anything behind a login, and it learns which sites you are checking. Pasted headers have none of those limits. Copy them from DevTools while you are logged in, and nothing about your site leaves this browser.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Your main HTML pages, ideally one anonymous and one logged-in page. Headers such as CSP and framing protection matter most on documents, less on images or scripts.
HSTS or Content-Security-Policy is missing or weak. They are the two critical headers, so the grade cannot reach A without both being strong.
No. The filter it controlled was removed from browsers because it could be abused. Send 0 or leave it out, and rely on a Content-Security-Policy instead.
There is no need. A bare product name such as nginx reveals little. What matters is hiding the version number, which tells attackers which known vulnerabilities to try.