Every check / code-stores-credentials
Does your site keep login tokens where any script can read them?
We read the script files your site serves from its own domain for writes to localStorage or sessionStorage under a name such as token, password, auth or jwt.
How it decides
The check matches the name of what is stored, never reads the value, and speaks up when it finds one.
Run this check on any website
Free, with no account. It sends the site nothing an ordinary visitor would not.
Why it matters
Every script on the page can read browser storage, including other companies' and anything an attacker injects, so a login token kept there is one script away from being stolen.
In more detail
A cookie marked HttpOnly is invisible to scripts, which is the reason that setting exists.
Who fixes it, and where it runs
- Who usually fixes it
- Whoever built your site
- Which plan runs it
- The free scan, on any website
- 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
- An intruder
- Listed under
- Things that should not be public
- The standards
- Its name in a report
code-stores-credentials