Domain β‰  Email

Buying example.com from a registrar gives you the right to use the name. It does NOT give you a working email address at [email protected]. Email is a separate service called email hosting, and you have to either subscribe to a provider or run your own server (almost never the right choice).

What Email Hosting Provides

  • Inboxes β€” actual mailboxes that store messages, accessible via web/IMAP/POP.
  • SMTP relay β€” sending infrastructure that maintains a good IP reputation so your mail doesn't end up in spam.
  • Spam filtering on incoming mail.
  • Deliverability tooling β€” DKIM signing, SPF support, DMARC reporting.
  • Calendar, contacts, file sharing in the bigger products.

How DNS Records Connect Domain to Email

Email-to-domain wiring happens through DNS records you set at your domain registrar:

  • MX records β€” tell other mail servers where to deliver mail addressed to @example.com.
  • SPF (TXT) β€” lists who is authorized to send mail as example.com.
  • DKIM (TXT) β€” public key the receiver uses to verify the cryptographic signature on each outgoing message.
  • DMARC (TXT) β€” tells receivers what to do with mail that fails SPF/DKIM and where to send aggregate reports.

Skip any of these and your deliverability suffers, even with a perfectly configured email provider.

The Four Mainstream Providers

  • Google Workspace ($6/user/month). Best deliverability, best UX, integrates with everything. The default for most professional teams.
  • Microsoft 365 ($6/user/month). Similar to Google Workspace; better choice if your team already lives in Outlook + OneDrive.
  • Zoho Mail (free for 5 users at one domain, $1–4/user paid). Solid product, much cheaper, slightly weaker integrations outside its own ecosystem.
  • Hostinger / Namecheap / Bluehost private email ($1–3/user/month). Cheapest option; deliverability is ok if you set DKIM/SPF/DMARC correctly. Limited storage, slower web UI.

The Free Tier That Sometimes Works

Cloudflare Email Routing is free and forwards mail addressed to your domain to an external mailbox (Gmail, ProtonMail, etc.). You can receive at [email protected] but you can't send from it directly through Cloudflare β€” for that you'd need Gmail's "Send mail as" feature plus an SMTP relay.

Useful for personal use or one-off addresses. Not appropriate for a business that sends transactional or marketing email.

Self-Hosting Email: Almost Always a Mistake

Running your own Postfix/Dovecot stack gives you control but creates real problems:

  • Your IP will start in spam folders. Building reputation takes 3–6 months of careful sending.
  • Major providers (Gmail, Outlook) routinely block residential and small-cloud IP ranges by default.
  • You're now responsible for spam filtering, abuse reports, blocklist removals, and security patches.
  • Maintenance time alone costs more than $6/month/user.

Self-host email only if email is your business and you have dedicated infra people. Otherwise, pay $6.

Recommendation by Use Case

  • Solo founder / small team: Google Workspace. Done in 10 minutes, works forever.
  • Bootstrapped, cost-conscious: Zoho Mail free tier, then Zoho paid as you grow.
  • Personal, just need forwarding: Cloudflare Email Routing β†’ your existing Gmail.
  • Enterprise, Microsoft shop: Microsoft 365.
  • Hosting + email bundled cheap: Hostinger or Namecheap private email β€” fine for low volume.

The Setup Checklist

  1. Sign up with provider, add your domain.
  2. Provider gives you MX, SPF, DKIM, and verification TXT records.
  3. Set those records at your registrar's DNS panel.
  4. Wait for propagation (usually 5–30 minutes).
  5. Provider verifies β€” your mailbox is live.
  6. Add a DMARC record at _dmarc.yourdomain.com, start with p=none for monitoring, escalate to quarantine after a few weeks.
  7. Send a test email. Check it doesn't land in spam.

That's the entire workflow. The DNS step is where most people get stuck β€” every record matters and a typo breaks delivery silently.