A temporary inbox is not a mailbox with a short life. It is an address the service generates on demand, allows to receive for a fixed window, and then stops serving. Understanding the difference explains most of the surprises people hit — why an address sometimes arrives with a delay, why a site rejects it outright, and why nothing can be recovered afterwards.

What happens when you open the page

The address does not exist until you ask for it. Nothing is registered, nothing is reserved, and no account is created. You are given a receiving address and a countdown, and the clock starts at the moment of generation rather than at the first message that arrives. If you generate an address and then get distracted for twenty minutes, those twenty minutes are gone.

Alongside the address you are given a recovery token. That token is the only way to reopen the same inbox from a different browser or device. A private access cookie normally keeps you attached to the inbox you created, which is why it persists while you stay in the same browser and disappears when you clear cookies or switch machines.

Where the mail goes

Mail intended for the address is delivered by the sending organisation to the TempMails inbound path, and the service makes it visible in your inbox until the countdown ends. Three consequences follow:

  • Delivery depends on the sender. The sending side has to be willing to deliver to the address. If a website blocks disposable domains, the message is refused long before it reaches us, and nothing appears in the inbox.
  • Delivery is not instant. Sending systems queue mail. A verification message that takes thirty seconds through a mainstream provider can take several minutes through a slower corporate gateway, which matters when your inbox is counting down.
  • The inbox is passive. You see what arrives. There is no forwarding rule you can set, and no push notification, so a message that arrives after you close the tab is only visible if you reopen the inbox before it expires.

Sending, limits, and abuse controls

Where sending is enabled, it is deliberately narrow: plain text, a small number of recipients, and rate limits per address. The operator can switch sending off entirely. That is not a technical limitation being worked around — it is the control that stops the service being turned into a bulk mail relay, which would get the sending domain blocked and take the receiving side down with it.

Rate limits also apply to generation. Creating addresses in a loop consumes shared delivery resources, so the service slows that down. If you see a security check before an address is issued, it exists for the same reason.

Why an address expires

A short life is the feature, not a restriction. An address that disappears is an address whose inbound mail stops being a liability: there is no long-term store to breach, no archive to subpoena, and no mailbox accumulating years of newsletters you forgot about. This is also why an expired inbox is never reopened: the Extend time control works only while the countdown is still running, and every inbox stops at the operator's configured maximum lifetime. A window that could be reopened on request would not be short.

What this design does not give you

  • It is not anonymity. A temporary address hides your everyday address from the site you give it to. It does not hide your IP address, your browser fingerprint, or anything else about the connection.
  • It is not privacy against the operator. Mail is processed to display it in your inbox. Do not treat a temporary inbox as a channel for secrets.
  • It is not a substitute for a real account. Anything with a payment method, a legal record, or long-term value belongs in a mailbox you control permanently.

If you need the message later, forward it to your own mailbox before the countdown ends. That single habit removes almost every problem people report with temporary email.