Test Email: A Disposable Inbox for Dev and QA
When you build a feature that sends mail, like a sign-up confirmation, a password reset, or a receipt, you need somewhere to send it that is not your own inbox. A test email is a throwaway address you point your app at during development.
It catches the message so you can check it, then clears itself. It works like any temporary email, but here the job is quality assurance, not privacy.
Your Next Inbox Lasts 10 Minutes
Click once and use a private address that cleans up after itself - No account needed.
Your 10 Minute Mail Address:
Waiting for incoming emails...
What developers use a test email for
Transactional email flows
- Sign-up and verification: Trigger the welcome mail and confirm the activation link actually works.
- Password resets: Fire a reset and check the token, the expiry, and the URL it points to.
- Receipts and invoices: Place a test order and read the receipt exactly as a customer would.
SMTP and delivery checks
Before you ship, you want to know the mail leaves your server at all. Sending to a test inbox is a fast SMTP sanity check. If the message lands, your credentials, ports, and from-address are wired up right. If it never shows, you have caught a config bug in staging instead of production.
What to check in each test message
- Links: Click every button and link so none point at localhost or a dead route.
- Rendering: Read both the HTML and plain-text versions so the layout holds up.
- Dynamic fields: Confirm names, dates, and amounts fill in correctly and do not show as blank tags.
- Spam signals: A quick read tells you if wording or missing headers might trip a filter. Our spam protection notes cover the basics.
Fitting a test inbox into your workflow
Matching the timer to the job
For a quick one-off check, the default timer is plenty. When you run a longer QA pass, or wait on a queued job to fire, reach for a longer window like 30 minute mail so the address is still live when the mail finally lands.
Need several addresses to test different roles, such as admin and member? Spin up a new one from the email generator for each. Curious how the self-destruct works underneath? This guide to the 10 minute inbox explains it.
Test email versus a fake email you type by hand
| Test email | Fake email typed by hand |
|---|---|
| A real, working inbox | Often does not exist at all |
| Mail truly arrives, so you can inspect it | May bounce and tell you nothing |
| Built for checking the message itself | Only useful for skipping a required field |
- A test email is a live inbox you point your app at during development.
- It catches resets, confirmations, and receipts within seconds.
- Check links, rendering, and dynamic fields before you ship.
- No account, no API key, and the address clears itself afterwards.
See also: temporary email, random email and dummy email.
Frequently asked questions
Can a test email receive password reset and verification mail?
How long should a test email stay active?
Is a test email good for load or bulk testing?
Do I need an account or API key to use it?
Start testing your emails now
Point your next sign-up, reset, or receipt at a throwaway address and see exactly what your users will get. Copy the test email at the top of this page to begin, then let the address clean itself up with automatic expiration once your checks are done. Check our full FAQ for anything else.