Picture a small online shop whose contact address, hello@example.com, sits in the website footer and the social media bio. That same address is also the login for the social accounts, the order and shipping tools, and the payment dashboard. Every important system points at an address the whole internet can see.
Executive Summary
- Keep one public address for customers. Use different, unpublished addresses for logins, and give payments, domain and email-admin accounts a dedicated mailbox.
- Separation limits who knows your login addresses, and per-service aliases can hint at where spam began. It does not replace unique passwords or multi-factor authentication.
- Move one critical account at a time, confirm the new address receives mail, then retire the old login.
Quick Answer: No, do not use one address for everything. Publish one address for customer contact and use private addresses for logins, with payments, domain and email admin on a dedicated mailbox. Aliases are enough for low-risk tools, but forwarding to one inbox does not separate who can read it. Send domain and email recovery to an address outside your domain, so it still works if your domain's mail stops.
Table of contents
What Separating Addresses Does and Does Not Do
Splitting addresses gives you two practical benefits. First, fewer people and systems learn which address you sign in with. A public contact address is easy to find, so using it as a login name hands over half of the sign-in to anyone who looks. Second, if each service gets its own alias, the alias that starts receiving junk can point to where it was shared. That is a clue, not proof, because addresses can also leak through other routes.
Separation does not stop password guessing, phishing or a stolen session. The FTC's small business cybersecurity guidance advises against reusing passwords, and CISA's Secure Our World tip sheet on staying safe online says to use multi-factor authentication on any site that offers it. Treat address separation as one layer on top of those habits.
A note on password changes: NIST SP 800-63B-4, the final revision published in July 2025, says the services that verify passwords must not require users to change them on a schedule, but must force a change when there is evidence of compromise. It is written as digital identity guidance for organizations that run authentication systems, including federal agencies, so it is not a rule for your own shop's accounts. It does point the same way as this guide: use a unique password for every account, and change one right away if you suspect it is exposed.
Four Uses, Four Kinds of Address
Sort your accounts into four groups, then choose the lightest option that keeps the right people out of the wrong mail.
| Use | Publish it? | Who needs access | Is an alias enough? | When a separate mailbox fits |
|---|---|---|---|---|
| Public contact desk | Yes: website, listings, social bio | Whoever answers customers | Yes, if the person reading it already has inbox access | When a support team shares it and should not see admin mail |
| Social media and ads | No | Marketing owner, plus any agency or contractor | Yes, one alias per platform, if the destination inbox already has the right access boundaries | When several people must receive platform notices, or when reset messages and sensitive notices must stay away from users of a shared inbox |
| Business tools: shop admin, shipping, accounting, help desk | No | Owner and trusted managers | Yes, one alias per tool, if the destination inbox already has the right access boundaries | When more than one person needs its notices or reset links, when staff change, or when reset messages and sensitive notices must stay away from users of a shared inbox |
| Payments and critical admin: payment dashboard, bank, domain registrar, email admin | Never | Owner and one named backup | Not on its own | Yes: a dedicated mailbox with its own password and multi-factor authentication |
Forwarding does not separate access. An alias or forwarder delivers mail to an inbox that already exists. Whoever can open that inbox can read every message sent to every alias, including password-reset links. Aliases separate the address you share, not the people who can read the mail. If an account needs its own readers, it needs its own mailbox.
Where Recovery Messages Should Go
Account recovery has a trap: the reset email can depend on the very thing you are trying to recover. If your domain registrar sends reset messages to you@yourdomain.com and mail on that domain stops because of a DNS mistake, an outage or a lapsed renewal, you cannot receive the message that would let you fix it.
For domain and email-admin accounts, choose a recovery address outside your domain, at a provider that stays reachable if your domain's mail goes down. Google follows the same logic: its Workspace documentation describes a secondary recovery address outside the domain used for the account. Keep that recovery mailbox unpublished, give it a unique password and multi-factor authentication, and test every few months that it still receives mail.
A Checklist for Moving Off One Address
Do not change everything in one afternoon. Work from the highest-risk accounts down, and change a login address only after you know the new one can receive mail.
- List what uses the old address. Search the inbox for welcome, verification, receipt and password-reset messages, and check your password manager. Note each service, its owner and its login address.
- Decide the roles. Choose the public address, a private address or alias for each group in the table, and a dedicated mailbox for payments and critical admin.
- Separate the three address roles. For each service, note its sign-in ID, its notification address and its recovery address, which may be three fields or one. Check which of them the service lets you change before you migrate. Work from payments, bank, domain registrar and email admin first, then social and ads, then everyday tools.
- Read each service's change steps. Procedures differ, and some services ask you to confirm from both the old and new address. Keep the old address accessible during the change, and edit only the fields the service allows.
- Prove it works. Verify sign-in with the current ID, or with the new ID if it changed. Then confirm that each supported verification and notification message reaches its configured destination, and check spam. Do not move on until each one does.
- Reset recovery options. Where the service supports a separate recovery address, set it before you test recovery. For domain registrar and email-admin accounts, use an address outside your business domain. Where testing is supported, verify recovery at the final configured destination. Store backup codes safely, and turn on multi-factor authentication if it is off.
- Retire the old login, not the old mailbox. Stop using hello@ as a sign-in ID only after a replacement ID has been confirmed. Keep hello@ active as your public contact address, including after the login change, and keep reading it for a few weeks to catch notices you missed.
- Record who has access. Keep a short list of addresses, owners and recovery routes, and review it when someone joins or leaves.
Each login still needs its own strong, unique password and multi-factor authentication. A new address does not replace either.
What to Do After a Breach Notice
First confirm the notice is real. Scammers send fake alerts, so do not click its links. As the FTC advises about phishing, contact the company through a website or phone number you already know is genuine.
If only your email address was exposed
Read the notice to see what was taken. If it lists only email addresses, expect more phishing aimed at that address and be wary of messages that mention the service. If you gave that service its own alias, you can stop using or filter that alias while your other addresses stay untouched. A public address such as hello@ cannot be retired that easily.
If credentials or an account may be compromised
Treat it as an incident. From the service's official site, set a new unique password and sign out of all devices. Turn on multi-factor authentication, check that the recovery email and phone are yours, and delete any forwarding rules you did not create. These steps follow the FTC's guide to recovering a hacked email or social media account. If you reused that password elsewhere, change it there too, starting with email and payments. This is the compromise-triggered change NIST describes, and it differs from routine rotation.
Key takeaway: Publish one address for customers, give logins private addresses or aliases, and put payments, domain and email admin on a dedicated mailbox with recovery outside your domain. Separate addresses support unique passwords and multi-factor authentication. They do not replace them.
Once you have decided which addresses stay public and which stay private, you need mailboxes on your own domain to hold them. Z.com US's Unlimited Email Hosting lets you create addresses on your domain, and its plan page says the only limit on accounts is your plan's total storage. That leaves room to keep hello@ for customers and give your payment and admin logins mailboxes of their own, with recovery pointed outside your domain. Compare the plans and storage options on the product page.
See Unlimited Email Hosting plans