Parse a Cookie or Set-Cookie header and build one, with every attribute explained and the difference between request and response cookies made explicit.
Waiting for a cookie header
Request cookies carry names and values. Attributes live on Set-Cookie only.
Waiting for a header
Paste a Cookie header — names and values, separated by `; `.
Cookie Header Inspector runs entirely on your device — no cookie value is uploaded, logged or stored.
You’re on the Free plan. Compare plans
Two different headers share the word cookie, and conflating them causes a surprising amount of confusion. `Cookie:` goes from the browser to the server and carries names and values only — one header, pairs joined by `; `. `Set-Cookie:` comes back from the server and carries one cookie with its attributes.
The attributes govern *sending*, not the cookie. Secure, HttpOnly, SameSite, Path and Domain tell the browser when to send the cookie back; they are never transmitted in a request. A request cookie therefore cannot be inspected for them, which is why this tool separates the two modes rather than offering one box.
Several `Set-Cookie` headers may never be folded into one with commas — the general rule for repeated headers does not apply, because the Expires attribute contains a comma itself. Nearly every HTTP library carries a special case for this, and the ones that do not produce cookies that silently fail to set.
SameSite is explained with its real defaults. Browsers now treat a cookie with no SameSite as Lax, which breaks cross-site POST flows that used to work. SameSite=None requires Secure, and a cookie sent with None and no Secure is rejected outright rather than downgraded.
No configuration is secure in every environment, and the findings say what each attribute does rather than issuing a verdict. Whether a cookie is safe depends on what is in it and who can read it — neither of which this tool can know.
Because they are not there. Attributes are set by Set-Cookie and govern when the browser sends the cookie; the request itself carries only names and values. A tool that shows attributes on a request cookie is showing you something that does not exist.
No. It is the documented exception to the rule for repeated headers, partly because the Expires attribute contains a comma. Each cookie needs its own header line, and libraries that join them break cookies silently.
Lax, in current browsers, where it used to be None. That change broke cross-site POST flows that relied on the old behaviour. SameSite=None is still available and requires Secure — without it the cookie is rejected.
They make the browser enforce rules at the moment the cookie is set. `__Host-` requires Secure, no Domain and Path=/, which makes the cookie host-locked and immune to being set by a subdomain. Their presence tells you those rules were met.
No. It is parsed in your browser, never logged, and never written to browser storage — which matters, because a session cookie is a credential.