Fake Mail Generator for Test Emails and Inbox Aliases
Make fake email addresses that can never reach a real person, for testing forms and apps, or + aliases of your own inbox that show which site shared your address.
- Reserved domains never reach real people
- Up to 500 at once, CSV export
- Runs offline, no server processing
Only use a domain you control. Mail to real domains can reach real people.
More options
Your email and site names stay in this browser. They are not sent to our server.
- Enter your email and at least one site name.
How to test it
- Copy one alias and send an email to it from another account.
- It should arrive in your normal inbox, with the full alias in the To line.
- If it bounces, your provider doesn't support + aliases. Use the Disposable Email Generator for that site instead.
- Create a filter or label for the alias, so mail from that site is sorted automatically.
Need to actually receive a code? Get a temporary inbox.
How this fake mail generator works
Domains reserved for testing
example.com, example.org and example.net are reserved by RFC 2606, and .test and .invalid by RFC 6761. No one can register them, so nothing sent there reaches a real inbox.
Aliases that point home
A + alias such as you+shop@gmail.com delivers to your normal inbox. The tag tells you which site used your address, and you can filter or block it later.
Made in your browser
Addresses are generated in your browser with cryptographically secure randomness. The tool does not send the addresses or alias inputs to a server, so generation works offline.
Fake mail or disposable email? Use this page when an address only has to look valid, such as test data or a form you're building. When you need to actually receive a code or link, use the Disposable Email Generator, which gives you a real temporary inbox.
Problems this tool fixes
Find the problem you ran into. Each fix sets the tool up for you.
| Your problem | How this tool fixes it | Fix |
|---|---|---|
| Testing and development | ||
| I need hundreds of email addresses for test data | Generate up to 500 at once with realistic names and download them as a CSV with first and last name columns. | |
| Our staging server keeps emailing real people | Use mail.invalid. Mail to .invalid can never reach a person, but it bounces, so also point staging at a mail catcher such as Mailpit instead of a live sending service. | |
| I need predictable addresses for automated tests | Numbered gives user001, user002 and so on, with your own prefix, so tests can refer to them by number. | |
| Protecting your own inbox | ||
| I want to see which site an email address was given to | Give each site its own alias like you+sitename@gmail.com. When mail arrives, the To line can show which alias received it. | |
| A site rejected my temporary address | Many sites block disposable domains but accept a Gmail or Outlook alias. If a form refuses the + sign, use a temporary inbox instead. | |
| I need to receive a verification code | Fake addresses can't receive mail. Use an alias of your own inbox, or a temporary inbox from the Disposable Email Generator. | Get an inbox |
Which fake email domains are safe
A fake email address is only safe if its domain can't belong to anyone. The internet's standards set a few names aside for exactly this.
RFC 2606 and RFC 6761: example.com, example.net, example.org, and anything ending in .test or .invalid
Made-up names are risky because they are often real. test.com, for example, is a registered domain, so an email to test@test.com can land in someone's mailbox. Even if a name is free today, anyone can register it tomorrow.
Plus aliases work differently: they are real addresses that your provider delivers to your main inbox. They don't hide who you are, and a site can remove the tag, which is why aliases help with sorting more than with privacy.
Sources: RFC 2606 (reserved domain names), RFC 6761 (special-use names), RFC 5233 (subaddressing).
Fake email mistakes that cause real problems
These mistakes can email a stranger or break a test.
test.com is a real domain. Test emails can land with its owner, and bounces hurt your sender reputation.
Realistic addresses at real providers belong to someone. Keep realistic names, but on a reserved domain.
Aliases don't hide your identity. Your real address is visible inside the alias. Use them to sort mail, not to stay anonymous.
Your own live domain may have a catch-all mailbox. Test mail can pile up in a real inbox. Use a subdomain you control or .test.
Good habits with fake and alias addresses
Do
- Use reserved domains for every test, demo and screenshot.
- Give each site its own alias so leaks are easy to trace.
- Set up filters for aliases you only want to read now and then.
- Send a test email before relying on an alias.
- Keep test data out of production mailing lists.
Avoid
- Made-up domains that might exist.
- Fake addresses on accounts you need to recover.
- Aliases on sites that must match your ID, such as banks.
- Using fake addresses to break a site's rules.
- Real customers' addresses in test databases.
Frequently asked questions
Short answers about safe domains, aliases and receiving email.
Are these fake email addresses safe to use for testing?
Yes, when you use the reserved domains. example.com, example.org and example.net are set aside by RFC 2606 for documentation and testing, and the .test and .invalid endings can never be real, so no email sent to them reaches a person.
Can I receive email at a fake address?
No. Test addresses are designed never to receive mail. If you need to receive a code or link, use our Disposable Email Generator, or an alias of your own inbox from the Aliases tab.
What is a plus alias?
It's your real address with a tag after a plus sign, such as you+shop@gmail.com. Email to it arrives in your normal inbox, and the tag shows which site you gave it to, so you can filter it or spot who shared your address.
Which email providers support plus aliases?
Gmail, Outlook.com and Proton Mail commonly support plus aliases, but provider rules can change and may vary by account. Send yourself a test email before relying on an alias for an important account.
Why not just type something like test@test.com?
Because test.com is a real, registered domain, like many made-up-looking names, so mail sent there can reach real people. Reserved domains can't reach anyone, but mail sent to them still bounces. Use them for test data and forms, and send real test mail through a mail catcher instead of a live sending service.
Is anything I type sent to your server?
No. The email address and site names are processed in your browser and are not sent to our server. The alias generator works without a server request.
Is it legal to use a fake email address?
Using test addresses in your own development and QA work is normal practice. Don't use fake or alias addresses to break a site's terms, create fake reviews or get around a ban.