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.
- Use any tool: generate a password, or type one into the strength checker.
- 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 Is NIST SP 800-63B?
NIST SP 800-63B is the part of the US National Institute of Standards and Technology Digital Identity Guidelines that covers authentication: passwords, one-time codes, security keys, and how services must handle them. It is written for federal systems, but its password section has become the reference most security policies, auditors, and frameworks point to.
Revision 4 supersedes Revision 3, published in 2017. This page summarizes the password rules from Section 3.1.1 and the rate-limiting rule from Section 3.2.2. It is a plain-language summary, not legal or compliance advice; for an audit or a contract, read the official text on the NIST website.
How Long Must a Password Be Under NIST Rules?
Revision 4 sets two minimums. A password used as the only authentication factor SHALL be at least 15 characters long. A password used only as part of multi-factor authentication may be shorter, but SHALL still be at least 8 characters. Services SHOULD allow passwords of at least 64 characters so people can use long passphrases.
Services SHOULD accept all printing ASCII characters and the space, and SHOULD accept Unicode characters, counting each Unicode code point as one character. In plain terms: let people type long passwords made of whatever characters they like, including spaces and accented letters.
Are Complexity Rules and Password Expiry Still Required?
No. Services SHALL NOT impose composition rules such as requiring a mix of uppercase, lowercase, digits, and symbols. The rationale in Appendix A is that people respond predictably: someone who wanted password picks Password1 when told to add a capital and a digit, and Password1! when a symbol is also required. The rule adds frustration, not strength.
Services also SHALL NOT require people to change passwords periodically. Forced rotation produces the same predictable patterns, such as Spring2025! becoming Summer2025!. A change SHALL be forced, however, when there is evidence that the password has been compromised, for example when it turns up in a breach.
What Does NIST Say About Blocklists?
When someone sets or changes a password, the service SHALL compare it against a blocklist of commonly used, expected, or compromised passwords. NIST's examples are passwords from previous breach corpuses, dictionary words, and context-specific words such as the name of the service and the username. The entire password is compared, not substrings or words inside it.
If the password is on the list, the service SHALL require a different one and SHALL give the reason. NIST notes that excessively large blocklists add little, because online guessing is already limited by rate limiting. The 2pass strength checker and breach check let you apply the same tests to your own passwords.
What Should People Choosing a Password Take From NIST?
- Length beats complexity: aim for 15 characters or more, or a passphrase of several random words.
- Do not bother with predictable decorations such as a capital first letter and a trailing 1!.
- Avoid anything on a common-password list, any dictionary word on its own, and anything about you or the service.
- Use a password manager: NIST requires services to allow password managers and autofill.
- Change a password when it may have leaked, not on a calendar.
The password generator and passphrase generator produce passwords that satisfy every one of these points without any thought on your part.
What Must Teams Building Login Systems Do?
- Allow password managers and autofill (SHALL), and permit paste (SHOULD).
- Offer an option to show the password while typing (SHOULD).
- Verify the entire password: never truncate it or ask for a subset of characters (SHALL).
- Never store password hints readable without logging in, and never prompt for security questions when a password is chosen (SHALL NOT).
- Give guidance to help people choose a strong password, especially after a blocklist rejection (SHALL).
- Rate-limit failed attempts: Section 3.2.2 limits consecutive failed attempts on one account to no more than 100 (SHALL).
- Normalize Unicode passwords with NFC before hashing (SHOULD).
Limited allowances for typing mistakes, such as trimming leading and trailing spaces, MAY be made if the password stays at the minimum length and is not significantly weakened.
How Should Passwords Be Stored?
Verifiers SHALL store passwords in a form that resists offline attack: salted and hashed with a suitable password hashing scheme that takes the password, a salt, and a cost factor. The salt SHALL be at least 32 bits and chosen to avoid collisions between accounts. The cost factor SHOULD be as high as practical and raised over time as computers get faster.
Verifiers SHOULD also apply an additional keyed hash or encryption step with a secret key stored separately from the password hashes, ideally inside a hardware security module or similar protected hardware. If the database is stolen without the key, guessing becomes impractical.
What Changed From Revision 3 to Revision 4?
Revision 3 (2017) already moved away from composition rules and periodic expiry, but phrased those as SHOULD NOT, and set 8 characters as the minimum for passwords people chose themselves. Revision 4 turns several of those recommendations into SHALL NOT requirements, raises the minimum to 15 characters for passwords used on their own, and makes allowing password managers a requirement.
For organizations still enforcing 90-day rotation and mandatory symbols, Revision 4 is the clearest signal yet that those rules should go, replaced by length, blocklists, breach monitoring, multi-factor authentication, and proper storage.
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.
- Password strength checker: See how fast a password could be guessed, which patterns weaken it, and whether it contains personal information.
- Breached password check: Check a password against Have I Been Pwned with k-anonymity: only a 5-character hash prefix leaves the browser.
- 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
What is the minimum password length in NIST SP 800-63B Revision 4?
At least 15 characters when the password is the only authentication factor, and at least 8 when it is used only as part of multi-factor authentication. Services should allow at least 64 characters.
Does NIST still require uppercase, numbers, and symbols?
No. Revision 4 says services shall not impose composition rules such as requiring mixtures of character types, because people satisfy them in predictable ways.
Does NIST require changing passwords every 90 days?
No. Services shall not require periodic password changes, but shall force a change when there is evidence the password has been compromised.
What is a password blocklist?
A list of commonly used, expected, or compromised passwords, such as breached passwords, dictionary words, and words tied to the service or username. New passwords on the list must be rejected with a reason.
Does NIST allow password managers and pasting passwords?
Yes. Services shall allow password managers and autofill, and should permit pasting passwords.
How many failed login attempts does NIST allow?
Section 3.2.2 requires services to limit consecutive failed attempts on a single account to no more than 100.
Is this page an official NIST document?
No. It is a plain-language summary of SP 800-63B Revision 4. For compliance or legal purposes, read the official publication on the NIST website.