How Temp Mail Works: From MX Records to Your Inbox

A temporary inbox can show you a message seconds after someone hits send, with no account and no password. It feels like magic, but it's really just standard email plumbing pointed at a throwaway address. Let's follow one email the whole way.

Step 1: An address is invented on the spot

When you open a temp-mail page, the service generates a random local part (the bit before the @) on a domain it owns — something like g9j4pdiyx9@example.com. Nothing is registered or reserved; the address simply becomes valid because the domain accepts mail for any name.

Step 2: The sender's server looks up where to deliver

When someone emails that address, their mail server asks DNS, “Which servers handle mail for this domain?” The answer is the domain's MX records. For a temp-mail service, those MX records point at infrastructure it controls (or a provider's mail-routing servers).

Step 3: A catch-all accepts the message

Normal mailboxes reject mail to unknown names. A temp-mail domain runs a catch-all instead: every address is treated as valid, so the message is accepted, scanned, and parsed — sender, subject, body, and any attachment details are pulled out and saved to a database for a short while.

Step 4: Your browser polls for new mail

The page you're looking at quietly asks the service's API every few seconds, “Anything new for my address?” When the stored message appears, it pops into your inbox view in near real time — which is why a verification code can show up almost instantly.

Step 5: Everything expires

A background job deletes messages after a set window (often an hour to a day). Generate a new address and the old one, plus everything it received, is gone. That auto-expiry is the whole point: convenience now, no residue later.

If you want the plain-English version without the hops, start with what a disposable email address is, or see how safe the whole thing is.

What happens the moment an email arrives, step by step

Here's the same journey laid out as a checklist, using a real example address on one of our mailbox domains. None of it is hand-waving — each step is a concrete piece of infrastructure doing one small job.

1. A website sends to your address. You hand a signup form something like g9j4pdiyx9@ynoxa.com, and its server treats that as an ordinary destination — it has no idea the inbox is disposable.
2. The receiving server accepts it. The sender looks up the domain's MX records, finds the mail servers we point them at, and delivers the message there.
3. A catch-all hands it off. Because the domain runs a catch-all route, the message isn't bounced for an “unknown” name — it's passed straight to a Cloudflare Worker for processing.
4. The Worker parses and stores it. The Worker pulls apart the raw email — sender, subject, body, attachment details — and writes the result to a database, keyed to your exact address.
5. Your inbox polls and shows it. The page you have open asks a small API for anything new, and the stored message appears within seconds — no refresh needed.
6. A sweep deletes it. A scheduled job runs on a timer and clears out messages once they pass their TTL — roughly 24 hours — so nothing lingers.

Quick questions about how it works

How fast does mail show up? Usually within a few seconds. The Worker stores each message on arrival, and your open inbox polls the API on a short loop — so the wait is roughly however long is left until the next check, not minutes.

Where is it stored, and for how long? In a database behind the Worker, keyed to your address, and only for about 24 hours. After that the scheduled sweep removes it for good — there's no archive and no way to recover a message once it's gone.

Can other people read my temporary inbox? Yes — and this is the honest limitation. Addresses are public and password-less, so anyone who knows or guesses your address can open the same inbox. Never route anything private, personal, or account-recovery-related through a throwaway inbox.

Can it send email? No. The whole setup is receive-only — there's no outbound path at all. You can read what arrives and reply-to addresses you see, but you can't compose or send a message from a temporary address.