Last Tuesday, a founder in a Discord server I'm in posted a screenshot. His SPF record was 412 characters long. Three different services layered on top of each other — Cloudflare for receiving, SendGrid for transactional, Gmail "Send mail as" for replies. The whole thing worked until it didn't, and then nobody could figure out which piece broke.

I've been there. Spent an entire Saturday night debugging why my "free" email setup was bouncing 30% of messages. The SPF lookup limit got me. I felt clever right up until I didn't.

That's the Cloudflare Email Routing trap. It's free. It's genuinely good at what it does. And it leads you down a path where "free" costs you hours debugging a Frankenstein email stack you built yourself.

But here's the thing — Cloudflare Email Routing isn't trying to be email hosting. It's forwarding. A different product for a different job. The confusion happens when people (myself included, circa 2024) use it as a substitute for actual mailboxes because the price is right. Zero dollars is hard to argue with.

Quick Verdict

TL;DR: Cloudflare Email Routing is free and works great for receive-only use cases — contact forms, domain parking, hobby sites. JustEmails at $49/year is the move when you need to actually send from your domain, use IMAP, or manage real mailboxes. If you're hitting Cloudflare's walls (no sending, SPF headaches, no IMAP), you've outgrown forwarding.

The question isn't "which is better." It's "do you need forwarding or hosting?"

Feature-by-Feature Comparison

Feature	Cloudflare Email Routing	JustEmails
Price	Free	$49/year
Receive email	Yes (unlimited)	Yes (unlimited)
Send from domain	No	Yes
Reply as your domain	No (requires workaround)	Yes
IMAP/POP3 access	No	Yes
Real mailboxes	No (forwarding only)	Yes (unlimited)
Webmail	No	Yes
Transactional API	No	Yes (1K/mo included)
SPF record	Adds Cloudflare, plus your relay	Single entry
DKIM signing	No (depends on relay)	Yes (auto-configured)
DMARC alignment	Tricky (forwarding breaks it)	Yes
Unlimited domains	Yes	Yes
Catch-all addresses	Yes	Yes
Storage	None (forwards to existing inbox)	10 GB included
Support	Community forums	Email support (4-hour target)

The table tells the core story: Cloudflare routes email elsewhere. JustEmails hosts it.

How Cloudflare Email Routing Actually Works

Cloudflare Email Routing isn't an email host. It's a forwarder sitting on your MX records. Here's the flow:

Someone sends to contact@yourdomain.com
Cloudflare receives it (your MX points to their servers)
Cloudflare forwards it to your personal Gmail, Outlook, or whatever
You see the email in your existing inbox

That's it. No mailbox created. No storage on Cloudflare's end. No way to access that email via IMAP. And critically — no way to reply as contact@yourdomain.com unless you configure a separate SMTP relay.

For hobby domains, this is perfect. I have three domains that exist solely to receive the occasional inquiry. Cloudflare handles them fine. Zero cost, zero maintenance.

The trouble starts when you need to reply.

The Sending Problem

Here's where most people hit the wall with Cloudflare.

You set up forwarding. Emails arrive in your Gmail. You hit reply. And the email goes out from your-personal-email@gmail.com, not from contact@yourdomain.com.

Some workarounds exist:

Gmail "Send mail as" + external SMTP relay: You can configure Gmail to send as your custom domain using a third-party SMTP server. SendGrid's free tier gives 100 emails/day. Amazon SES charges around $0.10 per 1,000 emails. Technically works. But now you're managing three services (Cloudflare receiving, Gmail interface, SendGrid/SES sending), and your SPF record needs to include all of them. For detailed DNS setup across any of these paths, check out our custom domain email setup guide. If you're confused about whether you need forwarding or aliases, our email alias vs forwarding breakdown explains the difference.

Zoho Mail free tier: Route through Cloudflare, but also create a Zoho free mailbox (up to 5 users) for sending. Except Zoho free doesn't allow third-party client access (no IMAP), so you're stuck in Zoho's webmail. And you're now maintaining two systems.

Just accept it: Some people reply from their personal email with a signature mentioning their business domain. Not professional, but it works for side projects.

None of these are clean. Not even close. And I say that as someone who ran the Gmail-plus-SendGrid setup for two years before admitting defeat.

Where Cloudflare Email Routing Wins

Credit where it's due. Cloudflare's offering has real advantages.

Price — Genuinely Free

No asterisks. No "free tier with limits." Cloudflare Email Routing is free on all plans including their free plan. Unlimited forwarding addresses, unlimited incoming volume. If your use case is receive-only, you can't beat free.

Setup Speed

Add your domain to Cloudflare (if it's not already there), enable email routing, add a destination address. Done. Five minutes if you're familiar with their dashboard. No MX record changes needed if you're already using Cloudflare for DNS — it handles that automatically.

Reliability

Cloudflare's network is massive. They're not going anywhere. Email forwarding is a rounding error on their infrastructure costs. You're getting enterprise-grade reliability for a consumer use case. (I'm mildly jealous of their infrastructure team, if I'm honest.)

Catch-All Simplicity

Want every email to *@yourdomain.com forwarded to one inbox? One toggle. No per-address setup. Good for parked domains where you just want to make sure you don't miss anything.

Where JustEmails Wins

Now the other side.

Sending From Your Domain

This is the big one. With JustEmails, you get actual SMTP credentials. Fire up Apple Mail, Thunderbird, or any email client. Send from contact@yourdomain.com. It goes out with proper headers, proper DKIM signing, proper SPF alignment. No relay chains, no workarounds.

For businesses, this isn't optional. You can't run client communication from forwarded-to-gmail@personal.com.

IMAP Access

Real mailboxes mean real IMAP. Use the desktop client you prefer. Access email offline. Search your full archive without leaving Gmail's web interface constraints.

Cloudflare forwards to Gmail, so technically you get Gmail's interface. But that Gmail inbox mixes your personal email with your business email unless you're paying for a separate Google account. Messy. JustEmails gives you dedicated mailboxes with dedicated access.

One DNS Setup

JustEmails auto-generates your SPF, DKIM, and DMARC records. Copy three TXT records and one MX record. Verify. Done.

The Cloudflare Email Routing + relay stack? Ugh. You need Cloudflare's include in SPF, your relay's include in SPF, DKIM keys from your relay (and possibly a second set for transactional), and MX records pointing at Cloudflare. Then hope the total SPF record stays under the 10-lookup limit. It's fragile. If you're migrating off a more complex setup, our DMARC p=none to p=reject guide walks through authentication rollout step by step.

Transactional Email Bundled

Need to send password resets, receipts, or notifications from your app? JustEmails includes 1,000 transactional API emails per month at no extra cost, with paid tiers at $25/year per 10K-emails/month if you need more. Our SMTP vs API transactional email guide covers when to use each method.

Cloudflare doesn't touch this use case. You'd bolt on SendGrid, Postmark, Resend, or SES separately. More accounts, more integrations, more billing.

Unified Inbox Across Domains

If you're managing 5, 10, or 40 domains (agencies, this is you), JustEmails' dashboard shows all inboxes in one view. Cloudflare forwards each domain to... wherever. You're stuck managing multiple Gmail filters or multiple destination accounts to keep things organized.

Pricing Reality Check

Cloudflare Email Routing: $0/year for forwarding. But if you need sending, add the cost of whatever relay you use (SendGrid free tier, SES at ~$0.10/1K, Postmark at $1.25/1K). And the time cost of debugging a multi-service stack.

JustEmails: $49/year flat. Unlimited domains, unlimited mailboxes, 10 GB storage, sending included, 1K transactional API emails/month included. Add $100/year per 100 GB if you need more storage. Add $25/year per 10K-email transactional tier if you're sending volume. See how this stacks up against the enterprise option in our JustEmails vs Google Workspace cost comparison.

For receive-only hobby domains, Cloudflare wins on price. For actual business email where you need to send and reply, JustEmails' $49/year is cheaper than the hidden costs (and debugging time) of stitching together a free stack.

The DMARC Problem

This is technical. Bear with me — it matters.

DMARC relies on alignment. The domain in your email headers needs to match the domain that signed the DKIM or is authorized in SPF. When Cloudflare forwards email, the original sender's DKIM signature often breaks (Cloudflare might modify headers). SPF also fails because the sending IP is now Cloudflare, not the original sender.

Cloudflare has mitigated some of this with ARC (Authenticated Received Chain) headers, but not all receiving servers honor ARC. Forwarded email through Cloudflare can end up in spam folders on the recipient's end — not your recipient, the person you forwarded to.

With a real email host like JustEmails, you're not forwarding. You're the originating sender. DKIM and SPF alignment are native. DMARC passes cleanly.

Who Should Pick What

Keep Cloudflare Email Routing if:

You only need to receive, not send
Your domain is a personal portfolio, hobby project, or parked site
You're fine with replies coming from your personal email
You enjoy tinkering with multi-service email stacks (no judgment)
Budget is hard zero and you're willing to trade complexity for cost

Switch to JustEmails if:

You need to reply from your custom domain
You want IMAP access with a desktop client
You're managing email for clients or a business
You're sending transactional emails from an app
You hit DMARC/SPF issues with the forwarding setup
You're spending more time debugging email than doing actual work (this was me)

Hybrid approach: Some people use Cloudflare for receive-only domains (parked domains, legacy domains) and JustEmails for their active business domains. Nothing wrong with that. Pick the right tool for each job.

Migrating From Cloudflare to JustEmails

If you've outgrown forwarding, the migration takes maybe an hour:

Sign up at JustEmails and add your domain
Copy the MX, SPF, DKIM, and DMARC records from the dashboard
In Cloudflare DNS, remove the email routing MX records
Add JustEmails' MX record
Add the TXT records for SPF, DKIM, and DMARC
Wait for propagation (usually 15-60 minutes)
Verify in the JustEmails dashboard — green checkmarks when it's live

Your Cloudflare account stays intact for DNS and CDN. You're just moving email from their forwarding service to proper hosting.

Final Verdict

Look, I'm not going to pretend this is a hard decision. It's actually pretty simple once you're honest about what you need.

Cloudflare Email Routing is a legitimately good free product. If you're receiving contact form submissions on a personal site, use it. Don't pay for what you don't need. I still use it for three parked domains.

But if you're catching yourself wiring up Gmail "Send mail as" with a third-party SMTP relay, adding multiple includes to your SPF record, and wondering why your emails land in spam — you've outgrown forwarding. That's not a knock on Cloudflare. They built a forwarder, and it forwards. The problem is using it as a substitute for hosting. I wasted probably 40 hours over two years doing exactly that.

JustEmails is $49/year. That's less than one month of Google Workspace. You get real mailboxes, real SMTP sending, IMAP access, and DNS that doesn't require a flowchart to debug. Not perfect — no product is — but it solves the sending problem without the duct tape.

Use the right tool. Sometimes that's free. Sometimes that's $4.08 a month.

Frequently Asked Questions

Can I send emails from my custom domain using Cloudflare Email Routing?

No. Cloudflare Email Routing is receive-only. It forwards incoming emails to an existing inbox (like Gmail) but doesn't give you any way to send from your custom domain. To reply as contact@yourdomain.com, you need either a workaround (Gmail's "Send mail as" with a third-party SMTP relay) or a real email host like JustEmails that includes outbound sending.

Is Cloudflare Email Routing actually free?

Yes — completely free with no volume limits on forwarding. Cloudflare doesn't charge for email routing even on their free plan. The catch is that it only forwards to existing inboxes; it doesn't give you mailboxes, IMAP access, or the ability to send. If you only need to receive, it's genuinely useful. If you need to reply from your domain, you'll pay elsewhere.

What's the cheapest way to send from a custom domain?

If you already have Gmail, you can use Cloudflare Email Routing for receiving plus a third-party SMTP relay (like SendGrid free tier or Amazon SES at ~$0.10/1K emails) for sending. Total cost approaches zero. But it's fragile — multiple services, multiple points of failure, and your sending domain's SPF record gets complicated. JustEmails at $49/year bundles receive + send + transactional API in one place with one DNS setup.

Should I migrate from Cloudflare Email Routing to JustEmails?

Depends on your use case. If you're running a personal blog or portfolio site and you just want to receive contact form submissions, keep Cloudflare — it's free and works. If you need to reply as your domain, manage multiple mailboxes, use IMAP with a desktop client, or send transactional emails from your app, JustEmails makes more sense. The migration is simple: add your domain, point MX records to JustEmails, and you're live in under an hour.

Try JustEmails

Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.

Start your 7-day free trial → · How it compares

Cloudflare Email Routing vs JustEmails: Free Forwarding or Real Mailboxes?