Cloudflare Docs
Email Routing
Visit Email Routing on GitHub
Set theme to dark (⇧+D)


The postmaster page provides technical information about Email Routing to professionals who administer email systems, and other email providers.

Here you will find information regarding Email Routing, along with best practices, rules, guidelines, and troubleshooting tools.

​​ Limits

Currently, Email Routing does not support messages bigger than 25 MiB.

​​ Outbound prefixes

Email Routing sends its traffic using both IPv4 and IPv6 prefixes, when supported by the upstream SMTP server.

If you are a postmaster and are having trouble receiving Email Routing’s emails, allow the following outbound IP addresses in your server configuration:




Ranges last updated: October 4th, 2022

​​ IPv6 support

Currently, Email Routing will connect to the upstream SMTP servers using IPv6 if they provide AAAA records for their MX servers, and fall back to IPv4 if that is not possible.

Below is an example of a popular provider that supports IPv6:

$ dig mx 3084 IN MX 5 3084 IN MX 20 3084 IN MX 40 3084 IN MX 10 3084 IN MX 30
$ dig AAAA 17 IN AAAA 2a00:1450:400c:c09::1b

Email Routing also supports IPv6 through Cloudflare’s inbound MX servers.

​​ Outbound hostnames

In addition to the outbound prefixes, Email Routing will use the domain for the HELO/EHLO command.

PTR records (reverse DNS) ensure that each hostname has an corresponding IP. For example:

$ dig +short
$ dig -x +short

​​ MX, SPF, and DKIM records

Email Routing automatically adds a few DNS records to the zone when our customers enable Email Routing. If we take as an example: 300 IN MX 13 300 IN MX 86 300 IN MX 24 300 IN TXT "v=spf1 ~all"

The MX (mail exchange) records tell the Internet where the inbound servers receiving email messages for the zone are. In this case, anyone who wants to send an email to can use the,, or SMTP servers.

​​ SPF record

A SPF DNS record is an anti-spoofing mechanism that is used to specify which IP addresses and domains are allowed to send emails on behalf of your zone.

The Internet Engineering Task Force (IETF) tracks the SPFv1 specification in RFC 7208. Refer to the SPF Record Syntax to learn the SPF syntax.

Email Routing’s SPF record contains the following:

v=spf1 ~all

In the example above:

  • spf1: Refers to SPF version 1, the most common and more widely adopted version of SPF.
  • include: Include a second query to and allow its contents.
  • ~all: Otherwise SoftFail on all other origins. SoftFail means NOT allowed to send, but in transition. This instructs the upstream server to accept the email but mark it as suspicious if it came from any IP addresses outside of those defined in the SPF records.

If we do a TXT query to, we get: 300 IN TXT "v=spf1 ip4: ~all"

This response means:

  • Allow all IPv4 IPs coming from the subnet.
  • Otherwise, SoftFail.

You can read more about SPF, DKIM, and DMARC in our Tackling Email Spoofing and Phishing blog.


DKIM (DomainKeys Identified Mail) ensures that email messages are not altered in transit between the sender and the recipient’s SMTP servers through public-key cryptography.

Through this standard, the sender publishes its public key to a domain’s DNS once, and then signs the body of each message before it leaves the server. The recipient server reads the message, gets the domain public key from the domain’s DNS, and validates the signature to ensure the message was not altered in transit.

Email Routing signs email on behalf of If the sender did not sign the email, the receiver will likely use Cloudflare’s signature for authentication.

Below is the DKIM key for

$ dig TXT +short
"v=DKIM1; h=sha256; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnraPy1d8e6+lzeE1HIoUvYWoAOUSREkNHcwxA/ueVM8f6FKXvPu/9gVpgkn8iUyaCfk2z1MW+OVLuFeH64YRMa39mkaQalgke2tZ05SnjRUtYEHYvfrqPuMT+Ouk+GecpgvrtMq5gMXm6ZfeUhQkdWxmMQJGf4fdW5I0piUQJMhK/Qc1dNRSskk" "TiUtXKnsEdjTN2xcnHhyj985S0xOEAxm9Uj1rykPqVvKpqEdjUkujbXOwR0KmHTvPyFpBjCCfxAVqOwwo9zBYuvk/nh0qlDgLIpy0SimrYhNFCq2XBxIj4tdUzIl7qZ5Ck6zLCQ+rjzJ4sm/zA+Ov9kDkbcmyrwIDAQAB"

​​ Sender rewriting

Email Routing rewrites the SMTP envelope sender (MAIL FROM) to the forwarding domain to avoid issues with SPF. Email Routing uses a scheme similar to the Sender Rewriting Scheme.

For example, when receiving an email at with a sender address of [email protected], Email Routing will rewrite the MAIL FROM to [email protected]. The rewriting happens during the SMTP session to the destination upstream.

This has no effect to the end user’s experience, though. The message headers will still report the original sender’s From: address.

​​ Spam and abusive traffic

Handling spam and abusive traffic is essential to any email provider. Email Routing filters emails based on advanced anti-spam criteria, powered by Area 1. When Email Routing detects and blocks a spam email, you will receive a message with details explaining what happened. For example:

554 <YOUR_IP_ADDRESS> found on one or more DNSBLs (abusixip). Refer to

​​ SMTP errors

In most cases, Email Routing simply forwards the upstream SMTP errors back to the sender client in-session.

​​ Contact information

The best way to contact us is using our community forum or our Discord server.