The safest test email is one that cannot reach a human. RFC 2606 reserves example.com, example.org and example.net precisely so that nothing addressed to them ever leaves your infrastructure — which is the default here.
What you can control
- Five local-part styles, from
first.lastto a random handle, so you can match whatever convention you are seeding. - Plus-addressing (
ada+billing@example.com) exercises the sub-address parsing that trips up a surprising number of signup forms. - Non-Latin names fall back to a Latin handle, so a Japanese record still produces an address a mailer can route.
- Custom domains let you point a whole batch at a catch-all you actually control.
Testing ideas
- Plus addressing. Turn on
+tagsub-addressing. Sign-up forms that reject+lose every user who filters mail that way, and deduplication that ignores it creates duplicate accounts. - Never send to a stranger. Keep the reserved domain while testing transactional mail.
example.comand.exampleare guaranteed by RFC 2606 never to deliver, so a misconfigured staging mailer cannot email a real person. - Disposable domains. The disposable option uses
.examplenames such asburner.example. Add them to your block-list in the test environment and confirm sign-up is refused, without putting a real provider's domain in your fixtures. - Case and uniqueness. Uppercase a generated address and sign up twice. Email uniqueness should be case-insensitive in practice.
What this is not
Reserved domains are guaranteed never to accept mail. Disposable-inbox domains listed here use the .example suffix and are equally inert — they are shaped like the real services without being them.