Recommended Free Tools
Cloudflare Email Routing can forward messages sent to addresses at your personal domain to an inbox you already use. It is an inbound forwarding service—not a full mailbox—and it does not, by itself, let you send or reply from your custom domain address. You need to use Cloudflare DNS, verify your destination inbox, and check existing mail records before turning it on.
What Cloudflare Email Routing does—and what it does not
Email Routing accepts incoming messages for addresses at your domain and forwards them to a verified destination address. You can also route messages to a Cloudflare Worker for processing. Cloudflare describes the service as free email forwarding for people who only need to receive mail; that does not make domain registration, a mailbox, or outbound email free. Cloudflare’s DNS documentation distinguishes forwarding from the SMTP provider needed to send and receive email using a domain.
As an Amazon Associate I earn from qualifying purchases.
A forwarded message arriving in an existing inbox does not configure that inbox to send replies as [email protected]. If you need to reply from the custom address, arrange a mailbox or an email-sending provider separately, and follow that provider’s sending and authentication setup.
What you need before setting it up
- A domain using Cloudflare DNS. Cloudflare states, “You must be using Cloudflare DNS to use Email Service.” Cloudflare’s Route emails guide covers the prerequisite.
- An inbox you can access to receive and complete Cloudflare’s destination verification message.
- A plan for your domain’s existing mail service, if any. Email Routing manages the domain’s MX records, which determine where incoming email is delivered. Enabling it can conflict with another provider’s MX setup. Review the DNS changes Cloudflare proposes before proceeding, and compare them with the records your current provider requires. Cloudflare’s domain configuration guide explains the routing records.
Set up a forwarding address
- Use Cloudflare DNS for the domain. If the domain is not already using Cloudflare DNS, move it to Cloudflare DNS before configuring Email Routing.
- Open the Email Routing setup. In the Cloudflare dashboard, go to Compute > Email Service > Email Routing and onboard the domain. Review the proposed DNS changes; onboarding can add the required root-domain MX and email-authentication records. Cloudflare estimates DNS updates on Cloudflare DNS usually complete in 5–15 minutes, although global propagation can take up to 24 hours. These are service timing estimates, not a guarantee that every message will arrive immediately. See Cloudflare’s domain configuration details.
- Add and verify a destination. Enter the existing inbox where you want messages delivered, then open Cloudflare’s verification message and complete the confirmation. An unverified destination cannot be used in an active routing rule. Cloudflare’s setup guide and routing-address documentation describe this step.
- Create the route. Choose the address’s local part—the portion before the at sign, such as
hello—select your domain, and set the verified inbox as the destination. Cloudflare also supports routing to Workers; for ordinary forwarding, select the inbox. - Test from a different account. Send a message from an email account other than the destination address, 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 they are being delivered to, so a self-send is not a reliable test.
Check existing MX records and plan changes carefully
MX records tell sending mail servers which service receives mail for your domain. Email Routing manages these records for its forwarding setup. If you already use a hosted mailbox or another mail provider, its required MX records may conflict with Cloudflare’s routing records. Do not assume you can keep both services receiving mail simply by adding both sets of records; check the providers’ instructions and decide which service should handle incoming messages. Cloudflare’s domain configuration documentation describes the records it uses.
#1 Best Overall
If you later switch away from Email Routing, plan the DNS change to avoid a gap: Cloudflare recommends unlocking the routing records and adding the replacement provider’s records before disabling Email Routing. Disabling the service removes the routing-related DNS records it added. Check that the new provider’s records are in place and that mail is flowing before completing the change.
Keep mail-server hostnames DNS-only
If you configure separate mail-server records for a mailbox or sending provider, keep the relevant SMTP, IMAP, and POP3 hostnames DNS-only. Cloudflare’s standard HTTP proxy does not proxy those mail protocols. This guidance is for mail-server hostnames you add; do not casually alter Email Routing’s automatically managed records. Cloudflare’s email troubleshooting guide explains the proxy limitation.
Authentication records help, but do not guarantee inbox delivery
Cloudflare’s routing setup includes email-authentication records such as SPF and DKIM. Missing or incorrect authentication can contribute to rejection, spam classification, or reduced trust, but the presence of those records does not guarantee inbox placement. If another service also sends mail for your domain, check its authentication requirements and make sure the domain’s DNS records account for the services you actually use. Cloudflare documents the routing records and related issues in its domain configuration and email troubleshooting guides.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWhen forwarding is enough
Email Routing fits a simple use case: you want an address at your domain to receive messages in an inbox you already have, and you do not need that setup to provide a mailbox or send as the domain. If you want to compose and reply using the custom address, use a mailbox or sending-provider arrangement that supports outbound mail, and configure its DNS requirements deliberately. The receiving and sending sides are separate decisions.
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.
