Blog
Temporary Email vs Fake Email: One Works, One Just Breaks Things
Typing asdf@asdf.com is not a privacy technique. What actually happens on the server when an address does not exist, who absorbs the cost, and why the distinction is worth caring about.
There is a habit of treating "temporary email" and "fake email" as the same trick with different branding. They are opposites. One is a working mailbox with a short life. The other is a string that looks like an address and belongs to nobody.
What actually happens when you invent an address
Type asdf@asdf.com into a signup form and a specific, well-defined sequence follows.
- The form checks the *shape* of the string. It has a local part, an at sign, and a domain, so it passes. Most validation stops here.
- The service accepts the signup and queues a verification email.
- Its mail server looks up MX records for the domain. Either none exist, or they point at a server that has never heard of that mailbox.
- The message bounces, or is accepted and then silently discarded.
- Your account sits in the database, permanently unverified, and you never receive anything.
You have not protected your privacy. You have created a broken record and, in most cases, an account you cannot use — because the feature you wanted was behind the verification link that had nowhere to go.
Who pays for it
Bounces are not free. High bounce rates damage a sender's reputation with the major mailbox providers, which degrades delivery for every other message they send, including messages to people who did want them.
If the domain you invented happens to be real, the cost lands on a third party. There are people who registered short, plausible-looking domains and now absorb a permanent stream of misdirected verification mail from strangers who never thought about where it would go.
None of that is catastrophic. It is just entirely pointless: real cost imposed, zero privacy gained.
The comparison
| Temporary address | Invented address | |
|---|---|---|
| Does the mailbox exist | Yes, for about an hour | No |
| Can you receive the verification | Yes | No |
| Does the account work | Yes | Usually not |
| What the sender experiences | Normal delivery, then a dead address | An immediate bounce |
| Who absorbs the cost | Nobody | The sender, or a domain owner who never asked |
| Privacy gained | Your real address stays out of the database | Same, but nothing works |
The last two rows are the whole argument. Both keep your real address out of the database. Only one of them leaves you with a working signup.
The grey area worth naming
There is a middle case: real, existing domains used as throwaways. These are worse than invented addresses, because the mailbox usually *does* exist and belongs to a real person. Your verification mail, your reset link, and eventually your order confirmations all arrive in a stranger's inbox.
Some of those addresses are famously flooded, to the point where the owners cannot use them. That is a small, real harm to an identifiable person, done for no benefit at all.
Where "fake" is a fair description
To be even-handed: a temporary address *is* fake in one sense. It is not a durable way to reach you, and a service that asked for a contact address did not get one.
That is a reasonable thing for a service to object to, and it is why disposable domains get blocked. The honest position is not "temporary addresses are always legitimate". It is:
- Legitimate: declining to hand a permanent channel to a form that only needs to send you one file.
- Not legitimate: using one to dodge a ban, a trial limit, or a one-account-per-person rule, which is outside acceptable use here as well as a breach of the service's terms.
- Simply broken: inventing an address that cannot receive anything.
What to do instead of inventing one
If your reason for typing nonsense is not wanting more mail, the tool you want is one of these:
- A disposable inbox when you need to receive one message and then disappear.
- An alias when you might want mail later but reserve the right to cut it off. The comparison is here.
- Your real address when the account will ever matter.
All three work. Inventing an address is the only option on the list that fails at the thing you were trying to do.
FAQ
Is using a fake email address illegal?
Generally not in itself. It breaches the terms of most services, and it becomes a serious matter when combined with fraud, evading a ban, or misrepresenting who you are.
Why do forms accept an address that does not exist?
Most validation checks the format only. Confirming that a mailbox really exists requires a live lookup, which is slow and unreliable, so services usually send the message and treat the bounce as the answer.
What happens to my account if the verification bounces?
It typically stays unverified. Many services restrict unverified accounts and delete them after a period, so you end up with neither the feature nor the account.
Is a documentation domain safe to use as a throwaway?
Domains reserved by standards for documentation harm no individual, which is better than picking one at random. They still cannot receive mail, so you are left with a broken signup.
Do services detect temporary addresses the same way as fake ones?
No, the mechanisms differ. Invented addresses are caught by the bounce after the fact. Disposable domains are caught before acceptance, by matching against maintained block lists.