Free Email Addresses on Your Own Domain With Cloudflare Email Routing (Step by Step)

An email address like hello@yourbusiness.com looks more established than yourbusiness2024@gmail.com. Customers trust it more, and it doesn’t break when you change email providers. But a full business email plan costs a monthly fee per user, which adds up when you’re starting out and mostly need to receive inquiries.

If your main need is “mail sent to my business address should land in the inbox I already check,” you can do that for free with Cloudflare Email Routing. We use Cloudflare for DNS on our own domains and set this up regularly. Here’s the full process, including the limitations you should know about before you start.

What Email Routing Does (and Doesn’t Do)

Email Routing is a forwarding service. You create addresses on your domain, and Cloudflare forwards anything sent to them to an inbox you already have (Gmail, Outlook, iCloud, whatever).

It does:

Receive mail at as many custom addresses as you want (hello@, billing@, jobs@…)
Forward each one to the same or different existing inboxes
Optionally catch mail sent to any address on your domain (a “catch-all”)
Optionally pass incoming mail to a Cloudflare Worker for custom processing, for developers who want it

It doesn’t:

Give you a new mailbox. Mail lives in your existing inbox.
Send mail as your custom address on its own. More on this below.

For a solo business or a small team that mainly needs a professional contact address, receive-and-forward covers most of what you need.

Before You Start: The One Requirement

Your domain’s DNS must be managed by Cloudflare. If you bought your domain from another registrar, you don’t have to transfer it. You add the domain to a free Cloudflare account and change the domain’s nameservers at your registrar to the two Cloudflare gives you.

When you add the domain, Cloudflare scans your existing DNS records and copies them over. Check that list carefully before switching nameservers. Every record your website and any existing services depend on needs to be there. If the scan misses one, that service will break when the nameservers change.

💡

Pro Tip

Screenshot your current DNS records before changing anything. If something stops working after the switch, the screenshot is the fastest way to see what’s missing. It takes ten seconds and has saved us hours.

The Mistake That Breaks Existing Email

This is the most important warning in this guide.

Email is delivered according to your domain’s MX records. When you enable Email Routing, Cloudflare adds its own MX records and needs them to be the ones in charge. If your domain already receives mail somewhere else (Google Workspace, Microsoft 365, or your web host’s mail), enabling Email Routing will redirect that mail away from the existing service.

So before enabling it, look at your current MX records:

No MX records, or ones you know are unused? Go ahead.
MX records pointing at a provider you actively use? Stop. Either keep that provider for mail and skip Email Routing, or migrate deliberately, having confirmed nobody still relies on the old mailboxes.

Step 1: Enable Email Routing

In the Cloudflare dashboard, select your domain and open Email → Email Routing. Start the setup. Cloudflare will offer to add the DNS records it needs:

Several MX records pointing at Cloudflare’s mail servers
A TXT record for SPF, which tells other mail servers that Cloudflare is allowed to handle mail for your domain

Let Cloudflare add them automatically. If you already have an SPF record, don’t create a second one, because a domain must have only one SPF record. Merge Cloudflare’s include: entry into your existing record instead.

Step 2: Add and Verify a Destination Address

A destination is the real inbox mail should be forwarded to. Add it in the Destination addresses section. Cloudflare sends a verification email to that inbox; click the link inside it. Until you do, nothing will be forwarded there. This step prevents anyone from using Email Routing to forward mail to an inbox they don’t own.

Step 3: Create Your Custom Addresses

Under Routing rules, create an address like hello@yourbusiness.com and choose the verified destination. Repeat for any other addresses.

Consider whether you want a catch-all. It forwards mail sent to any address at your domain, so a customer who types info@ instead of hello@ still reaches you. The downside is spam: spammers send to guessed addresses, and a catch-all accepts all of them. A sensible middle ground is a handful of explicit addresses and no catch-all.

Step 4: Test It

Send an email from a different account (not the destination inbox itself) to your new address. It should arrive within a minute or so. If it doesn’t:

Check that the destination address shows as verified.
Check the routing rule is enabled.
Check your destination inbox’s spam folder. Forwarded mail sometimes lands there at first.
In the Email Routing overview, check the activity log, which shows whether Cloudflare received the message and what it did with it.

Sending Mail as Your Custom Address

This is where most people get stuck. Replying to a customer from your Gmail will show your Gmail address, not hello@yourbusiness.com. To send as your custom address you need an outgoing mail (SMTP) server that’s authorized to send for your domain.

Your realistic options:

A transactional or SMTP email provider. Several offer free tiers suitable for low volume. You add their DNS records to your domain (SPF and DKIM), then add your custom address in Gmail’s Settings → Accounts → Send mail as using their SMTP details.
A full mailbox provider (Google Workspace, Microsoft 365, Zoho, Fastmail, and others). This replaces Email Routing entirely and gives you real mailboxes with sending built in. It’s the right choice once you have a team, need shared calendars, or send a lot of mail.
Cloudflare’s own sending options. Cloudflare has been expanding into outbound email. Check its current documentation, since what’s available, and on which plans, has been changing.

Whichever you choose, set up authentication records. SPF says which servers may send for your domain. DKIM cryptographically signs your messages. DMARC tells receivers what to do when a message fails those checks. Without them, mail from your custom address is much more likely to land in spam, or to be rejected outright by large providers, which have tightened their requirements in recent years.

A safe starting DMARC record, which only collects reports and doesn’t reject anything, looks like:

_dmarc.yourbusiness.com  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@yourbusiness.com"

Once reports show your legitimate mail passing, you can tighten p=none to p=quarantine and eventually p=reject.

When to Upgrade From Email Routing

Free forwarding is a great starting point, but it stops fitting when:

Several people need separate inboxes with their own logins.
You need to send a lot of mail as your domain, every day.
You need compliance features like retention policies, legal holds, or audit logs.
You want everything in one place: mail, calendar, and documents under one business account.

At that point a paid mailbox provider is worth the monthly cost. Because your domain is on Cloudflare, switching is a matter of replacing the MX records, and your addresses don’t change.

The Five-Minute Summary

Put your domain’s DNS on Cloudflare (free). Check that all existing records came across.
Check your current MX records. Don’t overwrite a mail service someone is using.
Enable Email Routing and let it add its MX and SPF records. Keep a single SPF record.
Verify your destination inbox, then create your custom addresses.
Test from a different account and check spam.
For sending, add an SMTP provider or a mailbox provider, plus SPF, DKIM, and DMARC.

You end up with a professional address on your own domain, at no monthly cost, and a clear path to upgrade when the business outgrows it.

❓ Frequently Asked Questions

Is Cloudflare Email Routing really free?

Yes. At the time of writing, Email Routing is included free with any domain on Cloudflare. Check Cloudflare’s current documentation for limits, since vendors adjust these over time.

Can I send email from my custom address with Email Routing?

Email Routing itself only receives and forwards. To send as your custom address, you need an outgoing mail (SMTP) service, configured in your email client’s ‘send mail as’ settings, or a full mailbox provider.

Do I have to move my website to Cloudflare?

No. Your domain’s DNS has to be managed by Cloudflare, but your website can stay hosted wherever it is now. You just recreate its DNS records in Cloudflare when you switch nameservers.

Want It Set Up Right the First Time?

We handle domains, DNS, and email authentication as part of every site launch, so your contact address works on day one.

Get in Touch See Pricing