a-z Uppercase A-Z Digits 0-9 Symbols !@#$About Password Strength Analyser
Assessing how strong a password actually is beats judging that it "looks complicated". Such tools usually answer on two axes: the composition of the password itself, covering length, alphabet size. The presence of common words or keyboard sequences, and whether it appears in known breach corpora, which is often decisive, since a twelve-character password already in a leak list has effectively zero strength. The algorithm estimates how many attempts an exhaustive search would need. A common approach computes the theoretical space from alphabet size and length, corrects for recognizable patterns such as repeated fragments, ascending sequences, years, and letter-to-digit substitutions, and finally converts it into the average time an offline high-speed attack would require. That figure is an order of magnitude rather than a precise value, which is exactly what distinguishes "a few minutes" from "centuries". Practical notes: Length dominates, and never reusing a password comes second, because one breached site exposes every account sharing the value. Using a password manager to generate a long random password per site is the accepted best practice; where memorization is required, a long passphrase of several unrelated words is both long enough and easier to recall than a random string. Keep personal information such as name, birthday and phone number out of passwords entirely, since that material is the easiest to guess in a targeted attack. Limits: Strength estimation only models attacks on the password itself, never how it was obtained. A phishing page, a compromised site, a service storing passwords in plaintext, or a sticky note on a monitor all defeat strong passwords more easily, so no password strength figure replaces two-factor authentication and basic hygiene. The time shown in a browser is also an approximation of a theoretical bound, and real cracking speed depends on the attacker's hardware and algorithm, so the same password can score several times differently across tools. Do not agonize over the number, only over whether the magnitude is sufficient. Data and privacy: this is the tool in the group that most needs a warning, since pasting a real password into any online service hands it over. This tool performs all estimation in the browser and sends no request. Even so, the safer routine is to enter a lookalike example with the same structure rather than your actual password. Strength assessment makes more sense inside a broader security policy: a strong password addresses the risk of being guessed, while two-factor authentication addresses the risk of being stolen, and the two threats differ enough that neither replaces the other. In organisational settings, mandating minimum length, rejecting passwords found in breach corpora, and detecting abnormal sign-ins beats enforcing complex composition rules, which mostly push users toward one predictable pattern they then write down. For individuals the cheapest improvement is to adopt a password manager, give every site a distinct long password, and enable two-factor authentication on the mailbox and primary accounts first. Periodically checking whether your frequent accounts appear in newly disclosed breach lists reduces real risk more than a one-off strong password does.
How It Works Internally
Estimation works along two lines: the theoretical search space set by alphabet size and length, and whether the value appears in known breach corpora or follows common patterns. The second is usually decisive, because attackers do not enumerate characters; they try known passwords and substitution rules first, so a long password already in a leak list has effectively zero strength. The score is an order of magnitude, not a precise value.
P@ssw0rd2026Looks complex by charset, but matches the common word-plus-year pattern in rule-based cracking, scoring far below a random string of the same lengthMeasured on This Page
| Fixed here | 16 identical characters scored 75.2 bits Strong, 20 scored 94.0 bits Very strong and 1000 scored 4700 bits; all now report 4.7 bits, Very weak |
|---|---|
| How | Each first occurrence contributes the full charset entropy while a repeat only contributes log2(distinct chars) — not a flat zero |
| Unaffected | Abcdef1! with eight distinct characters stays at 52.4 bits Medium; a 16-character random string stays at 104.9 bits Very strong |
| Phrase side | The default correct horse battery staple drops from 164.0 to 131.7 bits, still Very strong |
| Localised units | Crack-time units were hard-coded English (sec / min / M yr) even on the Chinese page; now on i18n |
What this computes is an upper bound, not real strength: it assumes independent random characters, so password still scores 37 bits and 123456 scores 19.9. The change only adds a repeat term (aaaaaaaa falls from 75 bits to 4.7), while dictionary words, keyboard runs and p@ssw0rd style substitutions remain outside the model. Real estimation needs a pattern-aware library such as zxcvbn, so read this page as at most this strong.
How to Use
- Open the Password Strength tool
- Enter the password to test
- View real-time strength rating (Very Weak to Very Strong)
- Check entropy, character set size, and estimated crack time
- Optimize your password based on the analysis
Use Cases
- Audit your own password — Estimate how long a new password resists brute force before deciding whether to lengthen it.
- Calibrate frontend thresholds — Tune the score bands for a signup strength bar so weak/medium/strong hints feel right.
- Security training — Demonstrate the crack-time gap between weak and strong passwords to raise team awareness.
- Review default credentials — Check whether a device or system's initial password is too simple and must be rotated.
- Compare strategies — See whether a long random string or a complex short password actually has higher entropy.
- Policy compliance — Paste a candidate password to confirm it meets your organization's length and complexity policy before setting it.
- Password manager audit — Export passwords from your manager and run them through the analyzer to identify weak entries that need rotation.
FAQ
How is the strength score computed?
Mainstream approaches estimate entropy from length, charset size, dictionary hits, and patterns like repeats or keyboard runs, then convert that to a crack time, rather than merely counting character classes.
Is the crack-time estimate reliable?
It is an order-of-magnitude reference based on an assumed guess rate. Real speed depends on attacker hardware and whether your password is stored with a salted slow hash. Treat it as relative, not a promise.
Which matters more, length or complexity?
Length usually pays off more. A 16-char random lowercase string often beats an 8-char "complex" password in entropy, so longer tends to be safer than fancier.
Why does P@ssw0rd score low?
Such symbol-for-letter substitutions are standard rules in attack dictionaries; cracking tools try them automatically, so they add little real strength.
Is the password I enter stored?
No. Analysis runs inside your browser, with no server upload and no logging. To be safe, test a structurally similar throwaway phrase rather than pasting your live primary password.
My password is complex, so why does it score as weak?
Complexity only widens the search space, while the assessment also checks breach corpora and common patterns. A twenty-character password built from a common word plus a year, or already leaked elsewhere, can be effectively worthless: attackers do not enumerate characters, they try known passwords and substitution rules first. The most effective fix is length and no reuse, not more symbols.
Can this score be used as security audit evidence?
Only as a reference. It measures the password itself and cannot tell whether it was captured by a phishing page, stored in plaintext, or reused on another site. An audit should cover password policy together with two-factor authentication, credential-leak monitoring and abnormal sign-in detection; a strength score alone overstates the overall posture.
Does a "strong" rating mean the password is actually safe?
Strength only measures resistance to brute force — it knows nothing about reuse across sites or known breaches. Even a strong password dies in credential stuffing. Real safety is a unique password per site plus a manager plus 2FA on critical accounts.