Does the 30 minutes start when I open the page?

No. The timer starts when a message arrives and restarts with every new message, so it counts from the last mail rather than from page load. A mailbox that keeps receiving never expires; one that goes quiet for 30 minutes is swept and emptied.

Can I extend a 30-minute email address?

Only indirectly: each new message that arrives resets the window. There is no countdown to pause and no way to renew an address that has already expired — the mailbox is deleted, so the next address you claim is a different mailbox with no history.

Is 30 minutes long enough for most sign-ups?

For a normal flow, yes — most verification mail lands in seconds and the code is used within a minute. It is not enough when a human has to approve the account, when a platform batches its mail, or when you need the address again days later for a security check.

What a 30-minute email actually gives you

Disposable inboxes advertise a duration — 10 minutes, 30 minutes, an hour, a day — and almost every one of them means the same thing, which is not what most people assume. The number is how long your mail survives, not how long the address belongs to you. Understanding that distinction is the difference between a service that works and one that loses your confirmation code.

The timer counts from the last message

On TempMail.cc, mail is kept for about 30 minutes after the most recent message arrives. Every new message restarts the clock. That is a sliding window, not a countdown from page load: a mailbox receiving mail steadily stays alive indefinitely, and one that goes quiet for half an hour is emptied and removed from memory.

The practical consequence is useful. If a sender is slow — a queue, a manual approval, a batch job that runs on the hour — your waiting time does not eat into the storage window, because the window only begins when the message finally lands. You are not racing a clock while you wait; you are racing it after the mail appears.

What expires, exactly

Three things, and they are worth separating:

Mail content is deleted about 30 minutes after the last message. No archive, no backup, no retrieval.
A recovery link dies at the same moment, because it points at that same memory and nothing else.
The address itself was never yours to begin with. While your tab is open it cannot be taken by anyone else; once the tab closes, the name is released after the server notices the dropped connection and can be claimed again.

Only the first two are a timer. The third is an ownership question, and it is the reason a memorable custom name is not a private one.

Choosing between short and long windows

Durations are a trade between exposure and convenience. Short windows are safer — the mail exists for less time and the address is harder to abuse — but they fail whenever a flow is slower than the window. Longer windows are convenient but concentrate more mail in one place for longer.

Window	Fits	Fails when
~10 minutes	A code you are actively waiting for, entered immediately	Any queue, manual review, or a form you fill slowly
~30 minutes	Normal sign-ups, several codes in a row, a two-step flow	Approval that takes an hour, or a security check the next day
~1 hour	Slow senders and multi-step onboarding	Nothing much, but the address stays reachable longer
24 hours or more	Anything where the address must still work tomorrow	It is not really disposable any more — an alias is a better tool

Thirty minutes sits deliberately in the middle: long enough that a delayed verification or a second confirmation still arrives, short enough that a leaked address stops being worth anything within the hour.

Why not let people pick the duration?

Because the number is not a product feature, it is a memory budget. Every live mailbox occupies heap, and a mailbox that lives for a day multiplies that cost by roughly fifty while serving the same one-time purpose. The constant is also what makes the service free and accountless: nothing needs to be tracked per user, because nothing is expected to survive.

Making 30 minutes work for you

Start the flow in the same session — open the inbox tab first, then the sign-up form.
Copy the address with the button rather than retyping it.
Use the code or click the link as soon as the message appears; do not leave it for later.
If you need the mailbox on a second device, copy a recovery link on the first one before the window closes.
If a sender has not delivered within a few minutes, suspect a blocked domain rather than a slow server.

When 30 minutes is the wrong tool

Anything that expects the address to answer later: account recovery, security checks on a new device, receipts for an order you might dispute, or a service that re-verifies after a few days. Those need a mailbox that persists, and the honest answer is a real provider — ideally an alias, which gives you the separation from your main inbox without the cliff edge. The FAQ lists what else this service deliberately does not do.

Three things the window does not protect you from

The lifetime is generous for a normal flow and does nothing at all for the three ways people actually lose mail. Worth knowing before you rely on the number.

A tab that sleeps. A background tab on a phone stops receiving pushes, and the connection drops without an error anyone notices. This is handled, but not by extending the window: the server keeps the messages it accepted, and they are replayed in one batch the moment the tab reopens and reclaims the address. So the mail is not lost, but it is invisible until you look — and if you were waiting on a code to type into the same phone, "reopen the tab" is the step people forget.

Someone else using the same name. Because an address is not a password, a name can be released and claimed again. If you close the tab and a visitor picks the same memorable string, they get a fresh empty inbox — not your old mail, which was swept — but from that point the name is theirs. This is why a random generated address is safer than a custom one you can spell in a sentence.

A sender that retries later. Mail servers queue and retry a failed delivery, sometimes for hours. A retry that succeeds after the mailbox has been swept does not resurrect it; the message is accepted and discarded like any other mail to a name nobody is watching. If a code "never arrived", the honest possibilities are a blocked domain, a silent rejection at the sending side, or a retry that landed after you stopped looking.