Every check / samesite-none-without-secure
Are browsers throwing away cookies your site depends on?
We read every cookie your homepage sets for SameSite=None without the Secure attribute, a pair Chrome, Edge and Firefox refuse.
How it decides
The check speaks up when it finds one, and names it. On a site served over plain http it stays quiet: browsers refuse a cookie marked Secure there, so https comes first, and the https check asks for it.
Run this check on any website
Free, with no account. It sends the site nothing an ordinary visitor would not.
Why it matters
Chrome, Edge and Firefox throw those cookies away, so whatever relied on them, a login or a basket, is failing for their users without any error you would see.
In more detail
Safari keeps them, and they can then be sent over an unprotected connection, where anyone on the same network can copy them. Adding Secure is one attribute.
Who fixes it, and where it runs
- Who usually fixes it
- Whoever built your site
- Which plan runs it
- The Business plan
- Proof you own the site
- Not needed. It sends your site nothing an ordinary visitor would not.
More about this check
- Who it is about
- A regulator
- Listed under
- Tracking and privacy
- The standards
- Its name in a report
samesite-none-without-secure