Pikkola Password Studio, tool No. 28

A password nothing else in the world is using.

Passwords with the character sets you pick, passphrases built from 7,776 words, and batches of API keys, UUIDs and hex secrets. Every string comes from your browser's own cryptographic random source, and the entropy count tells you what it is actually worth. The page has no network to send anything through, which is the part worth checking.

Make one now local only, no account, nothing stored
128
characters at most
7,776
passphrase words
0
requests made
01Generate

Three things, one random source.

Bytes come from the operating system through crypto.getRandomValues, and each draw is rejected if it would land outside a clean multiple of the pool size, so no character is more likely than another. Nothing is written to storage between visits, so a string you liked is gone once the tab closes.

Look-alikes are 0 O o 1 l I and the pipe, the seven that turn a copied password into a support ticket. Leaving them out costs under 2 bits at twenty characters.

02Check

Paste one, and see how long it would hold.

The box is a plain input in this tab. The check counts characters, works out the size of the pool they came from, and reads the string for the patterns every cracking rule tries first. No request is made, and the page could not make one if it tried.

Type or paste a password above. Nothing is sent, and nothing is kept after you close the tab.

03Method

How the strings are made, and what they cannot do.

01

Bytes from the operating system

crypto.getRandomValues fills a typed array from the same kernel source a password store uses. Each character comes from one 32 bit draw, and a draw that falls outside the largest multiple of the pool is thrown away and tried again. Without that step the first characters of the pool come up a hair more often, which is the flaw most generators ship.

02

No wire to send it on

The Content-Security-Policy on this page says connect-src 'none'. fetch, XMLHttpRequest, sendBeacon, EventSource and WebSocket are refused by the browser before a packet exists, including from a script that a future edit might add. There is no analytics tag and no font from a third party. Press view source to read the policy yourself.

03

Bits, not vibes

Entropy is length times the base two logarithm of the pool. A 94 character pool buys 6.55 bits per character, a lowercase pool 4.7, and a word from the 7,776 word list 12.9. Two characters of a lowercase pool are worth less than one character of the full set, which is why length with a wide pool beats a short string with a symbol in it.

04

What it will not do

It is not a password manager, so it cannot remember what it made. It cannot make a reused password new again: the second site has the same string as the first. It cannot tell you whether a password already sits in a breach dump, because that would need a query, and this page does not make queries. And a checked password is only as private as the device you typed it on.

04Privacy

The password never leaves the tab.

It is made in memory, shown on the page, and gone when the tab closes. There is no account, no cookie, no analytics and no database behind this site, and the policy in the page header forbids every kind of network request. What does leave is nothing: the only request this page makes is the one that loads it.

Read the privacy note
05Questions

The questions this tool gets

Is it safe to make a password in a web page?

Only if two things hold: the randomness comes from the browser's own cryptographic source rather than Math.random, and the string is never sent anywhere. Both are true here. This page asks crypto.getRandomValues for its bytes and declares connect-src 'none', which blocks every way a page can reach the network.

Why not Math.random()?

Math.random is fast, not unpredictable. Engines implement it with a short internal state, and after a few hundred outputs the next ones can be reconstructed. It is fine for animation timing and useless for a secret. crypto.getRandomValues draws from the operating system's CSPRNG, the same source a password manager uses.

How many bits do I need?

Sixty bits survives an online attack against a rate limited login form for longer than the account will exist. Eighty bits is the floor for something that might be attacked offline at speed, such as a stolen hash or an encrypted backup. Above 100 bits the number stops mattering, because the attack moves somewhere else on the system. A twenty character password from a 94 symbol pool carries about 130 bits.

Password or passphrase?

A passphrase wins when you have to type it and remember it: five words from a 7,776 word list is about 64 bits, seven words about 90, and the string survives a phone keyboard. A random password wins when a password manager holds it, because it can be longer per character typed and fits the length limits sites impose. Passphrase for the master password, passwords everywhere else.

Do look-alike characters really cost anything?

Removing 0, O, o, 1, l, I and the pipe from a 94 symbol pool leaves 87, which costs about 0.1 bits per character, around 2 bits over twenty. That is nothing next to the bits you keep by not mistyping a password into a login form at midnight. Character sets are the real lever: lowercase only is 4.7 bits per character, the full printable set is 6.55.

The keys are random strings, not registered keys, right?

Right. An API key here is a string with the entropy of a real one, for tests, fixtures, documentation and local use. Nothing is created on any provider. A prefixed key like sk_live_ in a screenshot will still be revoked by whoever scans GitHub, so label the test ones as test keys.

Where do the passphrase words come from?

The EFF large wordlist: 7,776 English words chosen to be short, spelled without ambiguity and safe to say out loud. It is published under CC BY 3.0 and included in this page, which is why the phrase works offline. Each word is worth about 12.9 bits, and the separator and capitalisation are not counted.

Does the check send my password anywhere?

No. The check is string arithmetic in the same script that draws the random bytes. There is no request, no cache entry and no history entry, and the browser's own form history is disabled on the field.