The page set no cookies
InfoConfirmedweb.cookies.none-set
What this check looks for
No cookies were set on the page we checked. There is nothing to grade here.
Why it matters
Nothing is wrong. It is recorded so the empty cookie table is explained rather than looking like a check that failed to run — and because a login page or a checkout would normally set one, so an unexpected absence is worth noticing.
What it costs your score
This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.
- Severity
- info
- Default confidence
- confirmed
- Status when triggered
- info
- Deduction
- 0 points
- Family cap
- none
- Category
- Web security
- Module
- Web cookies
- Fix owned by
- user
- In the ruleset since
- 2026.09
Technical detail
No Set-Cookie header was present on the final response from ‹origin›. Only that one page was requested, so cookies set elsewhere on the site — after signing in, for instance — are not covered by this check.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.
Other web cookies checks
- Cookie sets a Domain the browser will not accept, so it is discarded
- Cookie carries an attribute browsers cannot read
- Cookie can be read by JavaScript
- Cookie has no SameSite attribute
- Cookie is sent over unencrypted connections
- Cookie is shared with every subdomain
- Cookie name promises protections its attributes do not provide
- Cookie uses SameSite=None without Secure, so it is rejected