A11y Annotator
Audit HTML for alt text, labels, headings, and ARIA gaps with fix suggestions.
OpenRead pasted response headers cleanly and grab a baseline set of security headers.
Drop curl -I output or DevTools headers into Parse response.
The status line and each name: value pair are listed.
Open Security checklist and copy individual headers.
Generate the full set and copy or download it.
A security scan flags your app for missing headers, and the report quotes the raw output of curl -I. You want to read that response properly, see which protections are absent and copy sensible values to start from. This page handles both halves without sending a request anywhere.
There are three tabs. Parse response takes raw response text, such as curl -I output or a block copied from DevTools, keeps the HTTP status line and lists each header as name and value, skipping blank lines and anything without a colon. Security checklist shows eight recommended headers with a copy button on each row: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Opener-Policy and Cross-Origin-Resource-Policy. Generate headers writes the same eight as one block you can copy or download as headers.txt.
The tool does not fetch URLs. Browsers block a page from reading most response headers on other origins, so paste them in instead. Treat the generated values as a strict baseline rather than a drop-in config: the Content-Security-Policy only allows scripts from your own origin, and the HSTS value includes preload, which is slow to undo, so adjust both before deploying. Shape the policy with the Content Security Policy builder, and look up unfamiliar status lines in the HTTP status code reference.
Parsing and generation are plain string handling in your tab, so internal hostnames or cookies in a pasted response stay private.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
A web page is not allowed to read most response headers from another site because of CORS. Run curl -I against the URL, or copy the headers from the DevTools Network panel, and paste them into Parse response.
No. The same eight headers and values are produced whatever domain you enter; the field only labels the status message. Edit values such as the CSP sources yourself.
Only if every subdomain already works over HTTPS. Preload asks browsers to hard-code HTTPS for your domain, and getting removed from that list can take months, so start with a short max-age and add preload last.