Password Strength Checker

Type a password and see the bits, the estimated crack time and what is wrong with it.

— — · —

The analysis runs in this page. Nothing is transmitted — open your browser's Network tab and check while typing.

This checker never sends the password anywhere — the analysis runs in the page. That matters more than the algorithm: a strength checker that transmits the password is worse than none at all.

The score is entropy-based with penalties for the patterns attackers actually try first: repeated characters, keyboard sequences, digits only, years, and common password words. It is not a full dictionary attack simulation, and the page does not claim to be.

How to use it

  1. Type or paste a password into the field.
  2. Read the bit count first, then the estimated crack time.
  3. Fix the listed notes before worrying about the colour of the bar.

How the estimate is calculated

The base figure is the size of the character set actually used, multiplied by length, in bits. A password of only lowercase letters has a 26-character set; adding digits raises it to 36, and so on. The result is then reduced if a weak pattern is found — a 12-character password with '1234' in it is not worth the full 12-character figure.

The crack-time estimate assumes 10^11 guesses per second, roughly a multi-GPU offline attack against a fast hash. Against a slow hash such as bcrypt it is pessimistic by several orders of magnitude; against a site storing plaintext it is optimistic.

Reviewed 2026-10-21. This tool runs entirely in your browser — no server, no account, and nothing you generate is stored.

Frequently asked questions

Is it safe to type my real password here?

The analysis is local, so nothing is transmitted. If you want certainty, open developer tools, watch the Network tab while typing, and confirm no request is made.

Why does a long password sometimes score lower than expected?

Because length alone is not the whole story. A 20-character password made of a dictionary word repeated scores near the floor — attackers try patterns before they try brute force.

What crack time should I aim for?

Beyond a few centuries against an offline attack, which is roughly 80 bits. Above that, the practical risk shifts to phishing and reuse rather than guessing.

Related tools

More from Passwords.