campaignmonitor.com email records
What campaignmonitor.com publishes in public DNS for SPF, DKIM, DMARC, MX and BIMI, resolved on 2026-08-04.
SPF
v=spf1 ip4:146.88.16.0/23 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 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:_spf.mailgun.org include:_spf.eu.mailgun.org include:21755729.spf03.hubspotemail.net ip4:85.222.130.192/26 ip4:85.222.138.192/26 ip4:96.43.144.0/20 ip4:136.146.128.64/27 ip4:136.146.208.0/21 ip4:136.147.32.0/19 ip4:182.50.78.64/28 include:_spf.salesforce.com ~all
10 of 10 DNS lookups — close to the limit.
The record authorises this sending platform: Salesforce (Sales & Service Cloud).
DMARC
v=DMARC1; p=none; rua=mailto:cm_rua@campaignmonitor.com, mailto:e5bffb4e@inbox.ondmarc.com; ruf=mailto:e5bffb4e@inbox.ondmarc.com; rf=afrf; pct=100;
- policy
- p=none
- applies to
- 100% of mail
- reports
- mailto:cm_rua@campaignmonitor.com,
- alignment
- adkim=r, aspf=r
DKIM
Keys found on 2 of 10 probed selectors:
MX
Notes on this configuration
SPF uses exactly 10 of the 10 permitted DNS lookups. It is valid, but has no headroom.
DMARC policy is p=none, which only monitors and blocks nothing.
Check it live
The above is a snapshot from 2026-08-04. Re-resolve it now: