What it means
A cookie your site sets is missing a protective flag. This guide covers the cookie findings:
a cookie set over HTTPS without Secure, a session cookie without HttpOnly, a cookie without
SameSite, SameSite=None without Secure, or a __Host- or __Secure- cookie that breaks its rules.
The detail names the cookies; we never record their values.
Why it matters
Without Secure, the browser also sends the cookie over plain HTTP, where anyone on the network
can steal it. Without HttpOnly, any script on the page, including injected ones, can read a session
cookie. Without SameSite, other sites can trigger requests that carry it, which enables cross-site
request forgery. Browsers reject SameSite=None without Secure outright.
How to fix it
- Add
Secureto every cookie on an HTTPS site. - Add
HttpOnlyto session and authentication cookies, which scripts never need. - Add
SameSite=Laxby default,Strictfor sensitive actions, andNone; Secureonly for cookies that must work inside other sites. - For
__Host-cookies useSecure; Path=/and noDomain;__Secure-cookies needSecure.
Most frameworks set these in one place, such as the session cookie settings.
Check it worked
Run the HTTP and security headers check again. The cookie table should show the flags, and the cookie findings should be gone.