Custom Domain Aliases vs Privacy Alias Services

Quick answer for custom domain alias vs privacy alias

Privacy aliases hide the destination from the website. They do not hide the message from the alias vendor.

Custom-domain aliases hide nothing from the destination inbox and little from a determined party. They give you portability.

Websites that block disposable lists may accept your domain and still block Relay domains. That is why 291 exists as a sibling.

MailerZ vs SimpleLogin is a sibling comparison. This page is the category split.

Authoritative mail transport is still IETF RFC 5321 — Simple Mail Transfer Protocol. email forwarding. aliases catch all. send reply.

The real decision

Buyers want one app to be both CFO-stable and anonymous. Those goals fight.

Decision: recovery and vendors versus masks and churn.

Catch-all FORWARD is not a privacy feature. It is a harvest feature.

A suite is neither. It is a mailbox.

When this path is enough

• You can staff exclusive MX and named aliases.
• You will keep Header From intact.
• You can probe from another mailbox.

When this is the wrong ticket

• History is empty and leftovers remain.
• You want an inbox placement SLA.
• You plan to rewrite visible From.

Technical mail flow

Custom: site sends to you@yourdomain, MX you control, dest inbox.

Privacy: site sends to random@provider, their MX, dest inbox.

If the privacy vendor dies, the mask dies. If you keep the domain, you can point MX elsewhere.

Send-as branded From is a custom-domain job. Privacy masks often reply through their app.

Step-by-step decision path

1. Inventory leftovers. Screenshot current MX, SPF, DKIM, NS.
2. Verify the domain. TXT as the dashboard states.
3. Create named aliases first. Do not cut MX onto empty maps.
4. Publish one MX set. Delete Google, Microsoft, registrar leftovers.
5. Prove from another mailbox. Unique subject. Header From intact.
6. Only then send-as if paid. Dashboard SPF/DKIM. Outbound probe.
7. Store the proof packet. MX, hop, headers, plan name.

Worked examples

A freelancer used Relay for newsletters and MailerZ for clients. Two tools. Correct.

They put invoices on a Relay mask. The mask vanished. They could not reset QuickBooks. Domain alias next time.

A privacy-first buyer wanted no logs. We store hops 14/90 days. They used /security and chose accordingly.

Unlimited masks sold them a privacy app. They still needed hello@ on a real domain.

They expected MailerZ to strip identity from headers. We do not rewrite From. Honest.

Failure modes and proof

MailerZ workflow and product boundary

Secuno LLC operates MailerZ. Site: mailerz.net. App: mail.mailerz.net. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not IMAP. Not an open relay.

What MailerZ does

• Accept MX for verified domains.
• Rewrite envelope MAIL FROM with SRS on the forward.
• Leave Header From and MIME intact.
• Hold unknowns on Free. Optional paid FORWARD.
• Paid SMTP from approved identities. Dashboard SPF, DKIM, and DMARC instructions.
• 550 for unauthorized From. Not an open relay.

What MailerZ does not do

• Guarantee Gmail Primary or any inbox placement rate.
• Host IMAP, Calendar, or a Workspace suite.
• Send-as on Free.
• SOC 2, ISO 27001, HIPAA, review counts, or an uptime SLA. Controls: Security and Trust Center.

Plans: pricing. Free $0, 1 domain, 10 aliases, 1 seat, 14-day store, send-as disabled, SMTP and API disabled. Solo $40/year, 5 domains, 25 aliases, 90-day, 2,500 outgoing, 20/hour. Starter $8 or $80, 8/50/5, 5,000, 40/hour. Business $19 or $190, 25/200/25, 12,000, 60/hour. Agency $39 or $390, 100/500/50, 20,000, 60/hour. Unlimited is $99/month or $990/year. Annual Starter, Business, and Agency include two months free versus monthly. Solo is yearly only.

Cost, alternatives, and trade-offs

Field notes

Related: /custom-domain-email-alias, /private-email-alias, /email-alias-service, /anonymous-email-forwarding.

Cite privacy vendors as nofollow if you link commercially.

No SOC 2 theater.

Re-read both categories before a buy.

Search demand for custom domain alias vs privacy alias usually arrives as a screenshot, not a sentence. Ask for the received copy, the public MX set, and the plan name before you change a record. Custom Domain Aliases vs Privacy Alias Services is a workflow, not a checkbox.

Write a one-paragraph policy the team can reuse for custom domain alias vs privacy alias. Name the hop (inbound versus outbound), the proof artifact, and the thing you will not do (dual MX, From rewrite, second SPF record). Put the paragraph in the ticket template.

Change control matters more than a clever record. One person owns DNS for this domain. Adding an include, a selector, or a backup MX requires a ticket. Most regressions in custom domain alias vs privacy alias are Friday edits without a probe.

Self-send remains invalid for custom domain alias vs privacy alias. Gmail can short-circuit. Outlook can look local. Use a mailbox on another provider and a unique subject. If the customer refuses, the ticket stays open.

Leftover MX masquerades as every authentication and spam incident. If history is empty, custom domain alias vs privacy alias is the wrong title until two resolvers agree on one product. Delete aspmx, Microsoft, and registrar MX. Wait TTL.

Free HOLD and missing aliases masquerade as outages. History shows the hold. Create the named local-part or accept that unknowns stay. Catch-all FORWARD is paid, optional, and a spam trade-off — not a debugger for custom domain alias vs privacy alias.

Paid send-as is a different hop from inbound custom domain alias vs privacy alias. Free cannot send. Unauthorized From is 550 / 550 5.7.1. Publishing prettier DNS will not authorize a From the product has not approved.

Destination filters still win after a clean hop. Custom Domain Aliases vs Privacy Alias Services does not include an inbox placement SLA, review counts, or a Primary guarantee. Say that once, early, so the customer stops buying a story you cannot ship.

Proof packet for custom domain alias vs privacy alias: public MX from two resolvers, inbound received copy with Header From, Authentication-Results, outbound received copy if they send, plan name, and the SMTP line if anything refused. That packet ends folklore.

Retention is 14 days on Free and 90 on paid. Export headers while they live. custom domain alias vs privacy alias arguments without artifacts become myths. The destination inbox is the archive, not the hop store.

Agencies should not blend clients in one custom domain alias vs privacy alias thread. One domain, one matrix, one MX screenshot. Agency plan limits are 100 domains, 500 aliases, 50 seats, 20,000 outgoing, 60/hour — still not unlimited, still not an SLA.

Security hygiene: no SMTP passwords in the custom domain alias vs privacy alias ticket, no message bodies in chat, no invented SOC 2. Controls live on the Security and Trust Center. Secrets rotate if they leaked.

Related operations stay on real routes: forwarding, send-as, troubleshooting, tools, delivery recovery, docs, pricing. Do not invent a pillar. If custom domain alias vs privacy alias is actually leftover MX, say leftover MX.

Refresh cadence is at least quarterly, sooner after a domain transfer, panel change, ESP trial, or dashboard host change. Custom Domain Aliases vs Privacy Alias Services goes stale when the zone changes and the runbook does not.

If two products still share MX after you explained the coin flip, stop adding records. Exclusive MX is a hard stop. custom domain alias vs privacy alias cannot be correct on a split path.

If Header From is already rewritten, stop tuning SPF for custom domain alias vs privacy alias. Change the hop. MailerZ will not offer a From-replace control. Honest identity is the product.

If the customer wants a suite, sell the suite as Calendar and a hosted mailbox, not as a magic fix for custom domain alias vs privacy alias. Workspace and Microsoft 365 are different architectures with their own filters and their own 550s.

Hourly and monthly send-as ceilings (disabled/2,500/5,000/12,000/20,000 outgoing; 20/40/60/60 per hour by plan) produce refuses that look like custom domain alias vs privacy alias outages. Read counters before you republish DKIM.

Null MX plus a real MX is another lie. Remove the lone-dot refuse if you intend to receive. Empty inbound plus a pretty custom domain alias vs privacy alias essay is still a refuse-all.

After you change anything, wait TTL, probe from another mailbox, and store the new received source next to the MX screenshot. Custom Domain Aliases vs Privacy Alias Services is done when proof exists, not when the panel is green.

Field story 1 for custom domain alias vs privacy alias: A freelancer used Relay for newsletters and MailerZ for clients. Two tools. Correct. Keep that story in the runbook so the next person does not reopen Custom Domain Aliases vs Privacy Alias Services from zero.

Field story 2 for custom domain alias vs privacy alias: They put invoices on a Relay mask. The mask vanished. They could not reset QuickBooks. Domain alias next time. Keep that story in the runbook so the next person does not reopen Custom Domain Aliases vs Privacy Alias Services from zero.

Field story 3 for custom domain alias vs privacy alias: A privacy-first buyer wanted no logs. We store hops 14/90 days. They used /security and chose accordingly. Keep that story in the runbook so the next person does not reopen Custom Domain Aliases vs Privacy Alias Services from zero.

Field story 4 for custom domain alias vs privacy alias: Unlimited masks sold them a privacy app. They still needed hello@ on a real domain. Keep that story in the runbook so the next person does not reopen Custom Domain Aliases vs Privacy Alias Services from zero.

Field story 5 for custom domain alias vs privacy alias: They expected MailerZ to strip identity from headers. We do not rewrite From. Honest. Keep that story in the runbook so the next person does not reopen Custom Domain Aliases vs Privacy Alias Services from zero.

For custom domain alias vs privacy alias, symptom “Empty history” usually means Leftover or cached MX. Isolate it with Two resolvers. Do not stack a second change until that proof exists.

For custom domain alias vs privacy alias, symptom “Unknowns missing” usually means Free HOLD. Isolate it with History hold. Do not stack a second change until that proof exists.

For custom domain alias vs privacy alias, symptom “Header From rewritten” usually means Wrong hop. Isolate it with Received From. Do not stack a second change until that proof exists.

For custom domain alias vs privacy alias, symptom “SMTP 550 send-as” usually means Free or unauthorized From. Isolate it with History line. Do not stack a second change until that proof exists.

For custom domain alias vs privacy alias, symptom “spf=fail hop two” usually means Naive envelope. Isolate it with Return-Path. Do not stack a second change until that proof exists.

For custom domain alias vs privacy alias, symptom “Still spam after clean hop” usually means Destination filters. Isolate it with Not an SLA. Do not stack a second change until that proof exists.

For custom domain alias vs privacy alias, symptom “Self-send clean” usually means Short-circuit. Isolate it with Other mailbox. Do not stack a second change until that proof exists.

For custom domain alias vs privacy alias, symptom “Wrong DNS panel” usually means NS ≠ registrar UI. Isolate it with NS lookup. Do not stack a second change until that proof exists.

Setup step “Inventory leftovers.” for custom domain alias vs privacy alias: Screenshot current MX, SPF, DKIM, NS. Skip it and Custom Domain Aliases vs Privacy Alias Services turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Verify the domain.” for custom domain alias vs privacy alias: TXT as the dashboard states. Skip it and Custom Domain Aliases vs Privacy Alias Services turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Create named aliases first.” for custom domain alias vs privacy alias: Do not cut MX onto empty maps. Skip it and Custom Domain Aliases vs Privacy Alias Services turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Publish one MX set.” for custom domain alias vs privacy alias: Delete Google, Microsoft, registrar leftovers. Skip it and Custom Domain Aliases vs Privacy Alias Services turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Prove from another mailbox.” for custom domain alias vs privacy alias: Unique subject. Header From intact. Skip it and Custom Domain Aliases vs Privacy Alias Services turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Only then send-as if paid.” for custom domain alias vs privacy alias: Dashboard SPF/DKIM. Outbound probe. Skip it and Custom Domain Aliases vs Privacy Alias Services turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Store the proof packet.” for custom domain alias vs privacy alias: MX, hop, headers, plan name. Skip it and Custom Domain Aliases vs Privacy Alias Services turns into a second ticket next week. Do the step, store the artifact, then continue.

Trade-off on custom domain alias vs privacy alias: choosing Exclusive MX + named aliases gets you Debuggable path and gives up You must delete leftovers. Write that exchange on the quote so nobody pretends it is free.

Trade-off on custom domain alias vs privacy alias: choosing Dual MX backup gets you Feels safe and gives up Coin-flip misses. Write that exchange on the quote so nobody pretends it is free.

Trade-off on custom domain alias vs privacy alias: choosing From rewrite gets you Cosmetic SPF and gives up Trust and DKIM. Write that exchange on the quote so nobody pretends it is free.

Trade-off on custom domain alias vs privacy alias: choosing Suite seats gets you Hosted mailbox and gives up Per-user price. Write that exchange on the quote so nobody pretends it is free.

Custom Domain Aliases vs Privacy Alias Services is enough when You can staff exclusive MX and named aliases. If that condition is false, stop implementing custom domain alias vs privacy alias and reopen the decision.

Custom Domain Aliases vs Privacy Alias Services is enough when You will keep Header From intact. If that condition is false, stop implementing custom domain alias vs privacy alias and reopen the decision.

Custom Domain Aliases vs Privacy Alias Services is enough when You can probe from another mailbox. If that condition is false, stop implementing custom domain alias vs privacy alias and reopen the decision.

Custom Domain Aliases vs Privacy Alias Services is the wrong ticket when History is empty and leftovers remain. Name the correct system instead of forcing custom domain alias vs privacy alias to cover it.

Custom Domain Aliases vs Privacy Alias Services is the wrong ticket when You want an inbox placement SLA. Name the correct system instead of forcing custom domain alias vs privacy alias to cover it.

Custom Domain Aliases vs Privacy Alias Services is the wrong ticket when You plan to rewrite visible From. Name the correct system instead of forcing custom domain alias vs privacy alias to cover it.

Write custom domain alias vs privacy alias in the subject line of the ticket and the layer in the first sentence. If the layer is leftover MX, say leftover MX. If the layer is HOLD, say HOLD. If the layer is a destination 550, paste the text. Custom Domain Aliases vs Privacy Alias Services stays short when the first sentence is honest.

Keep a standing calendar note for custom domain alias vs privacy alias: monthly external probe, leftover MX lookup, and a glance at send-as counters if you are paid. Five minutes. The outage you avoid is the Friday dual-MX restore.

When two vendors disagree about custom domain alias vs privacy alias, believe artifacts: two resolvers, one received copy, one history row. Do not believe the prettier admin center. Registrar dots lie. Composer UIs lie. Self-send lies.

Teach the next hire the MailerZ split before they touch custom domain alias vs privacy alias: envelope may change, Header From must not, Free cannot send, unknowns HOLD, leftover MX is a hard stop, no inbox SLA, no SOC 2 sticker. That speech prevents a class of tickets.

If custom domain alias vs privacy alias appears in an RFP, answer with published caps and hop evidence. Decline inbox-rate clauses. Decline fake certifications. Point at pricing and the Security and Trust Center. Custom Domain Aliases vs Privacy Alias Services is not a place to invent enterprise theater.

Export while the 14- or 90-day window still has the custom domain alias vs privacy alias hop. Future-you will not remember the SMTP sentence. The destination mailbox remains the archive. We will not grow the store because a blog asked.

Do not bundle unrelated edits with custom domain alias vs privacy alias. Rotating SMTP while republishing MX while enabling FORWARD is how you lose the ability to name the failure. One change, one probe, one stored copy.

If you need a suite, buy a suite for Calendar and a hosted mailbox. If you need a hop, buy a hop. Custom Domain Aliases vs Privacy Alias Services does not become Exchange because a quote stacked seats next to aliases.

FAQ

Key takeaways

• Exclusive MX is a hard stop.
• Header From stays the original sender.
• SRS is envelope-only.
• Free holds unknowns and cannot send-as.
• 550 means read the text.
• Self-send lies.
• No inbox SLA.
• 14- or 90-day store is not an archive.
• MailerZ is not IMAP.
• No SOC 2, ISO, or HIPAA claims.

Conclusion and next action

Pick durability or masks. MailerZ is durability on a domain you own.

Next action: list addresses that must work next year versus signups you will never recover.

Review quarterly, or sooner if DNS hosts or dashboard instructions change. Author: MailerZ editorial, Secuno LLC.