Windsurf
Missing security headers on a Windsurf app
Windsurf's agent edits a project you deploy yourself. The public check is of that deployment. Secrets the agent wrote into client code show up if the browser downloads them.
Headers the document response already sends, or does not send.
What the scan can see
Content-Security-Policy, Strict-Transport-Security on HTTPS, X-Content-Type-Options, framing protection via X-Frame-Options or CSP frame-ancestors, and Referrer-Policy. A missing Permissions-Policy is informational and does not drop the letter by itself. Either framing control is enough.
What it does not do
The scan does not score how strict a CSP is beyond whether it exists and whether frame-ancestors is set. A header that exists only on an API route we never request is not graded.
The scan does not read the Windsurf session or your local files.
What to do next
Add the missing headers on the host, redeploy, and scan again. Turn HSTS on only after HTTP already redirects to HTTPS.
Questions
Does this open my Windsurf project?
No. The scan does not read the Windsurf session or your local files.
Can the scan prove missing security headers is fully fixed?
The scan does not score how strict a CSP is beyond whether it exists and whether frame-ancestors is set. A header that exists only on an API route we never request is not graded.
What should I do if the scan finds it?
Add the missing headers on the host, redeploy, and scan again. Turn HSTS on only after HTTP already redirects to HTTPS.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.