Test your application's email flows
Use a separate inbox for each test identity to inspect the email your application sends without filling your personal mailbox.
Check the complete sign-up flow
Create an inbox, copy its address into your application's sign-up form, and trigger the verification email. Check the sender, subject, plain text, HTML layout, and verification link. Use a fresh inbox when you need an independent test identity.
Repeat with password resets and one-time codes. Confirm that expired or already-used links fail correctly in your own application. Delivery delays can come from the sender or recipient provider; a missing message alone does not identify the cause.
Inspect attachments and message source
Open a message to preview supported attachments or download them. Use View Source to inspect the original email and export .eml files when you need a reproducible example for a bug report.
Remote images remain blocked until you choose to load them. Enable them only when needed to inspect your own template.
Choose the right mailbox for ongoing tests
Public disposable domains can be rejected by sign-up services and their availability can change. For repeatable automated tests or long-lived accounts, use an email testing provider with an explicit retention policy or a domain and mailbox you control.