trustyourinbox

Pardot SPF and DKIM setup

The validation key and DomainKey TXT records to publish for Pardot, now Marketing Cloud Account Engagement, why there is no SPF include to add, and why an SPF-fail in your reports is expected.

Verified 2026-08-30 against the official Pardot documentation.

What you are setting up

Pardot is now Marketing Cloud Account Engagement, the Salesforce marketing automation product. Everything below is the Account Engagement flow; the console labels changed, the DNS work did not. If you send from Sales Cloud or Service Cloud (the CRM itself), that is a separate product with a separate DKIM setup, covered in our Salesforce guide.

You publish two TXT records per sending domain: a validation key that proves you own the domain (required before Pardot will send from it at all), and a DomainKey record so Pardot signs DKIM as your domain. There is no SPF include to add for alignment. DKIM is what carries DMARC for Pardot mail, and it is the piece people skip because the domain already says “verified” after the validation key.

Publish SPF and DKIM

In Account Engagement, open Admin > Domain Management (in the Lightning app: Account Engagement Settings > Domain Management). Click Add New Domain, enter the domain or subdomain you send from, and click Create domain. In the Actions column, click Expected DNS Entries. Pardot lists the records to publish, all TXT:

Type:  TXT     (validation key, proves ownership)
Host:  @   (or the subdomain you are verifying)
Value: the validation key Pardot shows you

Type:  TXT     (DomainKey, the DKIM public key)
Host:  <selector>._domainkey      e.g. 200608._domainkey
Value: the DomainKey value Pardot shows you

The DomainKey selector and key are assigned by Pardot, so copy the exact host and value from Expected DNS Entries rather than reusing an example. Publish every entry that view lists. Then return to Domain Management and click Check DNS Entries. Allow time for DNS to spread before you expect signing to start; the domain shows as verified when the records resolve, and a link with details appears if something is wrong.

On SPF: receivers check SPF against the Return-Path, and Pardot mail carries a Salesforce bounce address, which Salesforce covers with its own SPF record. An SPF include on your domain does not make Pardot mail align, so if Expected DNS Entries does not list an SPF value, do not add one; it would spend one of your ten lookups for nothing.

Sending from more than one domain? Repeat the whole flow for each one, so every From domain has its own DomainKey record.

Add DMARC

Standard _dmarc TXT record, nothing Pardot-specific. Start in monitor-only mode:

Type:  TXT
Host:  _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Build it with our DMARC builder and progress past p=none once your reports are clean. Pardot signs DKIM with your sending domain, so as long as the DomainKey record is in place your mail passes DMARC on the DKIM leg.

The Pardot gotcha

SPF will show as failing, and that is normal. Pardot sends with a Salesforce return-path (something like bounce.s7.exacttarget.com or bounce.s10.mc.pd25.com), so SPF authenticates for Salesforce but does not align to your domain. Account Engagement mail passes DMARC because DKIM aligns, and the SPF column stays red. Do not weaken your policy over it, and do not add an SPF include hoping to fix it; only a custom return-path on your own domain, which Salesforce sets up through a support case, makes SPF align. The second trap is the DNS host appending your domain: if your provider turns _domainkey.yourdomain.com into _domainkey.yourdomain.com.yourdomain.com, enter only the host portion. Finally, keep the tracker domain (the go.yourdomain.com CNAME to go.pardot.com) separate from the sending domain; it is for link branding, not authentication, and Salesforce warns against using the same domain for both.

Confirm it worked

  • Check DNS Entries in Pardot. The domain should show verified with the DomainKey in place; if it does not, wait for DNS to spread and check again.
  • Send a test and read the headers. Send a list email or a test from Pardot, open the message, and confirm the DKIM signature shows d=yourdomain.com and dmarc=pass. Our header analyzer reads it back plainly.
  • Watch the reports. Pardot should pass DMARC via aligned DKIM. In trustyourinbox it is labeled a known sender, and the source view separates the expected SPF-alignment miss from a real failure.

Let trustyourinbox publish Pardot for you.

Connect Cloudflare or AWS Route 53 once and the Pardot records are one click. We email you the exact record, wait five minutes, write it, and read it back from public DNS. Then we keep watching this sender in your DMARC reports and alert you when Pardot mail starts failing.

Was this page helpful?

Keep reading.

Start with one domain. See it with your own data.

Free for one domain, no card. Add one DNS record and the first reports usually arrive within a day.

  1. Monitoring
  2. Quarantine
  3. Reject