Email senders
Intercom DMARC setup: SPF, DKIM and alignment
How Intercom authenticates your mail with two CNAME records, why you do not add it to SPF, and what commonly blocks domain authentication.
SPF include for Intercom
Intercom does not need an SPF include on your domain.
DKIM for Intercom
- Selectors
- intercom
- How to enable it
- One CNAME record at intercom._domainkey on your domain. Intercom shows the target in your settings and requires a CNAME because it may rotate its private keys.
Intercom signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Intercom’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A custom return-path on your domain, set by a CNAME record that Intercom shows in your settings. Intercom does not document the hostname.
Sending ranges of Intercom
Use these to recognize Intercom in your reports. They change over time, so do not copy them into your SPF record.
Intercom does not document this.
Does your domain authorize Intercom?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Intercom documentation
- Intercom: Connect your email support channel
- checked 2026-11-09
- Intercom: Troubleshooting email authentication issues (DKIM, DMARC, and DNS Setup)
- checked 2026-11-09
- Intercom: Email sending FAQs
- checked 2026-11-09
- Intercom: Your guide to Google & Yahoo's new requirements for email senders
- checked 2026-11-09
How it authenticates
Intercom DMARC setup asks for three DNS records: two CNAMEs, which point one name at another, and one TXT. Go to Settings > Channels > Email > Domains & addresses, verify the address, then choose Authenticate your domain. Intercom shows the Name and Value of each record.
The first CNAME sets up DKIM (DomainKeys Identified Mail), the signature on each message, under the selector intercom. The second sets the return-path, the address that receives bounces, so that SPF (Sender Policy Framework) can align with your domain. Without it, receivers check SPF against Intercom's domain, which passes but does not align with yours.
The third record is DMARC. Publish it as a TXT at _dmarc, starting with this value:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace the report address with a mailbox you monitor.
If you already have a DMARC record, keep it. A domain can hold only one.
What to watch for
One Intercom help answer offers include:sparkpostmail.com as an alternative to authenticating the domain. Prefer the CNAME. The include leaves the return-path outside your domain, so SPF stays unaligned, and it adds lookups to a record limited to 10.
When validation fails, check the DNS entry first. Intercom lists these causes:
- A TXT record where a CNAME belongs.
- The domain typed twice in the Name field, because the provider appends it automatically.
- A Cloudflare record left proxied. Set it to DNS only, with a grey cloud.
- Trailing dots on GoDaddy.
Authenticating does not move your existing messages. Update the From address on each ongoing outbound message, or they keep their old sender.
Intercom does not publish the return-path hostname or say how it behaves under strict alignment. Read your reports before you set aspf or adkim to s, and before you tighten the policy. Test the signature with the DKIM checker, using selector intercom.