Replit
Cookie flags 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.
Secure, HttpOnly, and SameSite on cookies the page already sets.
What the scan can see
Each Set-Cookie on the document is checked for Secure, HttpOnly, and SameSite. The cookie value is not copied into the report. A response with no Set-Cookie is not flagged.
What it does not do
Cookies set later by JavaScript after the page loads, or on a path we do not fetch, are not seen.
The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
What to do next
Set the three flags on the server. Use SameSite=Lax unless the cookie is only needed on your own site, in which case Strict is tighter. Do not put a session secret in a cookie that script can read.
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 cookie flags is fully fixed?
Cookies set later by JavaScript after the page loads, or on a path we do not fetch, are not seen.
What should I do if the scan finds it?
Set the three flags on the server. Use SameSite=Lax unless the cookie is only needed on your own site, in which case Strict is tighter. Do not put a session secret in a cookie that script can read.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.