How to set up DMARC/DKIM/SPF for Campaign Monitor

Updated on 24 Oct 2026: We updated the Campaign Monitor setup steps for subdomain DNS records, DKIM signing delays, and DMARC enforcement under RFC 9989.
Campaign Monitor authentication depends on aligned DKIM. Add the sending domain in Campaign Monitor, publish its generated DKIM TXT record, and confirm that a DMARC policy covers the visible From domain. Campaign Monitor recommends an optional SPF include, but its default return-path uses a Campaign Monitor domain. SPF can therefore pass without satisfying DMARC, making aligned DKIM the required DMARC pass path for this setup.
Use the exact DNS values shown in your account. Campaign Monitor generates a unique DKIM key, so copied examples cannot replace the account value. The platform's authentication instructions are the source of truth for the generated host, value, and verification state.
Working authentication target
A Campaign Monitor message should show DKIM=pass with the DKIM signing domain aligned to the visible From domain, and DMARC=pass. SPF alignment can fail without breaking DMARC when aligned DKIM passes.
Add your sending domain
Add the exact domain used after the @ in the campaign's From address. If campaigns use news@mail.example.com, authenticate mail.example.com. Authenticating example.com does not authenticate mail.example.com in Campaign Monitor. Use a registered domain your organization owns; a public mailbox domain such as gmail.com cannot be authenticated in your account.
- Click the profile image, select Account settings, then open Sending domains.
- Click Set up a sending domain, or Add domain when another domain already exists.
- Use the organizational domain or sending subdomain that appears in the visible From address, then click Continue.
- Choose the option to add the TXT record yourself, or share the generated instructions with the DNS administrator.
- You will return after publishing DNS and select I've added the records.

Campaign Monitor sending domain setup screen
|
|
|
|---|---|---|
Platform | Generates the DKIM key | |
Domain | Visible From domain | Controls DKIM alignment |
DNS access | Required | Publishes TXT records |
TTL | 300 seconds or DNS host minimum | Controls cache time |
Values to confirm before generating DNS records
Set up SPF
Campaign Monitor recommends include:_spf.createsend.com as an optional addition to the sending domain's SPF TXT record. It already handles SPF for its default return-path domain, so adding this include does not create SPF alignment. If you add it, merge it into the existing policy and check SPF's limit of ten DNS-querying terms, including those reached through nested includes.
SPF example for mail.example.com with no existing SPF policyDNS
Type: TXT Host: mail.example.com Value: v=spf1 include:_spf.createsend.com ~all TTL: 300
The examples use full DNS hostnames. In the example.com DNS zone, enter mail for mail.example.com if your DNS host appends the zone name. Use @ only for the zone apex. SPF is not inherited by subdomains, so check the exact sending domain before adding a record.
- Query TXT records at the exact sending domain and find the single value beginning with v=spf1.
- Add include:_spf.createsend.com immediately after v=spf1. Preserve existing authorized senders and the final all qualifier, including an existing -all.
- Combine every authorized sender into one SPF policy. Multiple SPF records cause permerror.
- Allow cached DNS answers to expire, then have Campaign Monitor re-check the domain. Lowering the TTL does not shorten the lifetime of answers already cached under the old TTL.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
Suped's SPF checker should return one syntactically valid SPF record with no permerror. It cannot change Campaign Monitor's standard return-path domain. That limitation affects DMARC alignment, not the standalone SPF authentication result.
SPF authentication
- SPF checks the SMTP MAIL FROM domain, normally visible in the delivered Return-Path header.
- SPF can pass for Campaign Monitor infrastructure.
SPF alignment
- Return-path and visible From domains.
- Campaign Monitor's default return-path domain is not aligned with your visible From domain.
SPF is not the DMARC pass path
SPF alignment failure is expected with Campaign Monitor's default return-path. DMARC still passes when DKIM passes with a signing domain that meets the visible From domain's alignment requirement. If DKIM fails too, DMARC fails.
Set up DKIM
DKIM is the decisive control for Campaign Monitor DMARC alignment. For a new sending domain, generate a key in Campaign Monitor, publish the displayed TXT record without changing its selector or value, and verify it inside the same Sending domains screen. If the domain already has a Campaign Monitor key, check for active use before replacing it.
- Use the Name or host shown by Campaign Monitor. It commonly starts with cm._domainkey.
- Paste the complete public key as one TXT record. If the DNS host splits a long value into quoted character strings, keep those strings inside that single record. Never publish a private key in DNS.
- Match the name to your DNS zone. For cm._domainkey.mail.example.com in the example.com zone, enter cm._domainkey.mail if the host appends example.com. Enter cm._domainkey only when the zone itself is mail.example.com.
- After the record is visible in DNS, click I've added the records or Re-check record in Campaign Monitor. Allow up to 30 minutes after verification for DKIM signing to start, then test a live send.
- Use the authenticated domain as the From domain in the next campaign.
DKIM record shape, replace the value with your generated keyDNS
Type: TXT Host: cm._domainkey.mail.example.com Value: [copy the exact value shown in Campaign Monitor] TTL: 300

Campaign Monitor generated DKIM TXT record
DKIM success criteria
- The selector resolves to the exact public key.
- A live campaign header shows DKIM=pass.
- Under relaxed DKIM alignment, d= and the visible From domain share the same organizational domain. With adkim=s, the domains must match exactly.
- The same message shows DMARC=pass.
Avoid DKIM conflicts across accounts
Before authenticating the same sending domain in another Campaign Monitor account, check who uses its existing DKIM selector. Replacing the public key at cm._domainkey.mail.example.com breaks verification of messages signed with the old private key. Publishing both keys as separate TXT records at that same hostname is also invalid.
- Use a separate sending subdomain for the other account and authenticate it independently when separate keys are needed.
- For an existing key pair, Campaign Monitor has a Use existing details option. Coordinate reuse or replacement with the administrator responsible for the current signer before changing DNS.
Keep DKIM records used by other senders at their own selectors. Adding Campaign Monitor authentication does not authenticate email sent through those other systems.
Set up DMARC
Check whether a DMARC policy already covers the visible From domain before publishing a record. A subdomain without its own DMARC record can inherit the organizational domain's sp policy, or p when sp is absent. For a domain without an applicable policy, start with p=none and aggregate reporting. Keep any existing p=quarantine or p=reject policy and fix Campaign Monitor authentication before sending.
Starting DMARC record for mail.example.com without an existing policyDNS
Type: TXT Host: _dmarc.mail.example.com Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com TTL: 300
- Check _dmarc.mail.example.com and any inherited policy at _dmarc.example.com. Keep only one DMARC TXT record at each hostname; do not add a weaker subdomain policy over inherited enforcement.
- Replace dmarc@example.com with a working aggregate-report mailbox or reporting address. When using an external reporting domain, confirm that the report recipient publishes the required DNS authorization.
- Use the DMARC record generator when you need extra tags or a reporting address.
- For mail.example.com in the example.com DNS zone, enter _dmarc.mail if the DNS host appends the zone. Use _dmarc only when editing the mail.example.com zone itself.
- Return to Campaign Monitor's Sending domains page and select Re-check record.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
Suped's DMARC checker should show the applicable policy, including inheritance where relevant. A p=none record requests monitoring without DMARC-based enforcement; add rua to request aggregate reports. The quarantine and reject policies request handling of DMARC failures, while receiving servers retain the final delivery decision.
Do not overwrite an enforced policy
If a direct or inherited DMARC policy already enforces quarantine or reject, leave that protection in place. Publish and verify Campaign Monitor DKIM before the next send. Adding p=none at the sending subdomain can override inherited enforcement and increase spoofing exposure.
Verify and troubleshoot
Verify with a real Campaign Monitor campaign, not only DNS lookups. Send to a mailbox you control, inspect the receiver's Authentication-Results header, and compare the visible From domain with the DKIM signing domain. Require DKIM=pass and DMARC=pass with the expected domain alignment.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
Send a Campaign Monitor test to the address generated by Suped's email tester. Review the authentication results, visible From domain, return-path, and DKIM selector with the signing domain. A plain editor preview does not prove that the production sending path signs the message correctly. Test automated journeys separately if they use a different From domain or sending path.
- Resolve the DKIM selector and SPF host at the exact sending domain, then check the applicable DMARC record, including any inherited organizational-domain policy.
- Check DKIM=pass and confirm that header.d meets the DMARC alignment requirement for header.from. In DKIM-Signature, d= is the signing domain and s= is the selector.
- A passing SPF result can remain unaligned because Campaign Monitor uses its own return-path. Do not treat this alone as failure.
- Require DMARC=pass through aligned DKIM before increasing policy enforcement.
- Test each Campaign Monitor client, From domain, and campaign path that can sign differently.
Illustrative receiver results for an authenticated Campaign Monitor messagetext
Authentication-Results: receiver.example; dkim=pass header.d=mail.example.com header.s=cm; spf=pass smtp.mailfrom=cmail2.com; dmarc=pass header.from=mail.example.com
|
|
|
|---|---|---|
DKIM missing | Wrong hostname or signing not active yet | Check the DNS zone suffix; allow up to 30 minutes after verification |
DKIM fails | Wrong, truncated, or replaced public key | Compare the complete key and check for selector conflicts |
SPF permerror | Duplicate or limit | Merge and recount |
SPF unaligned | Platform return-path | Rely on aligned DKIM |
DMARC fails | No aligned pass | Fix DKIM alignment |
Multiple records found | More than one DKIM TXT record at the same selector | Coordinate active signers and retain one matching public key |
Fast fault isolation for Campaign Monitor authentication

Campaign Monitor verified sending domain status
For background on what the header results mean, Campaign Monitor's email authentication documentation explains how SPF, DKIM, and DMARC participate in the send.
Monitor Campaign Monitor authentication
DNS checks show current publication, but they do not show whether every live campaign stays aligned. Suped is our DMARC reporting and email authentication platform. Use its aggregate reports to review Campaign Monitor's DKIM results by sending source and investigate failures after DNS or sending-domain changes.
- Put the Suped-provided aggregate reporting address in the DMARC rua tag.
- Confirm Campaign Monitor against your sending activity and its passing, aligned DKIM signature before marking the source as authorized.
- Enable available notifications for authentication failures and unfamiliar sources. Report-based alerts depend on when receiving servers submit their data.
- Separate expected unaligned SPF results from DKIM failures. Check the affected signing domain and compare its published selector with the value in Campaign Monitor.
A replaced DKIM key or deleted TXT record can break alignment after setup. Suped's DMARC monitoring helps investigate those changes in reported sending data. Aggregate reports are generally sent daily, so use a fresh live-message test when confirming an urgent fix.
Investigate changes that affect authentication
- The Campaign Monitor signature stops validating.
- The signing domain no longer meets the visible From domain's alignment requirement.
- A new sender begins using the domain.
- The published DMARC policy or reporting destination changes.
Move safely to p=reject
Move to p=reject only after Campaign Monitor and every other legitimate sender pass DMARC consistently. Use report data to identify each source, verify an aligned SPF or DKIM pass, remove obsolete senders, and then stage enforcement. Campaign Monitor needs aligned DKIM before enforcement is enabled.
Ready for enforcement
- Every legitimate sender has an owner.
- Aligned DKIM passes in live reports.
- Residual failures are unauthorized or understood.
- DNS access and incident ownership are documented.
Not ready
- Unclassified sources still send meaningful mail.
- Campaign Monitor signatures fail or lack the required domain alignment.
- Expected forwarding effects are not separated from sender faults.
- Nobody will see a failure spike after enforcement.
Use Suped's source-level reporting to check legitimate traffic before each policy change. Start with p=none where enforcement is not already active, then move to p=quarantine and p=reject after reviewing failures at each stage. RFC 9989 makes pct historic, so do not rely on percentage-based enforcement. Stage by policy level or a separately configured sending subdomain instead.
- Classify every source in aggregate reports and confirm who owns it.
- Require aligned DKIM for Campaign Monitor and an aligned pass for each other authorized sender.
- Set p=quarantine after legitimate sources are ready, then review reports covering normal campaigns and less frequent sending paths before tightening the policy.
- Set p=reject when legitimate sources pass consistently and remaining failures are understood. Remove pct from the record; it no longer provides percentage-based staging under RFC 9989.
- Continue monitoring DKIM failures and new sources, and review published policy changes after enforcement.
Reject requests rejection of DMARC failures
At p=reject, failed or unaligned Campaign Monitor DKIM leaves no DMARC pass path in the standard setup, and the policy requests rejection. The receiving server makes the final handling decision. Complete a live test after any sending-domain or DKIM change before the next large campaign.
Campaign Monitor authentication FAQ
These checks cover the common follow-up cases that appear after Campaign Monitor starts sending against an active DMARC policy.
Yes. DMARC passes when at least one of SPF or DKIM passes authentication and meets the visible From domain's alignment requirement. Campaign Monitor's default return-path uses its own domain, so aligned DKIM is the DMARC pass path for this setup.
Publish the generated DKIM TXT record and confirm an applicable DMARC policy, either directly at the sending domain or inherited. Campaign Monitor recommends include:_spf.createsend.com as an optional addition to your single SPF record. Do not create duplicate SPF or DMARC records at the same hostname.
DNS changes often become visible within minutes, but cached answers and DNS host settings can delay visibility for up to 48 hours. After Campaign Monitor verifies the domain, DKIM signing can take up to another 30 minutes to start. Re-check the domain and test a fresh message before sending at volume.
No. Passing DMARC confirms authentication and domain alignment. Receiving servers also evaluate sender reputation and recipient complaints, along with consent and message content. Investigate those factors when an authenticated campaign still reaches the spam folder.
No. Keep p=reject or p=quarantine, publish the Campaign Monitor DKIM record, and verify a live message before sending at volume. Downgrading the policy weakens domain protection and is unnecessary.

