One address per service turns every signup into a switch you can turn off, and every leak into a named suspect. The idea is simple: instead of handing your real address to every shop, forum, and newsletter, you hand each one a different forwarding address that delivers to your real inbox. When one sender gets noisy, you silence that alias without touching anything else. When spam arrives on an alias you gave to exactly one company, you know where it escaped from.
The Three Kinds of Alias
| Type | How it works | Weakness |
|---|---|---|
| Plus addressing | Your address with a tag, like you+shop@example.com | Anyone can strip the tag and reach your real address |
| Forwarding alias | A separate address that forwards to your inbox | Depends on the alias provider staying in business |
| Catch-all domain | Any address at your domain delivers to you | Accepts everything, including dictionary spam |
Plus addressing is free and built into Gmail and many other providers, but it is not private: the tag is visible, and removing it reveals the real address. A forwarding alias from a service like SimpleLogin, Fastmail, or Apple’s Hide My Email hides the real address properly, because the sender never sees it. A catch-all on your own domain is the most flexible option, since any address you invent on the spot already works, but it also accepts mail to addresses you never created, which invites spray-and-pray spam.
A Naming Scheme That Survives
The scheme matters less than its consistency. Pick one pattern and use it everywhere, so you can reconstruct an alias from memory when a service asks you to confirm it. Workable patterns include the service name plus a fixed word (shopname-shop@yourdomain), or a short code for the category (shopname-shopping@yourdomain). Avoid putting your real name or birth year in aliases; the point is that a leaked alias reveals nothing about you beyond the service that received it.
Keep a list. A password manager’s notes field works, or a simple note with two columns: service and alias. The list is what makes the system useful a year later, when a breach notice arrives and you need to know which alias to kill.
One more habit makes the scheme practical: decide, for each alias, whether replies matter. A forwarding alias can usually reply through the alias address, so the service never learns the real inbox. That matters for support threads and order problems, where the reply chain is the record. If replies do not matter — a newsletter, a download link — a receive-only alias is enough, and there is no reply path to protect.
Tracing a Leak
When spam arrives on an alias, the alias is the evidence. If the alias went to one service only, that service leaked it, sold it, or was breached. Check the service’s breach history first, then decide: if the service still matters to you, replace the alias with a fresh one and update the account; if it does not, disable the alias and let future mail to it bounce into nothing.
This is the one investigation most people never run, and it is the one that turns spam from a mystery into a fact. A real inbox address gives you no such trail: spam there could have come from anywhere, and every suspect is equally likely.
Killing a Noisy Alias
Disabling an alias is the whole payoff. The sender keeps sending, and the mail stops arriving, with no unsubscribe link to click and no confirmation trap to dodge. That matters because some unsubscribe links confirm an address is live, which is why the trap exists at all: clicking tells the sender a human reads the mail. An alias kill avoids the question entirely.
Before killing an alias tied to an account you still use, move the account first. Change the account’s address to a new alias, confirm the change lands, and only then disable the old one. Password resets, order confirmations, and security alerts all travel through that address, and disabling it before the move locks you out of exactly the messages you need.
What Aliases Do Not Do
Aliases hide your address, not your activity. They do not encrypt message content, hide your IP address, or protect data already held by the service you signed up with. A breach at that service still exposes whatever you gave it; the alias only stops the exposure from spreading to your real inbox and to every other service. Treat aliases as address hygiene, not as anonymity, and they will do the job they are built for.
Final Verdict
One address per service is the cheapest structural fix in email: it costs minutes to set up, it converts spam from a flood into a set of individual switches, and it hands you evidence when something leaks. Start with the ten noisiest senders, give each a fresh alias, and disable the old shared address for those senders. The inbox will not become empty, but it will become legible — and a legible inbox is one you can actually control.
