Minutes 1–3: find the routes

Search your password manager and inbox for the accounts connected to this area. Note which ones use a private account address, which have a public contact alias, and which no longer have a clear owner or purpose.

Minutes 4–6: find the weak link

A visible address is scraped, copied and retained far beyond its original page. Look first for public addresses used for recovery, temporary routes attached to durable accounts, reused passwords and aliases that receive unrelated mail.

Minutes 7–9: make one repair

  • Publish a dedicated route
  • State useful contact boundaries
  • Check reply identity
  • Replace it when abuse wins

Choose the highest-consequence problem, not the longest list. Confirm the replacement before disabling anything.

Minute 10: leave a note

Treat public contact as infrastructure designed to absorb exposure. Record what changed and set the next review for a natural event. Reply behaviour can expose an underlying address if the service does not preserve the alias.

A ten-minute audit is successful when tomorrow is simpler.

Give the next relationship its own route.

Create an MXDuck alias