Password Strength Checker
Check how strong a password is and see estimated crack times based on its entropy, entirely in your browser with nothing sent or saved. Compare a short complex password against a long simple one, or spot a keyboard-pattern password during a security review.
Start typing a password above to see its strength analysis.
Usage examples
Checking a password before using it on a new account
Type a candidate password to see its estimated strength, crack-time ranges, and any risky patterns before you commit to using it.
Understanding why a password that 'looks complex' is actually weak
A password like 'Password123!' mixes character types but matches a well-known pattern — this tool flags it as weak despite its length and variety, because real attackers try common patterns first.
Comparing a short complex password against a long simple one
Try a short password with symbols and a long passphrase of ordinary words side by side to see how much length alone improves the brute-force crack-time estimate.
Checking a password generated by a password manager
Paste a randomly generated password like 'xT9#mK2$pL8qR' to confirm it registers as 'Very strong' with no detected weaknesses before saving it to an account.
Spotting a keyboard-pattern password during a security review
Type something like 'qwertyuiop' or 'asdf1234' to see how the keyboard-run detector flags it as weak even though it mixes letters and digits and is reasonably long.
Quick reference
Crack time (offline, fast hardware: 10B guesses/sec)
| Length | Digit (10) | Lowercase (26) | Lowercase + Uppercase (52) | Lowercase + Uppercase + Digit (62) | Lowercase + Uppercase + Digit + Symbol (88) |
|---|---|---|---|---|---|
| 4 | Instantly | Instantly | Instantly | Instantly | Instantly |
| 6 | Instantly | Instantly | Instantly | 3 seconds | 23 seconds |
| 8 | Instantly | 10 seconds | 45 minutes | 3 hours | 2 days |
| 9 | Instantly | 5 minutes | 2 days | 8 days | 183 days |
| 10 | Instantly | 2 hours | 84 days | 1 year | 44 years |
| 11 | 5 seconds | 2 days | 12 years | 82 years | Centuries |
| 12 | 50 seconds | 55 days | Centuries | Centuries | Centuries |
| 13 | 8 minutes | 4 years | Centuries | Centuries | Centuries |
| 14 | 1 hour | Centuries | Centuries | Centuries | Centuries |
| 15 | 14 hours | Centuries | Centuries | Centuries | Centuries |
| 16 | 6 days | Centuries | Centuries | Centuries | Centuries |
| 18 | 2 years | Centuries | Centuries | Centuries | Centuries |
| 20 | Centuries | Centuries | Centuries | Centuries | Centuries |
Crack time (online, rate-limited: 100 guesses/sec)
| Length | Digit (10) | Lowercase (26) | Lowercase + Uppercase (52) | Lowercase + Uppercase + Digit (62) | Lowercase + Uppercase + Digit + Symbol (88) |
|---|---|---|---|---|---|
| 4 | 50 seconds | 38 minutes | 10 hours | 21 hours | 3 days |
| 5 | 8 minutes | 17 hours | 22 days | 53 days | 305 days |
| 6 | 1 hour | 18 days | 3 years | 9 years | 74 years |
| 7 | 14 hours | 1 year | Centuries | Centuries | Centuries |
| 8 | 6 days | 33 years | Centuries | Centuries | Centuries |
| 10 | 2 years | Centuries | Centuries | Centuries | Centuries |
| 12 | Centuries | Centuries | Centuries | Centuries | Centuries |
Frequently asked questions
Is this an exact measure of how crackable my password really is?
No. This is a simplified, educational heuristic estimate based on character variety, length, and a few common weak patterns. It is not a guarantee of real-world security, and it does not check your password against live breach databases like Have I Been Pwned — this site makes no network requests at all.
Is my password sent anywhere or saved?
No. Everything happens locally in your browser using JavaScript. Your password is never transmitted over the network and is never written to local storage, cookies, or any other persistent storage — it only exists in the page's memory while you're typing, and disappears when you leave or reload the page.
Why do you show two different crack-time estimates?
A single number can be misleading. The 'online, rate-limited' estimate assumes an attacker guessing through a normal login form with basic rate limiting (100 guesses/second). The 'offline, fast hardware' estimate assumes an attacker who has stolen a password database and is guessing offline with powerful GPUs (10 billion guesses/second). Real-world risk depends heavily on which scenario applies.
Why does a common password show 'Instantly' even if it's long?
Real attackers don't brute-force character-by-character first — they try dictionaries of known common and breached passwords. If your password matches one of those, length and character variety barely matter, because it would be one of the very first guesses tried.
What's the single best thing I can do to improve my passwords?
Use a password manager to generate and store long, random, unique passwords for every site — that way a breach on one site can't be used to break into your other accounts. When you do need to remember a password, prefer length (a long passphrase of several random words) over complexity.
What counts as a 'symbol' character for the character-type check?
Any printable character that isn't a letter or digit — punctuation marks like !, @, #, $, %, and similar symbols all count. Spaces and non-ASCII characters (like emoji or accented letters) may not be recognized the same way, since this tool's heuristic is built around standard keyboard characters.
Why does adding one more character sometimes jump the strength rating a lot?
Brute-force difficulty grows exponentially with length, not linearly — each additional character multiplies the total number of possible combinations by the size of the character set used. So going from 7 to 8 characters can have a much bigger effect on estimated crack time than it might seem, especially once a password crosses this tool's 'tooShort' threshold of 8 characters.