Free Business Email vs Cloudflare Email Forwarding
Google results for “free business email” often show Cloudflare Email Routing + Gmail send-as. That stack can look like hello@yourdomain.com for $0 — but it is forwarding, not a hosted mailbox.
MailShrine Free includes 1 mailbox and 2 aliases (for example you@ + hello@ + info@) on a domain you own. That is a different product.
Real-life example: Studio North
Kemi followed a YouTube “$0 Cloudflare email” video. Receiving worked; mobile reply-as broke; a contractor could not be removed without sharing her Gmail.
She moved to MailShrine Free for a real inbox while keeping Cloudflare only as DNS.
Head-to-head
| Cloudflare Routing + Gmail | MailShrine Free | |
|---|---|---|
| Monthly email cost | $0 | $0 |
| Real mailbox on host | No | Yes |
Webmail for @domain | Via Gmail | Native webmail |
| Aliases / addresses | Many forwards | 2 aliases + 1 mailbox |
| Team offboarding | Manual / messy | Change host access |
| Calendar “from” quirks | Common with send-as | Cleaner with real mailbox |
When forwarding is OK
- Solo hobby project
- You accept Gmail as the only UI forever
- Zero interest in IMAP to Outlook as
@domain
When Free hosted mail wins
- Customers depend on you daily
- You want aliases without Gmail App Password drama
- You may add a second human soon (startups)
What you need to switch
DNS access (update MX away from routing) + MailShrine Free + a test window.
Step 1: Inventory Cloudflare rules
List every forward address you publish publicly.
Step 2: Add MailShrine domain + MX
Publish MailShrine MX/TXT; remove routing MX that conflicts (setup).
Step 3: Recreate addresses
Mailbox for your name; aliases for hello@ / info@ (aliases).
Step 4: Dual-run briefly
Keep an eye on Cloudflare destination Gmail during TTL (DNS timing).
Step 5: Retire send-as
Remove brittle Gmail SMTP send-as once MailShrine round-trips pass.
Checklist
- Understood forwarding ≠ mailboxCompleted
- MX moved to MailShrineCompleted
- Free 1+2 configuredCompleted
- Gmail send-as removedCompleted
Common mistakes
- Running Routing MX and MailShrine MX together.
- Orange-cloud proxy on mail records.
- Never testing outbound from the new host.
Next steps
Citations & References
- Reference: Google: Email sender guidelines
- Reference: ICANN: What is DNS?
Written by Daniel O., Business Email Specialist. Daniel compares forwarding hacks with real mailbox hosting for SMEs.
