Expert Reviewed
Marcus Webb, B.Eng, Applied Mathematics SpecialistUpdated June 1, 2026Our Standards →

Last updated:

Password Generator

Generate strong, random passwords instantly with our free password generator. Customize length, symbols, numbers & special characters for maximum security on...

Secure Password Generator

Ad-FreeAI-Powered

Generate strong, random passwords, passphrases, and PINs. Analyze password strength with entropy calculation and estimated crack time.

Details

864

Quick Presets

Enter values above to see results.

Want to learn more? Browse our calculation guides and tutorials →

Reviewed by CalculatorApp.me Cybersecurity Team

Password Security: The Complete Guide

Entropy, brute-force resistance, NIST guidelines, and what makes a password truly unbreakable.

128 bits

Recommended minimum password entropy

3 billion

Compromised credentials in Have I Been Pwned

2.5 seconds

Time to crack 8-char lowercase password (2024 GPU)

550 yrs+

Time to crack 16-char random password

What Makes a Password Secure?

A secure password is one that is unpredictable (not derived from known patterns or personal information) and has high entropy — the measure of how many possible combinations an attacker must try to guess it. Every additional character exponentially multiplies the search space.

Modern attacks use GPU-accelerated cracking (e.g., Hashcat with RTX 4090) capable of testing 164 billion MD5 hashes per second — making short passwords catastrophically weak regardless of character variety. Length is now considered more important than character complexity alone.

NIST SP 800-63B (2017, updated 2024) fundamentally revised recommendations: prioritize length (minimum 8, recommend 15+), disallow periodic forced rotation, check against breach lists, and abandon complexity rules that produce predictable patterns (e.g., P@ssw0rd!).

Password Entropy & Cracking Time

Password Entropy
H = L × log₂(N)

H = entropy in bits
L = password length
N = character set size

Example: 12 chars, all ASCII printable (95):
H = 12 × log₂(95) = 12 × 6.57 = 78.9 bits

Each additional character adds log₂(N) bits of entropy. Longer is exponentially stronger.

Character Set Sizes
Lowercase a–z:        26 chars  (4.70 bits/char)
Lowercase + uppercase: 52 chars  (5.70 bits/char)
+ Numbers:            62 chars  (5.95 bits/char)
+ Symbols:            94–95 chars (6.57 bits/char)

Passphrase 5 words (from 7776-word list):
H = 5 × log₂(7776) = 5 × 12.92 = 64.6 bits

Passphrases (random words) are often more memorable AND more secure than short complex passwords.

Brute-force Cracking Time
Combinations = N^L
Time = Combinations ÷ hash_rate

RTX 4090 bcrypt (cost 12): ~184K/sec
RTX 4090 MD5:           ~164B/sec

MD5, 8 chars, full ASCII:
95^8 = 6.6×10¹⁵ ÷ 164B = ~11 hours avg

Hashing algorithm matters enormously. bcrypt/Argon2/scrypt are designed to be slow — protecting even shorter passwords.

NIST Entropy Estimation (SP 800-63B)
- First character:  4 bits
- Characters 2–8:  2 bits each (14)
- Characters 9–20: 1.5 bits each
- Characters 21+:  1 bit each
- Dictionary check: −6 bits
- NIST notes: this model
  is outdated; prefer
  measuring character set
  entropy instead

NIST 800-63B now recommends against complexity rules and mandatory rotation. Focus on length + breach checking.

NIST SP 800-63B Password Guidelines (2024)

GuidelineOld RecommendationNIST Current Guidance (800-63B)
Minimum length8 characters8 minimum; 15+ recommended; 64+ maximum
Complexity rulesUpper+lower+number+symbol requiredNOT required (produces predictable patterns)
Mandatory rotationEvery 90 daysOnly if compromise is suspected
Password hintsAllowDisallow
Security questionsAllowDisallow
Breach database checkNot standardRequired — check against known compromised credentials
MFAOptionalStrongly recommended

History of Password Security

1961

First computer password (MIT CTSS)

Fernando Corbató's CTSS time-sharing system at MIT introduced the first computer password system to protect users' files from each other.

1976

Unix crypt() function

Unix's crypt() implemented hashed password storage using a modified DES algorithm — the first mainstream password hashing system, still seen in /etc/shadow.

2004

Bill Gates predicts end of passwords

At RSA Conference 2004, Bill Gates predicted passwords would 'not be able to meet the challenge' of security — a prediction still being proven true 20 years later.

2012

LinkedIn, eHarmony mega-breaches

170M+ LinkedIn password hashes (SHA-1, no salt) were cracked within hours of leaking, revealing the systemic failure of weak hashing functions.

2017

NIST SP 800-63B published

NIST fundamentally revised password recommendations: no mandatory rotation, no complexity rules, minimum 8 characters, maximum 64+, breach database checking required.

2023–24

Passkeys begin replacing passwords

FIDO2/WebAuthn passkeys (Apple, Google, Microsoft) use public-key cryptography — no password transmitted or stored — beginning the gradual end of the password era.

Key References

Password Myths vs. Facts

Changing passwords frequently makes them more secure.

NIST 800-63B explicitly recommends AGAINST mandatory periodic rotation unless compromise is suspected. Forced rotation leads to predictable patterns (Password1 → Password2!) and post-it notes.

P@ssw0rd! is a strong password because it has symbols and numbers.

Dictionary-based substitutions (@ for a, 0 for o) are fully known to crackers. P@ssw0rd! would be cracked in seconds by any modern attack.

A short complicated password is better than a long simple one.

Entropy depends on both length and character space. 'correct-horse-battery-staple' (4 words, 28 chars) has ~44 bits of entropy — far stronger than 'Tr0ub4dor&3' (28 bits).

Password managers are risky because all your passwords are in one place.

A reputable password manager (Bitwarden, 1Password) with a strong master password is vastly safer than reusing passwords or writing them on paper. Zero-knowledge architecture means the provider cannot see your vault.

Frequently Asked Questions

How does this password generator work?
It uses your browser's crypto.getRandomValues() — a CSPRNG — to randomly select characters from your chosen character set. No passwords are transmitted to our servers.
How long should my password be?
NIST recommends a minimum of 8 characters; CISA recommends 16+ for privileged accounts. For critical accounts (bank, email, work), use 20+ characters.
Should I use a passphrase instead of a password?
For human-memorable passwords, yes. A 5-word passphrase (e.g., 'correct horse battery staple pen') has ~64 bits of entropy and is easier to remember than 'xK@9!mQz'.
Is the generated password stored anywhere?
No. Generation is entirely client-side. Nothing is sent to our servers or logged.
What password manager should I use?
Open-source options: Bitwarden (free, audited), KeePassXC (offline). Commercial: 1Password, Dashlane. All use zero-knowledge architecture — your master password is never stored.
What is multi-factor authentication (MFA) and should I use it?
MFA requires a second factor (authenticator app, hardware key) in addition to your password. Even if your password is stolen, MFA prevents account access. Use it on all critical accounts.
What is credential stuffing?
Automated attacks that try username/password combinations from leaked databases on other services. The defense: use unique passwords for every account (a password manager is essential for this).
What are passkeys?
FIDO2-based authentication using public-key cryptography. A passkey is stored on your device; the private key never leaves. No password is transmitted — eliminating phishing and credential stuffing.
How do I check if my password was leaked?
Use Have I Been Pwned (haveibeenpwned.com) to check your email and passwords against 12+ billion breached records. HIBP uses k-anonymity so your full password is never transmitted.
What hashing algorithm should websites use for passwords?
Argon2id (NIST recommended, winner of Password Hashing Competition), bcrypt (work factor 12+), or scrypt. Never MD5, SHA-1, or unsalted SHA-256 for passwords.
How does salting protect passwords?
A random value (salt) added before hashing ensures identical passwords produce different hashes. This prevents rainbow table attacks and ensures each password must be cracked individually.
What is a rainbow table attack?
A precomputed table of hash values for common passwords. Defeated entirely by salting. A 10-character random salt means ~82-trillion times more cracking effort per password.

References

Related Calculators

Protect Your Digital Life

Strong passwords, secure generators, and digital tools — everything to stay safe online.

Browse All Tools →