gizmobench

Random Email Generator

This makes a batch of test email addresses, up to 1,000 at a time, every one of them different and every one on example.com, example.net or example.org: the three domains RFC 2606 reserves so that documentation and testing have addresses which can never reach anybody's real mail server. That is the difference from most random email generators, which hand back plausible addresses at gmail.com or yahoo.com and leave a seeded test database quietly mailing a stranger. The part before the @ comes from lists written for this tool, 194 adjectives and 214 nouns in the words style, 113 given names and 99 family names in the name style, or from random characters. Type a domain you own into the field and the tool will use it, alongside a visible warning that mail to that domain may really be delivered. Nothing is uploaded and nothing is fetched: click an address to copy it, copy the batch, or download it as CSV or JSON.

Addresseswords local parts · example.com

Building addresses

Local part

Press More for another batch. Every address in a batch is different, and the count can go up to 1,000 at a time. Click any address to copy it on its own.

  • This batchno two addresses the same
    nothing generated yet
  • Possible local partsquiet.harbor, copper.lantern7
    4,151,600 in the words style
  • Domainreserved for testing
    example.com is reserved by RFC 2606, so mail to it goes nowhere.
Reserved domains, and that is the point. example.com, example.net and example.org are set aside by RFC 2606 for documentation and testing, so mail to them goes nowhere and a test run cannot reach a stranger’s inbox. That is why they are the default here and why no real provider is offered. These are not mailboxes and cannot receive anything: if you need to receive mail, you need a mail service, not a generator.

Common questions

Can these addresses receive mail?
No. They are generated strings, not mailboxes: nothing is registered anywhere, no server is holding mail for them, and the reserved domains publish no mail service at all, so a message addressed to one of them is never delivered to anybody. That is exactly the property that makes them safe to paste into a form, a fixture file or a seed script. If what you actually need is to receive a message, a confirmation link or a one-time code, you need a mail service rather than a generator: a disposable inbox provider, a catch-all address on a domain you own, or a local capture tool such as a development SMTP server that shows you the message your own application sent.
Why example.com instead of a normal looking domain?
Because RFC 2606 set example.com, example.net and example.org aside for documentation and testing. They are held for that purpose rather than sold to anybody, nobody has a mailbox there, and no message sent to them arrives. A domain that merely looks made up is a different thing: plenty of invented domains turn out to be registered, and a few of them run a catch-all mail server, so an address you thought was imaginary quietly lands in somebody's inbox. This tool offers the reserved three and nothing else by default, which is why it never asks you to trust a guess.
Is it safe to use a random gmail.com address for testing?
No. Any address you invent at a live provider may already belong to somebody, and a test run that mails it reaches a real person who never asked to be in your test data. It also skews the provider's spam signals against your sending domain. If you need mail you can actually read, use a plus tag on your own address, which most providers accept and route straight back to you, or a local SMTP capture tool. You can still type gmail.com into the domain field here and the tool will use it, because it is your call, but it shows a plain warning on the page saying that an address on a live provider can really be delivered.
How many addresses can I generate at once?
Up to 1,000 in one batch, and every address in a batch is different: a local part that has already been used is drawn again, and if a style ever runs out of room a number is appended rather than the batch coming back short or repeating itself. There is room to spare. The words style alone can build over four million different local parts, the name style around a million, and the random style more than a thousand million million. Press More for a fresh batch at any time; the count, the style and the domain are remembered in this browser, and the addresses themselves are not stored anywhere.
Do these addresses belong to anyone?
No. They are assembled from word lists written for this tool, 194 adjectives and 214 nouns and, in the name style, 113 given names and 99 family names, joined on a domain where no mailbox can exist. Nothing is looked up, nothing is fetched and no list of real people or real addresses is involved. If a name-style address such as elena.torres@example.com happens to match somebody's real name, that is coincidence, and since the domain accepts no mail it still identifies nobody and reaches nobody.
What are the three local part styles?
Words joins an adjective and a noun with a dot, about a third of them ending in one or two digits: quiet.harbor, copper.lantern7. Name uses the given and family name lists in three shapes: elena.torres, elena.torres72 and j.okafor. Random is ten characters, a letter followed by nine letters or digits, such as k7f2m9qx3b. Every style keeps the part before the @ to plain lowercase letters, digits and dots, never starting or ending with a dot, never two dots in a row, and always inside the 64-character limit RFC 5321 sets, so an ordinary form validator accepts them. A validator that goes further and checks whether the domain accepts mail will refuse them, which is the point: they accept no mail.

Addresses are assembled from word and name lists written for this tool, or from random characters, on the domains RFC 2606 reserves for testing, so mail sent to them goes nowhere. They are not mailboxes and cannot receive anything, and they do not belong to anyone. Enter a domain you own and this will use it, in which case delivery is your own arrangement.