Cookie Security Analyzer
Review Set-Cookie security flags and get a practical header to fix them.
Quick answer
Paste response Set-Cookie lines to review cookie transport, script access, cross-site behavior and scope in your browser. The analyzer checks attributes and name prefixes, then suggests a header to review. It cannot verify the setting origin, application behavior or whether a browser accepted the cookie.
Check the rest of your website
Use the free vulnerability scanner to review related website configuration.
Related checks and learning
Frequently asked questions
Is my cookie data uploaded?
No. Parsing runs locally, with no input storage or analysis API. Analytics record only tool use, never pasted values. Replace live cookie values before sharing screenshots.
What do Secure and HttpOnly do?
Secure limits cookie delivery to secure connections, with a localhost exception in browsers. HttpOnly prevents script access through document.cookie, but scripts can still initiate requests that carry the cookie. Neither flag fixes an XSS vulnerability.
Which SameSite setting should I choose?
Strict restricts cross-site sending most strongly. Lax permits some top-level navigation cases. None enables cross-site sending and requires Secure. Choose based on your authentication and embedding flows, then test in browsers.
What do __Host- and __Secure- require?
__Secure- requires Secure and an HTTPS setting origin. __Host- also requires Path=/ and forbids Domain. Prefixes are case-sensitive. Pasted text cannot prove the origin was HTTPS.
What is a Partitioned cookie?
Partitioned requests CHIPS storage separated by top-level site and requires Secure. It does not replace HttpOnly, SameSite or application authorization. Browser support and third-party cookie policies affect behavior.
How are grades and fix snippets calculated?
These are Protego review heuristics: F for any high finding, C for multiple warnings, B for one warning, A otherwise. Informational findings do not lower the grade. Snippets replace values with a placeholder and preserve valid SameSite choices. Review domain sharing and script needs before deploying.
Are duplicate names and large cookies always invalid?
No. Identical names can exist under different paths or domains. RFC 6265 recommends at least 4096 bytes per cookie, counting name, value and attributes; browser limits vary. This tool measures the pasted field value and flags larger entries for review.
References
Rules checked against these sources on November 16, 2026.