Cloudflare Email Routing for a custom domain

A personal or small-business brand wants email like [email protected] without paying for a hosted mailbox. Cloudflare Email Routing provides that by forwarding inbound mail for your domain to an existing inbox, and it is available free on Cloudflare-managed DNS.

What it offers

Email Routing sits on a domain whose DNS is managed by Cloudflare and forwards incoming mail to destinations you own. Each routing rule maps an email pattern to a destination address or a Worker for programmatic handling:

• Custom addresses: rules that map hello@, billing@, or any local part to your inbox.
• A catch-all rule: forwards every unrecognised address to one destination, useful to see where mail lands.
• Destination verification: you confirm ownership of each address before mail is routed to it (Cloudflare emails a verification code); limits are around 200 routing rules per domain and 200 verified destinations per account.
• No message-count cap on forwarding: the service receives unlimited inbound mail and passes it to the destination inbox; there is no mailbox hosting to fill up.

Set it up

1. Confirm the domain is on Cloudflare with DNS managed there. Open the domain and select Email Routing.
2. Add the destination address and complete the verification email Cloudflare sends.
3. Create routing rules, for example [email protected] to your personal inbox, and enable a catch-all rule if you want everything forwarded.
4. Set the associated DNS records (the MX and the routing TXT records Cloudflare places) as instructed so inbound mail reaches the service, then test by sending to the custom address and confirming it lands in the destination.

Because the forwarding domain appears in the security checks, the SPF, DKIM and DMARC guide explains the records that keep the destination provider happy with forwarded mail.

What it cannot do

Email Routing is forward-only. There is no hosted mailbox or webmail, and you cannot send outbound email directly from the custom address through the service alone. Sending still needs a separate SMTP provider or an email-sending service. For pure receiving, the limits rarely matter; for a full collaboration suite (calendar, storage, outbound), a paid mailbox remains the fit.

Prevention

• Keep destination addresses verified and current in the account, or mail silently fails to route.
• Do not point the same domain's email at a host you are about to move; coordinating the migration is covered in the email DNS migration guide.
• If you were forwarding via an old host, reconcile the records so you do not run two mail paths at once.

Because the setup changes the DNS on the domain, read the Cloudflare DNS records guide to place MX and SPF records correctly, and the email migration article for moving an existing mailbox into the forwarding model.