Use Cases

How to create a test email address that actually receives mail

A working test address takes about ten seconds and no account. Here is the fastest way to get one, why made up addresses fail, and when a temporary inbox is the wrong tool.

On this page
  1. Three steps, start to finish
  2. Why test@example.com does not work
  3. Choose the username and the domain yourself
  4. Send the test and read what arrives
  5. Keep it longer, or destroy it now
  6. When a temporary address is the wrong tool
  7. Testing the email your own app sends

The fastest way to create a test email address is to open an inbox that already exists rather than making one up. Go to InboxDome, and an address is generated and waiting before the page has finished settling. Copy it, paste it into whatever you are testing, and the message appears in the same tab a few seconds later. That is really all there is to how to create a test email address: no account, no password, no confirmation step.

Three steps, start to finish

  1. Open the homepage. A random address is minted for you, something in the shape of k7f2p9@mail.inboxdome.com, shown in a bar with a Copy button beside it.
  2. Copy it and use it. Paste it into the signup form, the checkout, the password reset box, or whatever is supposed to send you mail.
  3. Watch the inbox. Messages arrive live in the page underneath the address. There is nothing to refresh and no app to install.

Under the address sit five actions: New address, QR code, Share link, Recent inboxes and Delete inbox. The QR code moves an address onto a phone you are testing on, and Recent inboxes gets you back to one from ten minutes ago.

Why test@example.com does not work

Most people’s instinct for how to create a test email address is to type something like test@example.com into the form and hope. That address cannot work. RFC 2606 reserves .test, .example, .invalid and .localhost, plus example.com, example.net and example.org, specifically so they can appear in documentation without ever colliding with a real name. Nothing behind them accepts mail.

The send therefore bounces, or it is dropped in silence, and either way you learn nothing about whether your email works. The worse version of the same mistake is inventing a domain that somebody does own, in which case a stranger receives your test.

There is a smaller trap too. A form that accepts an address is not a form that delivered to it: browser validation on an <input type="email"> is a syntax check, never a delivery check. A test address has to be real enough to receive.

Choose the username and the domain yourself

Above the address are two modes: Random username and Your own username. Pick the second, type something like checkout-test, choose a domain from the dropdown, then press Generate. You get checkout-test@ plus the domain you picked, assuming nobody holds it already.

Two reasons this is worth the extra five seconds. A readable local part tells you at a glance which test a message belongs to when several are running. And some signup forms reject specific domains, so being able to switch is the difference between testing your own flow and testing somebody else’s blocklist.

Send the test and read what arrives

Trigger whatever you are checking, then watch. Mail lands in the list as it arrives, so a verification code is usually readable before you have switched back to the other tab.

Messages render in a sandboxed frame, which matters more than it sounds. Scripts inside an email never run. Remote images stay blocked until you allow them, so the tracking pixel in a marketing template does not report you as having opened it. Links keep their real destination, visible before you click, and open in a new tab with no referrer passed along. No third party analytics scripts run on the inbox page. The security page has the full detail.

One deliberate limit: the address is receive only. You cannot reply from it. That is the reason it cannot be turned into a spam cannon, and the reason the address you hand out cannot be used to impersonate you.

Keep it longer, or destroy it now

By default the inbox deletes itself 24 hours after it is created. While it is open you can push that back with the extend buttons, to a hard maximum of seven days. Attachments live exactly as long as the message they came with, and a cleanup job sweeps every 15 minutes, so “deleted” means gone rather than hidden.

If you finish sooner, Delete inbox purges it on the spot, and the address stays dead afterwards instead of being handed to the next visitor. The retention page lists what is kept and for how long, including the short, access restricted security logs.

One thing to treat carefully: the inbox is opened by a secret carried in your private link, and only a hash of that secret is stored. Guessing an address gets an intruder nothing, but anyone you send the full link to can read the mail. Share it like a password.

When a temporary address is the wrong tool

Do not use one for anything you might need to get back into. A bank, a domain registrar, a tax portal, an account holding your work or your money: all of those eventually send a recovery mail, and if the inbox expired months ago that path is closed. A disposable inbox is right for a one time code, a download gate, a trial you will not renew, or a form you are testing. It is wrong for anything that has to still work next year.

For a durable address that is still separate, plus addressing is the usual answer: you+shop@example.org reaches your normal mailbox while staying easy to filter and easy to trace if it leaks. RFC 5233 defines the convention as a subaddress, and many providers, including Gmail, honour it. Some sites reject the plus sign, and anyone can strip the suffix, so treat it as a labelling tool rather than a privacy one.

Testing the email your own app sends

If you need to create a test email address by hand more than a few times a week, that is a job for code. The Email Testing API makes an inbox in one call and blocks until the message arrives in the next:

curl -X POST https://inboxdome.com/v1/inboxes \
  -H "Authorization: Bearer idk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"domain":"smart","ttlSeconds":3600}'

curl "https://inboxdome.com/v1/inboxes/inb_.../wait?for=otp&timeoutSeconds=30" \
  -H "Authorization: Bearer idk_live_..."

From there you can assert on the content, on the links, and on the SPF, DKIM and DMARC results, which is how you catch a reset mail that arrives but lands in spam. If you are still weighing platforms, the comparison of email APIs worth building on covers which ones handle receiving properly. The free tier covers 100 inbox tests a month with no credit card, and there are setup guides for Playwright, Cypress and GitHub Actions. If you drive tests from an AI agent, the MCP server exposes the same capabilities as seven tools, and the rundown of email MCP servers shows how it compares.

Disclosure: InboxDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.

Key takeaways

  • A test address is only useful if it can genuinely receive mail, so an invented one proves nothing.
  • Opening the InboxDome homepage hands you a working address immediately, with no account, password or confirmation step.
  • Addresses at example.com and .test are reserved by RFC 2606 and accept no mail at all.
  • The inbox deletes itself 24 hours after it is created, and you can extend it while it is open to at most seven days.
  • Never use a temporary address for an account you may need to recover later.

Sources

  1. RFC 2606: Reserved Top Level DNS Names — Why example.com, .test and .invalid can never receive real mail.
  2. RFC 5233: Sieve Email Filtering, Subaddress Extension — The plus addressing convention, defined as a subaddress.
  3. MDN: the email input type — What a browser does and does not check before a form accepts an address.

Links last checked August 28, 2026.

Frequently asked questions

Is a test email address the same as a fake email address?

No, and the difference is the whole point. A fake address such as test@example.com cannot receive anything, so it tells you nothing about whether your mail was sent, delivered or readable. A test address is a real, working mailbox that you did not have to create an account for.

Do I need to sign up to create a test email address?

No. Opening the InboxDome homepage generates an address for you straight away. There is no account, no password and no email confirmation, which is what makes it quick enough to use for a single form.

How long does the test address last?

The inbox deletes itself 24 hours after it is created. While it is open you can extend it, up to a maximum of seven days, and you can delete it yourself at any time. A cleanup job runs every 15 minutes.

Can I reply from a test email address?

No. InboxDome is receive only, on purpose. That means the address cannot be used to send spam or to impersonate anyone, which is also why it stays welcome at the far end.

InboxDome TeamEmail infrastructure builders

The InboxDome team runs the temporary-email service and email-testing API this blog belongs to. We write about disposable inboxes, email privacy and testing transactional email, based on operating the infrastructure ourselves.