Cookie Header Explainer

Explain pasted cookie headers with missing-attribute warnings shown first.

On-device No sign-up Free to use

Inspect input controls

Showing an example. Edit to see your own.

?

One cookie per line. Values are masked in all results. Only the documented producer syntax is supported.

?

name=value pairs separated by semicolons; no attributes.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

Inspect one session cookie with Secure and HttpOnly but no explicit SameSite attribute.

Inspected 1 Set-Cookie line and 0 request cookie pairs; 1 missing-attribute wording note; values masked.

Loading the tool. Your result will appear here.

https://usefreetools.net/cookie-header-explainer · 20 November 2026

Was this helpful?

How to use Cookie Header Explainer

  1. Paste one Set-Cookie line per cookie, using non-sensitive sample values when possible.
  2. Enter the response host, comparison path and explicit reference UTC time.
  3. The cookie explanation updates as you edit the pasted headers. Review missing-attribute notes and clear private header text when you finish.

Example: Cookie Header Explainer

Inspect one session cookie with Secure and HttpOnly but no explicit SameSite attribute.

You add
Set-Cookie lines: session=example; Path=/; Max-Age=3600; Secure; HttpOnly; Reference UTC time: 2026-10-03T00:00:00Z; Host receiving the setting response: site.example; Path for scope comparison: /
You get
Inspected 1 Set-Cookie line and 0 request cookie pairs; 1 missing-attribute wording note; values masked.

Options

Set-Cookie lines
One cookie per line. Values are masked in all results. Only the documented producer syntax is supported.
Optional request Cookie header
name=value pairs separated by semicolons; no attributes.
Reference UTC time
The initial value is 2026-10-03T00:00:00Z.
Host receiving the setting response
The initial value is site.example.
Path for scope comparison
The initial value is /.

Supported inputs and limits

  • Up to 30 Set-Cookie lines, 100 request pairs and 20,000 combined characters.
  • This explains supported pasted syntax without setting cookies or contacting a website.
  • Domain matching has no public-suffix database, and Expires accepts exact IMF-fixdate only.
  • Browser defaults, lifetime caps, eviction, cookie acceptance and tracking purpose are not inferred.
  • The relative expiry follows the entered reference time, which can differ from the real setting response.
More details

Results mask values, but names, hosts and paths may still reveal details.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Scope and protection flags are different checks

Path and Domain describe where a cookie may apply. Secure relates to HTTPS transport; HttpOnly limits script access rather than stopping every form of misuse. This offline explanation does not set a cookie, simulate all browser policies or establish that a session is secure. Keep application authentication and cookie interpretation separate.

Use a reference time deliberately

A relative Max-Age needs a starting time to produce a stated expiry. The reference field is not a reading from the actual setting response. If you enter an old or arbitrary time, the calculated expiry follows it. Masked values reduce accidental output disclosure, but names, hosts and paths can still reveal application details.

Questions about Cookie Header Explainer

Why paste Set-Cookie lines separately?

Expires can contain a comma. Combining headers by commas can split a valid date and change their meaning.

Which expiry wins if both are present?

A valid Max-Age takes precedence over Expires. The entered reference time is used for the stated relative expiry.

Does masking make shared input safe?

Results mask values, but pasted headers can contain sensitive names and metadata. Do not share real session credentials.

Page updated · Project managed by Tony Hines · Report a problem with Cookie Header Explainer