What is a dummy email address?

A dummy email address is a disposable inbox used for development and QA testing — not tied to a real person, usable for any number of test runs, and discarded when no longer needed. Unlike a shared test inbox, a dummy address is isolated per session, preventing test data from different runs mixing together. VanishInbox generates one instantly with no setup, and it auto-deletes after 10 minutes.

Does a dummy email address receive real SMTP mail?

Yes. VanishInbox operates real email infrastructure — a Cloudflare Worker receiver that processes inbound SMTP mail from any sending server. When your application sends an email to a VanishInbox address, it goes through normal email delivery channels and arrives in the inbox within seconds. It is not a mock — it is a real, live inbox.

Can I use a dummy email for automated testing pipelines?

VanishInbox is built for manual and exploratory testing — a developer with a browser tab. For fully automated CI/CD pipelines, consider Mailpit (self-hosted, Docker-based) or Mailtrap (commercial API). VanishInbox works well alongside these tools: automated pipelines for CI, VanishInbox for manual QA and external delivery verification.

How is a dummy email different from a shared test inbox?

A shared team test inbox (like test@yourcompany.com) mixes emails from all developers and test runs in one place. When two developers run registration tests simultaneously, both verification codes land in the same inbox — impossible to isolate. A dummy address per session or per test run means each inbox is completely isolated. No coordination, no collisions, no cleanup.

What if the service I'm testing blocks disposable email domains?

VanishInbox offers five domains: fommie.com, whoopza.org, fommie.online, fommie.store, and whoopza.store. If you are testing against your own application, domain blocklists are usually not an issue. If testing against a third-party service that blocks known disposable domains, try the less common domains — they are far less likely to appear on standard blocklists than well-known services with a single primary domain.

Can I inspect the HTML of emails in VanishInbox?

Yes. Emails are rendered in a sandboxed iframe, which displays HTML email content as it would appear to a real user — including images, layout, and styling. The sandbox prevents external scripts and tracking pixels from executing, which also makes it safe to inspect potentially malicious test emails. The raw content is visible for debugging.

🧪 Real SMTP · HTML rendering · Auto-clears in 10 min

Dummy Email Address

A free disposable inbox for development and QA testing. Receives real SMTP mail from any sender, renders HTML emails, and auto-deletes after 10 minutes. No sign-up, no test account management.

Also known as: dummy inbox · test email address · throwaway email for testing · temp email for developers

Why a Dummy Address Beats a Shared Test Inbox

😞 Shared team inbox ([email protected])

✗All developers share the same inbox — emails mix between sessions
✗Parallel test runs produce unidentifiable verification codes
✗Old test data accumulates and interferes with new tests
✗Requires login credentials to access
✗Can't test against external services without exposing the address
✗Manual cleanup required after every test run

✅ VanishInbox dummy address

✓Fresh isolated inbox per session — zero cross-contamination
✓Generate a new address per developer or per test run
✓Auto-clears after 10 minutes — no cleanup required
✓No login — open the page and you're ready
✓Works against any external SMTP sender in real conditions
✓Five domains to avoid blocklists on third-party services

4 Testing Scenarios — Step by Step

The most common email flows developers test with a dummy inbox

📝

Registration & email verification

Steps

01Generate a dummy address above
02Submit it in your sign-up form
03Watch the confirmation email arrive (usually 5–15s)
04Click the verification link or copy the code
05Confirm the activation flow completes end-to-end

What to check

Delivery speed, link validity, token format, redirect URL

🔢

OTP & two-factor authentication

Steps

01Trigger an OTP send in your application
02Switch to VanishInbox — inbox refreshes every 5s
03Copy the code within the expiry window
04Verify the code is accepted by your auth flow
05Test re-requesting a new OTP invalidates the old one

What to check

Delivery speed, code format, expiry behaviour, invalidation logic

🔑

Password reset flow

Steps

01Trigger a password reset for a dummy-email account
02Receive and open the reset email
03Inspect the reset link — is the token correct?
04Test the link in both staging and production environments
05Verify the link expires after use or after a time limit

What to check

Token format, link expiry, environment (staging vs prod), redirect

📨

Transactional email delivery

Steps

01Trigger any transactional send from your ESP
02Receive it in VanishInbox and inspect the HTML
03Check rendering — layout, images, fonts, responsive
04Verify From name and From address are correct
05Check all links are absolute and point to the right env

What to check

HTML rendering, From address, link targets, plain text fallback

Read the full developer guide — CI/CD integration, template inspection, spam score testing →

Email Testing Checklist

Run through this before shipping any feature that touches email

☐Confirmation email arrives within 30 seconds

☐Verification link or code works and activates account

☐OTP is correctly formatted and not expired on arrival

☐Password reset link redirects to the correct URL

☐Email renders correctly in the HTML inbox viewer

☐All links are absolute (not relative paths)

☐From name and address are correctly set

☐Subject line variables are substituted correctly

☐Plain text fallback is included and readable

☐Re-requesting an OTP invalidates the previous one

☐Welcome email fires after activation, not before

☐Email does not land in the spam folder (test periodically)

Dummy Email — Frequently Asked Questions

What is a dummy email address?: A dummy email address is a disposable inbox used for development and QA testing — not tied to a real person, usable for any number of test runs, and discarded when no longer needed. Unlike a shared test inbox, a dummy address is isolated per session, preventing test data from different runs mixing together. VanishInbox generates one instantly with no setup, and it auto-deletes after 10 minutes.
Does a dummy email address receive real SMTP mail?: Yes. VanishInbox operates real email infrastructure — a Cloudflare Worker receiver that processes inbound SMTP mail from any sending server. When your application sends an email to a VanishInbox address, it goes through normal email delivery channels and arrives in the inbox within seconds. It is not a mock — it is a real, live inbox.
Can I use a dummy email for automated testing pipelines?: VanishInbox is built for manual and exploratory testing — a developer with a browser tab. For fully automated CI/CD pipelines, consider Mailpit (self-hosted, Docker-based) or Mailtrap (commercial API). VanishInbox works well alongside these tools: automated pipelines for CI, VanishInbox for manual QA and external delivery verification.
How is a dummy email different from a shared test inbox?: A shared team test inbox (like [email protected]) mixes emails from all developers and test runs in one place. When two developers run registration tests simultaneously, both verification codes land in the same inbox — impossible to isolate. A dummy address per session or per test run means each inbox is completely isolated. No coordination, no collisions, no cleanup.
What if the service I'm testing blocks disposable email domains?: VanishInbox offers five domains: fommie.com, whoopza.org, fommie.online, fommie.store, and whoopza.store. If you are testing against your own application, domain blocklists are usually not an issue. If testing against a third-party service that blocks known disposable domains, try the less common domains — they are far less likely to appear on standard blocklists than well-known services with a single primary domain.
Can I inspect the HTML of emails in VanishInbox?: Yes. Emails are rendered in a sandboxed iframe, which displays HTML email content as it would appear to a real user — including images, layout, and styling. The sandbox prevents external scripts and tracking pixels from executing, which also makes it safe to inspect potentially malicious test emails. The raw content is visible for debugging.