Cursor
Clickjacking protection on a Cursor app
Cursor writes the repo on your machine. Visitors see the host you deployed to. A key in a local .env is invisible here. A key compiled into the deployed JavaScript, or returned at /.env, is not.
Whether another site can frame the page.
What the scan can see
The scan looks for X-Frame-Options or a CSP frame-ancestors directive. One of them is enough. If both are missing, the finding is that the page can be framed.
What it does not do
We do not embed your page in a test frame. The header is the evidence.
The scan does not open the Cursor workspace, the chat, or git history on your laptop.
What to do next
Add Content-Security-Policy: frame-ancestors 'none', or X-Frame-Options: DENY, unless a specific partner must embed the page.
Questions
Does this open my Cursor project?
No. The scan does not open the Cursor workspace, the chat, or git history on your laptop.
Can the scan prove clickjacking protection is fully fixed?
We do not embed your page in a test frame. The header is the evidence.
What should I do if the scan finds it?
Add Content-Security-Policy: frame-ancestors 'none', or X-Frame-Options: DENY, unless a specific partner must embed the page.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.