Findings · 2026-09-30 · By VSNARY | Emmanuel Orta
Our security headers skipped every signed-in session
A new Content-Security-Policy and tighter CORS headers were checked live and called done. Signed-in sessions received neither. The check had only ever looked signed out.
On 24 September 2026 crawlcheck.io added a report-only Content-Security-Policy and tighter CORS headers, checked them on signed-out page loads and called the work done. Signed-in sessions received neither: a coding error in the step that prepares signed-in pages left the header steps after it with nothing to attach headers to, while the page itself still loaded normally. It was fixed the same day. Every header or access change is now tested both signed in and signed out before it counts as shipped.
On 24 September 2026 crawlcheck.io shipped two security changes in one afternoon: a Content-Security-Policy in report-only mode, and a tightening of the CORS headers so that credentialed cross-origin requests were answered only where intended. Both were verified on the live site. Both were verified signed out. For every signed-in session, neither change was applied.
What did a signed-in visitor get? #
| Session | CSP header | Tighter CORS | Checked before release? |
|---|---|---|---|
| Signed out | applied | applied | yes |
| Signed in, before the fix | absent | absent | no |
| Signed in, after the fix | applied | applied | yes |
Signed-in pages go through one extra preparation step that signed-out pages skip. A coding error in that step meant the steps after it, the ones that add the two headers, received something that was not yet a finished page. They found no headers to change and passed it along unchanged. The page was completed just before sending, so it looked and worked exactly as before, without the new headers.
Why did nobody notice? #
Three things hid it. Signed-in pages behaved normally. The policy was in report-only mode, so even where it was applied nothing was blocked, and where it was absent nothing looked different. And the verification fetched the changed pages anonymously, read the new headers and stopped. A single signed-in fetch would have caught it. It was found the same afternoon by re-reading the code while preparing another change, and one signed-in request confirmed it.
What was fixed, and was anything exposed? #
The error was fixed in the next release the same day, and the check was rerun signed in and signed out on pages whose content differs between the two. When the policy later moved from report-only to enforced, that switch was tested both ways first. No data was exposed: the handling of private content on signed-in pages ran correctly throughout, and the missing CORS tightening only restricted a kind of credentialed cross-origin request that no legitimate client makes. It is published because the change was announced as live and was not live for the sessions it mattered most for.
How do you check your own headers both ways? #
Fetch the same page twice and compare the headers: once plain with curl -sI https://example.com/account, and once with your session cookie copied from the browser, using -H "Cookie: …". Look for content-security-policy (or its report-only variant), strict-transport-security and the access-control- headers in both. Do it for every header, gate or middleware change, on a page that differs signed in. The rollout itself, from report-only to enforced, is in the CSP rollout guide, and the transport header is covered in the HSTS audit guide.
This is one of the corrections CrawlCheck publishes when its own output was wrong. All of them are listed together.
Live, as you read this: the corpus now holds 570,959 domains across 9,163 scans. The figures in this piece were measured on the date above; this line is not.
CrawlCheck’s dataset when this page loaded: 570,959 sites measured.
Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn
Questions this post answers
What went wrong with CrawlCheck's security headers?
For one release on 24 September 2026, a new Content-Security-Policy and tighter CORS headers reached signed-out visitors but not signed-in sessions, because a coding error in the step that prepares signed-in pages stopped the header steps after it from applying.
Why did signed-in pages still work?
The page was completed correctly before sending, so it looked and behaved as before. Only the two new headers were missing, and the policy was in report-only mode, so nothing was blocked or visibly different.
Was any customer data exposed?
No. The handling of private content on signed-in pages worked throughout. The missing CORS tightening restricted a kind of credentialed cross-origin request that no legitimate client makes.
How should I verify a new security header?
Fetch the same page signed out and signed in, with your session cookie, and compare the response headers. Do it on a page whose content differs between the two states.
What rule came out of it?
Every gate, header or middleware change is tested both signed in and signed out before it is called done.
Related findings
The main product
Found this on your own site? We fix it for $100.
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
Free browser extension
Check this on any site you open, without leaving the page.
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.
Write for the library
Measured something yourself? Submit an article.
Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.
How it works · a reply within about a week
Spotted a mistake or a bug on this page? Report an error. Confirmed errors are fixed and logged on the corrections page.
Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain (how). Those appear at once, marked verified.
Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.