include:_spf.createsend.com – Campaign Monitor
Short answer: include:_spf.createsend.com lets Campaign Monitor's mail servers pass SPF for your domain. It costs 1 of the 10 DNS lookups SPF allows (checked live).
| Service | Campaign Monitor |
|---|---|
| Lookups | 1 of the 10 DNS lookups SPF allows (checked live) |
| Record now | v=spf1 ip4:103.28.42.0/24 ip4:146.88.28.0/24 ip4:163.47.180.0/22 ip4:203.55.21.0/24 ip4:204.75.142.0/24 ip4:27.126.146.0/24 ~all |
Do you need it?
Yes, if you send mail through Campaign Monitor with your own domain. It is the include our Campaign Monitor setup guide uses. Optional, but Campaign Monitor recommends it: add include:_spf.createsend.com right after v=spf1 in your one SPF record. DMARC passes through DKIM either way.
Who uses it
In our scan of top websites on 23 Oct 2026:
- 11 of the 2,214 world's top-3,000 sites that publish SPF (0.5%)
- 3 of the 1,961 India's top-3,000 sites that publish SPF (0.2%)
- 0 of the 428 Indian government sites that publish SPF (0.0%)
Add it the right way
- Keep one SPF record per domain:
v=spf1 include:_spf.createsend.com ~all, plus your other senders in the same record – SPF generator. - Stay under 10 lookups in total; every include counts, nested ones too.
- SPF alone isn't enough for Gmail, Yahoo and Outlook: turn on DKIM and publish DMARC.
Check your domain
After the fix, send a test email to see SPF, DKIM and DMARC pass on a real message, then keep an eye on it: free DMARC monitoring shows every service that sends mail as your domain and which ones fail, in plain English.
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 28-page guide, checklist, 20+ providers.