Adding Cloudflare domain

If your domain's DNS is managed in Cloudflare, you connect it to Sendigram by adding six DNS records in the Cloudflare dashboard. It takes about 10 minutes, and verification usually completes within minutes, since Cloudflare updates DNS quickly.

This works whether you bought the domain from Cloudflare or only moved its DNS to Cloudflare from another registrar.

Once your domain is verified, your emails are sent from your own domain and pass the SPF, DKIM and DMARC checks that Gmail, Yahoo and Outlook require from bulk senders.

Before you start, make sure you have:

  • Access to the Cloudflare account where your domain is active
  • A Sendigram account

The one Cloudflare-specific step that matters most: the three DKIM records must be set to DNS only, not Proxied. Step 3 shows how.

Step 1. Add your domain in Sendigram

  1. Sign in to Sendigram.
  2. Open the profile menu and select Sender settings.
  3. Click Add domain.
  4. Enter your domain name, for example yourbrand.com, and confirm.

Sendigram shows the DNS records for your domain. Keep this window open, or come back to it later from the domain's View action. You will copy each record into Cloudflare in Step 3.

Step 2. Open your DNS records in Cloudflare

  1. Sign in to the Cloudflare dashboard in a new browser tab.
  2. Select the domain you added in Sendigram.
  3. Go to DNS → Records.

Leave existing records as they are. You only need to add new ones.

Step 3. Add the Sendigram records in Cloudflare

Add all six records from Sendigram: three DKIM records, one MX record, one SPF record and one DMARC record. For each one:

  1. Click Add record.
  2. Select the record Type shown in Sendigram.
  3. Fill in Name and the value field as described in the table below. Cloudflare names the value field differently for each type: Target for CNAME, Mail server for MX and Content for TXT.
  4. For each DKIM (CNAME) record, click the orange cloud so Proxy status shows DNS only (grey cloud).
  5. Leave TTL at Auto and click Save.

Important: Proxied DKIM records can't be verified. Cloudflare's proxy is built for website traffic and hides the real DKIM target, so email providers and Sendigram can't read it. Make sure all three CNAME records show the grey cloud.

Record Type in Cloudflare Name in Cloudflare Value in Cloudflare
DKIM (x3) CNAME, DNS only The part before your domain, ending in ._domainkey Target: copy from Sendigram, one value per record
MX MX sendigram Mail server: feedback-smtp.us-east-1.amazonses.com, Priority 10
SPF TXT sendigram Content: v=spf1 include:amazonses.com ~all
DMARC TXT _dmarc Content: v=DMARC1; p=none;

Always copy the values from your own Sendigram window. The table shows how each field maps, so check your screen if anything differs. Cloudflare accepts either the short name (sendigram) or the full one (sendigram.yourbrand.com) and adds your domain for you.

Already have an SPF record? You don't need to change it. Sendigram's SPF record sits on the sendigram subdomain, not on your root domain, so it doesn't conflict with your existing one, including records added by Cloudflare Email Routing.

Already have a DMARC record? If the list already has a TXT record named _dmarc (for example, one created by Cloudflare DMARC Management), keep it and skip the Sendigram DMARC record. A domain can only have one DMARC record.

Step 4. Verify your domain in Sendigram

  1. Go back to Sendigram and open Sender settings.
  2. Find your domain and click Check DNS records.

Cloudflare usually publishes new records within a few minutes. If the check doesn't pass right away, wait a while and click Check DNS records again.

Once your domain is verified, add a sender address on that domain in the Sender address tab and start sending.

Troubleshooting

  • DKIM records don't verify. Open each CNAME record and check that Proxy status is DNS only (grey cloud). This is the most common Cloudflare issue.
  • Records are saved but nothing verifies. Your domain may not be active in Cloudflare yet. Check the domain's overview page. If it says the nameservers are pending, finish switching nameservers at your registrar, or add the records at your registrar instead.
  • Your domain was added to Cloudflare by your hosting provider. Some hosts set up Cloudflare for you. In that case, add the records in your hosting control panel instead.
  • Verification still fails. Compare each record in Cloudflare with Sendigram, character by character, and check for extra spaces in the value.
  • Still stuck? Contact Sendigram support and include your domain name and a screenshot of your Cloudflare DNS records.
Still have questions?