How to set up email on your domain

Setting up email on your domain comes down to one mechanical step and one real decision. The mechanical step: add MX records — plus a few authentication records — to your domain’s DNS pointing at an email provider, so the world knows where to deliver mail for [email protected]. The real decision: whether that provider gives you forwarding — aliases that redirect into the inbox you already check — or a full hosted mailbox, a real inbox living on your domain. Forwarding is free or nearly free and takes minutes; a proper mailbox usually costs a few dollars per user per month. The rest of this guide is picking the right side of that fork.

Do you need forwarding or a real mailbox?

Forwarding means your domain receives mail and redirects it. [email protected] lands in your existing Gmail; set up as many aliases as you like, or a catch-all that scoops up anything sent to the domain. It costs nothing or close to it, and for a side project that mostly receives — signup confirmations, the occasional customer question — it’s genuinely all you need.

The honest catch: forwarding is receive-only. When you hit reply, the message goes out from your personal address, not your domain. There are workarounds — Gmail’s “Send mail as” is the common one — but sending as your domain is something you layer on top, not something forwarding services natively do. More on that below.

A hosted mailbox is the real thing: an inbox that lives on your domain, sends natively as your domain, and has its own storage, spam filtering, and apps. This is what you want once email is part of how the business presents itself — replying to customers, sending invoices, adding teammates. With one genuinely free exception, it means paying a provider.

A reasonable heuristic: start with forwarding while you’re validating, and upgrade to a mailbox once you’re sending email you’d want a stranger to take seriously. Switching later just means swapping records.

What are the free and cheap options?

Cloudflare Email Routing — free forwarding, if your DNS lives on Cloudflare. Unlimited inbound forwarding, catch-all included, no per-address fees, and limits a small business will never meet. The one requirement: your domain’s DNS must be managed by Cloudflare — you point your nameservers there, which is not the same as transferring the domain to another registrar; registration stays put. And it’s receive-and-forward only. The popular trick for replying as your domain lives in Gmail, not Cloudflare — under Settings → Accounts → “Send mail as,” Gmail emails a verification code to the alias — it arrives via your forwarding rule — and from then on Gmail can send using that address. It works, but it’s a community workaround, not a product guarantee.

ImprovMX — free forwarding at any registrar, $9/month to send. If you’d rather not move DNS to Cloudflare, ImprovMX works wherever your records already live: paste its MX and SPF records into your registrar’s DNS panel and you’re forwarding. The free tier covers one domain, 25 aliases, and 500 forwards a day, with a catch-all set up by default. Premium at $9/month is the interesting upgrade — real SMTP sending, so replies genuinely leave from your domain rather than through a Gmail workaround.

Zoho Mail — the one genuinely free hosted mailbox. The Forever Free plan gives up to 5 users real inboxes on one domain, 5 GB each. The limits are real: webmail and Zoho’s mobile app only — no IMAP or POP, so you can’t wire it into Apple Mail or Outlook. If you live in Zoho’s apps, it’s a remarkable deal; the paid Lite tier, at about a dollar per user per month, lifts those limits.

Fastmail — $5 per user per month, billed annually. No free tier beyond a 30-day trial, and its cheapest Basic plan excludes custom domains — Standard is the tier you actually want. You’re paying for a fast, focused email product without the suite baggage.

Google Workspace — roughly $7–8.40 per user per month, depending on billing. The free custom-domain Gmail of old is gone — Google ended the legacy free edition in 2022 — so Business Starter is the entry point now: the full Gmail experience on your own domain, plus Meet and pooled Drive storage. Microsoft 365’s entry tier is comparable in price if your world is Outlook-shaped.

Proton Mail — about $4 a month, billed annually. Proton’s free plan doesn’t support custom domains at all; Mail Plus is the entry tier, and the draw is end-to-end encryption rather than price.

What DNS records does email need — and why?

Four records, all pasted into the same DNS dashboard you used to connect the domain to a host — your registrar’s panel, or wherever your nameservers point. (Our registrar guide notes who hands DNS off to whom.)

• MX — the routing record. It names the mail server that receives your domain’s inbound mail (a hostname, never a bare IP). No correct MX, no incoming email — this is the record that makes everything work.
• SPF — a TXT record listing which servers are authorized to send mail as your domain. Receivers check the sending server against it.
• DKIM — a cryptographic signature on outgoing mail, proving the message came from an authorized sender and wasn’t altered in transit.
• DMARC — a TXT record telling receivers what to do when a message fails both SPF and DKIM (or fails to align with your domain): nothing, quarantine, or reject.

You don’t construct any of these by hand. Every provider above generates the exact values during setup; your job is copy, paste, save.

One callback that matters: if you followed our first-hour checklist, your domain carries a null MX record and an SPF record of v=spf1 -all — the pair that tells the world “this domain sends no email.” Right for a parked domain, wrong for one going live. Delete both before adding your provider’s records, or you’ll be instructing mail servers to reject your own messages.

And don’t treat SPF, DKIM, and DMARC as optional. Gmail and Outlook have both tightened sender-authentication requirements in recent years, and even for a one-person domain, having all three materially improves the odds your mail lands in inboxes instead of spam — and stops strangers spoofing your name.

Why isn’t my new email working yet?

Because DNS changes take time to spread. A new or changed MX record typically propagates within minutes to a few hours, occasionally up to 24–48 — and until resolvers worldwide see it, mail to your domain can bounce or, if you switched providers, keep landing at the old one. It’s the same caching behavior that delays a new website, and the same calm checklist applies: why isn’t my domain working yet? walks through it.

While you wait, send yourself a test from an unrelated account and resist the urge to “fix” records that are already correct. If mail still bounces well past the 48-hour mark, re-read the records — the usual culprits are a typo in the MX hostname, records pasted into a zone your nameservers don’t actually use, or that leftover null MX quietly telling everyone you don’t accept mail.

Email is the part of a domain you set up once and live with every day — a good argument for making sure the name after the @ is one you’re proud to send from. If that part is still unsettled, Domain Yoga generates around 250 availability-checked, brandability-ranked ideas in seconds. Pick the name first; the MX records take ten minutes.