Random Email Generator

Generate fake email addresses on reserved domains such as example.com and .test, so test sign-ups and seed data can never email a real person.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Random Email Generator?

Click Generate Email to get a random address made of an adjective, a noun and a number from 1 to 999, for example swiftmoon42@example.com. Click the copy icon to copy it and Generate Email again for another.

Every address uses a domain reserved for testing: example.com, example.org, example.net, mail.example.com, users.example.org, inbox.test, qa.test or staging.test. These domains are set aside by RFC 2606 and RFC 6761, so mail sent to them cannot reach a real mailbox.

This is a fake address generator, not a disposable inbox. You cannot receive mail at these addresses. For sign-up flows that send a confirmation link, use a mail-catching tool such as Mailpit or your provider's sandbox.

  • Addresses on RFC 2606 / RFC 6761 reserved domains only
  • Readable adjective-noun-number local parts
  • One-click copy
  • Generated in your browser with nothing stored
Read the guide: Random Numbers, Names and Emails for Test Data, Done Properly

Updated

How to use the Random Email Generator

  1. Click Generate Email.
  2. Click the copy icon next to the address to copy it.
  3. Paste it into the form, fixture or seed file you are working on.
  4. Click Generate Email again for a new address.

Worked example

Typical output

Input

Generate Email

Output

brightstar317@qa.test

Adjective, noun, a number from 1 to 999 and one of eight reserved domains. With 12 adjectives, 12 nouns, 999 numbers and 8 domains there are about 1.15 million combinations.

Background and insight

Test data that uses real-looking domains causes real problems. Addresses like happycat12@gmail.com or demo@test.com can belong to someone, and a staging environment that sends a password reset or newsletter to them leaks data and annoys strangers. Earlier versions of this tool used popular webmail domains; it now uses reserved names only.

RFC 2606 (1999) reserved example.com, example.net and example.org for documentation, along with the .test, .example, .invalid and .localhost top-level domains. RFC 6761 (2013) formalised how software should treat those names. IANA operates the example domains with a placeholder web page and no mail server, so messages to them bounce or are dropped.

Syntax is the other half of email testing. The generated addresses are deliberately plain: lowercase letters and digits. Real addresses can include plus tags (name+tag@domain), dots, hyphens and, under RFC 6531, non-ASCII characters, so add a few hand-written edge cases when you test validation.

Common use cases

  • Sign-up form testing

    Fill registration forms in staging without creating accounts tied to a real person's address.

  • Seed and fixture data

    Give test users contact emails that can never receive a stray notification.

  • Documentation and screenshots

    Use addresses in API examples and demos that point nowhere, as RFC 2606 intends.

  • Load and QA scripts

    Grab a batch of plausible addresses for manual QA passes.

Tips and limitations

  • Some validators reject the .test top-level domain because it is not in their TLD list. If that happens, generate again until you get an example.com, example.org or example.net address.
  • With about a million combinations, repeats are rare for a handful of addresses but likely in large batches. Add a sequence number if uniqueness matters.
  • Need to read the confirmation email? Point your app's SMTP at a local catcher like Mailpit or MailHog instead.
  • Avoid made-up domains such as test.com or demo.com in test data. Many are registered and some accept mail.

Sources and further reading

  1. RFC 2606: Reserved Top Level DNS Names, IETF. example.com and the .test, .example, .invalid and .localhost names
  2. RFC 6761: Special-Use Domain Names, IETF
  3. Example Domains, Internet Assigned Numbers Authority
  4. RFC 6531: SMTP Extension for Internationalized Email, IETF. Non-ASCII email addresses

Frequently asked questions

Are these random email addresses real?

No. They are fake addresses on domains reserved for testing, such as example.com and qa.test. No mailbox exists behind them, and the domains are set aside so that no one can register them and start receiving mail.

Can I receive email at a generated address?

No. This is not a temporary inbox service. Mail to example.com, example.org, example.net or a .test domain is never delivered. For flows that need you to click a link in an email, run a local mail catcher such as Mailpit or use a disposable inbox service.

Why use example.com for test email addresses?

Because RFC 2606 reserves example.com, example.org and example.net for documentation and testing, so they can never belong to a real person. Using real-looking domains like gmail.com or test.com risks sending staging mail to someone's actual inbox.

What is the .test domain used for?

.test is a top-level domain reserved by RFC 2606 and RFC 6761 for testing. It will never be delegated in the public DNS, so names under it, such as qa.test, are safe to use in fixtures and local environments.

Will a fake email pass form validation?

Usually. The addresses are syntactically valid, with simple lowercase local parts. Validators that check a list of known TLDs may reject .test, and validators that check MX records will reject all of them, because the reserved domains do not accept mail.

Is there an in-depth guide to the Random Email Generator?

Yes. “Random Numbers, Names and Emails for Test Data, Done Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.