Is Temporary Email Safe?

The honest answer has two halves. A temporary address protects you well from one specific thing, and protects you from nothing else. Knowing which is which is the whole of the safety question.

What it genuinely protects you from

Your real address spreading. This is the main benefit and it is a real one. The address you hand over cannot be sold, leaked in a breach, matched against other databases or used to find your other accounts, because within a day it will not exist. Whatever a company intended to do with it, it can no longer do.

Marketing that never stops. No unsubscribe link to hunt for, no preference centre designed to be confusing, no reappearance eighteen months later under a new brand name.

Being tracked across services. A stable email address is one of the most reliable identifiers there is. Data brokers use it to join records from different companies into one profile. A different disposable address each time breaks that join.

What it does not protect you from

Reading a message is still reading a message. Whatever arrives is exactly as trustworthy or untrustworthy as it would be in your normal inbox. Links can still be false, attachments can still be hostile, and a convincing message can still be a scam.

Other people reading your mail. On a public service with no password, and that includes guest use here, anyone who knows the address can open it. Addresses are not secret. Somebody who guesses a common name on a popular domain will find mail sitting in it.

Anything about your identity beyond the address. If you type your name into a form, your name is on the form. A disposable address hides one field, not the others.

How we reduce the risk on our side

Two measures matter, and they are both about the fact that the content of a message is written by a stranger.

Every message is cleaned before it is stored. Scripts are removed along with their contents, inline styles are stripped, and links that use anything other than ordinary web or mail schemes are discarded. This kills the classic attack where a message tries to run code in the page that displays it.

The message body is then shown inside an isolated frame with a strict policy that forbids scripts, forms and network requests. Remote images are permitted, because otherwise most legitimate mail looks broken, but that is the extent of what a message may do. Even if something survived the cleaning, it has nowhere to go.

Executable attachments are refused outright and never stored. Everything else is served as a download rather than displayed, from a separate location, so no file can execute in the context of the site.

What the sender still learns when you open a message

Remote images are allowed here, and that has a consequence worth stating plainly. A tracking pixel is a remote image one pixel across, and when the message is displayed, that image is fetched. The sender learns that the message was opened, roughly when, and the network address the request came from.

We keep remote images on because switching them off breaks the look of most legitimate mail, and a receipt or a confirmation that renders as a column of broken icons is worse for nearly everyone than the tracking is. But the trade is real, so treat it as known: opening a message here tells the sender the address is live and being read.

The practical effect is small for the usual case. You gave a shop an address that disappears tomorrow, and it learns that somebody opened its mail. It cannot join that to your other accounts, because the address links to nothing else. If even that is more than you want to reveal, do not open the message: the subject line and the sender are visible in the list without fetching anything remote, and a verification code is often visible there too.

Judging a message once it arrives

A disposable mailbox attracts the same fraudulent mail as any other, and it has one weakness the normal inbox does not: you have no history here, so a stranger's message has nothing to look inconsistent with.

Check the sending domain rather than the display name. The name is free text and can say anything; the part after the at sign is the claim worth reading, and a close variant of a real brand is the oldest trick there is.

Be suspicious of any message that arrives before you asked for one. If you used this address in exactly one place ten seconds ago, a message from somebody else did not find you by accident.

Treat a link in a message as a claim about where it goes, not a fact. Read the address it points at before following it, and reach the service through its own site rather than the link when anything about the message is asking for a password.

Attachments deserve the same suspicion here as anywhere. Executable files are refused outright and never stored, but a document can still be hostile, and a file arriving at an address you have used once is not something you were waiting for.

When not to use a temporary address

Account recovery. If the only way back into an account is a message to an address that expires tomorrow, you have not made an account, you have made a countdown.

Anything financial or official. Banking, payments, tax, government, legal. These need a mailbox you control permanently.

Anything genuinely private. Medical results, legal correspondence, anything you would be uncomfortable having read. A guest mailbox is open by design.

Work. Colleagues need to reach you next week.

The risks people worry about but should not

"Someone will read my old messages." They will not, because the messages stop existing. A guest mailbox and everything in it is deleted a day after the last time it was used, and there is no archive to recover from.

"My address will be sold." It will, probably, and it does not matter. By the time the list is traded, the address resolves to nothing.

"The site will get hacked and my data leaked." The interesting question is what data. There is no name, no phone number, no password for guests, and mail older than a day is gone. A breach here yields a list of expired addresses.

The risks people ignore but should not

Using it for account recovery. Far and away the most common way people get hurt. The address expires, the account becomes unrecoverable, and nothing can be done afterwards. This is not a security failure of the service; it is using a tool for the opposite of its purpose.

Assuming a code is private. A verification code sitting in an open mailbox is a code anybody can use. If somebody knows the address you used to register somewhere, they can request a password reset and read the result. For anything that matters, this alone rules out a guest mailbox.

Trusting a message because it arrived. Fraudulent mail arrives here exactly as easily as anywhere else. The address being disposable does not make its contents trustworthy.

Downloading whatever came. An attachment from an unknown sender is unsafe regardless of which mailbox it landed in.

Choosing between guest and account by what you are receiving

A simple rule that covers nearly everything:

• A code for a site you will never revisit. Guest mailbox, no thought needed.
• A code for a site you may sign into again. Register, so the mailbox is yours alone and nobody can request a reset and read it.
• Anything with your name, address or order details. Real mailbox or an alias, not this.
• Anything you might need in a month. Real mailbox, without exception.

A sensible way to use it

Think of your addresses as three tiers. Your real address goes to people you have an actual relationship with. A permanent alias goes to services you want to keep but might want to cut off later. A disposable address goes to everything else, which turns out to be most of the web.

Used that way it is safe, in the specific sense that it removes a risk you were otherwise taking every day without noticing.