The DNS records
Both values are generated per domain. Copy the record names and values from Expected DNS Entries.
DomainKey (DKIM)
Type: TXT · Host: <selector shown in Expected DNS Entries>._domainkey
<DomainKey value shown in Account Engagement>
Validation key (domain ownership)
Type: TXT · Host: @
<validation key shown in Account Engagement>
Publish it on the domain or subdomain you are verifying.
Set it up and turn on signing
- Open Domain Management: Admin > Domain Management in standalone Account Engagement, or Account Engagement Settings > Domain Management in the Lightning app. You need the Account Engagement Administrator role.
- Under Email Sending Domains, click Add New Domain if the domain isn't listed yet, then Expected DNS Entries for it.
- Copy the validation key and the DomainKey value, and have your IT team add each as a TXT record.
- Click Check DNS Entries in the Actions column. A verified domain shows green checkmarks; errors come with a link to details.
DMARC alignment
A published DomainKey lets Account Engagement sign with your sending domain, so the DKIM result can align with your From address under DMARC. Salesforce leaves the DMARC record itself to your IT team. For a test, send yourself an email and look for PASS under SPF and DKIM in the headers, from a From domain that matches the Domain Management page.
Key length and rotation
The DomainKey is a public key Account Engagement generates and you host, so a new key would mean a new TXT record from Expected DNS Entries. Salesforce's setup guides don't document a key length, selector naming or rotation schedule, and they note that a DomainKey generated outside Account Engagement may not show a green checkmark.
Common mistakes
- Publishing only the validation key. Sending works, but without the DomainKey your mail lacks an aligned DKIM signature.
- Mixing up the two TXT values. The validation key goes on the domain itself; the DomainKey goes on its
_domainkeyname. - Judging the result too early. Salesforce says a TXT entry added in the last 24 hours may not show a checkmark yet.
- Testing from the wrong domain or IP. Use your business unit's sending IP and a From domain listed on Domain Management.
Check your Account Engagement (Pardot) DKIM key
Enter your domain and the selector from your Account Engagement (Pardot) account. Free, reads public DNS only.
Frequently asked questions
Where do I find the Pardot DKIM record?
On the Domain Management page (Admin, Domain Management, or Account Engagement Settings, Domain Management in Lightning). Click Expected DNS Entries next to the sending domain and copy the DomainKey value, then publish it as a TXT record.
Is DKIM required to send from Account Engagement?
Salesforce's guide requires a verified sending domain, which uses the validation key, and recommends DKIM as an extra layer of authentication. Set up both, because DMARC needs an aligned DKIM signature.
How do I check that Account Engagement DKIM works?
Domain Management shows green checkmarks once the DNS entries are found. Then send a test message to yourself and confirm the headers show PASS for SPF and DKIM.
Sources
- Salesforce: Account Engagement Implementation Guide (Add and verify a domain for email sending; Implement DKIM authentication)
- Salesforce: Email Deliverability in Account Engagement
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Account Engagement (Pardot)'s documentation on November 3, 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
- 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
- IntercomCNAME: intercom
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for Account Engagement (Pardot)
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