Replit
Clickjacking protection on a Replit app
A Replit deployment is an ordinary website. The page, its same-origin scripts, and the headers from that host are what a visitor receives, and what this scan reads.
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 Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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 Replit project?
No. The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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.