Online Tool Store
Random Email Generator
Generate believable test email addresses at reserved domains that can never receive mail, with matching names and a CSV export. Runs in your browser.
🔒 This tool runs entirely in your browser. Your files are never uploaded to a server.
These are for seeding test data and filling forms in your own development environment. The default domains are reserved by internet standards for exactly this purpose, so mail to them cannot be delivered to anyone. This is not a disposable inbox — nothing here receives mail.
Click any address to copy it on its own.
How it works
- Choose how many addresses you need and which shape they should take.
- Pick a reserved domain, or enter one you control for a staging environment.
- Optionally add a plus tag to record which flow the record came from.
- Copy them, or download a CSV with matching first and last names for seeding a database.
Why the domain matters more than the name
An invented local part is harmless. An invented domain is not — and this is the part most fake-email generators get wrong:
asha.silva@gmail.com → probably a real person's mailbox
asha.silva@example.com → cannot exist, by standard
Seed a database with addresses at a real provider and the first time something sends a batch of notifications, real
strangers receive them. RFC 2606 exists to prevent that: it permanently reserves example.com,
example.org, and example.net, along with the .test,
.invalid, .example, and .localhost top-level domains. Nothing can be
registered there, so nothing can be delivered.
How many distinct addresses you can get
The name pools hold 25 first names and 25 last names, so the plain styles are bounded:
first.last → 25 × 25 = 625 combinations
firstlast + 2 digits → 625 × 90 = 56,250
random 10 characters → 36¹⁰ ≈ 3.7 × 10¹⁵
That is why asking for more addresses than a style can produce shows a note rather than quietly repeating itself: duplicate addresses in a seed file usually trip a unique constraint, which is a confusing failure to debug. Names are picked with your browser's cryptographic random generator using rejection sampling, so no name is quietly favoured.
The CSV export includes the first and last name behind each address, so the seeded user records are internally consistent — the person called Asha Silva has the matching address rather than an unrelated one.
FAQ
Can these addresses receive email?
No, and that is the point. The default domains are reserved by internet standards so that nothing can ever be delivered to them. This is a generator for test data, not a temporary inbox — if you need to receive a real confirmation message, you need a genuine mail service.
Why not generate gmail.com addresses?
Because a made-up address at a real provider is very likely to belong to somebody. Seeding a database with those means your test emails eventually reach strangers, and signing up somewhere with one is impersonation. Reserved domains remove that risk completely.
Which domains are safe, and who says so?
RFC 2606 reserves example.com, example.org, and example.net for documentation, and reserves the .test, .invalid, .example, and .localhost top-level domains. .test is intended for local testing and .invalid is guaranteed never to resolve. They exist precisely so examples and test fixtures cannot collide with real addresses.
What is the plus tag for?
On mail systems that support it, anything after a + is ignored for delivery, so user+signup@domain and user+checkout@domain both land in user@domain. In test data it is a convenient way to record which form or flow created a record, and it also exercises the trickier end of address validation.
Will these pass my form validation?
They should — the shapes generated are all valid addresses. That includes the plus-tag variants, which is worth testing deliberately: rejecting a + in an address is a very common validation bug, and real users with plus-addressed mailboxes hit it.
Can I use my own domain?
Yes, and it is often the better choice for a staging environment you control, since mail can be caught by a local trap instead of vanishing. Only use a domain you actually own — at a domain you do not, the addresses may reach real people.
How we compare
| Feature | Online Tool Store | Fake email generator sites | Temporary inbox services |
|---|---|---|---|
| Cannot reach a real person's mailbox | ✓ | Many use real provider domains | Real, but shared and public |
| CSV with matching names for seeding | ✓ | Rarely | ✗ |
| Warns when a style runs out of unique values | ✓ | ✗ | Not applicable |
| Nothing generated leaves your device | ✓ | ✗ | ✗ |
| Actually receives a confirmation email | ✗ | ✗ | ✓ |
Made for filling a staging database, testing a signup form, or checking that your validation accepts a plus-addressed mailbox — with addresses that provably cannot land in a stranger's inbox. It deliberately cannot receive mail; if you need to click a confirmation link, use a real inbox you control.