[{"data":1,"prerenderedAt":2348},["ShallowReactive",2],{"blog":3,"\u002Fblog":16},{"id":4,"title":5,"body":6,"description":7,"extension":8,"meta":9,"navigation":10,"path":12,"seo":13,"stem":14,"__hash__":15},"blog\u002Fblog.yml","Mailyond Blog",null,"Tips and guides on managing support and transactional email across multiple domains.","yml",{},{"icon":11},"i-lucide-newspaper","\u002Fblog",{"title":5,"description":7},"blog","_-kBpAC5HvDiru7QMgYorAQYc_NfvG5T33xFFJOH9m8",[17,224,465,871,1093,1445,1749,2065],{"id":18,"title":19,"authors":20,"badge":25,"body":27,"date":213,"description":214,"extension":215,"image":216,"meta":218,"navigation":219,"path":220,"seo":221,"stem":222,"__hash__":223},"posts\u002Fblog\u002Femail-hosting-for-multiple-domains.md","Email Hosting for Multiple Domains Without Per-Seat Fees",[21],{"name":22,"avatar":23},"Mailyond Team",{"src":24},"\u002Fimages\u002Flogo.png",{"label":26},"Guide",{"type":28,"value":29,"toc":203},"minimark",[30,43,48,51,60,63,67,70,77,88,94,100,103,107,110,125,128,132,135,163,170,174,177,180,192,196],[31,32,33,34,38,39,42],"p",{},"If you own more than one domain, email hosting for multiple domains turns into a pricing problem before it turns into a technical one. You want a real mailbox on each domain, a ",[35,36,37],"code",{},"hello@"," or ",[35,40,41],{},"support@"," that sends and receives properly, but every mainstream provider was built to charge per user, per domain. Add a second brand and the meter runs again. This guide walks the actual options for multiple domain email hosting, what each one really costs, where it breaks, and how to end up with every domain in a single inbox instead of a stack of separate logins.",[44,45,47],"h2",{"id":46},"why-email-hosting-for-multiple-domains-gets-expensive","Why email hosting for multiple domains gets expensive",[31,49,50],{},"The mainstream email hosts price by the seat, and a seat is tied to a domain. That model is fine when you are one company with one domain and ten people. It is exactly backwards when you are one person with five domains and barely any inbound on most of them.",[31,52,53,54,59],{},"Google Workspace is the clearest example. A paid mailbox starts at around $7 per user per month on the annual Starter plan. You can bolt extra domains onto a single account as free aliases, but an alias is not a separate inbox, it is another address pointing at the same identity. The moment you want a genuinely separate mailbox for a second brand, that is another paid user seat. We did the full plan-by-plan breakdown in the ",[55,56,58],"a",{"href":57},"\u002Fblog\u002Fgoogle-workspace-multiple-domains-pricing","Google Workspace multiple domains pricing"," guide, and the short version is that five real inboxes means five seats, whether or not any of them get much mail.",[31,61,62],{},"Microsoft 365 and Zoho follow the same per-user shape. Zoho is cheaper per seat, but you are still provisioning and paying per mailbox as you add domains. None of these were designed for the person who keeps buying domains for projects that may or may not happen.",[44,64,66],{"id":65},"the-options-for-multiple-domain-email-hosting","The options for multiple domain email hosting",[31,68,69],{},"Here are the routes people actually take, roughly from cheapest to most complete, and where each one bites.",[31,71,72,76],{},[73,74,75],"strong",{},"Forward everything into one Gmail."," Point every domain at a single Gmail inbox with forwarding. Reading is solved instantly and it costs nothing. Replying is where it falls apart: hit reply and the message goes out as your personal Gmail, not the domain it arrived on. Gmail's \"Send mail as\" tries to patch this and is the exact setup that trips DMARC, which we cover below.",[31,78,79,82,83,87],{},[73,80,81],{},"Google Workspace aliases."," Add domains as aliases on one Workspace account and they all land in your one mailbox for free. It looks like multiple domain email hosting on a budget, but it is one identity, so you cannot cleanly separate brands, and getting the correct \"from\" to stick on a reply is its own fight. Real per-domain inboxes mean per-user billing again. If you are weighing this route, the ",[55,84,86],{"href":85},"\u002Fblog\u002Fgoogle-workspace-alternative-for-multiple-domains","Google Workspace alternative for multiple domains"," guide has the trade-offs.",[31,89,90,93],{},[73,91,92],{},"Microsoft 365 shared mailboxes."," If you already live in Microsoft, shared mailboxes let you create a mailbox per domain without a separate license as long as each stays under the size cap. It is the cheapest \"real inbox\" route on that stack, but each mailbox is accessed separately, so you are clicking between them rather than working from one place, and you are managing Exchange domain config per brand.",[31,95,96,99],{},[73,97,98],{},"Cloudflare Email Routing."," Free and fast at forwarding mail from every domain you point at it, and popular for exactly this reason. It also cannot send a reply at all, and its separate programmatic sending product is API-only with no inbox and no reply button. Neither half gives you a mailbox you can actually work from.",[31,101,102],{},"Every one of these either bills per seat or solves reading while quietly skipping the harder half.",[44,104,106],{"id":105},"the-catch-nobody-prices-in-replying-as-each-domain","The catch nobody prices in: replying as each domain",[31,108,109],{},"The reason cheap forwarding setups feel broken is not the forwarding. It is the reply.",[31,111,112,113,116,117,119,120,124],{},"When you answer an email that came to ",[35,114,115],{},"support@brand-b.com",", that reply has to leave from ",[35,118,115],{},", signed for that domain, or it lands in the customer's spam folder. Since 2024 the large mailbox providers enforce this hard: outbound mail that does not pass SPF, DKIM, and DMARC for the domain in the \"from\" line gets filtered or bounced. A forward-to-Gmail or alias setup reads every domain fine and then sends replies that fail this check, which is how you end up with a customer who swears they never heard back. We wrote the full explanation in ",[55,121,123],{"href":122},"\u002Fblog\u002Freply-to-email-from-custom-domain","how to reply to email from a custom domain",".",[31,126,127],{},"So real email hosting for multiple domains is two jobs at once: see every domain's mail in one place, and reply as each domain without it looking forged. Price a provider on both, not just the first.",[44,129,131],{"id":130},"what-to-look-for-in-multi-domain-email-hosting","What to look for in multi-domain email hosting",[31,133,134],{},"Strip it down and the checklist is short:",[136,137,138,145,151,157],"ul",{},[139,140,141,144],"li",{},[73,142,143],{},"One inbox"," that reads mail from every domain you own, tagged so you know which brand each message hit.",[139,146,147,150],{},[73,148,149],{},"Authenticated replies"," from the right domain, so answers arrive and show the correct \"from.\"",[139,152,153,156],{},[73,154,155],{},"Flat pricing"," that does not climb every time you add a domain you barely check.",[139,158,159,162],{},[73,160,161],{},"An API to send from your apps",", if any of those domains ship transactional mail like receipts or password resets.",[31,164,165,166,124],{},"Most setups give you one or two of these. The forwarding ones read but reply badly. The per-seat ones reply fine but bill per mailbox and split into separate inboxes. The gap is having all of it in one place without taping three tools together, and that gap widens with every domain you add. For a deeper look at that split, see ",[55,167,169],{"href":168},"\u002Fblog\u002Fone-inbox-for-multiple-domains","one inbox for multiple domains",[44,171,173],{"id":172},"where-mailyond-fits","Where Mailyond fits",[31,175,176],{},"Mailyond is built for the per-domain math specifically. Instead of a seat per domain, it is one flat price for all of them, so a plan covers five domains the same as one and adding a project does not move the bill.",[31,178,179],{},"Setup is one 5-minute DNS setup per domain: add a few records (a DKIM TXT, a Return-Path CNAME, and an MX record), verify them in the app, and that domain can both receive and send signed mail. From there, every domain's mail lands in a single inbox tagged per domain, replies go out authenticated as the address the message came to so they pass DMARC, and there is a REST API for anything your apps need to send. The API is Resend-compatible, so existing send code points at it with one line changed.",[31,181,182,183,187,188,124],{},"You keep your main email wherever it already is. Mailyond runs alongside Gmail or Workspace, on a subdomain if you prefer, not instead of them. To be straight about it: if you own a single domain, an ordinary mailbox like Fastmail or Google Workspace is the calmer choice. The per-domain pain, and the savings, only show up at two or more. You can see the plans on the ",[55,184,186],{"href":185},"\u002F#pricing","pricing"," page or ",[55,189,191],{"href":190},"\u002Fsignup","start free",[44,193,195],{"id":194},"the-short-version","The short version",[31,197,198,199,202],{},"Email hosting for multiple domains is priced per seat by every mainstream provider, so real inboxes on several domains get expensive fast, and the cheap forwarding routes solve reading while breaking authenticated replies. What you actually want from multiple domain email hosting is one tagged inbox, replies signed per domain, flat pricing, and an API to send from your apps. That combination, at one flat price across every domain, is the gap ",[55,200,201],{"href":190},"Mailyond"," was built to fill.",{"title":204,"searchDepth":205,"depth":205,"links":206},"",2,[207,208,209,210,211,212],{"id":46,"depth":205,"text":47},{"id":65,"depth":205,"text":66},{"id":105,"depth":205,"text":106},{"id":130,"depth":205,"text":131},{"id":172,"depth":205,"text":173},{"id":194,"depth":205,"text":195},"2026-07-22","Email hosting for multiple domains usually bills per user per domain. Here are the real options, their costs, and how to run every domain from one inbox.","md",{"src":217},"https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F53621\u002Fcalculator-calculation-insurance-finance-53621.jpeg?auto=compress&cs=tinysrgb&h=650&w=940",{},true,"\u002Fblog\u002Femail-hosting-for-multiple-domains",{"title":19,"description":214},"blog\u002Femail-hosting-for-multiple-domains","fOCRQc-CFR-np8QZN1XuveH-tiZq4JYMQICMtx14sM0",{"id":225,"title":226,"authors":227,"badge":230,"body":231,"date":456,"description":457,"extension":215,"image":458,"meta":460,"navigation":219,"path":461,"seo":462,"stem":463,"__hash__":464},"posts\u002Fblog\u002Femail-forwarding-service.md","Email Forwarding Service: What It Does and Where It Breaks",[228],{"name":22,"avatar":229},{"src":24},{"label":26},{"type":28,"value":232,"toc":448},[233,236,240,247,250,253,289,292,296,336,339,343,349,352,378,381,385,388,395,398,405,409,415,421,427,433,439,441],[31,234,235],{},"An email forwarding service takes mail sent to your domain and redirects it to an inbox you already have. Gmail, Outlook, wherever. That's the whole job. Tools like ImprovMX, Cloudflare Email Routing, Addy.io, SimpleLogin, and Forward Email all do it well, and several do it for free. The catch is that forwarding isn't an inbox: you can't reply from the address without extra SMTP setup, and the moment you run more than one domain you're stitching together three or four tools. Here's what forwarding actually does, where it breaks, and how to tell when you've outgrown it.",[44,237,239],{"id":238},"what-an-email-forwarding-service-actually-does-and-where-it-stops","What an email forwarding service actually does (and where it stops)",[31,241,242,243,246],{},"Strip away the marketing and email forwarding is a one-way pipe. Mail hits ",[35,244,245],{},"you@yourdomain.com",", a rule catches it, and it lands in your existing Gmail or Outlook inbox. No new mailbox gets created. Most providers don't store your mail long-term. It's plumbing, not a mail client.",[31,248,249],{},"That's exactly why it's cheap or free. You're not paying for storage or an interface. You're paying (or not paying) for MX record routing.",[31,251,252],{},"Here's how the well-known email forwarding software options handle it:",[136,254,255,265,271,277,283],{},[139,256,257,260,261,124],{},[73,258,259],{},"Cloudflare Email Routing",": free, unlimited inbound volume, up to 200 routing rules per domain and 200 verified destinations per account. No inbox. Cloudflare does sell outbound sending now, but as a separate paid, API-only product; we broke that down in ",[55,262,264],{"href":263},"\u002Fblog\u002Fcloudflare-email-routing-send-email","our guide to sending with Cloudflare Email Routing",[139,266,267,270],{},[73,268,269],{},"ImprovMX",": free plan covers 1 domain with 25 aliases, receive-only. Premium at $9\u002Fmonth gets you 30 domains and SMTP sending (6,000 sends\u002Fmonth); the $24\u002Fmonth Pro tier stretches to 100 domains.",[139,272,273,276],{},[73,274,275],{},"Addy.io"," (formerly AnonAddy): free tier gives unlimited standard aliases but caps bandwidth at 10MB\u002Fmonth. Pro is $3-4\u002Fmonth for custom domains. Built for alias privacy, not business inboxes.",[139,278,279,282],{},[73,280,281],{},"SimpleLogin",": free plan allows 10 aliases with no custom domain. Premium is $30\u002Fyear for unlimited aliases and domains. Still alias-first, same privacy job as Addy.",[139,284,285,288],{},[73,286,287],{},"Forward Email",": open-source, free hosted forwarding for unlimited domains. Add IMAP\u002FSMTP send and receive and it's $3\u002Fmonth. Self-hosting is possible, but now you're running a mail server.",[31,290,291],{},"All five are legit domain email forwarding tools. r\u002Fselfhosted and r\u002Fwebdev recommend this exact stack constantly for cheap custom-domain email. For one domain, one person, one inbox to check, it works.",[44,293,295],{"id":294},"where-forwarding-falls-apart","Where forwarding falls apart",[136,297,298,309,324,330],{},[139,299,300,303,304,308],{},[73,301,302],{},"Replying looks wrong."," Hit reply on a forwarded message and it goes out from your personal Gmail, not the domain the mail came to. Gmail's \"Send mail as\" workaround increasingly fails DMARC, so replies land in spam or show \"via gmail.com\". We covered the mechanics in ",[55,305,307],{"href":306},"\u002Fblog\u002Fcloudflare-email-routing-reply","how to reply with Cloudflare Email Routing","; the same physics apply to every forwarder.",[139,310,311,314,315,318,319,321,322,124],{},[73,312,313],{},"Every extra domain multiplies the mess."," Run ",[35,316,317],{},"hello@brand-a.com"," and ",[35,320,115],{}," through forwarding and you're juggling identity per reply inside one Gmail, or logging in and out of separate accounts. The full pain is its own post: ",[55,323,169],{"href":168},[139,325,326,329],{},[73,327,328],{},"No shared access."," Forwarding rules point at one personal inbox. Add a cofounder or a support person and you're sharing a password or buying seats somewhere else.",[139,331,332,335],{},[73,333,334],{},"No real archive."," Most forwarders relay and forget. If the destination inbox dies or you switch providers, there's no independent copy of your mail history.",[31,337,338],{},"Forwarding solves \"get the mail somewhere\". It was never built to solve \"run a business's email across domains\".",[44,340,342],{"id":341},"when-youve-outgrown-forwarding","When you've outgrown forwarding",[31,344,345,346,348],{},"We built ",[55,347,201],{"href":190}," for the point where the free stack stops being free in time terms: the founder with 3, 5, 10 domains who's already duct-taped Cloudflare rules to Gmail Send-As, lost a weekend to SPF and DKIM, and still can't reply cleanly as the right brand. (That founder was us. Mailyond runs on the fifth iteration of the setup that broke four times.)",[31,350,351],{},"What changes with an actual multi-domain inbox:",[136,353,354,360,366,372],{},[139,355,356,359],{},[73,357,358],{},"One inbox, every domain."," All your domains' mail in a single threaded view, tagged per domain, stored independently of any upstream provider.",[139,361,362,365],{},[73,363,364],{},"Reply as the right address, correctly."," Each domain is verified with one 5-minute DNS setup (DKIM, Return-Path, MX), so replies go out signed and pass DMARC. No \"via gmail.com\".",[139,367,368,371],{},[73,369,370],{},"Send from your app too."," A transactional send API on the same domains, Resend-compatible, so receipts and password resets don't need a second vendor.",[139,373,374,377],{},[73,375,376],{},"A different job than aliasing."," Addy.io and SimpleLogin are excellent at hiding your real address for privacy. Running a company's support and sales email across brands is a different job, and that's the one Mailyond does.",[31,379,380],{},"The honest version: if you just need mail redirected, use a forwarder. Cloudflare's is free and good. Mailyond is for when you also need to reply, send, and keep the history, across more domains than you have teammates.",[44,382,384],{"id":383},"pricing-logic-per-domain-per-seat-or-per-bundle","Pricing logic: per domain, per seat, or per bundle",[31,386,387],{},"This is where most comparisons get lazy, so let's be specific.",[31,389,390,391,394],{},"Forwarding tools price per domain or per volume: ImprovMX at $9\u002Fmonth for 30 domains, Addy.io Pro at $3-4\u002Fmonth, Forward Email at $3\u002Fmonth, Cloudflare at $0. Cheap. But none of those prices include the actual mailbox: you still need somewhere to read and reply, which usually means Google Workspace at $7-14 per user per month on top (",[55,392,393],{"href":57},"full breakdown here","). A 3-domain setup with a \"proper\" inbox per brand quietly becomes $30-50\u002Fmonth.",[31,396,397],{},"Workspace prices per seat, which is the wrong axis for a solo founder with five brands: you have more domains than people.",[31,399,400,401,404],{},"Mailyond prices per bundle of domains: ",[55,402,403],{"href":185},"$10\u002Fmonth covers 5 domains"," with 3,000 emails, inbox and send API included; $40\u002Fmonth covers 30 domains for agencies. Adding a project doesn't change the bill. The question to ask before picking a tool: are you paying for people, or for domains? If you've got more domains than teammates, per-seat pricing is the wrong deal.",[44,406,408],{"id":407},"faq","FAQ",[31,410,411,414],{},[73,412,413],{},"What's the difference between email forwarding and a hosted mailbox?"," Forwarding redirects incoming mail to an inbox you already have; no storage, usually no sending. A hosted mailbox stores mail, lets you reply as that address, and keeps a searchable history in one place.",[31,416,417,420],{},[73,418,419],{},"Is free email forwarding actually free?"," Cloudflare Email Routing and Forward Email's basic tier are genuinely free with no time limit. The catch is they're receive-only or capped, and you still need an inbox to receive into.",[31,422,423,426],{},[73,424,425],{},"Can I reply from a forwarded address without it looking spammy?"," Only if SPF, DKIM, and DMARC authorize the sending inbox for that domain. Skip that and replies land in spam or show \"via gmail.com\". This got strictly worse after the 2024 DMARC tightening.",[31,428,429,432],{},[73,430,431],{},"What is MX forwarding?"," Changing your domain's MX records to point at a forwarding provider's servers, which relay mail to your real inbox. It's the mechanism behind every tool in this article.",[31,434,435,438],{},[73,436,437],{},"Do I need email forwarding software if I only own one domain?"," Probably just a free option like Cloudflare Email Routing. Multi-domain inbox tools earn their price once you're managing several domains or need shared access.",[44,440,195],{"id":194},[31,442,443,444,447],{},"An email forwarding service is a redirect rule, and for one domain the free ones (Cloudflare, Forward Email) are genuinely enough. The breakage starts when you reply, and it compounds with every domain you add: broken DMARC, juggled identities, no shared access, no archive. If that's where you are, forwarding isn't the tool anymore. One ",[55,445,446],{"href":190},"5-minute DNS setup per domain"," gets you an inbox that receives, replies, and sends as every domain you own.",{"title":204,"searchDepth":205,"depth":205,"links":449},[450,451,452,453,454,455],{"id":238,"depth":205,"text":239},{"id":294,"depth":205,"text":295},{"id":341,"depth":205,"text":342},{"id":383,"depth":205,"text":384},{"id":407,"depth":205,"text":408},{"id":194,"depth":205,"text":195},"2026-07-15","An email forwarding service redirects mail to an inbox you already have. What the free tools do well, where forwarding breaks, and when you've outgrown it.",{"src":459},"https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F4065876\u002Fpexels-photo-4065876.jpeg?auto=compress&cs=tinysrgb&h=650&w=940",{},"\u002Fblog\u002Femail-forwarding-service",{"title":226,"description":457},"blog\u002Femail-forwarding-service","JsLkEjf2feyjq45Vy3rWYX0pQzuVqF03UqTT4wwynOI",{"id":466,"title":467,"authors":468,"badge":471,"body":472,"date":863,"description":864,"extension":215,"image":865,"meta":867,"navigation":219,"path":263,"seo":868,"stem":869,"__hash__":870},"posts\u002Fblog\u002Fcloudflare-email-routing-send-email.md","Cloudflare Email Routing Send Email: The Real Options",[469],{"name":22,"avatar":470},{"src":24},{"label":26},{"type":28,"value":473,"toc":854},[474,477,481,484,491,505,508,512,515,529,557,567,570,574,581,584,587,619,625,629,632,638,648,658,664,668,671,697,779,782,784,789,792,828,831,846,848],[31,475,476],{},"You set up Cloudflare Email Routing, got your domains receiving, and now you want to send email from those same domains. Maybe a password reset, an order confirmation, a reply to a customer. So you go looking for how to make Cloudflare email routing send email, and you land in a tangle of docs about Workers, bindings, and something called \"Email Service\" that might or might not be the same thing. Here is what is going on, how sending works, what it costs, and where it still leaves you stuck.",[44,478,480],{"id":479},"cloudflare-email-routing-still-does-not-send-email","Cloudflare Email Routing still does not send email",[31,482,483],{},"Let's clear up the naming first, because Cloudflare rebranded and it confuses everyone.",[31,485,486,487,490],{},"What used to be called \"Email Routing\" is now part of a broader product called ",[73,488,489],{},"Cloudflare Email Service",". Email Service has two halves:",[136,492,493,499],{},[139,494,495,498],{},[73,496,497],{},"Email Routing"," handles incoming mail. It forwards messages sent to your domain to another mailbox you already own. This is the part that is free and works on any Cloudflare plan. It receives. It does not send.",[139,500,501,504],{},[73,502,503],{},"Email Sending"," handles outbound mail. It launched in beta in 2025 and has been generally available since April 2026. This is the part you are looking for if you want to send email from your domain. It is a separate feature with its own setup, its own pricing, and its own limits.",[31,506,507],{},"So when people ask \"can Cloudflare email routing send email,\" the honest answer is: Email Routing itself cannot. Cloudflare added a separate sending feature under the Email Service umbrella, and that is what handles outbound. They are two tools that happen to share a product page.",[44,509,511],{"id":510},"how-email-service-sending-actually-works","How Email Service sending actually works",[31,513,514],{},"If you want to send email from a domain on Cloudflare, here is what you are working with. Email Sending gives you three ways to get mail out:",[31,516,517,520,521,524,525,528],{},[73,518,519],{},"Workers binding."," You write a Cloudflare Worker (a serverless function), add a ",[35,522,523],{},"send_email"," binding to your wrangler config, and call ",[35,526,527],{},"env.EMAIL.send()"," from your code. This is the native Cloudflare path, fast but dependent on Workers.",[31,530,531,534,535,538,539,538,542,538,545,548,549,552,553,556],{},[73,532,533],{},"REST API."," A standard HTTP endpoint. You POST a JSON payload with your ",[35,536,537],{},"to",", ",[35,540,541],{},"from",[35,543,544],{},"subject",[35,546,547],{},"html",", and ",[35,550,551],{},"text"," to ",[35,554,555],{},"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Faccounts\u002F{account_id}\u002Femail\u002Fsending\u002Fsend"," with a bearer token. This works from any platform, not just Workers.",[31,558,559,562,563,566],{},[73,560,561],{},"SMTP."," Authenticated SMTP submission to ",[35,564,565],{},"smtp.mx.cloudflare.net:465",". You can point any SMTP-capable app at it. Useful if you have existing code that speaks SMTP.",[31,568,569],{},"All three do the same thing under the hood. The catch is what surrounds them.",[44,571,573],{"id":572},"what-it-costs-and-what-limits-you-hit","What it costs and what limits you hit",[31,575,576,577,580],{},"Email Sending requires the ",[73,578,579],{},"Workers Paid plan",", which is $5\u002Fmonth. On the free plan you can only send to verified destination addresses (basically test sends to addresses you have confirmed). Sending to real recipients needs the paid plan.",[31,582,583],{},"On the paid plan you get 3,000 outbound emails per month included. After that it is $0.35 per 1,000 emails. Inbound routing is unlimited and free on both plans.",[31,585,586],{},"A few limits worth knowing before you build on this:",[136,588,589,595,601,607,613],{},[139,590,591,594],{},[73,592,593],{},"5 MiB max message size"," including attachments (25 MiB if sending to verified destinations only).",[139,596,597,600],{},[73,598,599],{},"50 recipients per email"," combined across to, cc, and bcc.",[139,602,603,606],{},[73,604,605],{},"30 domains per zone"," for both routing and sending combined.",[139,608,609,612],{},[73,610,611],{},"Daily sending limits"," start conservative for new accounts and scale up based on your reputation. You can request increases via a form.",[139,614,615,618],{},[73,616,617],{},"Transactional only."," Cloudflare's own FAQ says Email Service is for transactional email, not marketing or bulk. They plan to add that later.",[31,620,621,622,624],{},"There is also a quiet gotcha: emails sent from a Worker using the ",[35,623,523],{}," binding show up as \"dropped\" in the Email Routing summary, even when they delivered fine. You have to check the Email Sending metrics separately to track outbound success. That one catches people.",[44,626,628],{"id":627},"the-catches-that-are-not-in-the-pricing-table","The catches that are not in the pricing table",[31,630,631],{},"Those numbers are clear enough. The friction is in the setup requirements.",[31,633,634,637],{},[73,635,636],{},"You must use Cloudflare DNS."," Email Service only works on domains hosted on Cloudflare's nameservers. If your domain's DNS lives somewhere else, you either migrate it or you are out of luck.",[31,639,640,643,644,647],{},[73,641,642],{},"Each sending domain gets onboarded separately."," You pick a domain from your Cloudflare account, and Cloudflare adds MX, SPF, DKIM, and DMARC records to a ",[35,645,646],{},"cf-bounce"," subdomain. That is per domain. Five domains means five onboarding passes.",[31,649,650,653,654,657],{},[73,651,652],{},"There is no inbox and no reply button."," This is the one that matters most for people who found us through ",[55,655,656],{"href":306},"our Cloudflare email routing reply guide",". Email Sending is an API for firing outbound messages. It does not give you a place to read incoming mail, and it does not give you a way to hit \"reply\" on a message a customer sent you. You can build a Worker that receives an inbound email and fires back a response programmatically, but that is code, not an inbox. If you want to read a customer message and type a reply from your domain, Email Service does not have that.",[31,659,660,663],{},[73,661,662],{},"No multi-domain inbox."," If you run several domains, Email Routing can forward each one to a destination address, and Email Sending can send from each one. But there is no unified view across them. You are stitching together forwarding rules, Workers, and an external mailbox to approximate one inbox for multiple domains.",[44,665,667],{"id":666},"what-you-actually-need-vs-what-email-service-gives-you","What you actually need vs. what Email Service gives you",[31,669,670],{},"Strip it down and most people who go looking for \"Cloudflare email routing send email\" want more than just an API endpoint. They want:",[136,672,673,679,685,691],{},[139,674,675,678],{},[73,676,677],{},"Receive"," mail on their domain. Email Routing does this fine.",[139,680,681,684],{},[73,682,683],{},"Send"," email from that domain, authenticated. Email Service does this if you are on the Workers Paid plan and your domain is on Cloudflare DNS.",[139,686,687,690],{},[73,688,689],{},"Read and reply"," in one place. Neither half of Email Service gives you this.",[139,692,693,696],{},[73,694,695],{},"One inbox across every domain."," No. Each domain is its own config, and you still need an external mailbox to read anything.",[698,699,700,714],"table",{},[701,702,703],"thead",{},[704,705,706,710,712],"tr",{},[707,708,709],"th",{},"Requirement",[707,711,489],{},[707,713,201],{},[715,716,717,729,740,750,759,768],"tbody",{},[704,718,719,723,726],{},[720,721,722],"td",{},"Receive on your domain",[720,724,725],{},"Yes (free)",[720,727,728],{},"Yes",[704,730,731,734,737],{},[720,732,733],{},"Send from your domain",[720,735,736],{},"Yes (Workers Paid, API\u002FSMTP only)",[720,738,739],{},"Yes (REST API)",[704,741,742,745,748],{},[720,743,744],{},"Read and reply in one inbox",[720,746,747],{},"No",[720,749,728],{},[704,751,752,755,757],{},[720,753,754],{},"One inbox across all domains",[720,756,747],{},[720,758,728],{},[704,760,761,764,766],{},[720,762,763],{},"Requires Cloudflare DNS",[720,765,728],{},[720,767,747],{},[704,769,770,773,776],{},[720,771,772],{},"Per-domain onboarding",[720,774,775],{},"Yes, each domain separately",[720,777,778],{},"One 5-minute DNS setup per domain",[31,780,781],{},"None of this is to knock Cloudflare. If you are already building on Workers and you want to fire transactional emails from your edge code, Email Service sending is a solid, cheap option. 3,000 free sends on a $5 plan is hard to beat for pure outbound volume. The gap is everything around the sending: reading, replying, and managing mail across domains without writing Workers for it.",[44,783,173],{"id":172},[31,785,345,786,788],{},[55,787,201],{"href":190}," for the person who started with Cloudflare Email Routing, realized they also need to send, and then realized Email Service still does not give them an inbox to read and reply from.",[31,790,791],{},"Mailyond covers both halves on the same domain, without the parts that make Email Service awkward for this job:",[136,793,794,800,806,812,822],{},[139,795,796,799],{},[73,797,798],{},"Your DNS can stay where it is."," Cloudflare, your registrar, anywhere. Mailyond needs a few records per domain, verified in the app in about five minutes, and never asks you to move nameservers.",[139,801,802,805],{},[73,803,804],{},"Sending and receiving come configured together."," Verifying a domain sets up authenticated outbound (SPF, DKIM, aligned DMARC) at the same time, so both your replies and your API sends land in inboxes instead of spam.",[139,807,808,811],{},[73,809,810],{},"There is an actual inbox."," Mail to every connected domain arrives in one dashboard, tagged per domain, with a reply button that sends as the address the message came to. No Worker required.",[139,813,814,817,818,821],{},[73,815,816],{},"The send API is Resend-compatible."," If your app already uses the Resend SDK, you change the base URL and your ",[35,819,820],{},"emails.send()"," calls keep working.",[139,823,824,827],{},[73,825,826],{},"Pricing is flat per bundle of domains",", starting at $10\u002Fmonth for 5 domains, rather than per seat or per plan tier.",[31,829,830],{},"If Email Routing already does what you need and you only want programmatic sends from a Cloudflare-hosted domain, Email Service on the $5 Workers plan is a fair deal. Mailyond is for when the missing inbox and the Cloudflare DNS requirement start costing you evenings.",[31,832,833,834,837,838,840,841,843,844,124],{},"If you came here from a sending problem and also need to reply, read our breakdown of ",[55,835,836],{"href":306},"why Cloudflare Email Routing can't reply"," and the full ",[55,839,169],{"href":168}," guide. For the cost angle across providers, see our ",[55,842,86],{"href":85}," comparison or check the ",[55,845,186],{"href":185},[44,847,195],{"id":194},[31,849,850,851,853],{},"Cloudflare Email Routing does not send email. Cloudflare added Email Sending under the Email Service product (generally available since April 2026), and it works through a Workers binding, REST API, or SMTP. It requires the Workers Paid plan ($5\u002Fmonth), only works on domains using Cloudflare DNS, and is transactional only. 3,000 sends per month are included, then $0.35 per 1,000. What it does not give you is an inbox to read mail, a reply button, or one view across all your domains. If you need to send from your app and that is all, it does the job. If you also need to read, reply, and manage mail across several domains without writing Workers for it, that is the gap we built ",[55,852,201],{"href":190}," to fill.",{"title":204,"searchDepth":205,"depth":205,"links":855},[856,857,858,859,860,861,862],{"id":479,"depth":205,"text":480},{"id":510,"depth":205,"text":511},{"id":572,"depth":205,"text":573},{"id":627,"depth":205,"text":628},{"id":666,"depth":205,"text":667},{"id":172,"depth":205,"text":173},{"id":194,"depth":205,"text":195},"2026-07-14","Cloudflare Email Routing receives but does not send. Here is how Cloudflare Email Service sending works, what it costs, and the gap it still leaves.",{"src":866},"https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F4348401\u002Fpexels-photo-4348401.jpeg?auto=compress&cs=tinysrgb&h=650&w=940",{},{"title":467,"description":864},"blog\u002Fcloudflare-email-routing-send-email","qOUiKTl8cD_FHczq-QeOpiJqqofZUEQEkoFZMN4lcSI",{"id":872,"title":873,"authors":874,"badge":877,"body":878,"date":1086,"description":1087,"extension":215,"image":1088,"meta":1089,"navigation":219,"path":168,"seo":1090,"stem":1091,"__hash__":1092},"posts\u002Fblog\u002Fone-inbox-for-multiple-domains.md","One Inbox for Multiple Domains: Stop Juggling Mailboxes",[875],{"name":22,"avatar":876},{"src":24},{"label":26},{"type":28,"value":879,"toc":1079},[880,889,892,896,899,911,927,934,938,941,946,956,978,984,996,1000,1003,1028,1031,1033,1038,1041,1062,1065,1067],[31,881,882,883,885,886,888],{},"You own a handful of domains. One for the main product, one for a side project, maybe a couple you grabbed for ideas you might build. Each one has a ",[35,884,37],{}," or a ",[35,887,41],{}," that someone occasionally emails. And every one of them lives somewhere different: this one forwards to Gmail, that one is a Workspace seat you forgot you were paying for, the third bounces because you never finished setting it up. What you actually want is one inbox for multiple domains, a single place to read and reply to all of it, instead of logging into five things and never being sure which address an email came to.",[31,890,891],{},"This post is about why that turns out to be harder than it sounds, the common ways people try to fix it, and where each approach falls down.",[44,893,895],{"id":894},"why-one-inbox-for-multiple-domains-is-harder-than-it-looks","Why one inbox for multiple domains is harder than it looks",[31,897,898],{},"The problem splits into two halves that most tools only solve one of.",[31,900,901,902,905,906,910],{},"The first half is ",[73,903,904],{},"reading",". Getting mail from several domains into one place is the easy part. Forwarding does it, a unified email client does it, an alias does it. Nobody really struggles to ",[907,908,909],"em",{},"see"," their mail.",[31,912,913,914,917,918,920,921,923,924,926],{},"The second half is ",[73,915,916],{},"replying as the right domain",", and this is where it falls apart. When you answer an email that came to ",[35,919,115],{},", the reply has to actually go out from ",[35,922,115],{},", properly signed, or it lands in the customer's spam folder. Since 2024 the big mailbox providers enforce this hard: if your outbound mail doesn't pass SPF, DKIM, and DMARC for the domain in the \"from\" line, it gets filtered or bounced. We wrote the full breakdown in ",[55,925,123],{"href":122},", but the short version is that most \"one inbox\" setups quietly skip the authentication, so they read fine and reply badly.",[31,928,929,930,933],{},"So \"one inbox for multiple domains\" really means two things at once: every domain's mail in one view, ",[907,931,932],{},"and"," the ability to reply as each domain without it looking forged. Tools that nail the first and ignore the second are the reason a customer once told you they \"never heard back,\" even though you swear you replied.",[44,935,937],{"id":936},"the-approaches-people-try","The approaches people try",[31,939,940],{},"Here are the usual fixes, roughly in the order people reach for them, and where each one bites.",[31,942,943,945],{},[73,944,75],{}," Point every domain's mail at a single Gmail inbox. Reading is solved instantly and it's free. The catch is replying: hit reply and the message goes out as your personal Gmail, not the domain it came to. You can bolt on Gmail's \"Send mail as,\" but that's the exact path that breaks under DMARC. You end up with one inbox that can read everything and reply as nothing.",[31,947,948,951,952,955],{},[73,949,950],{},"A unified inbox email client."," Apps like Spike, Mailbird, and Edison Mail pull several accounts into a single view. They're genuinely nice for ",[907,953,954],{},"seeing"," everything in one list. But they unify accounts you already own and pay for separately, they don't provision a real mailbox per domain for you, and they inherit whatever sending setup each underlying account has. If those accounts can't authenticate sends for your domains, neither can the unified view. It's a better window onto the same problem, not a fix for it.",[31,957,958,960,961,318,963,966,967,970,971,974,975,977],{},[73,959,81],{}," You can add extra domains to one Workspace account as aliases for free, so ",[35,962,317],{},[35,964,965],{},"hello@brand-b.com"," both land in your one mailbox. It looks like one inbox for all your domains. The trouble is it's ",[907,968,969],{},"one identity",": you can't separate brands, and getting the right \"from\" to stick on a reply is its own fight. The moment you want a genuinely separate inbox per domain, you're paying for another user seat, which is the per-seat trap the rest of ",[55,972,973],{"href":220},"email hosting for multiple domains"," shares. We did the plan-by-plan math in the ",[55,976,86],{"href":85}," guide.",[31,979,980,983],{},[73,981,982],{},"Shared mailboxes in Microsoft 365."," Office 365 lets you create shared mailboxes per domain without a separate license if they stay under the size cap, which is the cheapest \"real inbox\" route if you're already on Microsoft. But each shared mailbox is accessed separately, so you're back to clicking between them rather than one inbox, and you're managing Exchange domain config per brand.",[31,985,986,988,989,992,993,995],{},[73,987,98],{}," Free, fast, and it forwards mail from every domain you point at it. It also can't send a reply at all. Cloudflare does sell a separate programmatic sending product now, which we break down in ",[55,990,991],{"href":263},"how to send email with Cloudflare Email Routing",", but neither half gives you an inbox or a reply button. We covered exactly ",[55,994,836],{"href":306}," and what that leaves you needing.",[44,997,999],{"id":998},"what-one-inbox-should-actually-mean","What \"one inbox\" should actually mean",[31,1001,1002],{},"Strip the workarounds away and the requirement is short:",[136,1004,1005,1011,1017,1022],{},[139,1006,1007,1010],{},[73,1008,1009],{},"Read"," mail from every domain you own in a single view, tagged so you know which brand it hit.",[139,1012,1013,1016],{},[73,1014,1015],{},"Reply"," from that same domain, authenticated, so the answer lands in the inbox and shows the right \"from.\"",[139,1018,1019,1021],{},[73,1020,155],{}," that doesn't climb every time you add a domain you barely check.",[139,1023,1024,1027],{},[73,1025,1026],{},"Send from your app too",", with an API, if any of those domains ship transactional email like receipts or password resets.",[31,1029,1030],{},"Most setups give you one or two. The forwarding ones read but don't reply. The mailbox ones reply but bill per seat and split into separate inboxes. The gap is having all of it in one place without taping three tools together, and that gap gets wider with every domain you add.",[44,1032,173],{"id":172},[31,1034,345,1035,1037],{},[55,1036,201],{"href":190}," for exactly this spot: someone running several domains who wants to read and reply per domain from one inbox, without the per-user math and without gluing tools together.",[31,1039,1040],{},"The idea is simple:",[136,1042,1043,1050,1053,1056,1059],{},[139,1044,1045,1046,1049],{},"Add a few DNS records per domain or subdomain (",[35,1047,1048],{},"support.yourdomain.com"," works) and verify them in the app, one five-minute setup. That sets up signed sending, so replies pass DMARC instead of breaking.",[139,1051,1052],{},"Receive mail to any address on any of your domains in a single shared inbox, tagged per domain.",[139,1054,1055],{},"Reply from the right domain, authenticated, so your answer arrives and shows the correct \"from.\"",[139,1057,1058],{},"One flat price, every domain, so adding a project doesn't change the bill.",[139,1060,1061],{},"Send transactional email from your app with a plain REST call, no second service needed. It's even Resend-API compatible, so existing code points at it with one line changed.",[31,1063,1064],{},"You keep your main email wherever it is. Mailyond runs alongside Gmail or Workspace, on a subdomain if you want, not instead of them. To be straight: it's live now, flat priced, and built around real multi-domain setups rather than a single mailbox. If you only own one domain, a normal mailbox like Fastmail or Google Workspace is the calmer choice. The pain only really shows up at two or more.",[44,1066,195],{"id":194},[31,1068,1069,1070,1072,1073,1076,1077,124],{},"One inbox for multiple domains breaks into two jobs: reading mail from every domain, and replying as each one without landing in spam. Forwarding and unified clients solve the reading and skip the replying. Aliases and shared mailboxes solve the replying but bill per seat or split into separate inboxes. If you run several domains and want to read and answer all of them in one authenticated place without the duct tape, that's the gap we built ",[55,1071,201],{"href":190}," to fill. For the cost side, see the ",[55,1074,1075],{"href":85},"Google Workspace alternative guide"," or check the ",[55,1078,186],{"href":185},{"title":204,"searchDepth":205,"depth":205,"links":1080},[1081,1082,1083,1084,1085],{"id":894,"depth":205,"text":895},{"id":936,"depth":205,"text":937},{"id":998,"depth":205,"text":999},{"id":172,"depth":205,"text":173},{"id":194,"depth":205,"text":195},"2026-06-30","Why one inbox for multiple domains is harder than it sounds, the five approaches people try, and how to read and reply as every domain in one place.",{"src":866},{},{"title":873,"description":1087},"blog\u002Fone-inbox-for-multiple-domains","M-c_Hq0BBfZP7SETqAIs_XDuv7084CWHkv0GqlNme4E",{"id":1094,"title":1095,"authors":1096,"badge":1099,"body":1100,"date":1438,"description":1439,"extension":215,"image":1440,"meta":1441,"navigation":219,"path":122,"seo":1442,"stem":1443,"__hash__":1444},"posts\u002Fblog\u002Freply-to-email-from-custom-domain.md","How to Reply to Email From a Custom Domain",[1097],{"name":22,"avatar":1098},{"src":24},{"label":26},{"type":28,"value":1101,"toc":1429},[1102,1108,1111,1115,1118,1125,1145,1155,1158,1162,1165,1170,1173,1176,1181,1184,1189,1192,1195,1199,1201,1224,1227,1231,1234,1237,1240,1334,1337,1341,1347,1350,1369,1374,1378,1383,1386,1391,1398,1403,1406,1411,1417,1419],[31,1103,1104,1105,1107],{},"You bought a domain, pointed your email at it, and now mail to ",[35,1106,245],{}," shows up fine. Then someone emails your support address, you hit reply, and the message goes out from your personal Gmail instead. Or it goes out from the domain and lands in their spam folder. So the real question: how do you reply to email from a custom domain so it actually arrives, looks professional, and comes from the right address every time?",[31,1109,1110],{},"Receiving on a custom domain is easy. Replying from it is the part that quietly breaks. Here's why it's harder than it looks, the free workarounds people try first and where each one bites back, and how to reply from every domain you own without gluing three tools together.",[44,1112,1114],{"id":1113},"why-replying-from-a-custom-domain-is-the-hard-part","Why replying from a custom domain is the hard part",[31,1116,1117],{},"Receiving mail just means pointing an MX record at something that catches it. Forwarding services, your registrar, Cloudflare, all of them do this in a few minutes.",[31,1119,1120,1121,1124],{},"Replying is a different job. When you send a reply from ",[35,1122,1123],{},"support@yourdomain.com",", the receiving server (usually Gmail, Outlook, or Yahoo) checks whether you are actually allowed to send as that domain. It looks at three things:",[136,1126,1127,1133,1139],{},[139,1128,1129,1132],{},[73,1130,1131],{},"SPF"," says which servers may send for your domain.",[139,1134,1135,1138],{},[73,1136,1137],{},"DKIM"," cryptographically signs the message so it can't be forged.",[139,1140,1141,1144],{},[73,1142,1143],{},"DMARC"," ties the two together and tells the receiver what to do if they don't line up: deliver, spam, or reject.",[31,1146,1147,1148,1154],{},"Since 2024, the big mailbox providers enforce this hard. Google and Yahoo both made authentication a requirement, not a nice-to-have (",[55,1149,1153],{"href":1150,"rel":1151},"https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F81126",[1152],"nofollow","Google's sender guidelines"," spell it out). If your reply is sent from a path that doesn't sign for your domain, it gets filtered or bounced. You think you replied. The customer thinks you ignored them. That is the whole problem in one sentence.",[31,1156,1157],{},"So \"reply from a custom domain\" really means \"send authenticated mail as that domain.\" Most of the free setups skip the authenticated part, which is why they work on day one and fail a month later.",[44,1159,1161],{"id":1160},"the-free-fixes-and-where-each-one-breaks","The free fixes, and where each one breaks",[31,1163,1164],{},"Almost everyone tries one of these three first. They all look fine until someone important doesn't get your reply.",[31,1166,1167],{},[73,1168,1169],{},"Fix 1: Gmail \"Send mail as\"",[31,1171,1172],{},"You add your domain address in Gmail under Settings, point it at an SMTP server, and now you can pick your domain in the \"from\" dropdown when you reply.",[31,1174,1175],{},"This used to just work, because nobody checked the signatures. That era is over. If the SMTP path you configured doesn't pass SPF, DKIM, and DMARC for your domain, Gmail Send-As becomes the exact reason your reply lands in spam. Plenty of people run it for years and never realize half their replies were silently filtered. It is the most common way to reply from a custom domain, and the most common way to do it wrong.",[31,1177,1178],{},[73,1179,1180],{},"Fix 2: A catch-all forward",[31,1182,1183],{},"You set up forwarding so anything to your domain lands in your normal inbox, then reply from there. Receiving works great. But the reply goes out as your personal address, not the domain. Forwarding is receive-only. It carries mail in, it does not let you answer as the domain it came to. You also lose the clean \"from\" your customer expects, which looks unprofessional and trains them to reply to the wrong address.",[31,1185,1186],{},[73,1187,1188],{},"Fix 3: Bolt on a sending service (Resend, Postmark, SES)",[31,1190,1191],{},"So you add a real transactional sender to handle outbound. Reasonable. Except sending services want their own DNS, and the second you run a sender plus a receiving\u002Fforwarding setup on the same domain, you hit the MX conflict: receiving wants one set of records, the sender wants another, and they fight. People burn an afternoon on this and post about it in forums constantly.",[31,1193,1194],{},"Even after you win that fight, you now run two stacks. One thing receives, another sends, and a single reply becomes a coordination problem across both. And you still don't have one place to read and answer mail, you have a sender API and an inbox that don't know about each other.",[44,1196,1198],{"id":1197},"what-you-actually-need","What you actually need",[31,1200,1002],{},[136,1202,1203,1208,1213,1219],{},[139,1204,1205,1207],{},[73,1206,677],{}," mail on your domain.",[139,1209,1210,1212],{},[73,1211,1015],{}," from that same domain, properly signed, so it lands in the inbox instead of spam.",[139,1214,1215,1218],{},[73,1216,1217],{},"One place to read and answer",", ideally across every domain you own.",[139,1220,1221,1223],{},[73,1222,1026],{}," if you ship transactional email like password resets or receipts.",[31,1225,1226],{},"The free setups each give you one or two of these. The gap is having all four without taping tools together, and that gap gets wider the more domains you run.",[44,1228,1230],{"id":1229},"doing-it-across-several-domains","Doing it across several domains",[31,1232,1233],{},"One domain is annoying. Several domains is where it stops being worth it.",[31,1235,1236],{},"If you run three or five projects, each on its own domain, the per-domain math gets ugly fast. A real mailbox per domain on Google Workspace is a paid seat each. Gmail Send-As across five domains is five fragile SMTP setups and five chances for DMARC to break. And a separate sender bolted onto each domain is five MX fights. You did not want an email department, you wanted to answer customers.",[31,1238,1239],{},"What you actually want is one inbox for multiple domains: every address across every domain you own landing in a single shared inbox, where you reply as the right domain without thinking about which one it was. Here is how the common approaches stack up.",[698,1241,1242,1261],{},[701,1243,1244],{},[704,1245,1246,1249,1252,1255,1258],{},[707,1247,1248],{},"Approach",[707,1250,1251],{},"Receives",[707,1253,1254],{},"Replies from your domain",[707,1256,1257],{},"One inbox, all domains",[707,1259,1260],{},"Sends from your app",[715,1262,1263,1277,1292,1306,1320],{},[704,1264,1265,1268,1270,1273,1275],{},[720,1266,1267],{},"Catch-all forward to Gmail",[720,1269,728],{},[720,1271,1272],{},"No (sends as you)",[720,1274,747],{},[720,1276,747],{},[704,1278,1279,1282,1284,1287,1290],{},[720,1280,1281],{},"Gmail Send-As + SMTP",[720,1283,728],{},[720,1285,1286],{},"Fragile (DMARC)",[720,1288,1289],{},"Sort of (one Gmail)",[720,1291,747],{},[704,1293,1294,1297,1299,1302,1304],{},[720,1295,1296],{},"Forwarding + a sending service",[720,1298,728],{},[720,1300,1301],{},"Yes, after MX wrangling",[720,1303,747],{},[720,1305,728],{},[704,1307,1308,1311,1313,1315,1318],{},[720,1309,1310],{},"A mailbox per domain (Workspace)",[720,1312,728],{},[720,1314,728],{},[720,1316,1317],{},"No (separate seats)",[720,1319,747],{},[704,1321,1322,1324,1326,1329,1332],{},[720,1323,201],{},[720,1325,728],{},[720,1327,1328],{},"Yes, signed",[720,1330,1331],{},"Yes, every domain",[720,1333,739],{},[31,1335,1336],{},"A couple of honest notes. If you own a single domain and just want clean personal email, a normal mailbox like Fastmail or Google Workspace is the calm choice, and you can stop reading here. The pain only really shows up at two or more domains, where buying a seat per domain feels absurd for inboxes you check twice a week.",[44,1338,1340],{"id":1339},"how-to-reply-from-a-custom-domain-in-a-few-minutes","How to reply from a custom domain in a few minutes",[31,1342,1343,1344,1346],{},"This is where ",[55,1345,201],{"href":190}," fits, because it was built for exactly this spot: you can receive on all your domains, but replying and managing it is a mess of forwarding rules and half-working hacks.",[31,1348,1349],{},"The setup is short:",[136,1351,1352,1357,1360,1363,1366],{},[139,1353,1045,1354,1356],{},[35,1355,1048],{}," works) and verify them in the app, one five-minute setup. That sets up signed sending for you, so DMARC passes instead of breaking.",[139,1358,1359],{},"Receive mail to any address on that domain in a shared inbox.",[139,1361,1362],{},"Reply from that same domain, authenticated, so your answer lands in the inbox and shows the right \"from\".",[139,1364,1365],{},"See and answer mail from every domain you own in one place, tagged per domain.",[139,1367,1368],{},"Send transactional email from your app with a plain REST call, so you don't need a separate sender. It is even Resend-API compatible, so existing code points at it with one line changed.",[31,1370,1371,1372,124],{},"You keep your main email wherever it is. Mailyond runs alongside Gmail or Workspace, on a subdomain if you want, not instead of them. To be straight: it is live now, flat priced, and built around real multi-domain setups rather than a single inbox. If \"I can receive but I can't reply\" is your problem, ",[55,1373,191],{"href":190},[44,1375,1377],{"id":1376},"common-questions","Common questions",[31,1379,1380],{},[73,1381,1382],{},"How do I send email from a custom domain at all?",[31,1384,1385],{},"You need a service that signs mail for your domain with DKIM and lines it up with SPF and DMARC. That can be a full mailbox (Workspace, Fastmail), a transactional sender (Resend, Postmark, SES) for app email, or a tool like Mailyond that does both the inbox and the sending. What you cannot do is send authenticated mail straight from a plain forwarding setup, which is why Send-As and catch-alls fall down.",[31,1387,1388],{},[73,1389,1390],{},"Can I reply from a catch-all address?",[31,1392,1393,1394,1397],{},"You can receive on a catch-all (",[35,1395,1396],{},"anything@yourdomain.com",") easily. Replying as that catch-all still needs authenticated sending for the domain. So a catch-all solves receiving, not replying, unless the tool behind it also signs your outbound mail.",[31,1399,1400],{},[73,1401,1402],{},"Why does my reply from my domain go to spam?",[31,1404,1405],{},"Almost always a DMARC failure. The reply was sent from a path that does not pass SPF and DKIM for your domain, so the receiver filters it. Fix the authentication and the spam problem goes away. This is the single most common reason custom-domain replies disappear.",[31,1407,1408],{},[73,1409,1410],{},"Is Cloudflare Email Routing enough?",[31,1412,1413,1414,1416],{},"No, it only forwards. It cannot send your reply. We wrote a full breakdown of ",[55,1415,836],{"href":306}," and what to use instead.",[44,1418,195],{"id":194},[31,1420,1421,1422,1424,1425,1076,1427,124],{},"Receiving on a custom domain is the easy half. Replying from it means sending authenticated mail as that domain, and the free fixes skip the authenticated part: Send-As breaks under DMARC, catch-alls reply as the wrong address, and bolting on a sender starts an MX fight and leaves you running two stacks. If you only have one domain, a normal mailbox is fine. If you run several and want to read and reply from all of them in one place without the duct tape, that is the gap we built ",[55,1423,201],{"href":190}," to fill. For the cost side of running email across many domains, see our ",[55,1426,1075],{"href":85},[55,1428,186],{"href":185},{"title":204,"searchDepth":205,"depth":205,"links":1430},[1431,1432,1433,1434,1435,1436,1437],{"id":1113,"depth":205,"text":1114},{"id":1160,"depth":205,"text":1161},{"id":1197,"depth":205,"text":1198},{"id":1229,"depth":205,"text":1230},{"id":1339,"depth":205,"text":1340},{"id":1376,"depth":205,"text":1377},{"id":194,"depth":205,"text":195},"2026-06-28","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.",{"src":459},{},{"title":1095,"description":1439},"blog\u002Freply-to-email-from-custom-domain","B5pf7GWQUYWEcEhkHnJUccWxqPiWvDcxowrjk_btl90",{"id":1446,"title":1447,"authors":1448,"badge":1451,"body":1453,"date":1742,"description":1743,"extension":215,"image":1744,"meta":1745,"navigation":219,"path":57,"seo":1746,"stem":1747,"__hash__":1748},"posts\u002Fblog\u002Fgoogle-workspace-multiple-domains-pricing.md","Google Workspace Multiple Domains Pricing: What It Actually Costs in 2026",[1449],{"name":22,"avatar":1450},{"src":24},{"label":1452},"Pricing",{"type":28,"value":1454,"toc":1733},[1455,1462,1465,1469,1472,1534,1537,1543,1546,1550,1553,1571,1577,1580,1584,1587,1637,1640,1643,1649,1653,1656,1659,1662,1665,1669,1672,1683,1686,1697,1699,1704,1707,1725,1727,1730],[31,1456,1457,1458,1461],{},"If you searched for Google Workspace multiple domains pricing, here is the short answer: Google does not charge per domain. Adding domains is free. You pay per ",[73,1459,1460],{},"user",", and that is where the bill grows.",[31,1463,1464],{},"That one sentence confuses almost everyone, because \"domains are free\" and \"this costs me $35\u002Fmonth\" are both true at the same time. Let's walk through the actual numbers.",[44,1466,1468],{"id":1467},"the-2026-price-list","The 2026 price list",[31,1470,1471],{},"Every Google Workspace plan is priced per user, per month. These are the current US prices:",[698,1473,1474,1490],{},[701,1475,1476],{},[704,1477,1478,1481,1484,1487],{},[707,1479,1480],{},"Plan",[707,1482,1483],{},"Annual commitment",[707,1485,1486],{},"Month to month",[707,1488,1489],{},"Storage (pooled)",[715,1491,1492,1506,1520],{},[704,1493,1494,1497,1500,1503],{},[720,1495,1496],{},"Business Starter",[720,1498,1499],{},"$7\u002Fuser\u002Fmo",[720,1501,1502],{},"$8.40\u002Fuser\u002Fmo",[720,1504,1505],{},"30 GB per user",[704,1507,1508,1511,1514,1517],{},[720,1509,1510],{},"Business Standard",[720,1512,1513],{},"$14\u002Fuser\u002Fmo",[720,1515,1516],{},"$16.80\u002Fuser\u002Fmo",[720,1518,1519],{},"2 TB per user",[704,1521,1522,1525,1528,1531],{},[720,1523,1524],{},"Business Plus",[720,1526,1527],{},"$22\u002Fuser\u002Fmo",[720,1529,1530],{},"$26.40\u002Fuser\u002Fmo",[720,1532,1533],{},"5 TB per user",[31,1535,1536],{},"Business plans cap at 300 users. Past that you're on Enterprise, which is \"talk to sales\" pricing.",[31,1538,1539,1542],{},[73,1540,1541],{},"The intro discount:"," when you sign up, Google usually offers 20% to 50% off for the first 3 months, depending on the plan and your region. Two things to know before you count on it. It only applies to your first 20 users. And after 3 months the price snaps back to the full rate, so do your math on the real price, not the promo one.",[31,1544,1545],{},"For email on a side project, Business Starter is the only plan that makes sense. The higher tiers buy you storage and meeting features, not better email.",[44,1547,1549],{"id":1548},"what-multiple-domains-cost-on-top-nothing-sort-of","What multiple domains cost on top: nothing, sort of",[31,1551,1552],{},"Google gives you two ways to add domains to one Workspace account, and they cost different amounts in practice:",[31,1554,1555,1558,1559,1562,1563,1566,1567,1570],{},[73,1556,1557],{},"Domain aliases"," (up to 20 per account) are free. Every user gets a duplicate address at the alias domain. If you are ",[35,1560,1561],{},"you@main.com"," and you add ",[35,1564,1565],{},"brand-b.com"," as an alias, you automatically get ",[35,1568,1569],{},"you@brand-b.com",". All of it lands in the same single inbox, under the same identity.",[31,1572,1573,1576],{},[73,1574,1575],{},"Secondary domains"," (up to 599 per account) are also free to add. The difference: secondary domains can have their own users. And every one of those users is a paid license, same price as any other user.",[31,1578,1579],{},"So the trick behind \"Google Workspace multiple domains pricing\" is that domains never show up on the invoice. Identities do. The moment you want a real, separate mailbox for a domain, that is a user, and that user costs $7 to $26.40 a month.",[44,1581,1583],{"id":1582},"the-math-for-real-setups","The math for real setups",[31,1585,1586],{},"Here is what that means for the setups people actually run, using Business Starter on the annual plan:",[698,1588,1589,1602],{},[701,1590,1591],{},[704,1592,1593,1596,1599],{},[707,1594,1595],{},"Setup",[707,1597,1598],{},"What you pay",[707,1600,1601],{},"What you get",[715,1603,1604,1615,1626],{},[704,1605,1606,1609,1612],{},[720,1607,1608],{},"1 user + 5 alias domains",[720,1610,1611],{},"$7\u002Fmo",[720,1613,1614],{},"One inbox. All 5 domains pile into it under one identity.",[704,1616,1617,1620,1623],{},[720,1618,1619],{},"5 users, one real inbox per domain",[720,1621,1622],{},"$35\u002Fmo ($42 month to month)",[720,1624,1625],{},"Clean separation, 5 logins, 5 mailboxes to check.",[704,1627,1628,1631,1634],{},[720,1629,1630],{},"Agency: 3 client domains, 2 seats each",[720,1632,1633],{},"$42\u002Fmo",[720,1635,1636],{},"Proper setup, and the bill climbs with every new client.",[31,1638,1639],{},"The $7 option sounds like the winner until you live with it. Replies default to your primary address unless you pick the right alias every time. There's no separation between brands. And if a client ever needs their own access, you're buying users anyway.",[31,1641,1642],{},"The middle option is the one people mean when they complain that Google Workspace \"charges per domain.\" Technically it doesn't. Practically, one real inbox per domain is $7\u002Fmonth per domain, billed annually, and $84\u002Fyear for a domain that gets four support emails a month feels bad.",[31,1644,1645,1646,1648],{},"There used to be a third option: keep one cheap account and use Gmail's \"Send mail as\" with free forwarding for the rest. That loophole is closing because of stricter SPF, DKIM, and DMARC enforcement. We covered why in our ",[55,1647,86],{"href":85}," breakdown.",[44,1650,1652],{"id":1651},"what-youre-actually-buying-be-fair-to-google-here","What you're actually buying (be fair to Google here)",[31,1654,1655],{},"One thing the cheap-alternative crowd skips: Google Workspace is not an email bill, it is a suite bill.",[31,1657,1658],{},"Every user gets Gmail, plus Drive storage (30 GB on Starter, 2 TB on Standard), Docs, Sheets, Meet, Calendar, and Gemini features. If your business already lives in Drive and Docs, the per-user price is buying real things, and a dedicated email tool will not replace them. Tools like ours give you email only. No storage, no docs, no video calls.",[31,1660,1661],{},"So the honest question is not \"is $7\u002Fuser expensive.\" It's \"am I paying for a suite I use, or am I paying suite prices to solve an email-routing problem.\"",[31,1663,1664],{},"If every user in your account genuinely works out of Drive and Meet, Workspace is fairly priced and you should probably stay. If you're buying users just to get inboxes on domains, you are overpaying for the part you actually use.",[44,1666,1668],{"id":1667},"when-workspace-pricing-works-and-when-it-doesnt","When Workspace pricing works, and when it doesn't",[31,1670,1671],{},"It works when:",[136,1673,1674,1677,1680],{},[139,1675,1676],{},"You have a real team where each person needs the full suite anyway.",[139,1678,1679],{},"You run one company on one domain, maybe with an alias or two for spelling variants.",[139,1681,1682],{},"You want storage and email from one vendor and one bill.",[31,1684,1685],{},"It stops making sense when:",[136,1687,1688,1691,1694],{},[139,1689,1690],{},"You're one person with 5 projects and you want a separate inbox per domain. That's $35\u002Fmonth, $420\u002Fyear, mostly for empty mailboxes.",[139,1692,1693],{},"You're an agency holding inboxes on client domains, where every new client means new licenses.",[139,1695,1696],{},"Your app sends transactional email anyway, because Workspace has no send API and you'll bolt on another tool regardless.",[44,1698,173],{"id":172},[31,1700,345,1701,1703],{},[55,1702,201],{"href":190}," for that second list. One flat $10\u002Fmonth covers 5 domains with a real inbox per domain, plus a REST API to send transactional email from your apps. Adding a domain is one five-minute DNS setup, and it doesn't change the bill.",[31,1705,1706],{},"To be straight with you, same as always: Mailyond is live now, and we are email only. If you need Drive, Docs, and Meet, keep a Workspace seat for that and point your project domains somewhere flat-priced.",[31,1708,1709,1710,1713,1714,1716,1717,1720,1721,1724],{},"For the full comparison with Fastmail, Zoho, and the forwarding services, read the ",[55,1711,1712],{"href":85},"alternatives breakdown",", or if the per-seat model is the whole problem, see the flat-priced routes in ",[55,1715,973],{"href":220},". If you got here from a Cloudflare setup, the related trap is that ",[55,1718,1719],{"href":306},"Cloudflare Email Routing can't reply",". Our pricing is ",[55,1722,1723],{"href":185},"here",", all of it on one screen.",[44,1726,195],{"id":194},[31,1728,1729],{},"Google Workspace multiple domains pricing in 2026: domains are free, users are $7 to $26.40 each per month, and the intro discount (20% to 50% off, first 3 months, first 20 users) doesn't change the long-term math. Aliases give you free addresses but one shared inbox. Real inboxes per domain cost one user each.",[31,1731,1732],{},"If each user needs the suite, that's fair pricing. If you just need to read and reply on a pile of domains, you're paying for Drive storage you'll never open. That's the gap we're building for.",{"title":204,"searchDepth":205,"depth":205,"links":1734},[1735,1736,1737,1738,1739,1740,1741],{"id":1467,"depth":205,"text":1468},{"id":1548,"depth":205,"text":1549},{"id":1582,"depth":205,"text":1583},{"id":1651,"depth":205,"text":1652},{"id":1667,"depth":205,"text":1668},{"id":172,"depth":205,"text":173},{"id":194,"depth":205,"text":195},"2026-06-12","Google Workspace doesn't charge per domain, it charges per user. Here's the real 2026 math for running email on multiple domains, with the intro discounts included.",{"src":217},{},{"title":1447,"description":1743},"blog\u002Fgoogle-workspace-multiple-domains-pricing","Kcd-SXof6mT4mMQXlU6id_WH_W4k2dhxMGxiLZjZuS0",{"id":1750,"title":1751,"authors":1752,"badge":1755,"body":1757,"date":2058,"description":2059,"extension":215,"image":2060,"meta":2061,"navigation":219,"path":85,"seo":2062,"stem":2063,"__hash__":2064},"posts\u002Fblog\u002Fgoogle-workspace-alternative-for-multiple-domains.md","Google Workspace Alternative for Multiple Domains",[1753],{"name":22,"avatar":1754},{"src":24},{"label":1756},"Comparison",{"type":28,"value":1758,"toc":2050},[1759,1762,1765,1769,1776,1779,1791,1796,1800,1803,1806,1814,1817,1821,1824,1849,1852,1856,1972,1975,1980,1986,1992,1997,1999,2004,2006,2023,2029,2042,2044,2047],[31,1760,1761],{},"If you run a few projects, you have probably gone looking for a Google Workspace alternative for multiple domains and walked away confused. The pricing pages all talk about \"users.\" Nobody tells you what happens when you own five domains but only want to read and reply to the odd support email on each one.",[31,1763,1764],{},"So let's clear it up, then look at what actually works.",[44,1766,1768],{"id":1767},"the-thing-nobody-explains-about-google-workspace-and-multiple-domains","The thing nobody explains about Google Workspace and multiple domains",[31,1770,1771,1772,1775],{},"Here is the part that trips everyone up: Google Workspace does not literally charge \"per domain.\" You can add extra domains to one account as ",[73,1773,1774],{},"domain aliases"," for free.",[31,1777,1778],{},"Sounds great. Until you use it.",[31,1780,1781,1782,538,1785,548,1787,1790],{},"A domain alias just forwards mail to your one primary mailbox. So ",[35,1783,1784],{},"support@brand-a.com",[35,1786,965],{},[35,1788,1789],{},"team@brand-c.com"," all land in the same inbox, under the same identity. You can't give each brand its own real inbox. You can't separate clients. And when you reply, getting the right \"from\" address to stick is its own fight.",[31,1792,1793,1794,124],{},"The moment you want a genuinely separate mailbox per domain, you are back to paying for another user at $7\u002Fmonth on the annual plan ($8.40 month to month). Five real inboxes is $35\u002Fmonth for email you barely check. That is the \"per domain\" cost people complain about, even if the bill technically says \"per user.\" We broke down the full plan-by-plan math in ",[55,1795,58],{"href":57},[44,1797,1799],{"id":1798},"send-as-used-to-be-the-loophole-its-closing","Send-As used to be the loophole. It's closing.",[31,1801,1802],{},"For years the workaround was Gmail's \"Send mail as.\" Receive everywhere with free forwarding, then reply from your normal Gmail and set the from address to match the domain.",[31,1804,1805],{},"That worked because nobody checked. Now they check.",[31,1807,1808,1809,1813],{},"Through 2024 and 2025, Gmail, Yahoo, and Microsoft tightened the rules for authentication. If your \"from\" domain doesn't line up with SPF, DKIM, and DMARC, your reply gets marked as spam or bounced. Google spells this out in its own ",[55,1810,1812],{"href":1150,"rel":1811},[1152],"sender guidelines",". The hacky multi-domain setup that used to be free is now the reason your customer never got your reply.",[31,1815,1816],{},"So the two cheap paths both have a catch. Aliases give you one shared inbox. Send-As is quietly breaking. That's why people start hunting for a real alternative.",[44,1818,1820],{"id":1819},"what-to-actually-look-for","What to actually look for",[31,1822,1823],{},"Before comparing tools, get clear on what you need. For most multi-domain founders it comes down to four things:",[136,1825,1826,1832,1837,1843],{},[139,1827,1828,1831],{},[73,1829,1830],{},"A real inbox per domain",", not one shared pile.",[139,1833,1834,1836],{},[73,1835,155],{}," that doesn't climb every time you add a project.",[139,1838,1839,1842],{},[73,1840,1841],{},"Setup that takes minutes",", not a DNS rabbit hole per domain.",[139,1844,1845,1848],{},[73,1846,1847],{},"A way to send too",", ideally an API if you ship transactional email from an app.",[31,1850,1851],{},"Most tools nail one or two of these. Very few do all four.",[44,1853,1855],{"id":1854},"the-main-alternatives-compared","The main alternatives, compared",[698,1857,1858,1877],{},[701,1859,1860],{},[704,1861,1862,1865,1868,1871,1874],{},[707,1863,1864],{},"Tool",[707,1866,1867],{},"Price",[707,1869,1870],{},"Multi-domain",[707,1872,1873],{},"Real inbox UI",[707,1875,1876],{},"Send API",[715,1878,1879,1895,1910,1926,1942,1957],{},[704,1880,1881,1884,1887,1890,1893],{},[720,1882,1883],{},"Google Workspace",[720,1885,1886],{},"$7\u002Fuser\u002Fmo (annual)",[720,1888,1889],{},"Aliases free, real inboxes cost per user",[720,1891,1892],{},"Yes (Gmail)",[720,1894,747],{},[704,1896,1897,1900,1903,1906,1908],{},[720,1898,1899],{},"Fastmail",[720,1901,1902],{},"$5\u002Fuser\u002Fmo",[720,1904,1905],{},"Up to 100 domains",[720,1907,728],{},[720,1909,747],{},[704,1911,1912,1915,1918,1920,1923],{},[720,1913,1914],{},"Zoho Mail",[720,1916,1917],{},"From $1\u002Fuser\u002Fmo",[720,1919,728],{},[720,1921,1922],{},"Yes (clunky)",[720,1924,1925],{},"Via ZeptoMail",[704,1927,1928,1930,1933,1936,1939],{},[720,1929,269],{},[720,1931,1932],{},"$9\u002Fmo",[720,1934,1935],{},"30 domains",[720,1937,1938],{},"No (forwarding)",[720,1940,1941],{},"SMTP only",[704,1943,1944,1946,1949,1952,1954],{},[720,1945,287],{},[720,1947,1948],{},"$3\u002Fmo",[720,1950,1951],{},"Unlimited",[720,1953,747],{},[720,1955,1956],{},"SMTP\u002FIMAP",[704,1958,1959,1961,1964,1967,1969],{},[720,1960,201],{},[720,1962,1963],{},"$10\u002Fmo flat",[720,1965,1966],{},"5 domains, one inbox",[720,1968,728],{},[720,1970,1971],{},"Yes (REST)",[31,1973,1974],{},"A few honest notes on these, because the table flattens real differences.",[31,1976,1977,1979],{},[73,1978,1899],{}," is the quiet winner if you just want clean email and don't send from an app. $5 covers a lot of domains. The catch: no transactional API, so if your product sends password resets or receipts, you still need a second tool.",[31,1981,1982,1985],{},[73,1983,1984],{},"Zoho"," technically does everything. It has the inbox, the domains, and a sending service. The interface feels like 2014, and the free tier only covers one domain. If you can live with the UI, it's the cheapest \"real\" option.",[31,1987,1988,1991],{},[73,1989,1990],{},"ImprovMX and Forward Email"," are forwarding services, not inboxes. They're great at getting mail from your domain into Gmail. They don't give you a place to read and reply per brand. Cheap, but only half the job.",[31,1993,1994,1996],{},[73,1995,1883],{}," is still the right call if email is your main daily driver and you want the full Gmail and Docs suite. For a pile of side-project domains, you're paying suite money for a forwarding problem.",[44,1998,173],{"id":172},[31,2000,345,2001,2003],{},[55,2002,201],{"href":190}," for the specific person stuck in the gap above: someone running several domains who wants one place to receive and reply per domain, without the per-user math and without gluing three tools together.",[31,2005,1040],{},[136,2007,2008,2011,2017,2020],{},[139,2009,2010],{},"One inbox, every domain you own, $10\u002Fmonth flat. Adding a project doesn't change the bill.",[139,2012,2013,2014,2016],{},"Run it on a subdomain like ",[35,2015,1048],{}," so your main email stays exactly where it is.",[139,2018,2019],{},"Send transactional email from your app with a plain REST call, so you don't need Resend on top.",[139,2021,2022],{},"Add a few DNS records per domain and you're done in about five minutes.",[31,2024,2025,2026,2028],{},"To be straight with you: Mailyond is live now, shaped around real multi-domain setups. If the per-domain tax is your problem, ",[55,2027,191],{"href":190}," and bring your domains over.",[31,2030,2031,2032,2035,2036,2038,2039,124],{},"If you came to this from a Cloudflare setup, the related trap is that ",[55,2033,2034],{"href":306},"Cloudflare Email Routing can't send replies",". For a wider look at the per-seat problem across providers, see ",[55,2037,973],{"href":220},". For the full pricing breakdown, see the ",[55,2040,2041],{"href":185},"pricing section",[44,2043,195],{"id":194},[31,2045,2046],{},"There is no perfect Google Workspace alternative for multiple domains yet, but there are good fits depending on what you need. Want plain email and don't send from an app? Fastmail. Want the cheapest full setup and can stomach the UI? Zoho. Just need forwarding into Gmail? Forward Email or ImprovMX.",[31,2048,2049],{},"Want one flat-priced inbox per domain plus an API to send, built for people juggling projects instead of running a company? That's the gap we're filling.",{"title":204,"searchDepth":205,"depth":205,"links":2051},[2052,2053,2054,2055,2056,2057],{"id":1767,"depth":205,"text":1768},{"id":1798,"depth":205,"text":1799},{"id":1819,"depth":205,"text":1820},{"id":1854,"depth":205,"text":1855},{"id":172,"depth":205,"text":173},{"id":194,"depth":205,"text":195},"2026-06-02","Google Workspace bills per user and Send-As keeps breaking. Here's how to run email across multiple domains without paying per domain.",{"src":866},{},{"title":1751,"description":2059},"blog\u002Fgoogle-workspace-alternative-for-multiple-domains","Aaku4z5VnZBgeG5EIrTMC-TQRnd302RlZw6tlH8dt4Q",{"id":2066,"title":2067,"authors":2068,"badge":2071,"body":2072,"date":2341,"description":2342,"extension":215,"image":2343,"meta":2344,"navigation":219,"path":306,"seo":2345,"stem":2346,"__hash__":2347},"posts\u002Fblog\u002Fcloudflare-email-routing-reply.md","Cloudflare Email Routing Can't Reply: Here's the Fix",[2069],{"name":22,"avatar":2070},{"src":24},{"label":26},{"type":28,"value":2073,"toc":2333},[2074,2080,2083,2087,2090,2101,2104,2108,2111,2116,2119,2122,2127,2130,2133,2135,2138,2159,2162,2166,2266,2269,2278,2285,2287,2292,2295,2315,2320,2328,2330],[31,2075,2076,2077,2079],{},"You set up Cloudflare Email Routing in five minutes, pointed your MX records, and mail to ",[35,2078,245],{}," started landing in Gmail. Then a customer replied, you hit reply, and the message went out from your personal Gmail address instead of your domain. So the obvious question: how do you actually reply to email with Cloudflare Email Routing?",[31,2081,2082],{},"Short answer: not from Email Routing. Cloudflare did add outbound sending in 2025, but it's a separate, API-only product with no inbox and no reply button, and it only covers domains hosted on Cloudflare. So if you just want to read a customer's email and reply from your domain, you still can't. It's worth understanding why before you reach for a workaround that quietly breaks.",[44,2084,2086],{"id":2085},"cloudflare-email-routing-is-receive-only-by-design","Cloudflare Email Routing is receive-only by design",[31,2088,2089],{},"Cloudflare Email Routing forwards mail. That's the whole feature. It takes a message sent to your domain and drops it into another mailbox you already own. It does not send mail, and there is no \"reply\" button anywhere in it. People have asked for \"allow replies\" in it since 2022, and that hasn't changed.",[31,2091,2092,2093,2097,2098,124],{},"Cloudflare did finally ship outbound sending, but as a separate product: ",[55,2094,489],{"href":2095,"rel":2096},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Femail-service\u002F",[1152]," added an Email Sending feature in 2025, generally available since April 2026. Before you get excited, read the fine print. It sends programmatically only, through a REST API, SMTP, or Workers bindings. There is no inbox and no reply button. And it only works for domains hosted on Cloudflare. It's built for an app firing off transactional email, not for a person reading a customer message and clicking reply. We cover its setup, pricing, and limits in ",[55,2099,2100],{"href":263},"our guide to sending email with Cloudflare Email Routing",[31,2102,2103],{},"So between the two products, Cloudflare can now receive your mail and let your code send mail. What it still doesn't give you is a place to read an email and reply to it from your domain. That part is your problem to solve.",[44,2105,2107],{"id":2106},"the-workarounds-and-why-each-one-bites-back","The workarounds, and why each one bites back",[31,2109,2110],{},"Everyone lands on the same two hacks. Both look fine on day one.",[31,2112,2113],{},[73,2114,2115],{},"Workaround 1: Gmail \"Send mail as\" + SMTP",[31,2117,2118],{},"You add your domain address to Gmail under Settings, point it at an SMTP server, and now you can pick your domain as the \"from\" when you reply.",[31,2120,2121],{},"This used to just work because nobody checked the authentication. That era is over. Through 2024 and 2025, Gmail, Yahoo, and Microsoft tightened the rules. If your \"from\" domain doesn't pass SPF, DKIM, and DMARC, your reply gets filtered to spam or bounced outright. Cloudflare forwarding doesn't sign your outbound mail, so the Send-As path is now the reason your customer never saw your answer. You think you replied. They think you ignored them.",[31,2123,2124],{},[73,2125,2126],{},"Workaround 2: Add a real sending service (Resend, Postmark, SES)",[31,2128,2129],{},"So you bolt a transactional email service onto the same domain to handle sending. Reasonable. Except sending services want their own DNS, and the moment you try to run a sender plus Cloudflare Email Routing on the same domain, you hit the MX conflict: receiving wants Cloudflare's MX records, the sender wants its own setup, and they fight. People burn an afternoon on this and post about it in the Cloudflare forums regularly.",[31,2131,2132],{},"Even when you get it working, you now run two stacks. Cloudflare for receiving. Another tool for sending. A reply isn't one action anymore, it's a coordination problem. And you still don't have a single place to read and answer mail across your domains.",[44,2134,1198],{"id":1197},[31,2136,2137],{},"Strip away the workarounds and the requirement is simple:",[136,2139,2140,2145,2150,2154],{},[139,2141,2142,2144],{},[73,2143,677],{}," mail on your domain (Cloudflare does this fine).",[139,2146,2147,2149],{},[73,2148,1015],{}," from that same domain, properly authenticated so it lands in the inbox.",[139,2151,2152,1218],{},[73,2153,1217],{},[139,2155,2156,2158],{},[73,2157,1026],{}," if you ship transactional email like password resets.",[31,2160,2161],{},"Cloudflare covers the first item. The other three are the gap.",[44,2163,2165],{"id":2164},"the-realistic-options","The realistic options",[698,2167,2168,2183],{},[701,2169,2170],{},[704,2171,2172,2174,2176,2178,2180],{},[707,2173,1248],{},[707,2175,1251],{},[707,2177,1254],{},[707,2179,143],{},[707,2181,2182],{},"Sends from app",[715,2184,2185,2198,2213,2227,2240,2253],{},[704,2186,2187,2190,2192,2194,2196],{},[720,2188,2189],{},"Cloudflare Email Routing alone",[720,2191,728],{},[720,2193,747],{},[720,2195,747],{},[720,2197,747],{},[704,2199,2200,2203,2205,2208,2210],{},[720,2201,2202],{},"Cloudflare Routing + Email Service",[720,2204,728],{},[720,2206,2207],{},"No (API only, no inbox)",[720,2209,747],{},[720,2211,2212],{},"Yes (CF-hosted domains)",[704,2214,2215,2218,2220,2222,2225],{},[720,2216,2217],{},"Cloudflare + Gmail Send-As",[720,2219,728],{},[720,2221,1286],{},[720,2223,2224],{},"Sort of (Gmail)",[720,2226,747],{},[704,2228,2229,2232,2234,2236,2238],{},[720,2230,2231],{},"Cloudflare + a sending service",[720,2233,728],{},[720,2235,1301],{},[720,2237,747],{},[720,2239,728],{},[704,2241,2242,2245,2247,2249,2251],{},[720,2243,2244],{},"Fastmail \u002F Google Workspace",[720,2246,728],{},[720,2248,728],{},[720,2250,728],{},[720,2252,747],{},[704,2254,2255,2257,2259,2261,2264],{},[720,2256,201],{},[720,2258,728],{},[720,2260,728],{},[720,2262,2263],{},"Yes, all domains",[720,2265,739],{},[31,2267,2268],{},"A couple of honest notes.",[31,2270,2271,2272,2274,2275,2277],{},"If you only own one domain and mostly want clean personal email, ",[73,2273,1899],{}," ($5\u002Fmonth) or ",[73,2276,1883],{}," is the calm choice. They receive and send properly with no glue. The pain only really shows up when you run several domains and don't want a separate paid mailbox for each one.",[31,2279,2280,2281,2284],{},"If you're technical and happy maintaining two services, ",[73,2282,2283],{},"Cloudflare for receive plus a sender"," works once you get past the MX conflict. Cloudflare's own Email Service can be that sender now, which keeps you in one vendor, but it's API-only and only for domains on Cloudflare, so it still doesn't give a non-developer a place to read and reply. Either way you're signing up for ongoing setup per domain, not a five-minute job.",[44,2286,173],{"id":172},[31,2288,345,2289,2291],{},[55,2290,201],{"href":190}," for the exact spot Cloudflare Email Routing leaves you in: you can receive on all your domains, but replying and managing it is a mess of forwarding rules and half-working hacks.",[31,2293,2294],{},"The idea:",[136,2296,2297,2303,2306,2309,2312],{},[139,2298,2299,2300,2302],{},"Receive on a domain or subdomain like ",[35,2301,1048],{}," with one short DNS setup, verified in the app.",[139,2304,2305],{},"Reply from that domain, signed correctly, so your answer lands in the inbox instead of spam.",[139,2307,2308],{},"See and answer mail from every domain you own in one place.",[139,2310,2311],{},"Send transactional email from your app with a plain REST call, so you don't need a second service.",[139,2313,2314],{},"Keep your main email on Gmail or Google Workspace. Mailyond runs alongside it, not instead of it.",[31,2316,2317,2318,124],{},"To be straight: Mailyond is live now, built around real multi-domain setups. If \"I can receive but I can't reply\" is your problem, ",[55,2319,191],{"href":190},[31,2321,2322,2323,2325,2326,124],{},"For the cost angle on all this, see why per-user billing makes Google Workspace awkward for multi-domain owners in our ",[55,2324,1075],{"href":85},", or check the ",[55,2327,186],{"href":185},[44,2329,195],{"id":194},[31,2331,2332],{},"Cloudflare Email Routing is great at one job: getting mail to your domain into a mailbox you already have. It won't send your reply, and Cloudflare's newer Email Service only sends programmatically, with no inbox to reply from and only for domains on Cloudflare. Send-As is breaking under tighter authentication rules, and bolting on a separate sender means two stacks and an MX fight. If you run more than a couple of domains and want to actually reply from them without the duct tape, that's the gap we're filling.",{"title":204,"searchDepth":205,"depth":205,"links":2334},[2335,2336,2337,2338,2339,2340],{"id":2085,"depth":205,"text":2086},{"id":2106,"depth":205,"text":2107},{"id":1197,"depth":205,"text":1198},{"id":2164,"depth":205,"text":2165},{"id":172,"depth":205,"text":173},{"id":194,"depth":205,"text":195},"2026-05-28","Replying to email forwarded by Cloudflare Email Routing sends from your personal Gmail. Why Send-As now fails DMARC, and how to reply from your domain.",{"src":459},{},{"title":2067,"description":2342},"blog\u002Fcloudflare-email-routing-reply","7Z_9dfy0tz1LRPmvckTezZTNfR6Z7YI68FL8eWCoZqY",1784750516686]