Every check / insecure-cookies
Are the cookies your site sets protected from being copied or read?
We read every cookie your homepage sets and look for two attributes: Secure and HttpOnly.
How it decides
The check reports each one that is missing and names the cookies, and asks for Secure only on a site served over https. A missing SameSite is a check of its own, and so are a login cookie that scripts can read and a cookie marked SameSite=None without Secure.
Run this check on any website
Free, with no account. It sends the site nothing an ordinary visitor would not.
Why it matters
A cookie often keeps a customer signed in.
In more detail
Without Secure it can cross an insecure connection where anyone on the network can copy it. Without HttpOnly any script on the page can read it. HttpOnly hides a cookie from your own scripts as well, so one they read, such as a consent choice or a form's security token, has to stay without it.
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 standard
- Its name in a report
insecure-cookies