Blog
What Is a Temporary Email? A Plain Explanation of the Mechanics
What actually happens when you press generate, why these mailboxes have no password, and the four-question test for deciding whether one belongs in your workflow.
A temporary email address is a mailbox that somebody else opened for you on a domain you do not own, which anybody can read, and which will be deleted on a schedule you did not choose.
That sentence sounds hostile. It is not. It is the most accurate one-line description of the product, and every sensible decision about when to use one follows directly from it.
What happens in the two seconds after you press generate
The interface makes this look like magic. It is four ordinary steps.
- Your browser asks the ShieldMail server for an inbox. Your browser never talks to the mail provider directly.
- The server picks the first provider in its chain that passed a recent health check, and asks that provider for a mailbox on one of its shared domains.
- The provider returns an address and an access token. The token is written into an HttpOnly cookie, which means the JavaScript running on the page cannot read it.
- The address, and only the address, is sent back to your browser and painted on the screen.
When you press Refresh, the same server uses that cookie to poll the provider and hands you whatever has arrived. There is no ShieldMail account, no ShieldMail mail server, and no ShieldMail copy of your messages.
Why there is no password
This is the part that surprises people, so it is worth being blunt about.
An ordinary mailbox is protected because you prove who you are before you read it. A temporary mailbox skips that step entirely, and that skip is the whole feature. It is why an address is ready in under a second instead of after a signup form, a confirmation email, and a captcha.
The cost is exact and unavoidable: if somebody else knows or guesses the address while it is alive, they can read the mail in it. On a service handing out thousands of addresses a day across a handful of shared domains, collisions are not a theoretical concern.
So the working assumption for anything landing in a temporary inbox should be that a stranger can read it. Most of the time that is fine. A PDF download link is not a secret. A password reset link very much is.
The four questions
Before pasting a disposable address anywhere, run these. A single "yes" in the wrong column means use something else.
- Will I ever need to log back into this? If yes, you need an address you still control next month.
- Could this account ever hold money, an order history, or a subscription? If yes, support will one day ask you to confirm ownership by email.
- Does the message itself grant access to something? Reset links and login codes are credentials, not notifications.
- Is the sender someone I want to hear from again? If yes, you are throwing away the channel on purpose.
Everything else — the newsletter you want to skim once, the whitepaper behind a form, the hotel Wi-Fi portal, the forum you will read but never post in — sits squarely in the safe column.
A worked example, both ways
Where it works. You want a comparison spreadsheet from a B2B vendor. The form demands a work email and the sales team will call you for a year. You paste a ShieldMail address, the download link arrives in about six seconds, you open it, you save the file, and an hour later the mailbox no longer exists. You got the artefact. They got an address that stops resolving. Nobody was deceived; you were simply not obliged to hand over a permanent contact channel in exchange for a PDF.
Where it fails. You use the same trick to register for a conference because the ticket is free. Three months later the venue changes and the notice goes to a mailbox that was deleted the same afternoon. You show up at the wrong building. The failure was not the tool. It was answering question one wrong: you did need that channel later, you just did not feel it at the time.
What the tool is not
It is not anonymity. The site you sign up to still records your IP address, your browser fingerprint, the time, and every field you filled in. Withholding your email address removes one identifier from that set. That is a meaningful reduction in how often your address lands in marketing databases, and it is nothing at all like being invisible. There is a fuller treatment of the gap in how temporary email helps protect your privacy online.
It is also not a way around a ban, a duplicate-account limit, or a free-trial restriction. Those uses are covered in acceptable use, and they are the fastest route to getting every disposable domain blocked for everybody else.
Where to go next
For the operational version — which button to press, what to do when a site rejects the domain — read how to use temporary email safely. If you are choosing between a temporary inbox and something longer-lived, disposable email vs email alias sets the two side by side.
FAQ
Is a temporary email address a real email address?
Yes. It resolves, it accepts mail from any sender, and messages arrive in the inbox on this page. It differs from an ordinary address in lifespan and in the complete absence of access control, not in how mail reaches it.
Can I send email from a temporary address?
No. The upstream providers issue receive-only mailboxes, so there is no outbound path. If a reply needs to reach the other party, you need an alias or a real account.
How long does the address stay alive?
Sixty minutes by default on ShieldMail, and each press of Extend adds another thirty. The mailbox is released when the timer ends and cannot be recovered.
What happens to mail that arrives after it expires?
It bounces or is silently discarded, depending on the provider. There is no queue and no forwarding, so somebody who writes to you the next day gets no reply and you get no notice.
Why do some websites refuse the address?
Large services buy and maintain lists of known disposable domains and reject them at the signup form. Pressing Change requests an address from a different provider pool, which is often enough to get through.