Password check.
How a password would be guessed, how long that takes under four kinds of attack, and whether it is already in breach data. Your password never leaves the page; the optional breach check sends the first five characters of its SHA-1 hash.
Tool · runs in your browserPassword
Strength
Loading dictionaries…
Time to crack
Waiting for a password.
Breaches
Enter a password, then press Check breaches.
Passphrase
Each word is drawn uniformly from the 7,776 words of the EFF Large Wordlist using crypto.getRandomValues, with rejection sampling so no word is favoured. That is 12.92 bits per word, plus 3.32 for the optional digit. Separator and capitals add nothing: the figure assumes the attacker knows the wordlist and every setting, so it is a floor, not a guess. The passphrase exists only in this page until you copy it; anything copied stays on your clipboard until something replaces it.
Wordlist: EFF Large Wordlist by the Electronic Frontier Foundation, used under CC BY 4.0. Dice numbers removed; words and order unchanged.
What leaves this page
- The password. Never sent. It lives in this tab’s memory while the page is open. This tool does not store it, log it or write it to the console. The field sets
autocomplete="off"and the common password-manager opt-outs; most honour them, though a browser may still offer to save what you type. - Strength. Computed entirely in the page. No request is made for it.
- Breach check, when on. One lookup per press of the button: a GET to
api.pwnedpasswords.com/range/followed by 5 hex characters of the password’s SHA-1 hash. Because of the padding header, the browser may first send a CORS preflight to the same URL. There are 1,048,576 possible prefixes, and the response lists every breached hash that shares yours, padded with fake entries so its size gives nothing away. Like any request, it also carries your IP address and user agent, and its Origin header names this site. - What the prefix still reveals. Twenty bits of the hash. If the password is in the breach corpus, it is one of the entries in that response. If it is not, someone holding the prefix could discard almost every wrong guess without testing it. That is why the check runs on a button press rather than as you type: checking every keystroke would send a prefix for each short, easily guessed fragment of the password.
- No analytics, no storage. This tool sets no cookies, uses no browser storage and reports nothing anywhere.