What Makes a Strong Password? The Complete Guide to Password Security
Your password is often the only thing standing between your personal data and an attacker. Yet most people still use weak, reused passwords that can be cracked in seconds. Here's everything you need to know about creating passwords that actually protect you.
Table of Contents
- Why Passwords Matter
- What Makes a Password Strong?
- Password Entropy — The Math Behind Strength
- How Passwords Get Cracked
- Length vs Complexity — Which Matters More?
- Common Password Mistakes
- The Passphrase Approach
- Password Managers — Why You Need One
- Two-Factor Authentication (2FA)
- How Passwords Are Stored (Hashing)
- Best Practices — The Complete Checklist
Why Passwords Matter
Passwords are the most fundamental layer of security on the internet. Despite decades of predictions about a "passwordless future," passwords remain the primary authentication method for the vast majority of online services — from email and banking to social media and cloud storage.
The stakes are high. A compromised password can lead to:
- Identity theft — Attackers can impersonate you, open accounts in your name, or file fraudulent tax returns.
- Financial loss — Access to banking, cryptocurrency, or payment accounts can result in direct monetary theft.
- Data breaches — One compromised account can cascade to others if you reuse passwords.
- Privacy violations — Personal emails, photos, health records, and private conversations can be exposed.
- Professional damage — Compromised work accounts can lead to corporate data leaks and career consequences.
According to Verizon's Data Breach Investigations Reports, compromised credentials consistently rank as one of the top attack vectors, involved in a large portion of data breaches globally. The good news? A strong, unique password dramatically reduces your risk.
What Makes a Password Strong?
A strong password is one that is difficult for both humans and computers to guess. It has four key properties:
| Property | Why It Matters | Example |
|---|---|---|
| Length | More characters = exponentially more combinations to guess | 16+ characters is ideal |
| Character variety | Using uppercase, lowercase, numbers, and symbols increases the pool | Kx9#mP2$vR7@nQ4 |
| Randomness | No patterns, dictionary words, or personal info that can be guessed | Random > predictable patterns |
| Uniqueness | Different password for every account prevents cascade breaches | Never reuse across sites |
The #1 Rule
Never reuse passwords. When one service gets breached (and they do — regularly), attackers immediately try those credentials on every other major service. This is called credential stuffing, and it's incredibly effective against people who reuse passwords.
Password Entropy — The Math Behind Strength
Entropy measures how unpredictable a password is, expressed in bits. Higher entropy = harder to crack. The formula is:
Entropy = L × log₂(R)
Where:
L = password length (number of characters)
R = size of the character pool
Examples:
8 chars, lowercase only (26): 8 × log₂(26) = 8 × 4.7 ≈ 37.6 bits
8 chars, mixed + numbers (62): 8 × log₂(62) = 8 × 5.95 ≈ 47.6 bits
8 chars, all types (95): 8 × log₂(95) = 8 × 6.57 ≈ 52.6 bits
16 chars, all types (95): 16 × log₂(95) = 16 × 6.57 ≈ 105 bits
20 chars, all types (95): 20 × log₂(95) = 20 × 6.57 ≈ 131 bits| Entropy (bits) | Strength | Practical Assessment |
|---|---|---|
| < 28 | Very Weak | Crackable in seconds. Never use. |
| 28–35 | Weak | Crackable in minutes to hours. |
| 36–59 | Fair | Reasonable for low-value accounts only. |
| 60–127 | Strong | Good for most accounts. |
| 128+ | Very Strong | Infeasible to brute-force with any known technology. |
Notice how doubling the password length doubles the entropy, but doubling the character pool adds far less. This is why security experts increasingly recommend longer passwords over shorter, more complex ones.
How Passwords Get Cracked
Understanding how attackers crack passwords helps you understand why certain practices matter:
1. Brute Force Attack
The attacker tries every possible combination systematically. A modern GPU can test billions of password hashes per second against weak algorithms like MD5.
Time to brute-force (at 10 billion guesses/second):
6 chars, lowercase: ~3 seconds
8 chars, lowercase: ~35 minutes
8 chars, mixed case + digits: ~14 hours
8 chars, all types: ~19 days
12 chars, all types: ~17,000 years
16 chars, all types: ~billions of years
Note: These times assume offline attacks against fast hashes.
Modern hashing (bcrypt, Argon2) makes each guess much slower.2. Dictionary Attack
Instead of trying every combination, attackers use lists of common passwords, English words, names, and known patterns. These lists contain millions of entries from previous data breaches.
Common passwords attackers try first:
123456 password qwerty
123456789 12345678 111111
iloveyou admin welcome
monkey dragon master
letmein abc123 football3. Rule-Based Attack
Attackers apply common transformations to dictionary words, because they know how people "strengthen" passwords:
Base word: "password"
Attackers try these variations automatically:
Password (capitalize first letter)
PASSWORD (all caps)
password1 (append number)
password123 (append common number sequence)
p@ssword (common substitution: a → @)
p@ssw0rd (multiple substitutions: a → @, o → 0)
Password1! (capitalize + number + symbol)
password2026 (append current year)
drowssap (reversed)
These patterns are trivially easy for cracking software.4. Credential Stuffing
When a website gets breached, the stolen email/password pairs are tested against other services. If you reuse passwords, one breach compromises all your accounts. Attackers automate this process, testing millions of stolen credentials against popular services within hours of a breach.
5. Phishing
No amount of password strength helps if you type your password into a fake login page. Phishing attacks trick users into voluntarily handing over their credentials. This is why two-factor authentication is so important — it provides a second layer of defense even when your password is compromised.
Length vs Complexity — Which Matters More?
This is one of the most debated topics in password security. The answer is clear: length wins.
Comparing passwords by their total possible combinations:
"Tr0ub4d&" (8 chars, all types)
= 95⁸ = 6.6 trillion combinations (52.6 bits)
"correcthorsebatterystaple" (25 chars, lowercase only)
= 26²⁵ = 2.4 × 10³⁵ combinations (117.5 bits)
The simple lowercase passphrase is astronomically stronger!
Even better — add some variety:
"Correct.Horse" Battery-Staple!" (32 chars, mixed)
= Practically uncrackable by any known methodNIST (the National Institute of Standards and Technology) updated their password guidelines in Special Publication 800-63B to emphasize length over complexity. Their key recommendations:
- Minimum 8 characters, but longer is always better
- Allow at least 64 characters maximum length
- Don't force complexity rules (mandatory symbols, etc.) — they lead to predictable patterns
- Check passwords against known breach lists
- Don't require periodic password changes — they actually reduce security
The Old Advice Was Wrong
For years, we were told to use short passwords with mandatory complexity (P@$$w0rd!) and change them every 90 days. NIST now says both practices are counterproductive — they lead to weaker passwords and user frustration. The current best practice is long, unique passwords managed by a password manager.
Common Password Mistakes
Even security-conscious people fall into these traps:
| Mistake | Example | Why It's Weak |
|---|---|---|
| Predictable substitutions | p@$$w0rd | Cracking tools try these substitutions automatically |
| Keyboard patterns | qwerty, 1qaz2wsx | These patterns are in every attack dictionary |
| Personal information | alice1990, fluffy2020 | Social engineering + social media makes these guessable |
| Appending numbers | password1, secure123 | One of the first variations attackers try |
| Year suffixes | Summer2026! | Season + year + symbol is an extremely common pattern |
| Password reuse | Same password everywhere | One breach compromises all your accounts |
The Passphrase Approach
A passphraseis a password made up of multiple random words. It's long (high entropy) but still memorable. The concept was popularized by the famous XKCD comic "correct horse battery staple."
Random password: Kx9#mP2$vR7@ (hard to remember, 78 bits)
Passphrase: mango-telescope-river-blanket (easy to remember, 77+ bits)
Both are similarly strong, but the passphrase is far more memorable.
Even stronger passphrases:
"correct horse battery staple" (~44 bits with 4 common words)
"mango telescope river blanket jazz" (~64 bits with 5 random words)
"Mango.Telescope.River!Blanket" (~90+ bits with mixed formatting)The key rule for passphrases: the words must be truly random, not a meaningful phrase. "I love my cat Fluffy" is terrible — it's a predictable sentence. "mango telescope river blanket" works because the words have no logical connection.
Use a method like Dicewareto select words randomly: roll physical dice and look up words in a numbered word list. This ensures true randomness that your brain can't unconsciously bias.
Password Managers — Why You Need One
The average person has 70–100+ online accounts. Remembering a unique, strong password for each one is humanly impossible. This is where password managers come in.
A password manager is software that:
- Generates strong, random passwords for each account
- Stores them in an encrypted vault
- Auto-fills login forms so you never need to type or remember passwords
- Syncs across all your devices
- Alerts you when passwords appear in data breaches
You only need to remember one strong master password (or passphrase) to unlock the vault. Everything else is handled automatically.
Is It Safe to Put All Passwords in One Place?
Yes — a reputable password manager is far safer than reusing passwords or writing them on sticky notes. Password managers use AES-256 encryption and zero-knowledge architecture, meaning even the company running the service cannot access your data. The encrypted vault is useless without your master password.
Two-Factor Authentication (2FA)
A strong password is your first line of defense. Two-factor authentication (2FA)is your second. Even if an attacker gets your password (through phishing, a data breach, or malware), they still can't access your account without the second factor.
| 2FA Method | Security Level | Notes |
|---|---|---|
| Hardware security key (FIDO2/WebAuthn) | Highest | Physical device (YubiKey, etc.). Phishing-resistant. |
| Authenticator app (TOTP) | High | Google Authenticator, Authy, etc. Time-based codes. |
| Push notification | High | Approve/deny from your phone. Convenient. |
| SMS codes | Moderate | Vulnerable to SIM swapping. Better than nothing. |
Enable 2FA on every account that supports it — especially email (the master key to password resets), banking, cloud storage, and social media. Even SMS-based 2FA, despite its weaknesses, blocks the vast majority of automated attacks.
How Passwords Are Stored (Hashing)
Responsible websites never store your actual password. Instead, they store a hash — a one-way mathematical fingerprint of your password. When you log in, the server hashes what you typed and compares it to the stored hash.
Your password: "MySecureP@ss123"
How a responsible site stores it:
bcrypt hash: $2b$12$LJ3m4ks9Hyl3pGSwKhMzpeOJvOS.gRqkL8IKHhC8mRxQfOz7v8MXi
Key properties of good hashing:
✓ One-way: Can't reverse the hash back to the password
✓ Salted: Each user gets a unique random salt, so identical
passwords produce different hashes
✓ Slow: bcrypt/Argon2 are intentionally slow to compute,
making brute-force attacks impractical
✓ Unique: Any change to the password completely changes the hash| Algorithm | Status | Notes |
|---|---|---|
| Argon2 | Recommended | Winner of the Password Hashing Competition. Memory-hard. |
| bcrypt | Good | Industry standard since 1999. CPU-hard with configurable cost. |
| scrypt | Good | Memory-hard. Used in some cryptocurrency protocols. |
| SHA-256 (with salt) | Acceptable | Fast — needs many rounds (PBKDF2) to be safe. |
| MD5 / SHA-1 | Broken | Too fast. Billions of hashes per second on GPUs. Never use. |
When a site gets breached, the security of your password depends on which hashing algorithm they used. With bcrypt, even a short password takes significant time to crack. With MD5, even a decent password falls quickly.
Best Practices — The Complete Checklist
- Use a password manager — Let it generate and store unique random passwords for every account. This is the single most impactful step you can take.
- Make passwords long — Aim for 16+ characters for generated passwords. For passwords you need to remember (like your master password), use a 4–5 word passphrase.
- Never reuse passwords — Every account gets a unique password. No exceptions.
- Enable 2FA everywhere — Use authenticator apps or hardware keys. SMS is better than nothing.
- Check for breaches — Use services like Have I Been Pwned to check if your email or passwords have appeared in known data breaches.
- Don't use personal information — No names, birthdays, pet names, addresses, or phone numbers in passwords.
- Be skeptical of login pages — Always verify the URL before entering credentials. Phishing is the #1 way passwords are stolen.
- Don't change passwords on a schedule — Only change passwords when you have reason to believe they're compromised. Forced rotation leads to weaker passwords.
- Secure your email — Your email account is the skeleton key for "forgot password" resets. Give it the strongest protection possible.
- Use generated passwords — Human-chosen passwords are inherently biased and predictable. True randomness from a password generator is always stronger.
Generate Strong Passwords Instantly
Use our free Password Generator to create strong, random passwords with customizable length, character types, and options — right in your browser with no data uploaded to any server.
Try Password Generator →References
- Grassi, P.A., et al. (2017). NIST Special Publication 800-63B — Digital Identity Guidelines: Authentication and Lifecycle Management. https://pages.nist.gov/800-63-3/sp800-63b.html
- Verizon. Data Breach Investigations Report (DBIR). https://www.verizon.com/business/resources/reports/dbir/
- Bonneau, J., et al. (2012). The Quest to Replace Passwords. IEEE Symposium on Security and Privacy. https://www.cl.cam.ac.uk/~jcb82/doc/B12-IEEESP-quest_to_replace_passwords.pdf
- OWASP. Password Storage Cheat Sheet. https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html
- Biryukov, A., Dinu, D., & Khovratovich, D. (2016). Argon2: the memory-hard function for password hashing and other applications. https://www.password-hashing.net/argon2-specs.pdf