Read the response headers
Across origins, JavaScript sees six safe response headers. HSTS and Content-Security-Policy are not among them, and neither is a Location the browser already followed. Something on the other side of the network has to look.
Pikkola Security & Header Studio, tool No. 19
A browser cannot tell you what a stranger's server said in its response headers. This can: one request from the edge, every redirect hop kept, and the six headers that decide whether a page can be framed, sniffed, downgraded or quietly loaded with someone else's script. Graded, explained, and written out as config lines you can paste tonight.
The address is fetched by our edge, not by your tab, so the headers are the ones any stranger sees. Redirects are followed one hop at a time and printed rather than hidden, because a chain that crosses to HTTP and back is worth knowing about.
100 / 100
Everything the final response carried, as it arrived.
HOW TO READ THIS
Each of these is a promise to the browser about what it may do with the response. None of them stops a determined attacker on their own. All of them remove a class of accident that is otherwise discovered by a stranger.
Across origins, JavaScript sees six safe response headers. HSTS and Content-Security-Policy are not among them, and neither is a Location the browser already followed. Something on the other side of the network has to look.
A browser hides the middle of a chain. Here each hop is a request of its own, with its status, its Location and how long it took, up to six hops. A hop that drops from HTTPS to HTTP stays visible instead of being smoothed over.
Before anything is fetched the host is resolved, and loopback, link local, private and cloud metadata ranges are refused. Redirect targets go through the same gate, so a public page cannot bounce the request into your network.
Watch reads up to ten of your domains once a day, the same way this page reads one, and adds the DNS records and the HTTPS handshake. The morning something changes, it sends one message to Slack, Discord or a webhook of your own.
!
The same eight checks, graded A+ to F. A header that disappeared, a grade that dropped or a score that fell is reported that morning.
A page that stops answering, a redirect that slips down to http, a certificate the browser would refuse.
A, MX, TXT and the DMARC record at _dmarc, compared with the last reading so a moved record is not discovered by a customer.
Slack, Discord, or any endpoint that accepts JSON. Send a test alert first and watch it arrive.
$7 a month$70 a year
Start monitoring, $7 a monthTen domains, one check a day. Cancel from your Gumroad library whenever you like.
No domains yet. Add one above and it is read straight away.
It goes to a Cloudflare Worker, which makes one request and returns the answer. No account, no cookie, no analytics, and nothing written down: there is no table of audited sites because there is no database. The site you audit does see a request from Cloudflare's network, not from your connection.
Cross-origin requests only expose a short list of response headers to JavaScript, and HSTS, Content-Security-Policy, X-Frame-Options and the rest are not on it. A redirect chain is not readable either, because the browser follows it before your code sees anything. A browser based check can only show the headers of its own page. This one asks a server to look.
To a Cloudflare Worker, which makes one request to that address and returns what came back. Nothing is written down: there is no database, no analytics and no log of the addresses that were checked. The target site does see the request, from Cloudflare's network rather than from your connection, which is also why it cannot be traced back to you.
Eight checks are weighted: transport 15, HSTS 20, Content-Security-Policy 25, frame protection 10, content type 10, referrer 10, permissions 5 and opener policy 5. A pass earns the full weight, a warning half, a failure nothing. Transport over plain HTTP caps the result at C, and a missing Content-Security-Policy caps it at A. The letter summarises the checklist, not the application.
Cloudflare does not add these headers by default, and a Pages project deployed by Direct Upload ignores a _headers file. On Pages, use a _headers file with a git based build, a Pages Function, or a Worker route in front of the site. On any zone, Transform Rules can add headers at the edge. The snippet on this page is written for a Pages _headers file and a Worker.
A server that fetches whatever address it is given can be used to reach things the visitor cannot: a router page, a database console, a cloud metadata endpoint. Every address is resolved first and refused if it sits in a private or link local range, and the same check runs again on each redirect target. That also means this tool cannot audit a site that only exists on your laptop.
Only the HTML, capped at 512 kB, and only to read the head. Scripts, stylesheets, images and fonts are never requested, so nothing on the page runs. If a site returns a huge HTML file, the head is still at the front of what was read.
No. It means these six responses are configured the way they are meant to be, which closes a set of browser level accidents. Authentication, authorisation, input handling, dependency updates and the application code itself are not looked at here, and a site can be clean on all six while still being broken in ways that matter more.
Made by one person, free to use