How Can You Verify That Your Passwords Never Leave This Browser?
You do not have to take our word for it. Browser developer tools list every request a page makes, so you can watch 2pass work and confirm that your passwords are never sent anywhere. The check takes about a minute.
- Open your browser developer tools with
F12, or Cmd+Option+I on a Mac, and select the Network tab.
- Reload the page and let it finish. You will see the page's own files, its web fonts, the word lists it uses, and one anonymous page-view request. Nothing has been typed or generated yet, so none of them can contain a password.
- Click the clear icon in the Network tab so that the log is empty.
- Type a password into the checker and watch the result change with every key.
- Look at the Network tab again. It is still empty. Generating, typing, checking, and copying happen in code that is already on the page, so there is nothing to send.
For extra proof, turn on offline mode after the page loads: the generators, the strength checker, and the calculator keep working, because they never needed the network. Only the breach check needs a connection, and only after you ask it to.
The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site, the anonymous analytics endpoint, and the Have I Been Pwned range API, so even a bug could not send a password somewhere else.
What Does the Strength Checker Look For?
The strength checker models how a real attacker guesses: the cheapest ways first. It looks for every piece of the password that matches something on an attacker's list, then finds the cheapest way to build the whole password out of those pieces. Characters that match nothing are counted as random characters from the character classes the password uses.
- The 10,001 most common passwords (the SecLists 10k list), ranked by popularity.
- The 7,776 words of the EFF wordlist, plus capitalized, reversed, and look-alike spellings such as P@ssw0rd.
- Sequences such as abc, 1234, and 9876, and repeats such as aaa or abcabc.
- Keyboard runs such as qwerty, asdf, and 1qaz2wsx.
- Dates and years, which are among the first things anyone tries.
How Should You Read the Result?
The result is an estimate in bits: the base-2 logarithm of the guesses an attacker would need with the patterns found. The verdict uses the 2pass scale: under 20 bits very weak, 20 to 39 weak, 40 to 59 fair, 60 to 79 strong, and 80 or more very strong. The pattern list shows what each piece was matched as, by type and character position, without ever repeating your password.
Password1! looks complex but rates very weak: the base word is near the top of every list, and a capital first letter plus a trailing digit and symbol is the most predictable decoration there is. Six random words rate strong, because no pattern explains them.
What Do the Crack Times Mean?
Guessing speed depends on where the attacker is. The checker shows four order-of-magnitude scenarios, the same ones used across 2pass:
- Online, rate-limited login: about 100 guesses an hour, the situation NIST requires services to enforce.
- Online, no rate limit: about 10 guesses a second against a careless service.
- Stolen database with a slow hash such as bcrypt or Argon2: about 10 thousand guesses a second.
- Stolen database with a fast hash such as MD5 or SHA-1: about 10 billion guesses a second.
The last scenario is the one that matters for a password you reuse, because you cannot know how every site stores it.
Why Does It Warn About Personal Information?
People who know you, or who have read your social media, try your name, children, pets, birthday, and phone number first. The checker flags passwords that contain an email address, a phone number, a Social Security number pattern, a payment card number that passes the Luhn checksum, a date, a year between 1940 and 2039, or an IP address.
The optional Words about you field lets you add names and words only you know are personal. They are treated as a tiny dictionary the attacker already has, exactly as NIST asks services to block context-specific words. Like the password, they are never sent and are wiped when you leave the tab. For personal information in longer text, 2count runs a similar scan.
What Are the Limits of the Strength Checker?
The checker is deliberately lean, and an estimate is not a guarantee. It only knows the words on its lists, so a password built from a place name, a foreign word, a song lyric, or an uncommon English word plus a few substitutions can score higher than it deserves. Real attackers use lists of billions of leaked passwords and rules that combine them.
Treat a strong verdict for a password you invented as an upper bound. The only passwords whose strength is known exactly are randomly generated ones, which is why the password generator and passphrase generator are the better fix than tweaking a weak password.
Why Does NIST Prefer Blocklists Over Complexity Rules?
NIST SP 800-63B Revision 4 forbids services from imposing composition rules such as requiring a digit and a symbol, because people respond predictably: password becomes Password1, then Password1!. Instead, services must reject passwords found on a blocklist of common, expected, or compromised values and explain why.
The strength checker follows the same idea. It does not reward a symbol for being a symbol; it asks whether the password is predictable. The NIST guide covers the full set of rules.
What Else Is on 2pass?
- Password generator: Random passwords from the browser's cryptographic generator, with character set toggles and exact entropy in bits.
- Passphrase generator: Passphrases of 3 to 12 words from the EFF large wordlist, with separator options and entropy shown.
- Breached password check: Check a password against Have I Been Pwned with k-anonymity: only a 5-character hash prefix leaves the browser.
- NIST password guidelines: What NIST SP 800-63B Revision 4 says about length, composition rules, expiry, blocklists, and storage.
- Password entropy explained: What password entropy is, how bits are counted, and how long a guess takes, with a calculator.
- Privacy and zero retention: Tool by tool, exactly what leaves your browser (almost nothing) and how to check it yourself.
Everything is on the 2pass home page. Part of the 2suite.io privacy-first ecosystem.
Frequently Asked Questions
Is it safe to type my real password into this checker?
The password is analyzed in this tab only. It is not sent, stored, logged, or put in the address bar, and it is wiped when you switch tabs, when the page is hidden, or after 3 minutes without activity.
Why does my complex-looking password rate weak?
Because it follows a pattern attackers try early, such as a common word with a capital first letter, look-alike symbols, a year, or a trailing digit and symbol. Predictability matters more than character variety.
How accurate is the strength estimate?
It is a lean estimate based on a 10,001-entry common-password list, the EFF wordlist, and known patterns. It can overrate passwords built from words it does not know. Randomly generated passwords are the only ones with exactly known strength.
What counts as personal information in a password?
Email addresses, phone numbers, Social Security number patterns, payment card numbers that pass the Luhn checksum, dates, years from 1940 to 2039, IP addresses, and any words you enter in the Words about you field.
Does the strength checker use zxcvbn?
No. It uses its own smaller estimator with similar ideas: matching common passwords, words, and patterns, then finding the cheapest combination. A deeper analyzer is not included yet.
Does a strong rating mean the password has not leaked?
No. Strength and exposure are different questions. Use the opt-in breach check to see whether a password appears in known breaches.