Parse cookie headers and check them against the rules browsers enforce. Paste a Cookie request header to see each name and value, or Set-Cookie response headers to see every attribute — Domain, Path, expiry, Secure, HttpOnly, SameSite — with warnings for problems like SameSite=None without Secure or a misused __Host- prefix. Copy the result as JSON. It's free, runs in your browser, and your cookies never leave your device.
| Attribute | Effect |
|---|---|
| Secure | Only sent over HTTPS |
| HttpOnly | Hidden from JavaScript |
| SameSite=Strict | Never sent on cross-site requests |
| SameSite=Lax | Sent on top-level navigation only (default) |
| SameSite=None | Always sent; requires Secure |
| Max-Age / Expires | Lifetime; none means session cookie |
| __Host- prefix | Must be Secure, Path=/, no Domain |
Common causes: SameSite=None without Secure, a __Host- cookie with a Domain or a Path other than /, or a Secure cookie set over plain HTTP. The tool flags the first two.
Set-Cookie is sent by the server to create or change a cookie, with attributes. Cookie is sent by the browser and contains only names and values.
It hides the cookie from JavaScript, which protects session cookies from being stolen through XSS.
Browsers treat it as Lax: the cookie is sent on top-level navigations from other sites but not on cross-site subrequests.
No. Parsing happens in your browser.
A request's Cookie header is a list of name=value pairs separated by semicolons; a response's Set-Cookie header is one cookie followed by attributes, and servers send one Set-Cookie line per cookie. The parser tells the two apart from the input, splits the cookie pair from its attributes, strips optional quotes and URL-decodes values for display while keeping the raw form. Domain, Path, Expires, Max-Age, Secure, HttpOnly, SameSite, Partitioned and Priority are recognized; Max-Age is converted to an absolute expiry and takes precedence over Expires, as RFC 6265 specifies. The checks follow what browsers enforce: SameSite=None without Secure is rejected; cookies named __Host- must be Secure with Path=/ and no Domain; __Secure- cookies must be Secure; Partitioned requires Secure. Softer warnings flag a missing Secure or HttpOnly, note that a missing SameSite defaults to Lax, and identify session cookies and headers that delete a cookie by expiring it. Parsed results can be copied as JSON.