Before you share the address
Pause at the point where an attacker knows the email used to reset several valuable accounts. Ask whether the relationship is temporary, whether recovery matters and what would happen if the address became public.
The checklist
- Keep it off public forms
- Protect it strongly
- Store backup codes
- Test recovery annually
Write down the purpose beside the credential. A label is small operational memory: it prevents a random-looking address becoming another mystery.
After the first message arrives
Confirm that the route works, that replies behave as expected and that important mail is not being forwarded somewhere unsafe. If the relationship grows, extend the lifetime before it becomes urgent.
Review without over-managing
Reserve a durable, strongly protected address for recovery and high-consequence services. Review on change—not every day. A hidden address still needs a unique password, strong MFA and monitored access.
Give the next relationship its own route.
Create an MXDuck alias