Fake Email Generator

How to use Fake Email Generator

1. Choose how many addresses you need.
2. Copy them into your seed data or mockup.
3. Add awkward valid formats by hand to test your validation.
4. example.com and .test are reserved by RFC 2606 and never deliver mail.
5. Plus-addressing, dots and long TLDs are all valid — test that your form accepts them.
6. Not usable for signing up to anything; nothing receives mail at these addresses.

example.com exists for this

RFC 2606 reserves example.com, example.net, example.org and the .test, .invalid, .example and .localhost top-level domains so they can be used in documentation and testing without ever reaching a real mailbox. Using a plausible-looking real domain instead means your test suite may genuinely send mail to a stranger — which happens, and is a recurring embarrassment in bug reports and screenshots.

Test addresses that break your validation

Most email validation is too strict and rejects valid addresses. Real addresses contain plus signs (user+tag@), dots in the local part, apostrophes, hyphens, and increasingly non-ASCII characters and new top-level domains longer than three letters. Addresses can legally be quite long. If your form rejects any of those, it rejects real customers — seed your test data with them deliberately.

Never use these to sign up for anything

A generated address is not a disposable inbox — nothing receives mail at it, so account verification and password reset will both fail, and providing false details typically breaches terms of service. If you want a real throwaway address, use a disposable mail service or your provider’s plus-addressing, which routes to your actual inbox while letting you filter and trace who leaked it.