About this generator
Pikkola, tool No. 28
Three generators and one honest calculator, all of it in a single tab and none of it on a wire.
Why the work happens in the tab
A password generator that sends the password somewhere is a password generator with a copy of your password somewhere. That copy may be logged, cached, indexed by a proxy or read by whoever runs the server next year. The only way to be sure it does not exist is for the string never to leave the machine that made it.
So this page makes everything in memory, shows it, and forgets it when the tab closes. It has no account, no database and no analytics. The Content-Security-Policy in the page header says connect-src 'none', which is the browser's own instruction to refuse every outbound request from this document. That is a stronger promise than a sentence on a page, because the browser enforces it, not us.
Where the randomness comes from
crypto.getRandomValues fills a 32 bit value from the operating system's cryptographic random source, the same one a password manager or an SSH client uses. Each character in a password is one draw. A draw that falls outside the largest multiple of the pool size is thrown away and repeated, so every character in the pool has exactly the same chance. Skipping that rejection step is the classic flaw: with a 62 character pool and a byte, the first eight characters come up about 0.5 percent more often than the rest.
Math.random is not used anywhere in this page. It is fast and it is predictable, and a password made from it is only as strong as the engine's internal state.
The passphrase list
Passphrases are built from the EFF large wordlist: 7,776 English words, chosen to be short, spelled one way and safe to say out loud. The Electronic Frontier Foundation published it under CC BY 3.0 for dice generated passphrases, and it is included in this page, so a passphrase can be made with the network switched off. Each word carries log2(7,776), about 12.9 bits. The separator, the capital letters and a trailing number are not counted, because the first ruleset any attacker runs already tries them.
What the number means
An entropy estimate is the base two logarithm of the number of strings the generator could have produced. A twenty character password from a 94 character pool sits in a space of 94^20, which is about 131 bits. A five word passphrase from the list sits in a space of 7,776^5, about 64 bits. The estimate describes the generator, not the string you happen to get: a weak string can come out of a good generator, and it is still weak.
The check in the second section measures something slightly different. It takes the string you paste, guesses the pool from the characters present, and multiplies. That overstates a phrase, a name or a keyboard walk, so the findings above the number matter at least as much as the number.
What none of this covers: reuse, a password typed into a site that logs it, a phishing page that collects it, a device with a keylogger. A 130 bit password on a compromised machine is a compromised password.
The keys are strings, not credentials
The API key, UUID and hex generators make strings with the shape and entropy of real credentials. Nothing is registered with any provider, and no format is validated against a real service. They are for tests, fixtures and documentation. A key that looks live in a screenshot will be treated as live by scanners that watch public repositories.
What it does not do
It does not store anything, so it cannot show you the password you made yesterday. It does not purge a reused password from the other sites that have it. It does not check a breach corpus, because that needs a query and this page does not make queries. It does not judge the site you are signing up to, and it cannot make a site's weak password policy into a strong one.
If something is wrong
Write to hello@pikkola.com with what you did and what happened. Never send a real password, even to us, and especially not to anyone who asks for one.