PASSWORD GAUNTLET

Type any password and watch four real cracking techniques hunt it — live. Then learn why some passwords die in seconds and others outlive the sun, and build one that survives.
All Levels

The Gauntlet — Test a Password

PROCESSED LOCALLY ONLY — nothing you type ever leaves this browser tab
Live strength estimate—
1
Common-Password List (top ~25)
instant
waiting...
2
Top-10k Dictionary
10,000 guesses · instant
waiting...
3
Dictionary + Mutation Rules (leet, years, caps)
~10M guesses · seconds
waiting...
4
Brute Force — every combination
10 GH/s vs MD5
waiting...
Gauntlet Verdict
vs MD5 · offline · 10 GH/s
—
vs bcrypt · offline · 100 kH/s
—

Passphrase Workshop

Diceware-style: random words beat clever substitutions. Click any word to re-roll just that word, or re-roll all. Then test your creation in the Gauntlet above.

Passphrase strength—

Why It Works — Four Lessons

Length beats complexity

Every added character multiplies the search space. A 16-char lowercase passphrase (~75 bits) outlives an 8-char "complex" password (~52 bits) by millions of times. Complexity rules mostly force humans into predictable patterns (Capital + word + digit + !).

Tr0ub4dor&3 → ~52 bits → cracked in ~3 days correct-horse-battery-staple → ~75 bits → ~550 years @10GH/s

What salts do

A salt is a random value stored beside the hash: hash(salt + password). It kills precomputed rainbow tables and forces every hash to be cracked individually — two users with the same password get different hashes. Salts are not secret; they just make attacks expensive per-user instead of free-for-all.

unsalted MD5("hunter2") → same hash everywhere, rainbow table = instant bcrypt($2y$10$N9qo8uLO...salt..., "hunter2") → unique, must brute-force at 100kH/s

Why reuse kills you

Your password's strength doesn't matter if it's already in a breach dump. Attackers take leaked email:password pairs and replay them everywhere (credential stuffing). One weak site falls, every account sharing that password falls — the strongest password in the world is worthless the second time you use it.

Site A breached → your P@ssw0rd!2026 leaks → attacker tries it on your email, bank, work VPN... → unique password per site = the breach dies at site A

Slow hashes save lives

MD5/SHA1 are built for speed — terrible for passwords. bcrypt, scrypt, and Argon2 are deliberately slow and memory-hungry. Same password, two realities: MD5 falls at 10 billion guesses/second; bcrypt at 100 thousand. That's a 100,000× tax on the attacker, for free.

8-char password, offline attack: MD5 @ 10 GH/s → ~6 hours bcrypt @ 100 kH/s → ~70 years