Fake Email Generator

Runs in browser Test Data

Emails derived from names or random tokens, using RFC 2606 reserved domains so no real inbox is affected, including edge-case forms (plus tags, dots, long local parts, IDN). All generated values are synthetic TEST DATA ONLY and do not belong to real people.

TEST DATA ONLY — all generated names, contacts, identifiers and numbers are synthetic and do not belong to real people or accounts.
Privacy: This tool runs entirely in your browser. Your input never leaves your device.

How to use Fake Email Generator

  1. Choose a style (or Mixed for a spread of edge cases) and a domain.
  2. Set the count, locale and format.
  3. Press Generate and use the valid column to separate positive and negative cases.

Fake Email Generator features

  • Reserved domains only (example.com/net/org, .test, .example, .invalid) — no real inbox can receive test mail
  • Styles: simple, dotted, plus-addressing, numeric, 64-character local part, quoted local part, IDN, IP-literal, mixed case, sub-domain
  • Deliberately invalid addresses for negative tests, each flagged and explained
  • Names in English, Arabic or Hindi drive the local part
  • Count of invalid rows in the summary
  • Seedable; JSON, CSV, SQL, XML, JSON Lines or table output

Fake Email Generator example

Edge-case emails

Input:

Style: Mixed · Emails: 4

Output:

nicholas.edwards+tag1@example.org      valid  Plus tag should route to the same mailbox
"Skylar Turner"@example.com           valid  Quoted local part with a space
مستخدم@مثال.إختبار                      valid  Internationalised address (EAI)
user@-example.com                       invalid Invalid address — expect rejection

Frequently asked questions about Fake Email Generator

Why example.com and .test domains?

RFC 2606 and RFC 6761 reserve example.com/net/org, .test, .example and .invalid so they can never be registered — test mail cannot reach a real person.

What edge cases can I generate?

Plus-addressing, multiple dots, a 64-character local part, quoted local parts with spaces, internationalised (IDN/EAI) addresses, IP-literal domains, mixed case and sub-domains, plus deliberately invalid addresses for negative tests.

Are the invalid addresses clearly marked?

Yes. Each row has a valid flag and a note explaining the case (missing @, double dots, spaces, trailing dot…).

Can I use my own domain instead of example.com?

No. The Domain menu is limited to nine reserved names — example.com, example.net, example.org, mail.example.com, qa.example.org, demo.example.net, test.example, app.test and staging.invalid — and “Random” picks one of the first three per address. The IDN, IP-literal and sub-domain styles set their own domain regardless. Keeping every address unregistrable guarantees test mail can never reach a real mailbox.