Skip to content
DMARC Pulse

Email senders

Campaign Monitor DMARC setup: DKIM, SPF and alignment

How Campaign Monitor signs your mail with DKIM, why it treats SPF as optional, and the DNS mistakes that hold back its customers.

SPF include for Campaign Monitor

Resolves in DNS
Add to your SPF recordTXT
include:_spf.createsend.com

Campaign Monitor does not require this include. If you use it, add it to the SPF record you already have: a domain must publish only one.

DNS lookups it uses
1 of 10
Needed in your SPF record
No
Last checked in DNS
2026-11-11

DKIM for Campaign Monitor

Selectors
cm
How to enable it
One TXT record on the sending domain, cm._domainkey, holding the public key Campaign Monitor generates under Account settings > Sending domains. Use existing details lets you enter your own selector and keys, but Campaign Monitor recommends generating new ones.

Campaign Monitor signs with your domain

The signature carries your domain in d=, so DKIM can align with your From address and pass DMARC on its own.

Envelope-from and SPF alignment

SPF counts for DMARC only when this domain matches the domain in your From address. If it is Campaign Monitor’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.

Envelope-from (Return-Path)
cmail1.com through cmail20.com, createsend7.com

Sending ranges of Campaign Monitor

Use these to recognize Campaign Monitor in your reports. They change over time, so do not copy them into your SPF record.

6 of 6
  • 163.47.180.0/22
  • 103.28.42.0/24
  • 146.88.28.0/24
  • 203.55.21.0/24
  • 204.75.142.0/24
  • 27.126.146.0/24

Updated 2026-11-15

Does your domain authorize Campaign Monitor?

Enter your domain. The SPF Checker reads your record and names the senders it authorizes.

Campaign Monitor documentation

How it authenticates

Campaign Monitor DMARC setup starts with DKIM (DomainKeys Identified Mail), the signature that ties a message to your domain. Open Account settings, then Sending domains, and add the domain you send from. Campaign Monitor generates a key and gives you a TXT record named cm._domainkey. Some DNS hosts want the full name, such as cm._domainkey.mail.example.com. Once it is published, click I've added the records. If you left the setup, use Re-check record in Sending domains.

The record sits on your own domain, which lets the signature pass DMARC alignment. Campaign Monitor treats DKIM and DMARC as required.

SPF (Sender Policy Framework) authorizes sending servers. Campaign Monitor calls it optional. By default it supplies SPF for its own return-path domains, the addresses that collect bounces. It lists cmail1.com through cmail20.com and createsend7.com. Mail on those defaults can still pass DMARC when DKIM is set up. The pages we checked do not say whether adding the include changes the return-path, so plan on DKIM and read your reports before you count on SPF.

What to watch for

Authenticating example.com does not cover mail.example.com. Add the exact domain in your From address.

If you add SPF, place include:_spf.createsend.com right after v=spf1 in your existing record. A domain must keep a single SPF record.

Leave a valid _dmarc record alone. The suggested v=DMARC1; p=none; only applies when you have none, and it requests no reports. Add a rua tag to receive them.

Some DNS hosts reject underscores or semicolons. Writing \; in place of ; can get past the semicolon limit. If it does not, Campaign Monitor says you must move DNS providers.

Keys created before 2013 may be 768-bit, and some servers ignore them. Delete the sending domain and add it again to get a 1024-bit key. Do this between campaigns, then replace the old TXT value with the new one, keeping only one: DKIM fails until you do.

Confirm the result with the DKIM checker, using the selector cm.

Check it now

Find and validate DKIM keys

Frequently asked questions

Do I need an SPF record for Campaign Monitor?
Campaign Monitor calls it optional but recommended. It says mail sent with its default SPF settings can still pass DMARC as long as you set up DKIM. To add it, put include:_spf.createsend.com in your one SPF record.
Which DKIM selector does Campaign Monitor use?
The record it generates is named cm._domainkey on your sending domain, so the selector is cm. If you entered your own keys through Use existing details, the selector is the one you typed.
Why do my Campaign Monitor emails show cmail2.com?
Campaign Monitor says some email clients flag mail as coming from one of its servers, such as cmail2.com, when the sending domain is not authenticated with DKIM. Authenticate the domain under Sending domains.
Does authenticating my main domain cover its subdomains?
No. Campaign Monitor says authenticating example.com will not authenticate its subdomains. Add each domain you send from, such as mail.example.com.
Should I replace my DMARC record with the one Campaign Monitor suggests?
No. Campaign Monitor says to skip that step if a valid _dmarc record already exists, because changing it can have serious effects on the rest of your email.

Sources consulted

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.