[{"data":1,"prerenderedAt":293},["ShallowReactive",2],{"\u002Fblog\u002Fsend-email-from-multiple-domains":3,"\u002Fblog\u002Fsend-email-from-multiple-domains-surround":284},{"id":4,"title":5,"authors":6,"badge":11,"body":13,"date":273,"description":274,"extension":275,"image":276,"meta":278,"navigation":279,"path":280,"seo":281,"stem":282,"__hash__":283},"posts\u002Fblog\u002Fsend-email-from-multiple-domains.md","Send Email From Multiple Domains: The Four Routes",[7],{"name":8,"avatar":9},"Mailyond Team",{"src":10},"\u002Fimages\u002Flogo.png",{"label":12},"Guide",{"type":14,"value":15,"toc":262},"minimark",[16,25,30,33,40,46,52,56,59,62,99,102,106,109,174,177,184,187,191,194,201,205,208,216,220,223,226,233,251,255],[17,18,19,20,24],"p",{},"One domain is a solved problem. You point some records at a provider, mail goes out, life continues. The moment you want to send email from multiple domains, the job changes shape, and not in the way people expect. It is rarely harder to send the message. What gets harder is everything around it: each domain needs its own authentication, most providers count domains rather than messages when they decide what to charge you, and the address you send ",[21,22,23],"em",{},"as"," stops being obvious. There are four routes people actually take, and each breaks somewhere different. Here is what each one does in 2026, with plan limits checked against vendor documentation on 25 August 2026.",[26,27,29],"h2",{"id":28},"what-changes-when-you-send-email-from-multiple-domains","What changes when you send email from multiple domains",[17,31,32],{},"Three things multiply, and only one of them is technical.",[17,34,35,39],{},[36,37,38],"strong",{},"Authentication is per domain, with no bulk path."," A receiving server decides whether to trust a message by checking records published on the domain in the From line. That means DKIM, a return path, and usually an SPF entry, published on every domain you send from, verified separately. Five domains is five passes through that flow, in whichever registrar each one happens to live at.",[17,41,42,45],{},[36,43,44],{},"Plan limits count domains, not volume."," This surprises people running tiny volumes. A side project sending 200 emails a month across four domains hits a paid tier long before a single-domain app sending 40,000 does.",[17,47,48,51],{},[36,49,50],{},"Identity gets ambiguous."," With one domain, the From address is whatever your account is. With six, every message has to go out as the right one, and every reply has to come back as the right one. This is the part that gets skipped at setup and discovered later, usually by a customer who says they never heard back.",[26,53,55],{"id":54},"route-1-one-mailbox-host-several-domains-on-one-account","Route 1: one mailbox host, several domains on one account",[17,57,58],{},"This is what most people mean when they search for it, and it is the route the Microsoft and Zoho community threads are full of. You have a mailbox provider already, you bought a second domain, and you want to send from it without starting over.",[17,60,61],{},"All three major hosts support it, with different shapes:",[63,64,65,82,93],"ul",{},[66,67,68,71,72,75,76,81],"li",{},[36,69,70],{},"Google Workspace"," lets an account hold up to 600 domains, and up to 20 of those can be domain aliases. Worth knowing before you plan around it: in the Admin console you can only add a domain alias to your ",[21,73,74],{},"primary"," domain, and secondary domain aliases need the Directory API. Billing is per user, so the domains are free and the people are not. The full math is in ",[77,78,80],"a",{"href":79},"\u002Fblog\u002Fgoogle-workspace-multiple-domains-pricing","Google Workspace multiple domains pricing",".",[66,83,84,87,88,92],{},[36,85,86],{},"Microsoft 365"," wants the domain added and verified in the tenant first, after which you add an alias on the existing user, and no extra licence is needed if all the mail lands in the same mailbox. Sending as that alias is a separate switch that has to be turned on in the Exchange admin centre before Outlook will offer it, which is why so many threads end with a ",[89,90,91],"code",{},"551 5.5.1 Unable to relay non-accepted domain"," error and a confused admin.",[66,94,95,98],{},[36,96,97],{},"Zoho Mail"," allows around 30 aliases on a single licence spread across any number of verified domains, all sharing one mailbox and one login.",[17,100,101],{},"The pattern is the same everywhere. Domains are cheap or free to add, and the aliases share a mailbox, which is fine at two domains and gets muddy at six. Everything arrives in one pile with no reliable sense of which brand it belongs to, and sending as the right alias becomes a dropdown you have to remember to change. It also does nothing for app-generated mail, which is a different problem with a different answer.",[26,103,105],{"id":104},"route-2-a-send-api-with-several-verified-domains","Route 2: a send API with several verified domains",[17,107,108],{},"If the mail comes from your application rather than a person, you want a sending API, and here the domain count is the thing to read on the pricing page.",[110,111,112,128],"table",{},[113,114,115],"thead",{},[116,117,118,122,125],"tr",{},[119,120,121],"th",{},"Provider",[119,123,124],{},"Domains included",[119,126,127],{},"Price",[129,130,131,148,163],"tbody",{},[116,132,133,142,145],{},[134,135,136],"td",{},[77,137,141],{"href":138,"rel":139},"https:\u002F\u002Fresend.com\u002Fpricing",[140],"nofollow","Resend",[134,143,144],{},"3 on Free (3,000 emails \u002F mo), 10 on Pro",[134,146,147],{},"$0 \u002F $20 per mo",[116,149,150,157,160],{},[134,151,152],{},[77,153,156],{"href":154,"rel":155},"https:\u002F\u002Fpostmarkapp.com\u002Fpricing",[140],"Postmark",[134,158,159],{},"10 on Free, but only 100 emails \u002F mo. 5 on Basic",[134,161,162],{},"$0 \u002F $15 per mo",[116,164,165,168,171],{},[134,166,167],{},"Mailgun",[134,169,170],{},"1 on Free and on Basic, 1,000 on Foundation",[134,172,173],{},"$15 \u002F $35 per mo",[17,175,176],{},"Resend raised its free tier to three verified domains, which quietly removed the single-domain wall a lot of older comparison posts still describe, so check the current number rather than a blog from last year. Postmark's free tier is the inverse trap: generous on domains, useless on volume at 100 messages a month. Mailgun is the one to watch, because its $15 Basic plan still allows one custom domain, meaning the multi-domain step there is $35 rather than $15.",[17,178,179,180,81],{},"The honest caveat: if you genuinely send tens of thousands of messages, these plans are good value and the per-domain framing stops mattering. It only bites at low volume across several domains. We worked that comparison out properly in ",[77,181,183],{"href":182},"\u002Fblog\u002Ftransactional-email-for-multiple-domains","transactional email for multiple domains",[17,185,186],{},"What no send API gives you is a place for replies to land. They are one-directional by design, and customers reply to receipts anyway.",[26,188,190],{"id":189},"route-3-cloudflare-if-your-nameservers-are-already-there","Route 3: Cloudflare, if your nameservers are already there",[17,192,193],{},"Cloudflare Email Routing has always received mail and never sent it. Cloudflare Email Service closes that half, and per-domain sending works if your domains use Cloudflare nameservers and you are on a Workers Paid plan at $5 a month. For a developer whose domains all sit there anyway, it is a genuinely cheap way to send from all of them.",[17,195,196,197,81],{},"The catches are the nameserver requirement, the per-domain onboarding that still applies to each one, and the fact that you are building the sending layer rather than buying it. We went through the whole setup, its limits and its costs in ",[77,198,200],{"href":199},"\u002Fblog\u002Fcloudflare-email-routing-send-email","Cloudflare Email Routing send email",[26,202,204],{"id":203},"route-4-forwarding-plus-send-as-which-is-the-one-that-breaks","Route 4: forwarding plus send-as, which is the one that breaks",[17,206,207],{},"Free forwarding into personal Gmail, then Gmail's \"Send mail as\" to reply, is the setup almost everyone tries first because it costs nothing. It stopped working properly in 2024.",[17,209,210,211,215],{},"Google, Microsoft and Yahoo began enforcing sender requirements that year, and a message sent through Gmail's SMTP claiming to be from your domain fails DMARC alignment for that domain. Sometimes it is filtered, sometimes it bounces, and from your side it looks sent either way. That is the worst failure mode available: silent. If this is the setup you are on, ",[77,212,214],{"href":213},"\u002Fblog\u002Freply-to-email-from-custom-domain","how to reply to email from a custom domain"," covers exactly why it fails and what actually fixes it.",[26,217,219],{"id":218},"where-mailyond-fits","Where Mailyond fits",[17,221,222],{},"Every route above answers half the question. Mailbox hosts let you send as several domains but bill per person and give you one undifferentiated pile of mail. Send APIs handle the application half cleanly and have nowhere for replies to go. Cloudflare handles sending if your nameservers cooperate. Forwarding fails DMARC.",[17,224,225],{},"Mailyond is built for the case where those halves are the same job: a handful of domains, modest volume on each, and mail that goes both ways. Connecting a domain is one 5-minute DNS setup with three records, a DKIM TXT, a Return-Path CNAME and an MX, and that single setup makes the domain both send and receive. Your DNS stays where it is, with no nameserver move.",[17,227,228,229,232],{},"After that, the API sends from any connected domain with one key, and it is Resend-wire-compatible on purpose, so an existing Resend SDK works by changing the endpoint and dropping in a ",[89,230,231],{},"myond_…"," key. Mail to every connected domain lands in one inbox tagged by domain, and the reply button sends authenticated as the address the message arrived at, so answers pass DMARC. Pricing counts bundles of domains rather than seats or domains: $10 a month for five domains, $40 for thirty, sends and receives drawn from one allowance.",[17,234,235,236,240,241,245,246,250],{},"Where we are not the answer: high sending volume, where Resend or Postmark are priced better for exactly that, and full mailbox suites with calendars and docs, where ",[77,237,239],{"href":238},"\u002Fblog\u002Femail-hosting-for-multiple-domains","email hosting for multiple domains"," covers the real options. Plans are on the ",[77,242,244],{"href":243},"\u002F#pricing","pricing"," page and there are ",[77,247,249],{"href":248},"\u002Fsignup","7 days free"," to try it against your own domains.",[26,252,254],{"id":253},"the-short-version","The short version",[17,256,257,258,261],{},"To send email from multiple domains you pick one of four routes: aliases on a mailbox host, a sending API, Cloudflare if your nameservers live there, or forwarding plus send-as, which fails DMARC and should be retired. Whichever you choose, every domain still needs its own authentication records, and most providers price by domain count rather than volume, so the second domain is what moves you up a tier. The question all four leave open is where the replies land and who they go out as. If you want sending and receiving on several domains to be one setup and one bill, that seam is what ",[77,259,260],{"href":248},"Mailyond"," was built for.",{"title":263,"searchDepth":264,"depth":264,"links":265},"",2,[266,267,268,269,270,271,272],{"id":28,"depth":264,"text":29},{"id":54,"depth":264,"text":55},{"id":104,"depth":264,"text":105},{"id":189,"depth":264,"text":190},{"id":203,"depth":264,"text":204},{"id":218,"depth":264,"text":219},{"id":253,"depth":264,"text":254},"2026-08-25","Send email from multiple domains without a separate stack per domain. The four real routes in 2026, what each one costs, and where each one quietly breaks.","md",{"src":277},"https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F4348401\u002Fpexels-photo-4348401.jpeg?auto=compress&cs=tinysrgb&h=650&w=940",{},true,"\u002Fblog\u002Fsend-email-from-multiple-domains",{"title":5,"description":274},"blog\u002Fsend-email-from-multiple-domains","jZb4YpV2QgygQn5_YAPjNpiK8yctZ1gHpikg2BUdB6M",[285,289],{"title":286,"path":213,"stem":287,"description":288,"children":-1},"How to Reply to Email From a Custom Domain","blog\u002Freply-to-email-from-custom-domain","How to reply to email from a custom domain without landing in spam: why it breaks, the workarounds that fail, and how to reply from every domain you own.",{"title":290,"path":182,"stem":291,"description":292,"children":-1},"Transactional Email for Multiple Domains: Where It Breaks","blog\u002Ftransactional-email-for-multiple-domains","Transactional email for multiple domains is priced by domain count, not volume. What Resend, Postmark, Mailgun and Mailyond really cost across five domains.",1787641796635]