Buyer Guides & Decision

Best email forwarding service for custom domains in 2026

Pick by tests, not adjectives. Keep Gmail or Outlook. Prove inbound from another mailbox. Free receives. Solo $40/yr starts send-as.

MailerZ editorial · Secuno LLC16 min read

The best email forwarding service for a custom domain in 2026 is the one that survives tests you can run this week: one MX set, Header From still the original author, leftover host records gone, a hop you can read, and send-as only if you paid for it. Adjectives age badly. Leftover MX does not. MailerZ is one product that takes that split: inbound MX plus optional authenticated SMTP around Gmail or Outlook. It is not a suite and not an inbox-placement SLA.

Best email forwarding service custom domain 2026: tests for MX, Header From, leftover MX, and paid send-as
Pick by jobs you can fail in public. Paying more does not file Primary.

Quick answer for best email forwarding service custom domain

In 2026 the shortlist is still “keep the inbox you trust, move MX to a forwarder that does not rewrite Header From, delete leftover MX, prove inbound from another mailbox.” MailerZ Free does that on one domain with ten aliases, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year when the domain must send. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm MailerZ pricing. Limits are not an inbox promise.

Google’s people-first content guidance is about pages, not SMTP; see creating helpful, reliable, people-first content. Do not treat a ranking essay as a deliverability badge. IETF RFC 5321 — Simple Mail Transfer Protocol is still how mail moves.

A “best” list that ranks vendors by adjectives without leftover MX, From-rewrite policy, and send-as ceilings is a brochure. Cloudflare Email Routing is inbound routing. ImprovMX is the closest commercial class. Microsoft 365 and Google Workspace are suites. None of them become MailerZ leftover-MX handling, stored hops, or paid SMTP because a 2026 headline named them.

Envelope SRS and an untouched Header From are the inbound rule that still matters. A rewrite to the relay domain can make the hop “authenticate” as the relay and fail as the author. MailerZ does not rewrite Header From, Subject, Date, Message-ID, body, or MIME. Destination filters stay with Gmail or Outlook.

The user problem and the decision criteria

People search “best email forwarding service custom domain” because last year’s $0 tool rewrote From, or leftover Google MX ate half the mail, or send-as was implied and never shipped. The 2026 version of that problem is the same physics with newer admin UIs.

2026 criteria for a custom-domain forwarder
QuestionIf yesIf no
Do you already trust Gmail or Outlook as the archive?A forwarder can be enough.You are shopping for hosting.
Must replies show the domain?Need paid authenticated SMTP. Free cannot.Inbound-only is a valid 2026 setup.
Can you delete leftover MX?Cutover is possible.Do not start. Split MX looks random.
Does the vendor rewrite Header From?That is a different product. Threads get worse.Alignment to the author can survive the hop.
Need Calendar, Drive, lockable mailboxes?Buy a suite. A forwarder will not grow into one.Do not buy seats for printed aliases.

Product surface: MailerZ features. Leaving another vendor: migration planner.

A 2026 buyer also confuses “best” with “most features on a comparison grid.” Catch-all, plus tags, disposable identities, and campaign APIs look like completeness. They are other jobs. If you print three role addresses and live in Gmail, you need MX, aliases, Header From intact, and maybe send-as. Ranking a vendor higher because it also mints random aliases is how you buy the wrong object.

Support quality is a real criterion and a hard one to fake in a blog. What you can demand without a quote is evidence: delivery history with a remote SMTP response, a hold queue you can open, and DNS diagnostics that do not invent a health score. If the vendor can only say “check spam,” you will debug 2026 the same way people debugged 2019.

Multi-domain agencies should count domains and operator seats, not “best for startups” badges. Free is one domain. Solo is five domains. Starter starts at eight. Business 25. Agency 100. If you already know you will onboard twenty client zones this year, start on a card that can hold them. Migrating MX twice in one year because you liked a $0 badge is not a best practice. Count the zones before you fall in love with a sticker.

A last 2026 check: can you explain leftover MX to the person who owns DNS? If not, the “best” vendor will still lose mail the first week. Write that explanation down. Then change records. That sentence is worth more than a roundup table.

Technical mail flow

A 2026 forwarder still speaks SMTP. The sending server looks up MX, connects, offers MAIL FROM, names recipients, and transfers content. MailerZ accepts for a verified domain and a matching alias, stores required content, then forwards to the destination you verified. Envelope SRS may rewrite the return path. Header From stays the author. Subject, Date, Message-ID, body, and MIME stay as received.

Custom domain forwarding flow in 2026: accept, SRS forward with Header From intact, Gmail or Outlook store
Inbound, hold, leftover MX, and send-as still fail independently. A 2026 sticker does not merge them.

Unknown local-parts on Free are held. Paid plans can forward them when you enable catch-all FORWARD. Holding is the safer default while you learn what the internet will try. Enabling catch-all on day one to look “complete” is how harvested directories become the inbox.

Outbound SMTP exists on paid plans only. The session authenticates, checks the From identity, applies hourly and monthly caps, and submits. Unauthorized or unhosted recipients get 550. MailerZ is not an open relay. Free cannot finish this hop. Do not paste a Free dashboard into Gmail Send mail as.

SPF, DKIM, and DMARC evaluate authorization. IETF RFC 7208 — Sender Policy Framework (SPF), IETF RFC 6376 — DomainKeys Identified Mail (DKIM), and IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC) are the documents. They do not move mail into Primary. A rewrite of Header From can make the hop authenticate as the relay. That is why From preservation is a 2026 selection rule, not a slogan.

Recovery is 14 days on Free and 90 days on paid. That store is hop evidence, not a second archive and not legal hold. Gmail or Outlook remains the system of record you search next year.

Leftover MX is still the silent 2026 outage. Old Google, Microsoft, or registrar records beside the new set split inbound. Some vendors reach Exchange. Some reach MailerZ. It looks random. Treat leftover MX as a hard stop on every vendor, including the one you just called best.

Self-send from Gmail to the same Gmail account can short-circuit in 2026 the same way it did five years ago. Budget an external mailbox. The probe is part of choosing a service, not optional polish.

Campaign mail is still out of scope. If the domain is a newsletter, buy a campaign platform. Solo’s 2,500 outgoing and 20 send-as per hour, Starter 5,000 and 40, Business 12,000 and 60, Agency 20,000 and 60 are stop signs, not negotiation.

Plus addressing is not a 2026 substitute for a domain alias. you+billing@gmail.com is a filter tag. Forms reject plus signs. A named billing@ on your domain still works because the local-part is ordinary. Privacy aliases that mint random strings are a third product. They hide a personal inbox from shops. They are a poor invoice identity. Do not rank a privacy tool as the best custom-domain forwarder unless hiding is the job.

Shared mailboxes inside Microsoft 365 and Google Groups look like role addresses and are still suite objects. They follow suite MX. A MailerZ alias follows MailerZ MX. Dual MX is not a clever 2026 hybrid. It is split delivery. Pick one inbound owner.

Disposable inboxes remain a trap for account recovery. If you recover a bank with a burner, the burner dies and the bank mail dies. A custom-domain alias is built to stay on the invoice next year. That durability is part of “best,” even when the sticker is $0.

Operator seats on Starter and above are dashboard logins. They are not hosted mailboxes. Agency’s 50 seats and 100 domains are for people who run many zones. If you need 100 IMAP users, you are not in the forwarding category anymore.

Catch-all FORWARD is still a policy, not a completeness badge. Free holds leftovers. Watch the hold queue before you pay to forward noise. A 2026 “best” setup that enables catch-all on day one is optimizing for “it arrived,” not for “you can explain what arrived.”

Header From preservation is not a paid add-on. Free and paid share it. If a cheaper tool rewrites From, you are no longer comparing price. You are comparing whether the author survived. MailerZ does not rewrite that header on any plan.

Step-by-step setup and decision path

  1. Write the 2026 job in one line

    Example: “Keep Gmail. Print hello@ and billing@. Reply as the domain.” That line excludes Free and excludes a suite if nobody needs Calendar as the system of record.

  2. Reject vendors that rewrite Header From if author identity matters

    Ask what they do to From, Subject, and Message-ID. If the answer is “we make it look local,” you are not comparing forwarders. You are comparing a relay identity.

  3. Add one domain and the aliases you can name

    Verify TXT. Map destinations. Do not loop. Free allows ten aliases. Solo allows twenty-five. Do not start a “best of 2026” bake-off on Free if you already printed twenty roles.

  4. Publish one MX set and delete leftovers

    Copy the dashboard MX. Read the public set from two resolvers. Remove obsolete Google, Microsoft, and registrar records. Paying does not merge two sets.

  5. Prove inbound from another mailbox

    Unique subject, Header From, delivery history. If history is empty, MX or the alias is wrong. If history says 250 and Gmail is empty, the destination filtered. Neither is an inbox SLA breach.

  6. Add send-as only after inbound works

    Upgrade to Solo or higher. Create SMTP. Add Gmail Send mail as or Outlook’s manual SMTP identity. Send outward. Confirm pricing the day you buy.

2026 decision path for best custom domain email forwarding service: job, MX, probe, paid send-as
Best practice is a test sequence, not a ranked table of logos.

Failure modes and proof

2026 failure, likely cause, next action
What you seeLikely causeProof
Some senders hit the old hostLeftover MX.Public MX from two resolvers.
Via / rewritten From on inboundThe vendor rewrote Header From, or you are reading the old copy.Raw headers. MailerZ should keep the author.
Gmail Send mail as will not verifyInbound unproven, leftover MX, or still on Free.Plan send-as flag, history, spam folder.
Self-send never appearsClient short-circuit.Repeat from another provider.
History delivered, empty inboxDestination filter.Spam, promotions, remote 250. No inbox SLA.
550 on sendUnauthorized From, unhosted domain, or cap.SMTP response, hourly and monthly counters.
Recovery gone after two weeksFree store ended.Paid 90-day store. Gmail is the archive.
Typos in holdFree HOLD or catch-all not FORWARD.Create the named alias.

Proof is a header block plus a MailerZ event. Do not send SMTP passwords. Do not publish verification tokens. A 2026 “best” vendor that cannot show a remote SMTP reason is asking you to debug on vibes.

MailerZ workflow and product boundary

MailerZ is a custom-domain delivery layer operated by Secuno LLC. Point MX at MailerZ. Mail for a verified domain lands in Gmail or Outlook. Paid plans add SMTP. Site: mailerz.net. App: mail.mailerz.net.

  • Free $0: 1 domain, 10 aliases, 14-day store, send-as disabled, SMTP and API disabled.
  • Solo $40/yr: 5 domains, 25 aliases, 90-day, 2,500 outgoing, 20 send-as/hr.
  • Starter $8/$80: 8 / 50 / 5 seats, 5,000 outgoing, 40/hr.
  • Business $19/$190: 25 / 200 / 25, 12,000 outgoing, 60/hr.
  • Agency $39/$390: 100 / 500 / 50, 20,000 outgoing, 60/hr.
  • Unlimited $99/$990: uncapped domains and aliases, 180-day store, 100,000 outgoing, 300/hr.

MailerZ is not IMAP, not a suite, not an open relay, not an inbox SLA, not SOC 2 / ISO 27001 / HIPAA. Controls: Security and Trust Center. Unauthorized send returns 550 / 550 5.7.1. Annual Starter, Business, and Agency include two months free versus monthly. Solo has no monthly option. Dashboard seats are operators, not Gmail logins.

Cost, alternatives, and trade-offs

A 2026 bake-off that only compares stickers will pick the wrong object. Compare leftover-MX handling, From policy, store length, send-as ceilings, and whether you already paid for Gmail. Then read pricing.

2026 shapes, not a ranked logo table
ApproachYou getYou give up
MailerZ FreeInbound proof, ten aliases, Header From intact.Send-as, 90-day store, extra domains.
MailerZ paidSMTP, longer store, higher ceilings, optional catch-all FORWARD.Still no mailbox, no inbox SLA.
Another inbound routerSometimes enough if send-as is out of scope.Their rewrite rules and logging. Read their docs.
SuiteHosted store, admin, Calendar. Quote the vendor live.Per-user cost if Gmail already held the mail.

Cloudflare Email Routing remains inbound routing in 2026. ImprovMX remains the closest commercial class. Compare live plans, not last year’s screenshot. A best email forwarding service custom domain setup is the one whose tests you can recite before MX changes.

Time is still a line item. Leftover MX costs more than Solo. A Free-plan branded-reply promise costs more than the upgrade. Budget one external inbound test as part of the 2026 cutover.

If every teammate needs a hosted mailbox, the suite is the honest product. A forwarder will look “incomplete” because it is incomplete for that job. If two people need seats and twelve printed names are routes, price two seats plus MailerZ, not fourteen seats.

Quote vendors the day you buy. This page can drift. Microsoft and Google change suite packaging. Forwarders change alias ceilings. The tests do not: one MX set, Header From, leftover cleanup, external probe, send-as only when paid. That sequence is the 2026 definition of best that still works in 2027.

If you must bake off two forwarders, do it in series, not with dual MX. Prove vendor A on a spare domain or a spare week. Save the MX set. Cut over. Probe from another mailbox. Then, if you still need vendor B, repeat. Parallel MX is not a 2026 A/B test. It is split delivery. The vendor that “lost” half the mail may have been the leftover host, not the worse product.

MailerZ is not a Gmail replacement and not a hosted mailbox. Keep the inbox you already search. Use this layer when the job is a domain route you can prove, plus paid send-as when From must travel. If every person needs a stored mailbox, Calendar, and admin, buy the suite and stop ranking forwarders.

Registrar cost sits next to the forwarder and is not optional. A .com renewal is often tens of dollars. Quote your registrar. DNS at the same registrar is usually included. That line does not change when you move from Free to Solo. The delivery layer is the incremental bill.

Monthly versus yearly is cash flow. Starter, Business, and Agency yearly cards include two months free versus twelve monthly payments. Solo is $40 per year only. Do not prepay Agency because a 2026 roundup used a large integer.

Open a body for break-glass recovery and expect an audit row. That is a control, not a SOC 2 badge. Do not send SMTP passwords or verification tokens to support. The artifacts that close a “best vendor” argument are the dated pricing card, the public MX set, and hop history with a remote SMTP response.

A bake-off ticket that still works next year

Logos change. Alias ceilings change. The artifacts that still decide a vendor in 2027 are the same ones that should decide one this week: public MX from two views, Header From on original, a unique-subject history row, leftover hosts named or “none,” and whether send-as is on the plan you actually bought. Paste those five lines before anyone ranks adjectives. If a vendor cannot show hop history, you cannot finish the ticket.

Do the bake-off in series on a spare domain, not with dual MX. Confirm MailerZ pricing the day you buy. A 2026 roundup screenshot is not a card. Limits are not an inbox SLA.

FAQ

What is the safest way to handle best email forwarding service custom domain?

Name the jobs you can test: one MX set, Header From intact, leftover host MX deleted, an external inbound probe, and paid send-as only if replies must show the domain. MailerZ Free proves inbound. Solo at $40 per year is the smallest send-as plan. Do not pick a vendor by an adjective or an inbox-placement promise.

Does this require a new mailbox?

No. A custom-domain forwarder is not IMAP. Gmail or Outlook remains the store. Buy a suite if every person needs a hosted mailbox, Calendar, and admin.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a mailbox you already use. Branded replies need paid SMTP plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one forwarder MX set, and SPF, DKIM, and DMARC when you send. Leftover Google, Microsoft, or registrar MX is a hard stop in 2026 the same as it was in 2021.

What should I test before production?

Send a uniquely titled message from an unrelated mailbox. Confirm Header From and delivery history. If send-as is required, upgrade first and send outward. Self-send can hide routing errors.

Key takeaways

  • Best in 2026 means tests: one MX set, Header From intact, leftover MX gone, external probe.
  • MailerZ Free proves inbound. Solo $40/yr starts send-as.
  • Starter $8/$80, Business $19/$190, Agency $39/$390. Confirm /pricing.
  • Limits are not an inbox-placement SLA.
  • Envelope SRS only. Header From untouched.
  • Not IMAP, not a suite, not an open relay, not SOC 2.
  • Self-send lies. Probe from another mailbox.
  • Suites are for stored humans. Forwarders are for routes.

Conclusion and next action

If you came here for the best email forwarding service for custom domains in 2026, skip the logo table. Write the jobs. Keep the inbox you trust. Publish one MX set. Delete leftovers. Prove inbound from somewhere else. Pay for send-as only if the domain must leave as From. MailerZ fits that sequence. It does not replace a suite or file Primary.

Ready to run the 2026 tests

Start free with one domain and prove inbound.

Inbound on Free. Solo when send-as is the job. Sign in if the domain is already there.

Review quarterly, or sooner if MailerZ limits or provider DNS guidance changes. Author: MailerZ editorial, Secuno LLC.