Web & Dev

Password Strength Guide

Password entropy, crack times, and what actually makes a password strong.

Entropy basics

Bits of entropylog₂(possible combinations)
Lowercase only (26)4.7 bits per char
Alphanumeric (62)5.95 bits per char
With symbols (~94)6.55 bits per char
Diceware (7776 word list)12.9 bits per word

Rough crack times (offline, 10 billion guesses / sec, time to try every combination)

PasswordEntropyCrack time
"password"27 bitsinstant
"P@ssw0rd1"43 bitsminutes (dictionary)
12 lowercase random56 bits~110 days to exhaust the space
14 alphanum random83 bits~39 million years
16 mixed + symbols105 bits~1.2 × 10¹⁴ years
4-word Diceware52 bits~4 days
6-word Diceware77 bits~700 000 years

What actually helps

  • Length beats complexity. 20 random lowercase letters is stronger than 8 weird symbols.
  • Use a password manager. Random 20+ char passwords per site.
  • Enable MFA. Password compromises happen; MFA blocks the attack.
  • Check against breaches. Have I Been Pwned's k-anonymity API, or 1Password Watchtower.
  • Avoid predictable patterns. Substitutions (@ for a) add almost no entropy.

Worked example: from length to crack time

Entropy is length times bits per character, and it only holds for truly random choices. Twelve random lowercase letters: 12 × log₂(26) = 12 × 4.70 = 56.4 bits, a space of 256.4 ≈ 9.5 × 1016 guesses. At 10 billion guesses per second that is 9.5 × 106 seconds, about 110 days to exhaust and roughly half that on average. Add just 8 more lowercase letters (20 in all, 94 bits) and the same attacker needs about 6 × 1010 years to exhaust the space, because every added character multiplies the work by 26. A four-word Diceware passphrase is 4 × 12.9 = 51.7 bits, about 4 days at that rate; six words is 77.5 bits, about 700,000 years.

The rate above is a fast offline attack against an unsalted fast hash. Against a slow password hash such as bcrypt, scrypt or argon2, the guess rate falls enormously, which is why the hash a site uses matters as much as your password. Entropy figures also assume the attacker has no shortcut: a word from a dictionary, a keyboard pattern or a reused password is cracked in far fewer guesses than its length suggests.

Current official guidance

  • NIST SP 800-63B requires user-chosen passwords of at least 8 characters, and says systems should accept at least 64 characters so passphrases work.
  • It advises screening new passwords against lists of known-breached and commonly used values, instead of imposing composition rules such as “one symbol and one capital”.
  • Reuse is the biggest practical risk: a strong password leaked from one site is tried on every other. A unique password per site, stored in a manager, limits the damage to one account.
  • A passphrase is strong only if the words are chosen by dice or a generator. Words you pick yourself, such as a favorite quote, are far more guessable than 12.9 bits each.

Notes

  • Bcrypt/argon2/scrypt slow per-guess rates down by 10⁵ – 10⁶×; hardware attacks on fast hashes (MD5, SHA-1) are orders of magnitude faster.
  • NIST SP 800-63B dropped the "rotate every 90 days" rule in 2017 — rotation without compromise is counterproductive.
Was this article helpful?