Forward Domain Email with Cloudflare

Why use a custom domain address?

Owning a domain gives you a much cleaner way to manage incoming mail without running your own mail server:

Unlimited aliases for filtering: Give every service its own address (shopping@example.com, github@example.com, bank@example.com) and route them all to one inbox, where filters can label or mute them automatically.
A cleaner public identity: hi@yourdomain.com on a resume, invoice, or company page looks far more intentional than a random free-mail handle.

All you need is a domain on Cloudflare DNS and an existing inbox (like Gmail) to receive the forwarded messages—or an agent connected to Cloudflare to configure it for you.

How Cloudflare Email Routing works

Cloudflare Email Routing is an inbound forwarding layer, not a full mailbox or SMTP server. It accepts mail sent to hello@example.com and forwards it to a verified destination inbox you already use.

When you onboard a domain, Cloudflare automatically adds the required MX, SPF, and DKIM DNS records. DNS propagation usually finishes in 5–15 minutes, though it can take up to 24 hours.

Manual setup in 4 steps

Open Compute → Email Service → Email Routing, click Onboard Domain, and select your domain.
Under Destination Addresses, add your personal inbox and click the verification link Cloudflare emails to it.
Under Routing Rules, create a custom address (such as work@example.com), choose Send to an email, and select your verified destination.
Send a test email from a different account (sending from the same Gmail account that receives the forward often deduplicates in Gmail’s UI). Check Spam if it does not arrive right away.

One inbox, unlimited addresses

Cloudflare supports up to 200 individual routing rules per domain, or you can enable the catch-all rule so that any address at @example.com lands in your destination inbox. You can also turn on subaddressing (me+shopping@example.com), which preserves the +tag for inbox filters or Cloudflare Email Workers.

Inbound only by default

Email Routing creates receiving aliases, not separate mailboxes. If you hit “Reply” in Gmail, the reply comes from your Gmail address—not your custom domain—unless you pair it with an outbound SMTP provider (such as Resend, Fastmail, or Gmail’s custom “Send mail as” SMTP).

Let an agent configure it

Cloudflare publishes agent setup guides for tools that support Skills and MCP. Once your agent is authenticated, hand it this prompt:

Set up Cloudflare Email Routing for example.com.
Forward all incoming addresses to me@gmail.com using a catch-all rule.
Show me every DNS and routing change before applying it.
Do not remove or replace existing mail records without my approval.

The agent can stage the DNS and routing rules, and you only need to click the destination-address verification link in your inbox. If your domain already uses another mail provider, review the existing MX records carefully before approving any changes.