Safe Fake Email Addresses for Testing (and Why Domains Matter)
“[email protected]” might look harmless, but test.com is a real domain — and real people may receive your test emails. Realistic addresses on reserved domains are safer and make your tests and demos far more convincing.
Use reserved domains
RFC 2606 reserves example.com, example.net, example.org and the .test top-level domain for documentation and testing. Mail to them can never reach a real inbox. RandNow uses these by default, and lets you enter your own domain when your staging server catches all mail.
What to test in email flows
- Uniqueness checks and case-insensitive matching (
Sarah.Mitchell@vssarah.mitchell@). - Plus-addressing and dots in local parts.
- Greeting personalisation in templates.
- Bounce and unsubscribe handling in staging.
When you need a working inbox
Generated addresses don’t receive mail. If you need to click a verification link, use a catch-all on your own test domain or a disposable inbox service — and never use someone else’s real address.
Pro tips
- Generate 100 addresses at once to seed bulk-import tests.
- Set a custom domain such as qa.yourcompany.com for staging.
- Combine with the Random Name Generator for matching display names.