Moving a business website to Cloudflare can improve the way website traffic is managed and protected. But for many business owners, one concern comes before anything else: what happens to their business email?
If your company relies on addresses such as [email protected], [email protected] or [email protected], an email outage can be disruptive. Customers may be unable to reach you, invoices may be delayed, and important messages could be missed.
The good news is that Cloudflare can generally be used alongside business email services without interrupting email delivery. The key is to configure DNS records correctly when setting up the domain.
Does Cloudflare Host Your Business Email?
Cloudflare’s standard website protection and DNS services do not automatically replace your existing email hosting provider.
You can continue using a separate email service, such as Microsoft 365, Google Workspace or a business email hosting provider, while using Cloudflare to manage your website’s DNS and proxy traffic.
The distinction is important. Your website and email may use the same domain, but they rely on different DNS records and services.
For example, your website may use records that direct visitors to your hosting server, while your email service relies on MX records to identify where incoming messages should be delivered.
When moving a domain to Cloudflare, the email-related records must be preserved and configured correctly.
Which DNS Records Keep Business Email Working?
Several DNS record types may be important when setting up your domain.
MX records identify the mail servers responsible for receiving email for your domain. If these records are missing or incorrect, incoming messages may fail to reach your mailbox.
SPF records help receiving mail systems determine which servers are authorised to send messages for your domain.
DKIM records publish information used to verify email signatures, helping receiving systems check whether signed messages have been altered and whether the signature corresponds to the domain.
DMARC records specify how receiving systems should handle messages that fail relevant email authentication checks and provide a way to receive authentication reports.
Your domain may also use additional records for email verification, autodiscovery or other provider-specific functions.
Not every business needs the same record values. You should copy the correct records from your email provider rather than guessing their contents.
Why Does Email Sometimes Stop Working After a Cloudflare Migration?
One common cause is that existing DNS records were not copied correctly before the domain’s nameservers were changed.
When you move DNS management to Cloudflare, the records in the new DNS zone must match the services you intend to keep using. If an MX record is missing, for example, incoming email may be affected.
Another possibility is an incorrect or incomplete SPF, DKIM or DMARC configuration. These problems may affect email authentication or deliverability even if basic email sending and receiving still appear to work.
A third issue involves proxy settings. Website records that should pass through Cloudflare’s proxy must be distinguished from records used for services such as email. Standard email-related DNS records should not be configured as ordinary proxied website traffic.
The exact configuration depends on the service and protocol involved, so follow Cloudflare’s and your email provider’s documentation when setting up the domain.
How to Move Your Website to Cloudflare Without Losing Email
Before changing nameservers, document the domain’s existing DNS records. Include website records, MX records, SPF, DKIM, DMARC and any verification records used by your email provider.
Next, create or review the DNS zone in Cloudflare. Confirm that the website records point to the correct destination and that all necessary email records have been added with the correct values.
Pay particular attention to the DNS-only setting for mail-related hostnames. Cloudflare’s standard web proxy is not a general-purpose proxy for ordinary email protocols.
Before considering the migration complete, test both services. Open the website, send an email from the business domain, send a message to it from an external address, and confirm that the messages arrive as expected.
If your organisation uses Microsoft 365, Google Workspace or another managed email platform, verify any provider-specific DNS requirements as well.
What If Your Email Is Already Not Working?
If email stops working after a DNS change, avoid making random edits to the DNS zone.
First, confirm that the domain’s MX records match the values required by your email provider. Then review the sending authentication records and any recent DNS changes.
Determine whether the issue affects incoming messages, outgoing messages or both. That distinction can help narrow down the cause.
If only outgoing messages are affected, SPF, DKIM, DMARC or the sending service’s configuration may need attention. If incoming messages fail, the MX records or receiving mail service should be investigated.
Keep a record of any changes and test again after correcting the relevant settings. DNS changes can take time to become visible across different resolvers, depending on caching and the records’ previous TTL values.
Can Tremhost Help With Cloudflare and Business Email?
Tremhost provides Cloudflare-based website protection for businesses that want help with technical configuration.
Its Cloudflare services can be explored alongside the business’s existing hosting and email arrangements. For website protection, Armor Guard is advertised at $9 per month per website.
If your organisation needs assistance with both website security and business email, explain which email platform you use and what you need configured. Confirm the exact services and support included before purchasing.
The objective is to ensure that website protection is introduced without unintentionally disrupting the email systems your business depends on.
Final Thoughts
Using Cloudflare for your website does not automatically mean you must change your business email provider. Website traffic and email delivery can continue operating through their respective services when the domain’s DNS records are configured correctly.
Before changing nameservers, record the existing DNS configuration, preserve the required email records and test sending and receiving after the migration.
A careful setup helps your business benefit from Cloudflare’s website capabilities while keeping its essential communication services working.
