Email forwarding and email hosting are not the same thing. Most domain registrars offer forwarding for free, and many new domain owners set it up thinking they have business email. They do not.
This piece explains what each actually does, where each breaks, and when forwarding is acceptable vs when you need proper hosting.
Email forwarding: how it works
Email forwarding is a routing rule at the DNS level. You configure your domain registrar (GoDaddy, Namecheap, Cloudflare, Spaceship) to forward any email sent to you@yourcompany.com to your personal inbox, usually you@gmail.com.
What happens when someone emails you:
- They send to
you@yourcompany.com - Your registrar’s mail server receives it
- The mail server forwards it to
you@gmail.com - It appears in your Gmail inbox, from the original sender
The professional illusion works — at the receiving end. The collapse happens when you reply.
The reply problem
When you reply to a forwarded email in Gmail, Gmail sends the reply from you@gmail.com — not from you@yourcompany.com. The thread now shows your personal Gmail address. The professional domain address disappears.
Workarounds exist: Gmail’s “Send mail as” feature lets you configure a custom From address using your domain. This partially solves the reply problem but introduces its own limitations:
- You are using Gmail’s SMTP servers, which have a mixed reputation (shared with millions of free users)
- Google’s terms allow them to disable this feature for free accounts
- You still have no admin control, no proper audit logs, no user management
Email hosting: how it works
Business email hosting gives you dedicated mailboxes on a mail server configured specifically for your domain.
When someone emails you@yourcompany.com:
- The email goes to your hosting provider’s mail servers (configured via your domain’s MX records)
- It is stored in your mailbox on those servers
- You access it via webmail, or via an email client using IMAP
- When you reply, the reply sends from
you@yourcompany.com— your domain, your infrastructure
No aliases, no forwarding hacks. Your domain, end to end.
Deliverability: the gap that matters
Email forwarding is a deliverability problem waiting to happen.
When your registrar forwards a message, the forwarded message now comes from the registrar’s IP address — not the original sender’s IP. This can trigger SPF failures at the receiving end, because the forwarded message appears to come from an IP that was not on the original sender’s SPF record.
Forwarding also means your outbound email sends via Gmail’s free-tier SMTP infrastructure. Gmail free accounts have lower sending reputation than Google Workspace accounts. The inbox placement rate (IPR) of email sent via Gmail’s free SMTP is measurably lower than email sent via a dedicated hosting plan.
When forwarding is acceptable
Forwarding is acceptable in one specific scenario: you are a solo consultant, you send very few emails (fewer than 20/day), you are not running any active outbound communication, and you need a custom domain address for less than the cost of hosting.
Even then: Zoho Mail Forever Free gives you 5 proper mailboxes at your domain for $0, with full send/receive at your domain, without the reply-address collapse problem. Forwarding is strictly worse than Zoho Free in every dimension.
The honest recommendation
If you bought a domain and are considering forwarding:
- Stop.
- Set up Zoho Mail Forever Free (free, 5 mailboxes, your domain, 45 minutes)
- Or set up Google Workspace (14-day trial, full admin control, then $7.20/seat/mo)
If you are at a registrar that is bundling email forwarding as part of a hosting package, confirm it is forwarding and not hosting. Forwarding is free because it costs almost nothing to provide. Hosting has real infrastructure behind it.
Related: What is an MX record? | Inbox placement rate explained