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

Pair a per-service alias with a unique password or passkey. 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 retailer leaks credentials that attackers try on unrelated accounts. 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

Aliases complement strong authentication; they do not replace it.

  • Generate unique passwords
  • Store the matching alias
  • Enable strong MFA
  • Update both after a breach

Give the next relationship its own route.

Create an MXDuck alias