Test password strength: entropy, time-to-crack, pattern warnings
Real-time entropy estimate, time-to-crack at 100B guesses/sec, pattern warnings, and a 7-point checklist. Type or paste a password to evaluate.
The Strength Tester evaluates a password against several axes simultaneously: information entropy (bits), estimated time to crack at 100 billion guesses per second (modern GPU cluster), and a battery of pattern checks (common passwords, sequential runs like 12345 or qwerty, repeated characters, l33t-speak substitutions of common words).
Entropy is the cleanest single metric: it is the log-base-2 of the search space. A truly random 14-character password from 95 printable characters has log2(95^14) ≈ 92 bits — strong. A 6-word EFF passphrase has 6 × log2(7776) ≈ 77 bits — also strong. A common dictionary word with l33t substitutions has maybe 25 bits — weak.
Use the tester to evaluate candidates from the Password Generator, to audit existing passwords (only paste in a private window), or to learn what makes a password strong by experimenting with the inputs.
Frequently asked questions
What does "time to crack" actually mean?
It assumes an attacker can compute 10^11 password hashes per second — roughly what a high-end GPU rig can do for a fast hash like MD5 or SHA-256. For slow hashes (Argon2id, bcrypt, scrypt), the actual rate is 10^4–10^6/sec, and time-to-crack is millions of times higher than what we display.
Why does my long password score low?
Pattern detection. "P@ssw0rd1!" is 11 characters but is a known common-password variant — the search space attackers explore is far smaller than naive entropy suggests.
Is the password I type sent anywhere?
No. The evaluation runs entirely in the page. There is no network call, no log, no remote dictionary lookup.
What is a good entropy target?
For online accounts (rate-limited): 60+ bits. For offline-attackable secrets (key passphrases, encrypted file passwords): 80+ bits. For long-term high-value secrets (root keys, recovery codes): 100+ bits.
Why does "trustno1" rank so badly?
Because it appears in every password breach corpus. The pattern detector recognizes common passwords and substitutes regardless of length or symbol use.