Our verdict: great for receiving, incomplete for a business identity
If your domain already uses Cloudflare DNS and you only need to receive mail at a professional address, Email Routing is a low-cost way to do it. Cloudflare lists it as available on Free and Paid plans [1]. The gap is outbound mail. Cloudflare's postmaster documentation says Email Routing does not support sending or replying from your Cloudflare domain, and that the reply will be sent from your destination address [3]. A customer who writes to hello at your domain may therefore get a reply from a personal Gmail address.
We would use it for low-volume inboxes such as a contact address on a portfolio site, and choose a real mailbox once replies need to come from the domain.
What it does and does not do
Cloudflare also says it rewrites the envelope sender to a Cloudflare-controlled forwarding domain while leaving the From header unchanged [3]. Cloudflare also documents that it adds DKIM signatures to forwarded mail [3].
| Question | What Cloudflare documents |
|---|---|
| Plan availability | Available on Free and Paid plans [1] |
| DNS requirement | You must be using Cloudflare DNS [4] |
| Records added | MX records, an SPF TXT record and a DKIM TXT record [4] |
| Routing rules | 200 per domain; each rule maps to one destination or one Worker [2] |
| Destination addresses | 200 per account, shared across domains; all must be verified [2] |
| Inbound message size | 25 MiB; larger messages are rejected [2] |
| Sending or replying from your domain | Not supported by Email Routing [3] |
| Bounce reports | Does not forward non-delivery reports to the original sender [3] |
Setup procedure
- Confirm the domain's nameservers point to Cloudflare; Email Routing requires Cloudflare DNS [4].
- Write down any existing MX records. If another provider currently receives your mail, enabling routing will change where mail is delivered.
- Enable Email Routing for the domain and let Cloudflare add its MX, SPF and DKIM records [4].
- Add a destination address, such as your Gmail address, then open the verification email Cloudflare sends and select Verify email address [4].
- Create a custom address rule, for example hello at your domain, pointing to that verified destination.
- Send a test from a different account and check that it arrives, including in the spam folder.
The reply gap and your options
Because Email Routing only receives and forwards, you need a decision about replies before you print the address on invoices.
- Reply from the destination address. Simplest, but customers see a personal address [3].
- Use Gmail's 'Send mail as' with an outgoing (SMTP) server from a provider that sends for your domain. Google's help page asks work and school accounts to enter an SMTP server, username and password, and notes that starting January 2027 Gmail will no longer support 'Send as' for third-party email addresses such as @yahoo.com or @outlook.com [5]. Confirm how that change affects your setup before building on it.
- Move the address to a real mailbox provider, such as a free or paid business email plan, which sends and receives at your domain.
Who it fits, and who should skip
It fits a freelancer or very small business that already manages DNS in Cloudflare, receives a handful of inquiries a week, and can live with replying from another address or has a separate sending setup. Skip it if you need shared inboxes, an archive held at your domain, or professional replies without extra configuration. Also skip it if your domain's DNS is hosted elsewhere and you do not want to move it, since Cloudflare DNS is required [4].
Pitfalls and decision rule
Hypothetical example: a photographer receives about ten inquiries a week at hello at her domain and replies to most within a day. Routing to Gmail costs nothing extra and works for receiving. Once she starts sending quotes and invoices, replies from a personal address look inconsistent, which is the point to add a mailbox at the domain. Our rule: use Email Routing for receive-only addresses; use a real mailbox once replies must come from the domain.
- Forgetting to verify the destination address; rules only deliver to verified destinations [2].
- Overwriting a working mail provider's MX records by enabling routing on a domain that already receives mail elsewhere.
- Expecting delivery failure notices: Email Routing does not forward non-delivery reports to the original sender [3].
- Sending attachments over 25 MiB to the routed address; they are rejected [2].
Questions before you decide
Is Cloudflare Email Routing free?
Cloudflare's Email Routing documentation says it is 'Available on Free and Paid plans.' You must be using Cloudflare DNS for the domain.
Can I reply from hello at my domain with Email Routing?
Not through Email Routing itself. Cloudflare's postmaster page states that Email Routing does not support sending or replying from your Cloudflare domain, and that a reply will be sent from your destination address.
How many addresses can I forward?
Cloudflare's limits page lists 200 routing rules per domain and 200 destination addresses per account, shared across all domains. Each destination address must be verified.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Cloudflare Docs: Email Routing overview Accessed 13 Oct 2026
- Cloudflare Docs: Email Routing limits Accessed 13 Oct 2026
- Cloudflare Docs: Email Routing postmaster Accessed 13 Oct 2026
- Cloudflare Docs: Enable Email Routing Accessed 13 Oct 2026
- Gmail Help: Send emails from a different address or alias Accessed 13 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.