Password Audit & Policy Generator
Strength checker, entropy, NIST 2024 compliance, character composition · 100% in browser
Check password strength
All analysis runs in your browser — nothing is sent to any server.
Runs in your browser — nothing is sent to any server. NIST SP 800-63B aligned.
What Is a Password Strength Checker?
A password strength checker analyses a password's randomness and resistance to attack without ever sending it to a server. It calculates entropy — a measure of unpredictability in bits — by looking at the size of the character pool (lowercase, uppercase, digits, symbols) and the password's length. More bits means an attacker must try exponentially more combinations.
Beyond raw entropy, a good checker detects structural weaknesses: keyboard walks like qwerty or 12345, leet speak substitutions like p@ssw0rd, and year patterns like 2024 — all of which dramatically reduce effective entropy even when character diversity looks adequate. The tool also estimates crack time at 1 billion guesses per second (a realistic offline attack rate) so you can see exactly how much time your password buys.
Audit Your Password in Seconds
Type your password
Paste or type a password into the checker. All processing is local — nothing leaves your device.
See entropy & score
Instantly view entropy in bits, strength label (Very Weak to Extreme), and crack time at 1B guesses/second.
Review pattern warnings
The tool flags keyboard walks, leet speak, and year patterns that reduce real-world security.
Follow improvement suggestions
Get specific, actionable tips to increase entropy and remove detectable patterns.
Password Entropy & Crack Time Reference
The table below shows how entropy bits translate to real-world crack times at 1 billion guesses per second — a conservative estimate for a modern GPU-based offline attack. Character set size has a major impact: adding symbols or uppercase letters increases the pool and therefore the entropy per character.
| Entropy | Rating | Crack time (1B/s) | Example |
|---|---|---|---|
| ~40 bits | Weak | Seconds to minutes | 6-char lowercase + digits |
| ~56 bits | Fair | Hours to days | 8-char mixed case + digits |
| ~72 bits | Good | Centuries | 12-char full set (upper+lower+digit+symbol) |
| ~128 bits | Excellent | Heat death of the universe | 20-char full set or 6-word passphrase |
Character set impacts: digits only (10 chars) gives 3.32 bits per character; lowercase only (26) gives 4.7 bits; full printable ASCII (~95) gives 6.57 bits. Adding just one character type can add 1–2 bits per character — significant at scale.
When Developers Audit Passwords
Validate Password Policy
Check whether a proposed password policy actually produces strong passwords by testing representative examples.
Audit Existing Passwords
Review legacy passwords in migration projects to identify weak ones that should be reset before go-live.
User Onboarding Flows
Validate minimum entropy requirements during account creation to enforce better hygiene from the start.
Compliance Checks
Verify password policy meets NIST SP 800-63B requirements for length, complexity, and banned patterns.
API Key Strength
Check that generated API keys or secrets have sufficient entropy before deploying to production.
Passphrase Evaluation
Compare entropy of passphrases vs. random passwords to choose the right strategy for different use cases.
Frequently Asked Questions
1Is it safe to type my real password here?
2How is entropy calculated?
entropy = length × log₂(character set size). The character set size depends on which categories are present — lowercase (26), uppercase (26), digits (10), and symbols (~33). It also applies a penalty for detected patterns like keyboard walks and leet substitutions.3What is the difference between zxcvbn and raw entropy?
4What qualifies as a strong password?
5Is it safe to type a password into a website to check it?
6What is a password security audit?
7How do I check if my password has been leaked?
8What is Have I Been Pwned?
9How is password crack time calculated?
10What is a dictionary attack?
11What is credential stuffing?
12What makes a password weak?
13Is it safe to type my real password here?
Developer Guides
Feedback for password_audit
Tell us what's working, what's broken, or what you wish we built next — it directly shapes our roadmap.
Good feedback is gold — a rough edge you hit today could be smoother for everyone tomorrow.
- Feature ideas often jump the queue when lots of you ask.
- Bug reports with steps get fixed faster — paste URLs or examples if you can.
- Name and email are optional; we won't use them for anything except replying if needed.
Stay Updated
Get the latest tool updates, new features, and developer tips delivered to your inbox.
- Product updates & new tools
- JSON, API & developer tips
- Unsubscribe anytime — no hassle