Keep the Cloudflare mail-server address path separate from the web proxy

An MX target needs the correct mail host address, not a website proxy endpoint.

Source facts

Cloudflare’s mail setup guide pairs an MX record with an A or AAAA address for the mail subdomain and shows that address as DNS-only. It states that ordinary Cloudflare service does not proxy SMTP on port 25. The exact records must come from the mail provider; receiving mail, sending mail, and email-authentication records serve different purposes.

Source: Cloudflare — Set up email records.

Applicability

This concerns DNS for mail services using Cloudflare authoritative DNS.

DSE recommendation

DSE recommends identifying every hostname used by MX, submission, IMAP, and webmail before changing proxy status. Keep ordinary mail transports on the provider-supported DNS-only path and review webmail separately as a web service. Preserve SPF, DKIM, and DMARC during a website migration. Do not repoint mail to the website’s address solely because both services share a domain or because the homepage works through Cloudflare. Keep the MX target, its resolved address, and its approved proxy status together in the mail inventory. Have the messaging owner approve them during a website DNS migration. Test the actual delivery path independently from webmail so success of one service cannot hide a broken transport hostname.

Verification

Query the domain’s MX and each target’s address records, then compare them with the mail provider’s instructions. Perform authorized inbound and outbound delivery tests and inspect server evidence separately from DNS. Verify the client-facing TLS hostname and avoid reporting delivery success from a DNS lookup alone.

Official reference

Cloudflare — Set up email records. Reviewed October 20, 2026.