Password Strength Checker
Measure password entropy and estimate crack time, analysed entirely in your browser.
Never type a password you actually use into a website you have not verified. This page analyses input locally and makes no network requests, you can confirm that in the DevTools Network tab before typing. If in any doubt, test a password of the same shape rather than the real one.
Type a password to analyse it.
Features
- Entropy calculated in bits from the actual character pool
- Crack-time estimates across four attacker capabilities
- Detects dictionary words, keyboard runs and repetition
- Penalises predictable substitutions like @ for a
- Runs entirely in your browser
How to use it
- Type or paste a password into the field.
- Read the entropy figure and the verdict.
- Check the weaknesses list for specific problems.
- Use the suggest button if you need a stronger one.
What entropy measures, and what it misses
Entropy in bits describes the size of the search space: each additional bit doubles the number of guesses needed. A password drawn randomly from a 95-character keyboard set carries about 6.6 bits per character, so a 12-character random password is roughly 79 bits. Below 50 bits is weak against a determined offline attack, around 70 is reasonable, and above 100 bits is beyond any foreseeable brute-force capability.
The critical caveat is that this arithmetic only holds for randomly generated passwords. Entropy calculated from the character pool badly overstates the strength of anything a human chose. Password123! scores about 79 bits by that formula but appears in every cracking dictionary and falls in milliseconds. Real attackers do not brute-force blindly, they start with leaked password lists, dictionary words with common substitutions, and keyboard patterns. That is why the weaknesses panel matters more than the headline number.
The crack-time figures assume the attacker has stolen a database and is attacking the hashes offline, which is the realistic threat. The rates vary enormously by hashing algorithm: a consumer GPU manages billions of SHA-256 guesses per second but only tens of thousands against properly configured bcrypt or Argon2. That difference is entirely the defender's choice, which is why how a site stores your password matters as much as how you chose it. In practice, length beats complexity, uniqueness beats both, and a password manager beats trying to remember any of it.
Frequently asked questions
Related tools
Further reading
Read the full guide on the 123MiniApps blog.