Side by side
| mxproxy | Cloudflare Email Routing | |
|---|---|---|
| Price to receive | Free up to 10 messages/month; paid from $4.00/month | Free |
| DNS | Stays where it is: you only create MX and TXT records | Must use Cloudflare DNS (its nameservers) |
| Reply as the domain | SMTP with DKIM on every paid plan | Through Email Sending, in beta, with a paid Workers plan (3,000 emails/month included, then US$0.35 per thousand) |
| Destinations | Up to 10 inboxes per address, depending on the plan | Each destination must be verified by email before it goes into a rule; up to 200 destinations per account |
| Rules and addresses | 100 forwarders per domain on Personal; unlimited from Pro up | 200 rules per domain |
| Programmable | REST API, webhook and Telegram | Workers (your own code for each email) |
Cloudflare facts checked in its documentation on October 20, 2026. Sending (Email Sending) was in beta on that date.
When Cloudflare Email Routing is better
- The domain is already on Cloudflare and you only need to receive: it is free, with no published volume limit.
- You write code: with Workers you can handle each email however you like.
When mxproxy is better
- Your DNS is at a registrar, a host or your online store and you do not want to move it: just create MX and TXT records where it is.
- You want to reply as
hello@from Gmail or Outlook, with DKIM, without writing code. - An address has to reach several inboxes at once, or you want a spam filter with an adjustable level per domain.
Moving from Email Routing to mxproxy
Email Routing locks its MX, SPF and DKIM records. Disable it in Email Routing › Settings › Disable Email Routing, which removes those records, and create mxproxy’s in DNS › Records. The step by step is in the Cloudflare guide.