One password, made here, kept here
Each character is drawn from the pool you switch on, using crypto.getRandomValues. The W3C describes that interface as “a cryptographically strong pseudo-random number generator seeded with truly random values”. Nothing is uploaded, nothing is logged, and closing the tab is the end of it — so copy the password into a password manager before you leave.
What the rules actually say, and who they are written for
NIST’s current guidance is worth reading because it is more specific than the advice that circulates. In SP 800-63B-4 the requirements are addressed to the services that check your password rather than to you, and section 3.1.1.2 says they “SHALL require passwords that are used as a single-factor authentication mechanism to be a minimum of 15 characters in length”. A password used only alongside a second factor may be shorter, but still “a minimum of eight characters”.
Two of the other requirements are the interesting ones, because plenty of sign-up forms do the opposite. Services “SHALL NOT impose other composition rules (e.g., requiring mixtures of different character types)”, and they “SHALL NOT require subscribers to change passwords periodically” — though a verifier must force a change where there is evidence the secret has been compromised. They “SHOULD permit a maximum password length of at least 64 characters” too.
NIST writes these guidelines for US federal systems, and says the publication “may be used by nongovernmental organizations on a voluntary basis”. We are not telling you what any particular service must do.
Frequently asked questions
crypto.getRandomValues, the browser's cryptographic generator, which the W3C describes as “cryptographically strong”. Not Math.random, which is not meant for this.