Guide

How to Test Sign-Up, Verification and Password Reset Emails With a Disposable Inbox

By The GetDisposableMail team · Published · Updated · 7 min read

Cover for “Test Your Sign-Up Emails”: a laptop showing a QA checklist next to an inbox with a highlighted six-digit verification code

Sign-up and password-reset emails are the front door of most apps, and they break in quiet ways: a link that points to staging, a code that expires before it arrives, a template that looks fine in one client and is unreadable on a phone. Users rarely report these problems. They just leave.

A disposable inbox is the fastest way to check the whole flow the way a real user experiences it. This guide gives you a repeatable manual routine, the bugs worth hunting for, and an honest view of where temporary email fits next to proper test tooling.

Two kinds of email testing - you need both

  • Did my app generate the right email? Best tested automatically with a local mail catcher such as Mailpit, which captures everything your app sends in development so tests can read it. Fast, private, no rate limits.
  • Does the email actually reach a real inbox? That covers DNS, SPF/DKIM/DMARC, your email provider, queues and the rendered result. Here a real external inbox — like a temporary address — is the quickest honest check, especially before a release or after changing providers.

Before you start

  • Test only apps you own or are authorised to test.
  • Use a fresh address per scenario so results don’t mix. On GetDisposableMail, Change lets you pick a username like qa-reset-01; fair use is one new address per hour, so plan scenarios or reuse one inbox for related steps.
  • Keep the inbox tab open with the status showing “Live”, so you can time delivery.
  • For data that should never receive mail (seeds, fixtures, screenshots), use reserved domains such as example.com or .test, defined in RFC 2606.

Scenario 1: sign-up with a verification code

  1. Sign up with the temporary address and note the time.
  2. Measure how long the code takes to arrive. Anything over a minute will feel broken to users.
  3. Check the code banner: GetDisposableMail highlights a likely one-time code. If it doesn’t, the code may be buried in an image or oddly formatted — a hint that real users will struggle too.
  4. Enter the code. Then try it again: it should be single-use.
  5. Request a second code and try the first one — it should normally be invalid.
  6. Wait past the stated expiry and confirm an expired code is rejected with a clear message.
  7. Try a few wrong codes and confirm rate limiting or lockout behaves as designed.

Scenario 2: verification link or magic link

  1. Open the link from the inbox. Check the domain — links pointing at staging, localhost or a raw tracking domain are common release bugs.
  2. Open the same link a second time. A magic sign-in link should not log you in twice.
  3. Open the link in a different browser or device. Decide whether that should work and confirm it does what you intended.
  4. Check what happens after expiry, and that the error page offers a way to request a new link.

Scenario 3: password reset

The OWASP Forgot Password Cheat Sheet is the best single reference for the security side. In practice, check:

  • The reset form responds the same way for registered and unregistered addresses, so it doesn’t reveal who has an account.
  • The email arrives promptly and clearly says what to do if you didn’t request it.
  • The token is long, random, single-use and expires.
  • Requesting a new reset invalidates older links.
  • After a reset, existing sessions are handled the way your policy says (often: signed out).
  • The user is notified that their password changed.

Scenario 4: changing the account email

  • Start the change from an account, using a second temporary address as the new one.
  • Confirm the new address must be verified before it takes effect.
  • Confirm the old address receives a notice — that’s often the only warning a user gets if their account was hijacked.

Check the email itself

  • Sender and subject — recognisable brand name, no internal placeholders, no “test” left in production templates.
  • Plain-text part — present and readable. Some clients and screen readers rely on it.
  • Without images — our inbox blocks remote images by default, which is exactly how many privacy-conscious readers see your email. Is the code or button still visible?
  • Mobile — open the inbox on your phone (Save gives you a private link and QR code for the same inbox) and check the layout.
  • Links — all HTTPS, correct environment, no broken UTM parameters.
  • Authentication — send to a mailbox that shows the SPF, DKIM and DMARC verdicts and confirm they pass. Our SPF, DKIM and DMARC guide explains failures.

Common bugs this routine catches

  • Links pointing to staging or localhost after a deploy.
  • Codes expiring in less time than delivery takes at peak.
  • A new code request not invalidating the previous one.
  • Reset emails that confirm whether an address is registered.
  • Templates that rely entirely on remote images.
  • Missing DKIM after switching email providers, sending mail to spam.

Disposable domains and your own sign-up rules

If your product blocks disposable domains, your QA team will need an allow-listed test domain or a mail catcher — a temporary address will (correctly) be refused. If it doesn’t block them, decide deliberately. Our article on why some sites block disposable email covers the trade-offs from the user’s side.

Where temp mail fits - and where it doesn’t

Use a disposable inbox for exploratory testing, release smoke tests, checking a new email provider, and seeing your emails the way a real user does. Don’t point load tests, CI suites or scrapers at a public temp mail service — it’s against fair use, it’s slower than local tooling, and it would get you rate-limited. Our OTP field guide has more on why codes go missing in real-world delivery.

Write down what you measured

A release check is only useful if you can compare it with the last one. For each scenario, record the date, the environment, the sending provider, the time from request to arrival, whether codes and links worked as expected, and a screenshot of the email with images blocked. Over a few releases this becomes an early-warning system: a delivery time that creeps from five seconds to two minutes usually points to a provider, queue or authentication problem before users start complaining.

Frequently asked questions

Is it OK to use temp mail to test my own app?

Yes — testing sign-up, verification and password-reset emails for an app you build or are authorised to test is one of the most common legitimate uses. Testing on other people’s services without permission isn’t.

Can I use GetDisposableMail in automated tests?

It’s designed for people, not CI pipelines. Fair use is one new address per hour, and inboxes keep the newest 50 messages. For automated tests, run a local mail catcher such as Mailpit, or a testing service built for programmatic access.

Why use a real external inbox instead of a local mail catcher?

A local catcher proves your app generated the email. A real external inbox proves it was actually delivered over the internet — DNS, authentication and your provider’s sending pipeline included. You want both: the catcher for fast automated runs, an external inbox for a final real-world check.

Which domains should I use for fake test data?

Use the reserved names example.com, example.net, example.org or the .test and .invalid top-level domains (RFC 2606) for data that must never receive mail. Use a real disposable inbox only when you need the message delivered.

What should I check in a password reset email?

That it arrives promptly, the link works once and then expires, it doesn’t reveal whether an account exists, the old sessions are handled as designed, and the email tells the user what to do if they didn’t request it.

Sources and further reading

About the author. The GetDisposableMail team builds and runs this temporary email service. We write these guides from what we see operating a live disposable inbox, and we review them when the service changes. More about us.