The five myths
- It makes you anonymous
- It stops every phishing message
- It removes the need for strong authentication
- Every address should be temporary
- More addresses always mean more confusion
What is actually true
Use the receiving alias as one clue and verify important requests through a known route. That can reduce correlation, improve context and make one exposed relationship easier to replace. It is a control surface, not an invisibility cloak.
Why the distinction matters
A supposed bank warning arrives at an address used only for shopping. The address can tell you which relationship is involved, but it cannot certify the sender or erase information shared elsewhere.
Good tools solve a named problem. Myths ask them to solve every problem.
Use the modest superpower
A message sent to the correct alias can still be fraudulent after a breach.
- Check the receiving address
- Ignore urgency
- Open the service directly
- Report suspicious messages
Give the next relationship its own route.
Create an MXDuck alias