v0
Missing security headers on a v0 app
v0 generates UI you then deploy, often on Vercel. The scan starts at the deployed URL. It sees the shipped page, not the v0 chat that produced the components.
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.
A component that was generated but never deployed is not part of the check.
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 v0 project?
No. A component that was generated but never deployed is not part of the check.
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.