Domains & DNS

Free Email on a Custom Domain: Forwarding vs a Real Mailbox

A custom domain email address looks like a solved problem: several providers offer one for nothing, so you pick the first result and move on. Then you reply to your first serious enquiry and discover you are writing from a personal Gmail address, because the free thing you set up only receives.

“Free domain email” covers two products that are not the same, and the difference surfaces at exactly the wrong moment.

The two products

Forwarding. Mail sent to [email protected] is relayed into an inbox you already own. There is no mailbox, no storage, and no way to send from that address. You get a professional incoming address and nothing else.

A mailbox. An actual inbox on your domain, with storage, a webmail interface, and the ability to send as [email protected].

Almost every “free” result you will find is the first kind. That is not a trick — forwarding is genuinely useful and genuinely free — but it is a different thing from an inbox.

What the three common options actually give you

Cloudflare Email RoutingZoho Mail Forever FreeImprovMX (free)
CostFreeFreeFree
Gives you a mailboxNoYesNo
Can send as your domainNoYes, from Zoho’s own interfaceNo
Storage for your mailNone5 GB per userNone
Desktop client (IMAP/POP)n/aNot on the free plann/a
Number of addressesUnlimited aliasesOne domain, a small number of usersUnlimited aliases

Terms on all three shift; check the signup page before you build on them. The shape of each offer has been stable for years, though, and the shape is what you are choosing between.

Cloudflare Email Routing is the least surprising option if you already use Cloudflare for DNS. You verify a destination address, add a rule, and Cloudflare writes the MX records itself. A catch-all rule sends every address at your domain to one inbox, which is useful when you do not yet know which addresses you need. Note that it is inbound only — Cloudflare does sell an email sending product for applications, but that is transactional mail from code, not an inbox you can reply from.

Zoho’s free tier is the only one of the three that is a real mailbox. It supports a custom domain, a small number of users, and 5 GB each, and it can send. The constraint is access: the free plan does not include IMAP or POP, so you cannot connect it to Outlook, Apple Mail, or a third-party mobile client. You read and send through Zoho’s web interface or its own app.

ImprovMX is forwarding with a cleaner dashboard than most registrar-provided versions. Sending requires a paid plan.

Sending is the dividing line

If you only need to receive — a contact@ address on a page, a hello@ for enquiries you will answer from elsewhere — free forwarding is the correct answer and there is no reason to complicate it.

If you need replies to come from your own domain, the options narrow quickly:

  • Forwarding plus Gmail’s “Send mail as”. Gmail can be configured to send from an alias. It works, with a caveat: Gmail rewrites the sender for deliverability unless you supply external SMTP credentials, so your replies may carry via gmail.com. Recipients see it, spam filters notice it, and it undercuts the point of the custom address.
  • Zoho’s free tier. Replies come from your domain properly, with Zoho’s SPF and DKIM in place. The trade is that you are working inside Zoho’s interface, with no way to plug in the mail client you already use.
  • Anything that gives you IMAP. That is a paid plan, generally a few dollars per user per month.

The awkward truth is that “I need to send” is usually the point where free stops working, and the jump from free forwarding to a paid mailbox skips past the middle option most people would be happy with.

The cost that is not on the pricing page

Consider what happens when you want to leave.

Forwarding leaves nothing behind. No storage, no archive, no migration. You change the DNS record and you are done. This is a genuine advantage of the stripped-down option.

A free mailbox can hold you. Zoho’s free plan has no IMAP, and IMAP is the standard mechanism for exporting mail in bulk. If you have spent three years building a mailbox you cannot connect a client to, moving to another provider means leaving the history where it is. Decide the exit before you accumulate one.

This is the part of “free” that comparison tables never show: not what it costs per month, but what it costs to stop.

Deliverability, briefly

Two things worth knowing regardless of which you pick.

Forwarding breaks SPF alignment unless the forwarder rewrites the envelope. When mail is forwarded, the sending infrastructure is no longer the original sender, and SPF checks against the wrong domain. Good forwarders implement SRS to repair this. If mail forwarded through your domain lands in spam, this is the first thing to look at.

Authentication records belong on your domain. SPF, DKIM and DMARC all publish as DNS TXT records at whatever host is actually sending. If you send through Zoho, Zoho’s DKIM key goes in your DNS. If you send through an SMTP relay, that relay’s SPF entry goes in yours. Without them, you are relying on the recipient’s goodwill.

That is also why configuring a custom domain properly is a DNS task, not an email task: three or four records, all of them editable in the same place you manage everything else.

How to decide

  • Receiving only, one address, no team → Cloudflare Email Routing if your DNS is there, ImprovMX if it is not. Free, permanent, no maintenance.
  • One person, needs to send, lives in webmail anyway → Zoho’s free tier, with a note in your calendar to revisit the exit problem before the mailbox matters.
  • Needs IMAP, more than one user, or mail that must be exportable → pay for it. This is a genuinely small monthly cost and the alternatives are worse: an $8-per-month upgrade of a forwarder buys you less than a real mailbox costs.

The trap is not picking the wrong free option. It is staying on one long after it has stopped fitting, because the switch looks bigger than it is — and with a forwarding setup, it is not big at all.


Written by TestedHost. Every recommendation on this site comes from running the setup described, on a live deployment — not from a vendor spec sheet. Spotted something out of date? Tell us.