Temp mail lasts anywhere from ten minutes to a day depending on the service. On MailboxTemp a free inbox lasts 60 minutes from the moment it is created, each extension adds 10 minutes, and a Pro inbox lasts 24 hours. When the timer ends the address stops accepting mail and everything it received is deleted. Those are the facts most people need; the rest of this article shows where each number comes from in our own code and what we measured when we tested them.
How long a temporary email lasts is a design decision, not an accident, so it is worth understanding the mechanics before you rely on one for a multi-step signup.
How long does a temporary email last?
It depends entirely on the service, and the range is wide. Some sites brand themselves around "10 minute mail" and give you barely enough time to grab one code. Others run for hours or a few days. The common thread is that temp mail is deliberately short-lived: a long-lived anonymous inbox would defeat the purpose, because the whole value is that the address is gone before anyone can do anything lasting with it.
On MailboxTemp the two lifetimes are constants in the server configuration: freeTtlMs = 60 * 60 * 1000 and proTtlMs = 24 * 60 * 60 * 1000, one hour and twenty-four hours. The expiry is fixed at creation, now + TTL, and returned to you immediately. This is the real response from a free inbox we created on 1 November 2026 while writing this:
POST /api/inbox/generate
{"ok":true,"address":"wrl4u9a@fakhita.xyz",
"expires":"2026-11-01T17:07:14.133Z", …}
GET /api/inbox/wrl4u9a@fakhita.xyz
{"ok":true,"tier":"free","expires_at":"2026-11-01T17:07:14.133Z","ttl":3599}
The ttl field is the remaining lifetime in seconds, and the countdown on the inbox page is the same number. The address was created at 16:07:14, so the expiry is exactly one hour later.
Can you extend the timer?
Yes, while the inbox is still alive. The extend button on the page calls POST /api/inbox/{address}/extend, which runs a single database update: add ten minutes to the expiry, but only where the expiry is still in the future. We called it twice on the inbox above and read the metadata back each time:
before expires_at 2026-11-01T17:07:14.133Z ttl 3589
extend → {"ok":true}
after expires_at 2026-11-01T17:17:14.133Z ttl 4189 (+600 s)
extend → {"ok":true}
after expires_at 2026-11-01T17:27:14.133Z ttl 4789 (+600 s)
Each call moved expires_at forward by exactly 600 seconds, and the extensions stack. Calling extend on an inbox that has already expired returns {"ok":true} but changes nothing, because the WHERE expires_at > NOW() condition matches no row; the API documentation says the same in one line. Extending buys time; it does not make the inbox permanent, and a Pro inbox starts with a 24-hour window instead of needing to be nursed along.
What happens when it expires?
Three things happen, in this order, and the timing of each is worth knowing.
- New mail is refused at the door. Our mail server checks every recipient against the list of live inboxes before it accepts any content. An address that has expired, or never existed, gets a permanent-failure reply during the SMTP conversation. We sent a message to a made-up address on the same domain and got exactly this:
550 Mailbox not found or expired. The sender sees a bounce; nothing is stored. - Stored messages are purged by a scheduled job. A separate process runs a purge pass every five minutes (
purgeIntervalMsdefaults to 300,000 ms). Each pass deletes attachment files from object storage first, then runspurge_expired(), which deletes expired messages and then expired inbox records. Attachments go first so that no file is left orphaned when its database row disappears. - The address becomes unknown. Once the inbox record is gone, every API call for it returns
404 NOT_FOUND, the same answer as for an address that never existed.
One honest consequence of step two: for up to five minutes after the countdown reaches zero, between expiry and the next purge pass, messages that already arrived can still be displayed. Nothing new can arrive in that window, and nothing survives the pass. There are no backups of expired inbox content; we could not recover an expired message even if asked, which can you recover a temp mail? explains in depth. The full pipeline is on how MailboxTemp works.
Free versus Pro: the lifetime numbers side by side
| Free inbox | Pro inbox | |
|---|---|---|
| Lifetime from creation | 60 minutes | 24 hours |
| Extension per click | +10 minutes, stackable while live | +10 minutes, stackable while live |
| Message lifetime | Tied to the inbox; deleted with it | Tied to the inbox; deleted with it |
| Inboxes at once (signed in) | 1 | 5 |
| New inboxes per day | 10 per IP address | No daily cap |
| Custom address prefix | No | Yes |
| Purge after expiry | Next pass, within 5 minutes | Next pass, within 5 minutes |
The concurrent-inbox limits apply to signed-in accounts; an anonymous visitor's browser manages a single inbox at a time. The daily cap is counted per IP address per UTC day, and the eleventh request returns 429 DAILY_LIMIT_REACHED with the time the counter resets.
How to plan a signup around the timer
- Create the inbox last. Fill in the form first, then generate the address and paste it, so the whole hour is available for the confirmation step.
- Extend before you need to. If you are still working through a flow, press extend while the countdown is comfortably above zero; an inbox that has already expired cannot be extended afterwards.
- Save anything you will want later. Download links, PDFs and licence keys should be copied out before expiry; the purge is final.
- Use Pro or an alias for anything lasting more than a day. A free trial that confirms by email on day one and sends a receipt on day seven is not a job for a one-hour inbox. Our aliases versus disposable email comparison covers the alternative.
What data is and is not kept?
While the inbox is alive, the service holds the messages it received so it can show them to you, plus the creation time and the expiry. Once the inbox expires, that data is deleted rather than archived. There is no signup, no password and no profile for a free inbox, so there is no long-term account record tying the inbox to you in the first place. The thing that protects your privacy is the same thing that limits the tool: nothing is retained, so nothing can be recovered.
Is temp mail safe?
For throwaway signups and one-time codes, yes; for password resets, financial mail or anything you would mind a stranger reading, no, because a disposable inbox has no password and a short life. We answer that question properly, case by case, in is temp mail safe?; the safety guide turns it into a decision table, and temp mail vs VPN vs alias covers what it does not hide.
The bottom line
A MailboxTemp free inbox lives for 60 minutes, can be extended ten minutes at a time for as long as it is still alive, and a Pro inbox lives for 24 hours. At expiry the mail server refuses new messages immediately, and a purge pass within five minutes deletes attachments, messages and the inbox itself with no backup to restore from. Plan the signup so the confirmation arrives inside that window, save what you need before the countdown ends, and the timer stops being a limitation and becomes the feature it was meant to be. If you want the background first, read what a disposable email is or our best temp mail practices, then grab a free inbox on the MailboxTemp homepage.
Sources
- RFC 5321 — Simple Mail Transfer Protocol, including the 550 permanent-failure reply a server returns for an unknown or expired mailbox.
- Haraka, the SMTP server that performs the recipient check described above.
- MailboxTemp API documentation, the retention, extension and rate-limit values quoted in this article.