Generators
Create identifiers, passwords, placeholder data and other one-off values.
Other categories
About Generators
Everything in this category invents something: a password, a code, a page of placeholder text, a table of test rows. What they share is that the quality of the output depends entirely on where the randomness came from, and that is the part you cannot see by looking at the result.
So it is worth stating. Every generator here draws from the browser’s cryptographic random source, the same one used for encryption keys. `Math.random` appears nowhere in this module, and a test reads the source on every build to keep it that way. It is seeded from a value an attacker can often recover, which makes a password built on it guessable in a way its length suggests it is not — and a weak twenty-character password looks exactly like a strong one.
The second thing these tools have in common is that their output is meant to be inert. Generated email addresses use domains reserved by RFC 2606 and can never reach a real inbox; generated phone numbers come from a range set aside for fiction. That is what separates test data from an accident you spend a year apologising for.
Nothing generated here is stored, transmitted, or included in any analytics event. A password exists in the page and in your clipboard, and nowhere else.
Questions
Where does the randomness come from?
The browser’s cryptographic random source, with rejection sampling so no value is more likely than another. Math.random is not used anywhere in these tools.
Is a generated password ever sent anywhere?
No. It is created in the page, never written to storage, and never included in an analytics event.
Can the fake data reach real people?
No. Emails use domains reserved by RFC 2606 that can never be registered, and phone numbers come from a range set aside for fiction.
Do these tools work offline?
Once a page has loaded, its tool keeps working without a connection. Reloading the page needs the network again.