Using temporary email to test signup and email flows
Last updated 5 November 2026
When you're checking your own app, you often need a fresh address and a real inbox. A temporary inbox is a quick way to get both.
Mailly suits manual checks. It has no API, so it can't be part of an automated test suite. Use it only with apps you own or are allowed to test, and only with test accounts.
What it's good for
- Confirming that a signup or verification email arrives and its link works
- Walking through a password reset on a throwaway test account
- Checking the subject, sender name and body of a real delivered message
- Seeing whether your form accepts or rejects a disposable domain as you intended
- Getting a quick sign that your app can send mail to an outside domain
A quick manual test
- Open Mailly and copy the address. Click New when you want a clean inbox for another run.
- Trigger the email. Sign up or request a reset in your test environment.
- Watch the inbox. The page checks every 8 seconds, so allow for that when you judge delivery time.
- Open the message. Check the subject, sender, content and links.
- Follow the link. Then try it a second time, if the link should only work once.
- Check what happens next. Make sure the account reaches the right state in your app.
Keep real customer data out of these emails. Messages aren't encrypted on Mailly's server while they're stored.
Limits to plan around
| Limit | What it means for testing |
|---|---|
| No API, and a bot check on new addresses | You can't use it in CI or scripted tests. |
| The key stays in one browser | You can't share an inbox with a teammate or open it on your phone. |
| Messages last about an hour | You can't return to a message later to debug it. |
| No raw source or headers | You can't inspect SPF, DKIM or DMARC results here. |
| Attachments aren't stored, embedded images are removed, 5 MB limit | You can't check attachments, embedded images or very large messages. |
| Sandboxed HTML view | It isn't a preview of how Gmail or Outlook will show your email. |
| One public domain | You can't test on your own domain, and some services refuse this one. |
When to use a dedicated tool
If you're past a quick manual check, these kinds of tools fit better:
- A local mail catcher, such as Mailpit, captures your app's outgoing mail during development, so nothing goes out to the internet.
- A hosted testing service with an API, such as testmail.app, lets automated tests read messages.
Would a developer plan help you?
Mailly doesn't have one, and there's nothing to buy today. We're trying to find out whether API access, your own domain or longer retention would be worth building.
If you'd use it, tell us what you'd test and how many inboxes you'd need.