What is Cookie flags?
also: Secure, HttpOnly and SameSite attributes
// short answer
Settings on a website's cookies — Secure, HttpOnly and SameSite — that control when browsers send them and whether scripts can read them.
In plain English
Websites use cookies to remember things, such as who is logged in. Each cookie can carry flags that tell the browser how carefully to handle it:
- Secure — only send the cookie over encrypted HTTPS connections, never plain HTTP.
- HttpOnly — page scripts cannot read the cookie, so injected code cannot simply copy it.
- SameSite — limits sending the cookie when another site triggers the request.
Laxis a good default;Strictis stricter;NonerequiresSecure.
Set-Cookie: session=…; Path=/; Secure; HttpOnly; SameSite=LaxWhy it matters to a small business
Login cookies are effectively keys to an account. Missing flags make it easier for those keys to leak over an unencrypted connection or be stolen through cross-site scripting. For a shop or members area, that means customer accounts.
What to do
The free check lists the cookies your home page sets and which flags are missing. Session and login cookies should have all three. Your developer can usually fix this in the platform's configuration rather than in code.