From the User's View to the Wire
From the outside, a temporary inbox looks almost magical: open a page, receive an address, and messages appear seconds after a website sends them. If you are new to the idea, start with what temporary email is. This article goes one level deeper and follows a single message from the sender's mail server to your browser tab, using InboxBurn as the example.
Nothing here is exotic. A disposable email service uses the same internet mail standards as Gmail or your company's server. What differs is how addresses are created, who can read them and what happens when they expire.
Step 1: Domains and MX Records
Every email address ends in a domain, and every domain can publish MX (mail exchanger) records in DNS. When a sending server wants to deliver to [email protected], it looks up the MX records for example.com and gets back one or more hostnames with priorities. It then resolves those hostnames to IP addresses and connects to the one with the lowest priority number first.
A temporary email service owns several domains and points their MX records at its own receiving servers. Running multiple domains lets the service retire or add domains without disrupting everything at once.
You can inspect any domain's MX, SPF and DMARC records yourself with the email DNS checker.
Step 2: The SMTP Conversation
Mail between servers travels over SMTP, usually on port 25. The sender opens a connection and the two servers exchange a short, text-based dialogue. A simplified version looks like this:
S: 220 mx.example-receiver.com ESMTP ready
C: EHLO mail.sender.example
S: 250-mx.example-receiver.com
S: 250-STARTTLS
S: 250 SIZE 26214400
C: STARTTLS
S: 220 Ready to start TLS
(TLS handshake, then EHLO again)
C: MAIL FROM:<[email protected]>
S: 250 OK
C: RCPT TO:<[email protected]>
S: 250 OK
C: DATA
S: 354 End data with <CR><LF>.<CR><LF>
C: From: Example App <[email protected]>
C: Subject: Your verification code
C: ...headers and body...
C: .
S: 250 Queued
C: QUITA few details matter for temporary inboxes:
- EHLO introduces the sending server, and the receiver advertises capabilities such as STARTTLS and the maximum message size.
- STARTTLS upgrades the connection to TLS so the message is encrypted in transit between servers. Most large senders use it whenever the receiver offers it.
- MAIL FROM is the envelope sender, used for bounces. It can differ from the From header you see in the message.
- RCPT TO is the envelope recipient. This, not the To header, decides which inbox the message belongs to. A message can be addressed "To" one person and still be delivered to another through Bcc or forwarding, so the envelope recipient is the trustworthy value.
- After DATA, the receiver answers with a status code. A 2xx code means "accepted", a 4xx code means "try again later" and a 5xx code means "rejected permanently". Temporary failures are why some messages arrive minutes late; see why verification emails arrive late.
Step 3: Deciding Which Addresses Exist
A conventional mail server knows a fixed list of mailboxes. A disposable service creates addresses on demand. There are two broad designs:
- Catch-all: accept mail for any local part at the domain and sort it out later.
- Session-based: track addresses that have been created, with their expiry times, and attach incoming mail to the matching session.
InboxBurn creates an inbox session whenever an address is generated, either randomly or with a custom prefix, and stores its expiry time. A custom address can be claimed only while no other active session holds it, which prevents two people from sharing a live inbox.
The receiving side can also refuse mail at the SMTP stage, for example from senders an operator has chosen to reject, returning a 5xx code so the sender knows the message was not accepted.
Step 4: Authentication Signals
Before trusting a message's claims, a receiver can check three standards:
- SPF lists which servers may send mail for a domain. The receiver checks whether the connecting IP is allowed for the envelope sender's domain.
- DKIM adds a cryptographic signature to selected headers and the body. The receiver fetches the public key from DNS and verifies that the signed content was not altered.
- DMARC ties the two to the visible From domain and publishes the domain owner's policy for failures.
For a temporary inbox these are signals rather than gatekeepers. A message that fails them is more likely to be spoofed, and that can feed into spam scoring, but a service built for receiving sign-up mail cannot reject everything imperfect, because plenty of legitimate small senders have misconfigured records. If you send mail yourself, the spam checker shows how your messages look to filters.
Step 5: Parsing MIME
The raw message is not what you see in the inbox. Modern email uses MIME, which wraps content in parts:
multipart/alternativetypically carries the same message astext/plainandtext/html, letting the reader pick.multipart/mixedadds attachments alongside the body.multipart/relatedbundles inline images referenced from the HTML.
Each part can use its own character set and transfer encoding, such as quoted-printable or base64, and headers containing non-ASCII text use encoded words. The parser decodes all of this into a sender, subject, plain-text body, HTML body and a list of attachments with filenames, types and sizes.
Step 6: Making Untrusted HTML Safe
Email HTML comes from strangers. Rendering it directly in a web page would let a sender run scripts, steal the session or reshape the page. A temporary inbox therefore treats every message as hostile:
- Scripts, event handlers and dangerous elements are removed or neutralised.
- The message is displayed in an isolated, sandboxed frame rather than mixed into the application page.
- Remote content such as tracking images can reveal when a message was opened, so it needs careful handling.
Step 7: Scanning Attachments
Attachments are stored separately from the message body and scanned for known malware before they are offered for download. On InboxBurn, a message from a blocked or flagged source is not shown in the public inbox. No scanner catches everything, so the usual advice still applies: do not open unexpected executables or macro-enabled documents, even if a scan reported nothing.
Step 8: Storage and Real-Time Delivery
Once parsed, the message is written to a database linked to the inbox session, with its received time and expiry. Your browser learns about it in one of two ways:
- Push: the page keeps a WebSocket connection open and the server sends an event the moment a message is stored. This is why messages appear without a refresh.
- Polling: clients, including automated tests, periodically request the inbox list. Developers can also receive signed webhooks when mail arrives at inboxes created with their API key; see the API docs.
Step 9: Access Control With Inbox Tokens
There are no passwords on a public temporary inbox. Instead, when an address is created the service issues a random inbox token, and only someone presenting that token can list or read the messages. InboxBurn stores new tokens as hashes, so the raw token is not kept in the database.
The recovery link and QR code simply carry that token to another device. That makes them powerful: anyone with the link can read the inbox until it expires, so share it with no one.
Step 10: Expiry and Archiving
Each inbox has a lifetime chosen at creation, from 10 minutes to 7 days, 24 hours by default, and Extend adds 24 hours while it is active. A background job regularly looks for sessions past their expiry time.
When an inbox expires, public access ends: the token no longer opens it and the messages disappear from the inbox view. The content is not instantly erased, however. Expired message bodies are moved to an archive accessible to the service's administrators, as described in the privacy policy. This is an important difference from services that promise immediate destruction; you should never route sensitive personal data through any temporary inbox. After expiry, the address itself can be claimed again by someone else.
Step 11: Domains Under Pressure
Because disposable domains are public, websites add them to blocklists, and some mailbox providers treat them with suspicion. Operators respond by monitoring domain health, checking that each domain still receives mail correctly, and retiring domains that stop working. Why websites block disposable email explains the other side of that relationship.
Putting It Together
DNS tells senders where to go, SMTP carries the message, authentication checks add context, MIME parsing turns bytes into a readable message, sanitising and scanning make it safe to display, a token decides who can read it, and expiry decides how long it stays visible. Create an address and watch the first message arrive to see the whole pipeline in under a minute.