How to use multiple domain addresses from one Gmail inbox

Quick answer for multiple domain emails one gmail inbox

Map aliases on each domain to the same Gmail destination. Cut leftover MX on each zone. Probe each printed name from another mailbox. That is multiple domain emails one Gmail inbox as receive.

Custom domain Gmail does not merge DNS. Email forwarding to Gmail is per MX. A pretty inbox does not fix the second zone’s leftover host.

Gmail send as needs a paid identity per From you will use. hello@brand-a and hello@brand-b are two identities, usually two credentials or at least two approved Froms.

Free: one domain, ten aliases. Starter and up raise domain counts. Confirm /pricing. Agency exists for many client zones.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

custom domain gmail: the real decision

People add a second domain in the dashboard and forget DNS on that zone.

Personal .me and company .com share Gmail and share one leftover Google MX story.

Send-as on brand A, receive-only on brand B, both expected to reply branded.

Criteria: per-zone MX, per-zone probe, per-From send-as decision.

Technical mail flow for multiple domain emails one gmail inbox

Each sender looks up that domain’s MX, not your Gmail MX. Copies converge at Gmail because you mapped destinations there.

Filters in Gmail can sort by To: if you bother. That is client-side.

Self-send lies per zone the same way.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP or POP, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

gmail send as

Finish domain one in production before you add domain two. Parallel leftovers are how people quit.

1. Cut and probe domain one.
2. Add domain two on a plan that allows it.
3. Recreate that zone’s printed names.
4. Publish that zone’s MX. Delete its leftovers.
5. Probe those names.
6. Attach send-as only for Froms you will use.
7. Keep unknowns held per zone.
8. Review each zone quarterly.

Failure modes and proof

Second zone still on registrar forward.

One SMTP password for every brand.

Free plan, two domains expected.

Self-send on zone two.

Catch-all on every zone into one Gmail.

MailerZ workflow and product boundary

Paid plans add domain ceilings so one Gmail can sit behind several zones. We still require leftover cuts per zone. Not IMAP. Not a suite.

Agency is for client books, not for skipping names.

Related pages: email forwarding, send and reply, compare Google Workspace, and docs.

email forwarding to gmail

Do not buy Workspace seats to get a second domain identity. Buy domain capacity on a forwarder if Gmail is the store. Confirm pricing.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Label Gmail filters by To: address if two brands would confuse you.

Do not use one hello@ list copied blindly if the printed names differ.

Personal domain plus company domain: keep unknown hold on the personal zone especially.

When you sell a brand, remap that zone’s destination or delete MX. Do not leave it pouring into your Gmail.

WHOIS privacy on a personal domain is unrelated to MX.

Two zones can share a destination and still need two SPF/DKIM stories if both send.

A parked domain with leftover MX is a surprise inbox. Audit it.

Do not CNAME one domain’s mail to the other. Publish MX as documented.

Contractors should not receive every brand in their personal Gmail unless you meant that remap.

Document domain count versus plan before a sales call.

Longer operator notes

A two-brand week that does not collide

Finish brand A: aliases, MX cut, external probe, optional send-as. Only then add brand B on a plan that includes another domain. Recreate B’s printed names. Cut B’s leftovers. Probe B. Do not copy A’s MX hosts onto B without looking at B’s NS. Do not assume A’s leftover story is B’s.

Free is one domain. If you expected two zones on Free, read pricing before you promise a client. Starter and above raise domain counts. Agency is for many client zones. Confirm the live card.

Gmail filters on To: keep two brands from blurring. That is optional hygiene. It is not MX.

When a brand leaves

Remap or delete that zone’s MX. Revoke that zone’s SMTP. Do not leave a sold brand pouring into your personal Gmail. That is how you read someone else’s customers and fail a handoff.

Shared destinations during a build must have an end date. Write it. Calendar it.

Personal .me plus company .com in one Gmail is fine if unknown hold stays strict on the personal zone. Catch-all forward on the personal domain is how your company inbox dies.

Send-as across brands

hello@A and hello@B are two Froms. Attach both in Gmail if you will use both. Separate credentials if a contractor only works on A. A leaked form on B should not send as A.

SPF and DKIM are per sending domain. Pretty records on A do not sign B.

Do not CNAME mail for B to A. Publish MX as documented for each zone.

Parked domains with leftover MX are surprise inboxes. Audit them when you audit the live brands. One hundred leftover records is a later article. Two brands is this one.

Contractors should not receive every brand unless you mapped that on purpose. Default to remap, not to infinite CC culture.

Document domain count versus plan before a sales call so you do not onboard zone three on a one-domain ceiling.

More operational detail

Inventory sheet for N domains

Columns: domain, NS vendor, leftover MX yes/no, printed aliases, destination Gmail, send-as yes/no, credential id, last probe date, unique subject. If a row is blank, that zone is not production. One Gmail does not fill blanks.

Plan ceilings: count domains before you promise. Free is one. Confirm pricing for the rest. Do not onboard domain three on a handshake.

Filters: To: contains @brand-a.com → label A. Same for B. Optional. Do not confuse labels with MX.

Offboard: remove MX, revoke SMTP, export the alias list, change the destination if required by contract. Calendar the date.

Parked zones: audit leftover MX even if you never printed hello@. Surprise inboxes are still your problem if NS is yours.

Personal plus company in one Gmail: hold unknowns on personal. Never catch-all-forward both into the same Primary.

Two send-as Froms in one Gmail: pick the From every time until defaults are set. Brand mixups are compose errors, not leftover MX.

When domain count grows, Agency is capacity. It is not a reason to skip the inventory sheet.

MailerZ Free remains one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm MailerZ pricing. Unauthorized send is 550 / 550 5.7.1. Leftover MX is a hard stop. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP or POP. Mail Box is portal webmail, not SOC 2, not ISO 27001, not HIPAA, not an inbox-placement promise.

A complete worked story

Two brands, one inbox, zero shared leftovers

Brand A is production: aliases, MX cut, probe, optional send-as. Brand B waits. Then B gets its own NS check, own leftover cut, own printed list, own probe. One Gmail destination is the only shared row. Multiple domain emails one Gmail inbox fails when people copy A’s “it works” onto B without looking at B’s lookup.

Inventory columns: domain, NS, leftover yes/no, aliases, destination, send-as, credential, last probe, unique subject. Blank row means not production. Free is one domain. Count before you promise. Confirm pricing. Agency is capacity for many zones, not a skip-the-sheet pass.

Filters on To: keep brands readable. Offboard removes MX and SMTP for a sold brand so it stops pouring into personal Gmail. Parked zones still get leftover audits. Personal plus company in one Gmail means hold unknowns on personal — never catch-all-forward both into Primary.

hello@A and hello@B are two Froms and two signing stories. A leaked form on B should not send as A. Do not CNAME mail for B to A. Do not share one SMTP password across brands. When domain count grows, update the sheet first, the plan second, DNS third.

Contractors receive a brand only if you mapped it. Default to remap at contract end. Shared build destinations have calendar end dates. One Gmail is convenient. Convenience is how tenant mixups start if you skip the sheet.

Operator brief

A longer operator brief for multiple domain emails one gmail inbox

Teams that bookmark How to Use Multiple Domain Addresses From One Gmail Inbox usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about multiple domain emails one gmail inbox as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is Mail Box portal webmail, not IMAP, not POP, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening multiple domain emails one gmail inbox. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for how to use multiple domain addresses from one gmail inbox. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear multiple domain emails one gmail inbox works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep multiple domain emails one gmail inbox per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When How to Use Multiple Domain Addresses From One Gmail Inbox is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how multiple domain emails one gmail inbox stays a runbook instead of an incident.

A second worked pass for multiple domain emails one gmail inbox: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a multiple domain emails one gmail inbox mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

The From picker is where multi-domain send-as actually breaks

How to use multiple domain addresses from one Gmail inbox is easy on inbound and sloppy on outbound. Gmail will happily hold five Send mail as identities. The human still has to pick From. Brand A’s quote going out as hello@brand-b.com is not leftover MX. It is a compose error. Set a default only if you accept that default on every reply. Otherwise train the habit: look at From before Send.

Each From is its own SMTP pair and its own DKIM story. Do not CNAME mail for Brand B to Brand A. Do not share one MailerZ secret across brands so a leaked form on B can send as A. Free is one domain and SMTP Off. The second domain needs a plan that includes another domain slot and send-as On. Solo is $40 per year for five domains. Starter is $8 or $80 for eight. Confirm pricing before you promise Brand C on a handshake.

Filters on To: keep inbound readable. They do not fix a wrong From. Labels are not MX. Offboard a sold brand by removing its MX, revoking its SMTP user, and deleting its Send mail as identity so Gmail stops offering a dead From. Parked zones still get leftover MX audits even if you never printed hello@. Surprise inboxes are your problem if you operate the nameservers.

Prove each zone with a unique subject from another mailbox before you add the next From. Exclusive MailerZ MX. Leftover hosts gone. Two public views. Related: email forwarding and send and reply. One Gmail is convenient. Convenience is how tenant mixups start if the inventory sheet is blank.

FAQ

What is the safest way to handle multiple domain emails one gmail inbox?

Map each domain’s named aliases to the same Gmail, cut leftover MX on every zone, and probe each printed name from another mailbox. Free supports one domain. Paid plans add domain capacity. Send-as is per approved From.

Does this require a new mailbox?

No. One Gmail can be the destination for several domains.

Will it work with Gmail or Outlook?

Yes. This page uses Gmail as the shared store.

What DNS records are involved?

Per-domain MX, verify TXT, leftover removal, and sending records per domain that sends.

What should I test before production?

An external probe to each printed address on each domain. Self-send is invalid on every zone.

Key takeaways

• One Gmail, many MX cuts.
• Free is one domain.
• Probe each zone.
• Send-as per From.
• No shared leftover.
• Hold unknowns per zone.
• Remap when a brand leaves.
• Confirm pricing ceilings.

Conclusion and next action

Use one Gmail for many domains only after each zone has an honest MX set and a real probe.

Start free on the first domain. Sign in when you add the second — check the plan’s domain ceiling first. Keep an inventory sheet so a convenient shared inbox does not become a mix of leftover MX stories you can no longer name.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.