Free custom domain email forwarding: what you give up

Quick answer for free custom domain email forwarding

Use Free to prove exclusive MX and three printed names into Gmail. You give up send-as, a longer store, and more aliases. That is free custom domain email forwarding on this product.

Guide: Free is a lab and a tiny production. Setup: three names, leftover delete, external probe. Best practice: upgrade when the fourth printed string or a domain From is real.

A 550 on send-as is the plan telling the truth. It is not a Gmail reject.

Other vendors’ free tiers are their docs. Do not invent parity.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as Off, SMTP Off, API Off, and unrouted mail held or rejected only. Solo is $40 per year only, with send-as, SMTP, and API On. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise. Held inbound copies on Free still appear in Mail Box for fourteen days. Field maps: MailerZ documentation.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

free custom domain email forwarding guide: the real decision

Printed hello, sales, billing, and jobs on Free.

Pasted SMTP on Free and called it broken.

Expected Vault from a 14-day hop store.

Criteria: three names, no From, hold unknowns, exclusive MX.

Technical mail flow for free custom domain email forwarding

Inbound on Free is the same hop as paid: MX, named map, second SMTP, Header From intact.

Outbound as the domain does not exist on Free. Unauthorized is 550 / 550 5.7.1.

Hold is a tray. It is not a reject and not a fourth alias.

Leftover MX skips the hop entirely. Free cannot save a leftover miss.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP or POP, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

free custom domain email forwarding setup

Decide the three names. Then verify. Then cut leftovers.

1. Pick three printed local-parts.
2. Add and verify the domain.
3. Create those aliases. Leave catch-all on hold.
4. Publish exclusive MailerZ MX. Delete leftovers.
5. Probe from another mailbox.
6. Do not attach SMTP on Free.
7. Upgrade when a From or a fourth name is real.
8. Confirm live pricing before you promise a client twenty names.

Failure modes and proof

Five names on the homepage.

Free SMTP in WordPress.

Catch-all forward on Free (it is hold).

Self-send.

Called 14 days an archive.

MailerZ workflow and product boundary

Related: pricing, compare Google Workspace, aliases and catch-all, send and reply.

The paid-versus-free risk article is the risk aisle. This page is the ceiling list.

Related pages: pricing, compare Google Workspace, aliases and catch-all, and send and reply.

free custom domain email forwarding best practice

Free plus consumer Gmail is $0 for the hop. Solo $40/year is the usual first From. Workspace remains per seat. Confirm all live pages. No inbox SLA on Free.

Self-host threads that want “just forwarding” are describing this ceiling. Name it.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as Off, SMTP Off, API Off, and unrouted mail held or rejected only. Solo is $40 per year only, with send-as, SMTP, and API On. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise. Held inbound copies on Free still appear in Mail Box for fourteen days. Field maps: MailerZ documentation.

Field notes you can reuse

Agencies: Free is a lab domain, not ten client zones.

14-day store is hops, not Takeout.

Hold review weekly if you printed a new name.

Do not invent competitor free-tier numbers.

Quarterly leftover review.

SOC 2 is still no on every plan.

Free SMTP is disabled — this is not a campaign product.

Upgrade is a ceiling move, not a deliverability purchase.

Deeper field notes for free custom domain email forwarding

Say the ceiling in one breath

Free custom domain email forwarding on MailerZ is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. That sentence is the product. Everything else is a paid conversation. Teams get angry at Free when they wanted Solo and refused to read the card. The honest article names what you give up so the upgrade is a decision, not a surprise 550.

You give up a domain From. You give up an eleventh printed name. You give up catch-all forward. You give up a 90-day hop window. You give up extra domains. You do not give up leftover-MX rules. You do not get an inbox-placement SLA on Free or on Agency. You do not get SOC 2 by staying on Free longer.

What Free still does completely

Exclusive MX, named aliases, Header From intact, envelope SRS, delivery history for hops this layer saw, hold for unknowns. That is enough to take hello@, billing@, and jobs@ off a personal Gmail footer. It is enough to prove the hop before you pay. It is not enough to run WordPress as the domain. It is not enough to promise a client twenty roles.

Other vendors’ free tiers differ. Cite them if you compare. Do not invent MailerZ limits onto their cards or theirs onto ours. ImprovMX and Cloudflare Email Routing are different products. This page is this Free plan.

The 550 that is working as designed

Paste Free SMTP into a form and you should get 550 / 550 5.7.1. That is not Gmail greylisting. That is not DNS. That is the plan. Upgrade, or send from the Gmail address and accept the From. Do not open a ticket titled “SMTP broken” without the plan name. Do not mail the password to support.

Fifty outgoing per month is also a ceiling. Free is not a campaign product. If a plugin retries, you can burn the month. Paid hourly send-as limits are still ceilings. None of this is an inbox SLA.

Hold is what you keep, not what you give up

Unknowns held is a feature of Free. You give up automatic forward of harvest. That is the correct give-up. Promoting hold to a named alias is how the fourth name appears — and how you learn you need a paid ceiling. Do not dictionary-test hold. Do not call hold a reject.

14 days is hops, not memory

You give up a long recovery window. If you debug leftover MX two weeks late on Free, the miss may already be gone. Paid 90 days is still hops this layer stored, not Takeout, not Vault. If you need an archive, keep Gmail or buy a suite. Do not stay on Free because you thought 14 days was cheap eDiscovery.

When Free is the wrong first step

A law firm printing legal@ and privacy@ and needing send-as this week should start on a paid plan that fits, not on Free as theater. An agency with five client domains cannot live on Free’s one domain. A founder who already knows the From must travel can start on Solo. Free is for proof and tiny production. Using it as a protest against Workspace does not add aliases.

Self-host threads that want forwarding for zero dollars are describing this plan. They still owe exclusive MX and a named list of three. Zero dollars does not delete leftover Google hosts.

Upgrade triggers you can write on a sticky note

Fourth printed name. A From that is not @gmail.com. A second domain. A hold tray you are promoting every week. A debug that needed history older than fourteen days. Those are Solo or Starter triggers. They are not “deliverability purchases.” Paying does not move you to Primary.

Agency and client honesty

Do not put a client on Free and print five roles. Do not use one Free domain as a parking lot for ten zones. Agency exists so you can hold more domains and aliases. Confirm /pricing. Offboard still means delete MX you own.

A complete worked story

The footer had five names

They launched on Free with hello, sales, billing, jobs, and press. Two names never existed. Those senders sat in hold. They called it “free forwarding is broken.” It was a ceiling. They moved hello, sales, and billing onto the three slots, held the rest, probed, and upgraded the next week when press needed a From. Free had done its job. The footer had not.

Operator brief

A longer operator brief for free custom domain email forwarding

Teams that bookmark Free Custom Domain Email Forwarding: What You Give Up usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about free custom domain email forwarding as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is Mail Box portal webmail, not IMAP, not POP, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening free custom domain email forwarding. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for free custom domain email forwarding what you give up. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear free custom domain email forwarding works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep free custom domain email forwarding per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When Free Custom Domain Email Forwarding: What You Give Up is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how free custom domain email forwarding stays a runbook instead of an incident.

A second worked pass for free custom domain email forwarding: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a free custom domain email forwarding mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

What “free” still costs in operations

Free custom domain email forwarding is free in dollars and expensive in discipline. You still verify TXT on the nameservers that answer. You still publish exclusive MailerZ MX. You still delete leftover Google, Microsoft, Cloudflare routing, ImprovMX, and registrar hosts. You still probe from another mailbox. You still refuse self-send. None of that disappears because the card says zero. Teams that treat Free as “no process” are the ones who print five names and then open a ticket.

The operational cost you keep: a named list of three. The operational cost you skip: SMTP rotation, hourly send-as math, a second domain. If you feel those skipped costs anyway — a form that must send as the domain, a client zone, a fourth footer line — you are not on the wrong product. You are on the wrong plan. Confirm /pricing. Solo at forty dollars a year is the usual first honest upgrade. It is not a deliverability purchase.

How to explain Free to a client without lying

You may say: we can prove inbound on one domain and ten aliases at zero hop cost. You may not say: unlimited roles, branded send, ninety-day archive, inbox placement, SOC 2. You may not put their production footer on your lab Free account. Agency exists so client zones have a ceiling. Using Free as a protest against Workspace does not add aliases to the client’s domain.

If the client already has leftover Google MX, Free will look broken until leftovers die. Say that in the statement of work. The hop cannot show history for mail it never accepted. Delivery recovery on Free is fourteen days of hops this layer stored. That is not their old suite’s archive.

A week-one Free lab that does not paint you into a corner

Day one: one test domain you can break, three names you will actually print later, hold unknowns. Day two: exclusive MX, two public views. Day three: unique subjects from another mailbox, Header From intact. Day four: decide whether a From must travel. If yes, upgrade before the homepage ships. If no, ship the three names. Day five: write the upgrade trigger on a sticky note — fourth name, or a From, or a second domain. That is a Free week that stays honest.

Do not spend the week pasting SMTP into WordPress to “see if it works.” It will not. 550 is the lesson. Do not spend the week dictionary-testing hold. Do not spend the week comparing competitor free tiers with invented numbers. Cite their docs if you must. Nofollow commercial pages.

FAQ

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

Use Free to prove exclusive MX and three named aliases into Gmail. You give up send-as, a 90-day store, and a larger list. Hold unknowns. Do not paste SMTP on Free. Upgrade when a domain From or an eleventh printed name is real.

Does this require a new mailbox?

No. MailerZ is Mail Box portal webmail (Inbox, Sent, New email). It is not IMAP or POP. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as 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 MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• Three aliases.
• No send-as.
• Hold unknowns.
• 14-day hops.
• Exclusive MX still.
• 550 is honest.
• Upgrade for From.
• Confirm pricing.

Conclusion and next action

Free custom domain email forwarding proves inbound on a short list. You give up branded send and a long store. MailerZ will not hide that. Cut leftovers. Probe. Pay when the job grows.

Start free. Sign in if you already hit a 550 or an eleventh printed name.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.