The DNS records
Intercom shows the Name and Value of each record for your workspace. Copy them exactly; only the DMARC example below is fixed.
DKIM
Type: CNAME · Host: intercom._domainkey
<Value shown in Intercom>
Custom return path
Type: CNAME · Host: <Name shown in Intercom>
<Value shown in Intercom>
This one aligns SPF; it isn't part of DKIM.
DMARC (simplest record Intercom accepts)
Type: TXT · Host: _dmarc
v=DMARC1; p=none
Set it up and turn on signing
- Go to Settings > Channels > Email > Domains & addresses and add or edit the sending address.
- Verify the address through the confirmation email, then select Authenticate your domain.
- At your DNS host, put Intercom's Name in the host field and its Value in the target field for both CNAMEs, and add the DMARC TXT record.
- At Cloudflare, make each CNAME DNS only (grey cloud). Then select Validate authentication in Intercom.
- Intercom says propagation usually takes a few hours to 48 hours and can take up to 72. Until then the address shows an Unauthenticated warning.
DMARC alignment
Authenticated domains sign with your domain and use your return path, so DKIM and SPF can both align with your From address. Until then Intercom shows an Unauthenticated warning to you and to recipients. The shared intercom-mail.com domain is meant for setup and testing; Intercom says it isn't recommended long term because of deliverability risks, and suggests warming up a custom domain gradually.
Key length and rotation
Intercom explains its choice of CNAME over a TXT key directly: it may rotate its DKIM private keys in future, and the CNAME lets it publish the new key without asking you to edit DNS. It doesn't state a key length.
Common mistakes
- TXT instead of CNAME. Both authentication records must be CNAMEs; only DMARC is a TXT record.
- The domain added twice to the Name. Some DNS systems append it automatically.
- Orange-cloud CNAMEs at Cloudflare. Proxied records don't verify.
- No DMARC record. Intercom requires one with at least
p=none.
Check your Intercom DKIM key
The selector is filled in for you; add your domain. Free, reads public DNS only.
Frequently asked questions
What is Intercom's DKIM selector?
intercom. Intercom's troubleshooting article lists it for DKIM lookup tools, and its email settings article gives intercom._domainkey as the example record name. Copy the exact name and value from your workspace.
Why does Intercom use a CNAME for DKIM instead of a TXT key?
Intercom says it may rotate its DKIM private keys in future. A CNAME points your selector at a record Intercom controls, so a new key takes effect without you changing anything in DNS.
Why does Intercom show an Unauthenticated warning on my email address?
Because the DKIM and return-path CNAMEs, or the DMARC record, aren't verified yet. Publish all three, set Cloudflare records to DNS only, wait for DNS to update and select Validate authentication.
Sources
- Intercom Help: How to manage email settings
- Intercom Help: Troubleshooting email authentication issues (DKIM, DMARC, and DNS setup)
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Intercom's documentation on October 22, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- iCloud MailCNAME: sig1
- HostingerCNAME: hostingermail-a, hostingermail-b, hostingermail-c
- Private EmailTXT: privateemail, default (bought before 2 June 2026)
- IONOSCNAME: s1-ionos, s2-ionos, s42582890
- Rackspace EmailTXT: shown in the Cloud Office Control Panel
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- MailjetTXT: mailjet
- SMTP2GOCNAME: shown in SMTP2GO for your domain
- SparkPostTXT: scph<number> (generated, e.g. scph0316), your own (API)
- Elastic EmailTXT: api
- ResendTXT: resend
- MailerSendCNAME: ms1, ms2
- MailchimpCNAME: k2 and a second CNAME (Marketing), mte1, mte2 (Transactional)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- ActiveCampaignCNAME: acdkim1, acdkim2
- Constant ContactCNAME or TXT: ctct1, ctct2 (CNAME), generated per key (TXT)
- SquarespaceCNAME: squarespace
- Dynamics 365 Customer InsightsCNAME: CNAME1 and CNAME2 from the wizard (e.g. namkey1)
- MailerLiteCNAME: litesrv
- Campaign MonitorTXT: cm, your own (existing keys)
- KitCNAME: cka
- MarketoTXT: chosen by you in Marketo
- Account Engagement (Pardot)TXT: shown in Expected DNS Entries
- Customer.ioTXT: cio
- Zoho CampaignsTXT: numbered per account (e.g. 2232)
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
- Help ScoutCNAME: strong1, strong2
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for Intercom
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated