If you build or test software with email flows, a disposable inbox is one of the fastest ways to run a clean manual check without any setup.
What you can verify quickly
- Welcome and onboarding emails — does the right message arrive, does the copy look right, do the links work?
- Password reset flow — does the reset link arrive, is it correctly formatted, does it work?
- Transactional confirmations — order receipts, booking confirmations, subscription renewals
- HTML rendering — how does the email look when inline images and remote assets are blocked?
- Spam/phishing indicators — the sanitiser strips scripts and event handlers, which also makes obvious when a sending service has misconfigured HTML
How to use it for QA
- Open the generator and copy the address.
- Use the address as the test user email in your signup or trigger flow.
- Watch the inbox for the expected message. Open it to check content and links.
- If you need a second test run with a fresh state, press Change Email to generate a new address instantly.
When a dedicated tool is better
For automated test pipelines, CI environments, or high-volume sending tests, a proper transactional mail testing service (Mailtrap, Mailhog running locally, or a subdomain catch-all you control) is more appropriate. Those give you API access, retention control, and no dependency on a public service.
Questions
Can I use the temporary inbox in automated tests?
Not reliably. The inbox requires a browser session and does not have a documented public API for external polling. Use a self-hosted mail catcher for automation.
Does the inbox show the raw HTML source of an email?
No. The sanitised HTML is rendered in a sandboxed frame. To inspect raw source, use a dedicated tool like Mailtrap or your own catch-all mailbox.