GenerateRandomSearch

Test Account Generator

Generates a fake username, an email address on the reserved example.com domain (RFC 2606 — never a real, deliverable address), and a random password — for developers and testers exercising a signup or login form. No real person's data is used or implied.

What this generator does

Produces a complete fake identity for testing a signup form — a username, an address at example.com and a password. The domain matters: example.com is reserved by the IETF specifically so that it can never belong to anybody, so a test that accidentally sends mail cannot reach a real person.

How to use this tool

  1. Press generate for a new fake test identity.
  2. Use it to test signup forms, demos or QA scripts.
  3. Generate again any time for a fresh set.

Worked examples

A generated identity
Nova42 · Nova42@example.com · a 14-character random password (letters and digits) — three independently generated fields, one output.

Common use cases

  • QA-testing a signup or login flow
  • Populating a demo environment with placeholder accounts
  • Automated test fixtures

How this generator works

The username is one word drawn uniformly from a fixed list of 26 short words, with a two-digit number (00-99) appended using your browser's Web Crypto random generator — giving 2,600 possible usernames. The email is that exact username at the reserved example.com domain, which is never resolvable and cannot receive mail under RFC 2606. The password is a 14-character random string drawn from lowercase, uppercase and digits with the same generator that powers the main password generator. All three are generated independently in a single action.

Randomness and fairness

The username word, its suffix number and every character of the password are drawn independently using your browser's Web Crypto random generator. There is no seeded mode.

For how randomness is produced across the whole site, see how Generate Random works.

Limitations and good to know

  • These credentials are for testing your own forms and nothing else. Never use a generated password for a real account — it is displayed on screen and offers none of the protections of a password manager.
  • Addresses at example.com cannot receive mail, so any flow requiring email confirmation will not complete with one.
  • The username draws from a small fixed list of 26 words, so a test suite generating many accounts in a row will see repeats — this is not designed for bulk unique-identity generation at scale.

Uses the example.com domain, reserved by RFC 2606 for documentation and testing — these addresses are not real inboxes. Generated entirely in your browser and never sent anywhere.

Frequently asked questions

Will the example.com email actually receive anything?
No, and that's deliberate. example.com is reserved by RFC 2606 specifically for documentation and testing, so it can never be registered or receive real mail. A signup flow that requires email confirmation cannot be completed end-to-end with one of these addresses.
Can I use the generated password for a real account?
No. It's shown in plain text on this page for testing convenience, which is the opposite of how a real credential should be handled. Use the main password generator and a password manager for anything real.