DMARC for marketing platforms
Marketing Cloud Engagement authenticates through a Sender Authentication Package on a subdomain, either delegated to Salesforce with four NS records or self-hosted.
No SPF value to copy for this platformFor a self-hosted setup, Salesforce lists SPF TXT records for the SAP domain and those hosts. With delegation, Salesforce manages DNS entries on the subdomain.
<selector>._domainkey.<subdomain> TXT (self-hosted; value from Salesforce)Salesforce gives you your unique values during setup. Check your own package's records rather than copying another customer's.
email.example.com NS ns01 to ns04.ums-dns-salesforce.comemail.example.com NS ns1 to ns4.exacttarget.comValues in angle brackets are specific to your account. Copy the real ones from Salesforce Marketing Cloud rather than from this page.
v=DMARC1; p=none; rua=mailto:<your-business-id>@mail.yourdmarc.online, or build it with the DMARC generator. Delivery does not change at this stage.p=quarantine when your legitimate mail passes, and watch the reports for anything you missed.p=reject with sp=reject. Read the enforcement guide for what tends to break, and keep monitoring afterwards.Taken from Salesforce Marketing Cloud's own documentation, checked on 1 November 2026. Providers change these, so their setup screen wins over this page.
Check a real message against the Gmail, Yahoo and Outlook.com sender rules, or test whether a stranger can send mail as your domain. Both are free.
On the SAP domain itself and its bounce and reply hosts, with values Salesforce provides. For a self-hosted setup, Salesforce lists SPF TXT records for the SAP domain and those hosts. With delegation, Salesforce manages DNS entries on the subdomain.
Provided by Salesforce during setup. Salesforce gives you your unique values during setup. Check your own package's records rather than copying another customer's.
Only once a passing SPF or DKIM result is on your From domain or its organizational domain. Salesforce advises against using an existing domain, such as one hosting your corporate site, as an SAP domain: its records are likely to conflict and DNS generally cannot be delegated. Plan on a subdomain.
Start at p=none with a rua address, finish the Salesforce Marketing Cloud setup, then read your reports. Check that sends are from the SAP subdomain, not a registered From address on another domain, before you enforce at the root. Move to p=quarantine, then p=reject, once your legitimate mail passes.
Download to read the eBook