iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Cloudflare Email Routing can forward messages sent to addresses on your personal domain to an inbox you already use. It is an inbound forwarding service, not a full mailbox: it does not, by itself, let you reply from your custom domain address. You also need to use Cloudflare DNS, verify the destination inbox, and check existing mail records before enabling routing.
What Cloudflare Email Routing does—and does not do
Email Routing receives mail addressed to your domain, such as hello@example.com, and forwards it to a verified destination address, such as an existing personal inbox. It can also route messages to a Worker for processing. Cloudflare describes the service as free forwarding for people who only need to receive mail; that does not mean a domain, full mailbox, or outbound email service is included. Cloudflare’s email-records guide says an SMTP provider is needed to send and receive email from a domain.
So, can you reply using your domain email? Not with Email Routing alone. A forwarded message arrives at your existing inbox, but forwarding does not configure that inbox to send as hello@example.com. If you need to send or reply from the custom address, arrange a mailbox or an email-sending provider separately and follow its setup instructions.
What you need before setting it up
- A domain using Cloudflare DNS. Cloudflare’s requirement is direct: “You must be using Cloudflare DNS to use Email Service.” Cloudflare’s Route emails documentation
- An inbox you can access to receive and complete Cloudflare’s destination-verification message.
- A review of any current email provider’s MX-record requirements. MX records control where incoming mail for the domain is delivered, and Cloudflare’s routing records may conflict with another provider’s records. Cloudflare’s domain configuration guide
Set up a forwarding address
- Use Cloudflare DNS for the domain. If the domain is not already using Cloudflare DNS, make that change before attempting to use Email Service.
- Open the routing setup. In the Cloudflare dashboard, go to Compute > Email Service > Email Routing and onboard the domain. Review the proposed DNS changes before completing setup, especially if the domain already receives mail elsewhere. Cloudflare’s setup can add the required root-domain MX and email-authentication records. Route emails
- Allow DNS changes to take effect. Cloudflare says updates on Cloudflare DNS usually complete in 5–15 minutes, but can take up to 24 hours to propagate globally. These are service timing estimates, not guaranteed deadlines. Domain configuration
- Add and verify a destination. Enter the existing inbox where you want messages forwarded, then open Cloudflare’s verification message and complete the verification. An unverified destination cannot be used in an active routing rule. Route emails · Email routing rules and addresses
- Create the routing rule. Choose the address or local part (for example,
hello), select the domain, and choose the verified inbox as the destination. Cloudflare also supports routing to Workers. Email routing rules and addresses - Test from another account. Send a message from an email account other than the destination inbox, then check the destination inbox and its spam folder. Cloudflare notes that some providers may discard messages that appear to come from the same account to which they are being delivered. Route emails
Check existing mail records and plan changes carefully
Enabling Email Routing changes how incoming mail is directed: Cloudflare manages the domain’s routing MX records. If you already use a mailbox provider, compare its required MX setup with Cloudflare’s proposed changes before proceeding. Do not assume both providers’ MX records can remain in place without affecting delivery. Cloudflare’s domain configuration guide warns about conflicts with other providers’ MX records.
#1 Best Overall
If you later move to another email provider, Cloudflare recommends unlocking the routing records and adding the replacement provider’s records before disabling Email Routing. Disabling routing removes the routing-related DNS records Cloudflare added, so changing the order can interrupt mail flow. Domain configuration
For separately configured mail-server hostnames, keep SMTP, IMAP, and POP3 records DNS-only rather than using Cloudflare’s standard HTTP proxy; those mail protocols do not work through that proxy. This guidance applies to mail-server records you add, not as a reason to casually edit automatically managed Email Routing records. Cloudflare’s email troubleshooting guide
Rank #2
Understand SPF and DKIM records
Email Routing setup includes email-authentication records, including SPF and DKIM. Cloudflare notes that missing authentication records can cause messages to be rejected, treated as spam, or trusted less. Correct records help with authentication, but do not guarantee that a destination provider will place every forwarded message in the inbox. Review Cloudflare’s proposed DNS changes and its domain configuration guidance rather than deleting or replacing authentication records without understanding what uses them.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose forwarding or a mailbox based on how you use email
Forwarding suits a domain address you want to receive at an inbox you already check. A mailbox or sending-provider setup is the appropriate next step if you need an independent inbox, or need to send and reply as your domain address. That choice affects DNS: a separate provider may require its own MX records, so plan the configuration before changing Cloudflare-managed routing records.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
