Password Entropy Demystified: Mathematical Strength and NIST 800-63B Guidelines
Understand what password entropy estimates can and cannot tell you, how NIST SP 800-63B-4 guides password policy, and why length, blocklists, and unique passwords matter.
Password strength is often described with an entropy number, but that number depends on assumptions about how a password was created. This guide explains the basic model, why real human choices differ from random strings, and what current NIST guidance says about password policies.
Open the Password Generator → Check a password strength estimate →
What the entropy formula assumes
For a uniformly random string of length L chosen independently from an alphabet of R characters, the theoretical entropy is L × log₂(R) bits. This model is useful for comparing randomly generated candidates. It does not accurately measure a password someone invented from a name, phrase, keyboard pattern, or predictable substitutions: human choices are not uniformly random.
A strength meter estimates resistance to guessing using assumptions about common patterns and attacker behavior. It cannot prove that a password is safe, and its result may differ from another meter. Do not enter a real password into an untrusted checker. A locally running checker still depends on the integrity of the page and its scripts.
Current NIST guidance
NIST SP 800-63B-4, published in 2025, sets requirements for digital identity services. It requires a minimum of 15 characters when a password is used as a single factor. Passwords used only within multi-factor authentication may be shorter, but must be at least 8 characters. Verifiers should permit at least 64 characters, accept spaces and printable characters, and not impose character-class composition rules. They must check prospective passwords against a blocklist of commonly used, expected, or compromised choices. Routine periodic changes are not required, though a change is required when there is evidence of compromise. See the official NIST SP 800-63B-4 for full requirements and context.
Practical habits that improve account security
- Use a distinct password for every account, preferably stored in a reputable password manager.
- Choose a long passphrase or generate a random password; avoid predictable substitutions and reused phrases.
- Enable multi-factor authentication where available. Passwords alone are not phishing-resistant.
- Change a password promptly if it is exposed or the service reports a compromise.
Generate and review securely
A cryptographic generator should draw randomness from a cryptographically secure source such as the browser’s Web Crypto API, not Math.random(). A trustworthy implementation also avoids biased character selection. Use the Password Generator for a new unique secret, and keep passwords private; do not paste a real account password into a checker just to obtain a score.
Written by Dr. Sarah Chen
Senior Web Performance Engineer and browser runtime researcher. Ph.D. in Computer Science with a focus on compiler optimization and sandboxed execution. Research contributor on WebAssembly, HTML5 Canvas, and modern browser standards at IT Market Plus.
Ali Raza
Principal Software Engineer & Technical Architect with over a decade of experience in client-side web technologies, cryptography, and Core Web Vitals optimization. Founder & Editorial Lead at IT Market Plus.
Related Editorial Guides
Client-Side Cryptography: Why Computing in Browser Memory Protects User Privacy
See how browser-based cryptography can reduce data exposure, how Web Crypto works, and where client-side processing still needs careful security design.
Anatomy of JSON Web Tokens (JWT): Payload Decoding, Signature Verification & Claims
Understand JWT structure, base64url payload decoding, signature verification, claim validation, and safe handling of bearer tokens.
Web Security Primer: Mitigating Cross-Site Scripting (XSS) via Context-Aware HTML Entity Encoding
Learn how XSS happens and why safe text APIs, context-aware output handling, HTML sanitization, and defense-in-depth work together.