Check how hard a password would be to guess. Type it in and see a strength score, how long an attacker would need in four common situations, and specific tips to make it stronger. The check runs entirely in your browser: the password is never sent anywhere or saved.
| If an attacker tries | Estimated time to guess |
|---|
Checks
How to improve it
This is one of our free generators and security tools. Need a new password instead? Use the Strong Password Generator or the Passphrase Generator.
How to check a password
- Type or paste the password into the box. Use Show to see what you typed.
- Read the strength score and the estimated time to guess it.
- Follow the tips under the result, or generate a new password with one of our generators.
How the checker works
The score comes from zxcvbn, the open-source password strength estimator published by Dropbox under the MIT licence. Instead of counting character types, it looks for the patterns attackers try first: about 30,000 common passwords, names and surnames, English words, dates, repeated characters, sequences, keyboard walks and l33t substitutions. It then estimates how many guesses a smart attacker would need. The method is described in a USENIX Security 2016 paper by Daniel Lowe Wheeler.
| Score | What zxcvbn says it means | Guesses needed |
|---|---|---|
| Very weak (0) | Too guessable: risky password | fewer than 103 |
| Weak (1) | Protection only from throttled online attacks | fewer than 106 |
| Fair (2) | Protection from unthrottled online attacks | fewer than 108 |
| Strong (3) | Moderate protection if a site’s password database is stolen and slowly hashed | fewer than 1010 |
| Very strong (4) | Strong protection in that offline case | 1010 or more |
Score definitions from the zxcvbn documentation.
What the four times mean
- Online with rate limiting (100 guesses an hour): an attacker trying passwords on a login page that slows down repeated attempts.
- Online without rate limiting (10 a second): a service that does not limit attempts.
- Offline, slow hashing (10,000 a second): a stolen password database protected by a slow hash function and unique salts.
- Offline, fast hashing (10 billion a second): a stolen database hashed with a fast function such as SHA-256 or MD5.
These four scenarios and their rates are the ones built into zxcvbn. Real attacks vary, so treat the times as a comparison, not a promise.
What current password guidance says
- Length matters most: at least 15 characters for a password used on its own, or 8 with two-factor sign-in (NIST SP 800-63B).
- Sites should not force a mix of character types, and should accept long passphrases (NIST).
- Sites should check new passwords against lists of common or breached passwords (NIST).
- Use a different password for every account, and a password manager to remember them.
Need to share a Wi-Fi password? Turn it into a code with the QR Code Generator so nobody has to type it.
Frequently asked questions
Is it safe to type my password here?
The check runs in your browser and nothing is sent to us or saved. Even so, the safest habit is not to type a password you actually use into any website: test one with the same pattern instead, for example the same number of words or characters.
What makes a password strong?
Length and unpredictability. NIST SP 800-63B asks for at least 15 characters when a password is the only sign-in factor, and at least 8 when it is combined with a second factor. Random words or characters from a generator beat clever substitutions such as P@ssw0rd, which checkers like zxcvbn recognise.
Why does my long password still score low?
Because the checker looks for patterns, not just length. Common words, names, dates, keyboard runs such as qwerty, and repeated characters are guessed early, so a long password built from them can still be weak (zxcvbn).
Does this check if my password was leaked in a breach?
No. It estimates how guessable the password is, without sending it anywhere. A leaked password is unsafe however strong it looks, so change any password a breach notice tells you about, and use a different one for every site.
Sources
Checked on 19 November 2026:
- NIST SP 800-63B: Digital Identity Guidelines, authentication
- Dropbox: zxcvbn password strength estimator (GitHub)
- Wheeler (2016), zxcvbn: Low-Budget Password Strength Estimation, USENIX Security
How to cite this tool
Using this tool for coursework, a report or research? You can cite it like this (APA 7th edition):
Kumar, M. (2026). Password Strength Checker [Online tool]. FreeToolsLand. https://freetoolsland.com/password-strength-checker/
Related tools
- Strong Password Generator: random passwords or one built from your own words
- Passphrase Generator: easy-to-remember passwords from random words
- Base64 Decoder and Encoder: Base64 is encoding, not encryption