include:_spf.createsend.com lists the servers Campaign Monitor sends from. Campaign Monitor calls adding it “optional, but still a recommended action”: its mail carries Campaign Monitor’s own return-path, and “emails sent with the default SPF settings can still pass DMARC, so long as you set up DKIM.”
v=spf1 include:_spf.createsend.com ~all
| Belongs to | Campaign Monitor — email campaigns |
| Needed on your domain? | The service asks for it — though by default SPF checks a different domain for its mail |
What it costs, and is it in your record?
We measure include:_spf.createsend.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Campaign Monitor’s is there and what it costs.
What it covers
Campaign Monitor email campaigns.
Do you need it?
“By default, Campaign Monitor supplies an SPF record for you, authorizing the domains through which we send email (the domains used in the Return-Path address that machines read).” So SPF checks Campaign Monitor’s domains, not yours.
Campaign Monitor still suggests the include as further evidence for receiving servers — and asks you to verify DKIM first, since DKIM is what makes its mail pass DMARC.
Common mistakes
- Adding a second SPF record instead of adding the include to the existing one — Campaign Monitor says to add it right after v=spf1.
Sources
Checked on 26 September 2026 against these official sources:
- Manage your own authentication — help.campaignmonitor.com
- Email authentication — help.campaignmonitor.com