Every check / code-uses-weak-randomness

Does your site make security values with a predictable random number?

We read the script files your site serves from its own domain for Math.random() within about 60 characters of a word such as token, session, key or password.

How it decides

It is a near match, so some hits will be harmless, and a developer can tell which in a minute.

Run this check on any website

Free, with no account. It sends the site nothing an ordinary visitor would not.

Why it matters

That generator is built to be fast, not unguessable, and its output can be predicted from earlier values.

In more detail

If one of these becomes a session token or a password reset link, somebody can work out the next one. The browser's crypto API is the replacement, and it needs no library.

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
An intruder
Listed under
Things that should not be public
The standard
Its name in a report
code-uses-weak-randomness