The best email alias service for a custom domain maps durable public names to inboxes you already use. It is not a mailbox shop and not a plus-tag trick. Choose the operator that accepts exact local-parts on one MX set, keeps Header From intact, and lets you move the destination later. Prove inbound before you print the address.
Quick answer for best email alias service
Pick a best email alias service by the job, not by a feature checklist. The job is a printed string such as hello@yourdomain.com or billing@yourdomain.com that still works when the person behind it changes. That string is a recipient the domain’s MX must accept. It is not a tag on you@gmail.com, and it is not a new Workspace seat unless you decided to buy the suite.
MailerZ is one product in that class: inbound MX plus authenticated SMTP on paid plans, around the inbox you already operate. Envelope MAIL FROM can use Sender Rewriting Scheme. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. It is not Google Workspace, not IMAP, and not an open relay. Positioning for this row: durable aliases that route to existing inboxes.
Internet mail delivers to a recipient string. IETF RFC 5321 — Simple Mail Transfer Protocol is the transport standard. The sending server looks up MX, offers MAIL FROM, names RCPT TO, and transfers content. The receiving system decides whether that local-part is an alias, unknown, or a hosted mailbox. A “best” service is the one whose decision matches the addresses you actually publish.
Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only with fifteen aliases. Starter is $8 monthly or $80 yearly with fifty aliases. Business is $19 or $190 with two hundred. Agency is $39 or $390 with five hundred. Confirm numbers on MailerZ pricing. Those ceilings are inventory, not an inbox-placement SLA.
Product language for routes lives on aliases and catch-all controls. Catch-all is a policy for unknown local-parts. It is not unlimited aliases and not Gmail-style plus stripping on your domain. Inbound forwarding is covered on custom-domain email forwarding.
The user problem and the decision criteria
People shop “best email alias service” after a cheap trick fails. They used Gmail plus tags as public identities. Forms rejected the plus. A vendor stored you+acme@gmail.com as the account email. Or they bought a mailbox seat for support@ when nobody needed a second login. Or a registrar “forwarding” toggle rewrote From and broke replies.
The other failure is inventory blindness. Twenty experimental local-parts, no owner, catch-all on, and a Free plan that only allows three aliases. The service is blamed for a list the operator never mapped.
Decide with tests.
| Question | If yes | If no |
|---|---|---|
| Must the printed address stay when the person changes? | You need a named alias with a replaceable destination. | A personal mailbox local-part may be enough. |
| Is Gmail or Outlook already the archive? | A delivery layer is the product class. | You are shopping for hosting, not aliases. |
| Must replies show the domain? | You need paid authenticated SMTP, not inbound-only. | Free inbound aliases can be the whole job. |
| Will you publish more names than the plan allows? | Count aliases before you cut MX. Upgrade or delete experiments. | Start on Free and prove three routes. |
| Do you want every unknown local-part to arrive? | That is catch-all, not “best aliases.” Know the spam cost. | Hold unknown mail. Map what you print. |
Plus addressing is a mailbox convention. Google documents it on Gmail’s own domain; see Google Gmail Help — Using an address alias (plus addressing). IETF RFC 5233 — Sieve Email Filtering: Subaddress Extension describes subaddressing for filters. Neither document requires your custom-domain MX to strip +. A service that does not parse plus tags is not “worse.” It is honest about RCPT TO.
Role addresses belong on named aliases. sales@, support@, and billing@ should not be plus tags on a founder Gmail. They should not be extra Workspace seats if nobody logs into those seats. That is the money the alias model saves.
Contractors expose a bad alias choice quickly. If vendors@ points at a freelancer’s personal Gmail, you cannot take the history with you when the contract ends. The best service lets you change the destination in minutes. It cannot unsync a year of threads that already landed in that personal account. Pick destinations the company can keep.
Multi-domain agencies have a different ceiling. Free is one domain. Solo is three domains. Starter, Business, and Agency raise the domain cap. If you run ten client zones, count domains first, then aliases per zone. A “best alias service” that only hosts one zone will fail the agency job even if the alias UX is pretty.
Forms and banks still reject unusual local-parts. Underscores, long tags, and plus signs die in validation. Prefer short role names. Test the signup form that will store the address before you print it on packaging. The service cannot fix a form that refuses +.
Technical mail flow
An alias service is an MX answer plus a recipient table. Everything else is optional: catch-all, send-as, recovery storage. Judge the optional pieces after the table works.
Inbound
A customer sends to hello@yourdomain.com. Their server asks DNS for MX. If MailerZ MX is the published answer, the message arrives at MailerZ. The edge checks verification and whether the recipient matches an alias, a route, or an intentional catch-all rule. Unknown addresses on Free are held. Paid plans can forward unknown recipients when you enable that behavior.
After acceptance, MailerZ forwards to the destination you verified. Visible From stays the original sender. Envelope return path may use SRS so bounces do not impersonate that sender. Delivery history records the destination response. Gmail can still file the copy in spam. That is Gmail’s decision.
What is not an alias
A plus tag on your domain is another recipient string unless you mapped that exact local-part. Catch-all forward, if paid and enabled, can deliver unknowns. That is not the same as Gmail stripping + on gmail.com. Do not choose a service because marketing implied infinite tags.
Outbound
Receiving an alias is not sending as that alias. Free has no send-as. Paid plans add authenticated SMTP within hourly and monthly limits. You add MailerZ as Gmail’s outgoing server or Outlook’s manual SMTP identity. Unauthorized or unhosted send gets SMTP 550. Publish SPF, DKIM, and DMARC from the dashboard. 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) authorize. They do not inbox. The send surface is send and reply as your domain.
Alignment still depends on the visible From matching what those records authorize. If a leftover forwarder rewrites Header From, DKIM and DMARC stop lining up. MailerZ does not rewrite Header From. That is a selection criterion, not a slogan. Ask any candidate vendor what they change on the hop. If they cannot answer, they are not the best alias service for a domain that already has a reputation.
Self-send is a bad alias test. Gmail can short-circuit a message from an account to itself and skip the public MX path. You will think the alias failed when you never left the mailbox. Probe from another provider. Title the message uniquely so history and destination search can be matched by hand.
Loops look like vanishing mail. If the destination is another address on the same domain that routes back to the first alias, the hop never settles. Destinations must be real inboxes on Gmail, Outlook, or another host you control—not a second alias on the same MX.
Step-by-step setup and decision path
Choose, then cut. Do not publish MX for a vendor whose alias ceiling you have not counted.
Write every address you will print
Website, invoices, app stores, vendor accounts. If it is only a personal Gmail filter tag, it does not belong on this list.
Name the store
Gmail, Outlook, or a hosted suite. MailerZ is never the store. If you need Calendar and admin-managed seats, stop and buy the suite.
Count aliases against a plan
Three on Free. Fifteen on Solo. Fifty on Starter. Two hundred on Business. Five hundred on Agency. If the printed list is twelve names, Free is the wrong first invoice if you intend to map all twelve on day one.
Add one domain and map the names
Publish the verification TXT. Create each alias and destination. Complete destination verification. Do not point a destination back at the same alias.
Publish one MX set and delete leftovers
Copy MailerZ MX. Remove Google, Microsoft, registrar, or old-forwarder MX. Leftover MX is a hard stop. Use DNS diagnostics if the public set looks mixed.
Prove inbound from a different mailbox
Unique subject. Unrelated provider. Confirm Header From and history. Self-send lies.
Leave catch-all off until you have a reason
Unknown mail is held on Free. Paid catch-all forward collects typos and harvested guesses. Map
support@instead of hoping catch-all is a best-alias feature.Add send-as only for names you reply from
Free stops here. Paid SMTP, then Gmail Send mail as or Outlook SMTP. Field clicks: Gmail send-as guide.
Failure modes and proof
Most “this alias service is broken” reports are leftover MX, an unmapped local-part, or send-as attempted on Free. Work the evidence.
| What you see | Likely cause | Proof to collect |
|---|---|---|
| Mail to a plus-tagged domain address never arrives | Exact local-part was unknown. Free held it. | Alias list. History for that recipient. Catch-all setting. |
| Some senders reach the old host | Leftover MX or cache. | Public MX from two resolvers. |
| Cannot create the fourth alias on Free | Ceiling is three. Expected. | Plan card on pricing. Delete experiments or upgrade. |
| Replies leave as @gmail.com | No paid send-as, or Gmail used the default identity. | Plan. From selector. SMTP credential exists. |
| Self-send never appears | Gmail short-circuited to itself. | Repeat from another provider. |
| Held or 550 on send | Unauthorized From, unhosted domain, or plan limit. | Exact SMTP response in delivery history. |
| Loop or vanished mail | Destination pointed back at the alias. | Route table. Fix the destination to a real inbox. |
Proof is a pair: destination copy or sanitized headers, and the MailerZ event with timestamp plus remote response. Do not send SMTP passwords to support. Inbox placement is not proof the alias is correct.
Recovery storage is 14 days on Free and 90 days on paid plans. That is hop evidence, not a company archive. If you need legal hold, keep it in Gmail or a suite.
MailerZ workflow and product boundary
MailerZ is a custom-domain email delivery layer operated by Secuno LLC. The live site is mailerz.net. The app is mail.mailerz.net. An alias here is a durable routing rule: public name, destination inbox, change the destination later without reprinting the address.
What MailerZ does
- Accept inbound mail for verified domains and configured aliases.
- Preserve Header From on the forward into Gmail or Outlook.
- Hold unknown recipients on Free; allow paid catch-all forward when enabled.
- Store messages for 14 days on Free or 90 days on paid plans for recovery and evidence.
- Send through authenticated SMTP from approved identities on paid plans.
- Record delivery history for inbound and outbound hops.
- Count aliases against published plan ceilings.
What MailerZ does not do
- Strip plus tags on your custom domain the way Gmail strips them on gmail.com.
- Replace Gmail or Outlook with IMAP or webmail.
- Rewrite header From, Subject, Date, Message-ID, body, or MIME.
- Offer send-as on Free.
- Promise inbox placement, uptime SLAs, or review counts.
- Claim SOC 2, ISO 27001, or HIPAA. Controls live on Security and Trust Center.
- Act as an open relay.
- Send newsletters or purchased lists.
Seats are operators of the delivery layer, not mailbox licenses. Free and Solo are one seat. Starter is five. Business is twenty-five. Agency is fifty. If fifty people need hosted inboxes, that is suite math, not Agency alias math.
Delivery history is part of the alias job. When a vendor form says they emailed billing@ and you see nothing, you need the remote SMTP response, not a guess. MailerZ records that hop. A service with no history forces you to debug in the destination spam folder and the sender’s outbox at the same time.
Recovery is 14 days on Free and 90 days on paid. That window is for failed hops, not a seven-year archive. If the RFP wants a vault on the alias vendor, MailerZ is the wrong product. Keep the archive in Gmail, Outlook, or a suite that documents retention.
Cost, alternatives, and trade-offs
The best email alias service is often the cheapest when you were about to buy seats for names nobody logs into. It is the wrong invoice when every teammate needs Calendar and a vendor mailbox.
| Approach | You get | You give up |
|---|---|---|
| MailerZ aliases | Named routes, hop history, optional paid send-as. | Finite alias counts. No hosted mailbox. No plus stripping on the domain. |
| Suite aliases inside Workspace or Microsoft 365 | Vendor admin, suite apps, often plus addressing on that host. | Per-user cost if you only needed routing. |
| Gmail plus tags only | Free personal filters. No DNS. | No professional public string. Form breakage. Not transferable. |
| Catch-all as infinite aliases | Unknown local-parts can arrive on paid plans. | Typos and harvested guesses arrive too. |
Solo is 5 send-as messages per hour and 100 outgoing per month. Starter is 10 and 200. Business is 15 and 400. Agency is 25 and 800. Annual Starter, Business, and Agency billing includes two months free relative to paying monthly for a year. Solo has no monthly option.
Cloudflare Email Routing and other inbound routers can map named addresses. They do not become MailerZ leftover-MX handling, stored failed hops, or authenticated send-as because this article named them. ImprovMX is a closer commercial forwarding class; compare live plans rather than memory. Google’s suite packaging lives on Google Workspace — product overview and changes.
Do not score “best” by a blog’s invented review count. Score it by whether you can list aliases, delete leftover MX, and produce a destination copy plus a history row from an external send.
Hourly send caps matter if the alias is also the From identity. Solo is 5 send-as messages per hour. Month-end invoice bursts can stall on that cap even when the alias inbound path is perfect. Count the burst before you call Solo the best plan. Starter, Business, and Agency raise the hourly number. A campaign list still does not belong on any of those plans.
Time-box rollback. Keep the previous MX hostnames in a note, not in the live zone, until two external inbound tests pass. If you cancel the old forwarder before MailerZ MX is the only answer, you have a weekend without a store. The best alias service is the one you can enter and leave without split records.
Compare Workspace only when the suite is on the table. MailerZ versus Google Workspace is a store decision, not an alias beauty contest. If you already decided to keep Gmail, stop pricing seats for hello@. If you need Drive and admin for every human, stop shopping alias vendors.
Shared inboxes are a different product. If three people must search the same legal mailbox with vendor retention, an alias into one founder Gmail is the wrong store. MailerZ can route legal@ there. It cannot give you delegated admin or eDiscovery. Say that before you pick the cheaper invoice and call it the best alias service.
FAQ
What is the safest way to handle the best email alias service choice?
List every address you will print. Keep Gmail or Outlook as the store if that is already the archive. Pick a delivery layer that maps named aliases, publishes one MX set, and holds unknown recipients by default. Prove inbound from a different mailbox before you put the address on a form. Do not treat plus tags or catch-all as unlimited aliases.
Does this require a new mailbox?
No. An alias is a routing rule, not a seat. MailerZ is not IMAP and not webmail. The destination stays the inbox you already use. Buy a suite only if every person needs a hosted mailbox.
Will it work with Gmail or Outlook?
Yes for destinations. Gmail and Outlook receive the forwarded copy. Paid send-as uses Gmail Send mail as or a manual Outlook SMTP identity. Interface labels vary by Outlook version. Free has no send-as.
What DNS records are involved?
A verification TXT, one MX set, leftover MX removal, and the SPF, DKIM, and DMARC values shown in the dashboard if you also send as those aliases. Leftover Google, Microsoft, or host MX is a hard stop.
What should I test before production?
Send a uniquely titled message from an unrelated provider to each printed alias. Confirm Header From, destination delivery, and MailerZ history. Then send outward only if a paid plan includes send-as. Self-send from Gmail to the same Gmail account can hide routing errors.
Key takeaways
- The best email alias service maps durable public names to existing inboxes.
- An alias is not a mailbox seat and not a Gmail plus tag on your domain.
- Count printed addresses against plan ceilings before you cut MX.
- Free allows three aliases and no send-as. Paid raises both.
- Catch-all is not unlimited aliases.
- Publish one MX set. Leftover MX is a hard stop.
- Header From stays original on MailerZ inbound. Envelope SRS is the allowed rewrite.
- Prove inbound from another mailbox before you print the address.
- MailerZ is not SOC 2, not IMAP, and not a suite.
Conclusion and next action
If you came here for the best email alias service on a custom domain, choose the operator that treats aliases as inventory you can move. Keep the inbox. Map the names you print. Hold the rest. Add send-as only when replies must show those names. Do not buy seats for stamps. Do not use plus tags as brand addresses. Do not turn on catch-all to fake an infinite list.
MailerZ fits when you want durable aliases into Gmail or Outlook, hop history, and a recovery window you can inspect. It does not fit when every user needs a hosted mailbox, certified compliance reports, or campaign-scale sending. Start on Free if three aliases and inbound proof are the job. Move to Solo or another paid plan when you need more names, catch-all forward, or send-as.
Next action: write the printed list. Add one domain, create those aliases, and send a uniquely titled message from a mailbox that is not the destination. The MailerZ documentation has the field maps. The register path is one domain.
Ready to map real aliases
Start free with one domain and prove the path.
Three aliases on Free. Paid send-as when the From identity has to travel. Sign in if the domain is already there.
Review quarterly, or sooner if alias ceilings, provider behavior, or DNS guidance changes. Author: MailerZ editorial, Secuno LLC.