Email sending platforms: SPF, DKIM and DMARC setup
Most businesses send email from more tools than they think: a marketing platform for newsletters, a CRM for sales sequences, billing software for invoices, a help desk for tickets. Each one is a separate source in DMARC terms. If it puts your domain in the From address, it needs aligned DKIM or aligned SPF, or its mail fails DMARC once you enforce. This page explains the pattern they all share, what to ask each vendor, and where each platform's own setup guide lives.
These tools are often bought by teams that don't manage DNS, which is why they're the sources most often missed. Before anyone touches a record, agree who signs off on DNS changes. Who usually owns SPF, DKIM, and DMARC is a good place to start that conversation.
First, find out how the tool sends
A tool can send in one of three ways. Check its current settings before you add anything, because the work is different for each.
- It sends as your domain from the vendor's servers. This is the usual case for marketing platforms, transactional email services, and many CRMs and help desks. Your domain is in the From address, so your DMARC policy applies. The tool needs aligned DKIM and, if the vendor offers it, a custom Return-Path on your domain. The generic procedure is in How to add a third-party sender without breaking DMARC, and the platform guides below give the records for each vendor.
- It sends through your own mailbox platform. The tool connects to a user's Microsoft 365 or Google Workspace mailbox, or relays through it. Your mailbox platform's SPF and DKIM then authenticate the mail, so the work is in DMARC for Microsoft 365 or DMARC for Google Workspace, not in a sending-platform guide.
- It sends from the vendor's own domain, with your name in the display name and your address in Reply-To. Some invoicing and payment notifications work this way. Your DMARC policy doesn't apply, because the From domain isn't yours. That's fine for DMARC, though recipients see the vendor's domain. Don't "fix" it by forcing your address into From unless the tool can then authenticate it.
What to ask each vendor
Put these questions to the vendor, or find the answers in its domain-authentication settings:
- Can you DKIM-sign with our domain or a subdomain, so the
d=domain aligns with our From address? Which records, at which host names, and are they CNAME or TXT? - Can you use a custom Return-Path (MAIL FROM) on our domain, so SPF can align too? If not, DKIM is the only route to a DMARC pass. That's workable, but it means DKIM has to be right. The difference between the two routes is in SPF include vs DKIM from the vendor.
- Which SPF include do you need, and on which domain? The apex, or a Return-Path subdomain?
- Do we send from shared or dedicated IPs?
- If your setup offers to publish a DMARC record for us, will it overwrite the one we have? You want one DMARC record per domain, with
ruapointing at the reporting address our platform gives you. A vendor's samplep=nonerecord with norua, or someone else'srua, can quietly undo your reporting or your enforcement.
Platform guides and what we know about each
DMARC is never a setting inside a sending platform. It's a TXT record on your domain. What the platform controls is whether its mail carries aligned DKIM, and sometimes aligned SPF. The table shows the route each platform uses. Where we haven't confirmed a detail, the row says so. Copy record names and values from your own account, never from a table like this one.
| Platform | How it aligns with your domain | Custom Return-Path | Guide |
|---|---|---|---|
| Mailchimp (marketing) | Aligned DKIM through two CNAME records you copy from your account. Its domain authentication also asks for a DMARC TXT at _dmarc. No Mailchimp SPF include is part of the setup, and the envelope sender normally stays on a Mailchimp domain, so SPF won't align. |
We haven't confirmed one for marketing campaigns. Plan on DKIM. | Mailchimp SPF, DKIM and DMARC setup |
| Mailchimp Transactional | Two DKIM CNAMEs, mte1._domainkey and mte2._domainkey. It won't send to external recipients until the domain has DKIM and a valid DMARC policy. |
Yes, by pointing a subdomain (not the root) at the service with a CNAME. | Same guide, separate section |
| HubSpot (marketing email) | Connecting a sending domain sets up MX, two DKIM CNAMEs, an SPF include and a DMARC TXT. Copy every value from the portal. Needs Starter or higher. Sales, one-to-one and conversations inbox mail may not use this sending domain. | Not on the shared network. Possible with the dedicated IP add-on or the transactional email add-on. | HubSpot SPF, DKIM and DMARC setup |
| SendGrid | With automated security on: CNAMEs for a custom mail host (em plus a number) and DKIM selectors s1 and s2. With it off: MX and SPF TXT on that host, and a DKIM TXT at m1._domainkey. |
Yes, as an advanced option, and through the mail-host CNAME when automated security is on. | Not written yet |
| Klaviyo | A branded sending domain, set up by NS delegation or by static CNAMEs that carry SPF and DKIM. It can generate a p=none DMARC record; don't let that replace an existing one. |
No separate control; alignment comes from the branded sending subdomain. | Not written yet |
| Amazon SES | DKIM through CNAME records the console gives you. DMARC is a TXT you publish yourself. | A custom MAIL FROM subdomain (with its own SPF and MX) is needed for SPF to align. DKIM aligns without it. | Not written yet |
| Mailgun | Two DKIM CNAMEs with keys the vendor hosts and can rotate. Manual TXT keys are also possible. | Not confirmed yet. Ask the vendor. | Not written yet |
| Postmark | DKIM record details not confirmed yet. Use the values in your account. | Yes. A CNAME (default host pm-bounces) on your domain gives SPF alignment. DKIM can pass without it. |
Not written yet |
| Brevo | An ownership TXT, DKIM as one TXT or two CNAMEs, and a DMARC TXT. Its automatic setup may offer to replace an existing DMARC record; if you have one, use manual setup. | None found. SPF alignment on shared sending is uncertain. Plan on DKIM. | Not planned |
| Salesforce and Marketing Cloud, Constant Contact, ActiveCampaign, Zoho, Zendesk | Not confirmed yet. We won't guess at record types. Use the vendor questions above. | Not confirmed yet. | Not written yet |
| Google Workspace | Mailbox platform, not a sending platform. | Not applicable. | DMARC for Google Workspace |
| Microsoft 365 | Mailbox platform, not a sending platform. | Not applicable. | DMARC for Microsoft 365 |
Adding the records. The platform gives you the values. Your DNS host is where they go. If your DNS is on Cloudflare, read Add SPF, DKIM and DMARC records in Cloudflare DNS Add SPF, DKIM and DMARC records in Cloudflare DNS first, because a proxied or flattened DKIM CNAME is one of the most common reasons a platform won't verify a domain. For what a DMARC record should contain, see our DMARC setup page.
Then confirm it. A "verified" or "authenticated" badge in a platform means its records resolve. It doesn't mean its mail passes DMARC. Send a real message, check the Authentication-Results header for dkim=pass with header.d= on your domain, and then watch for the source in your aggregate reports (How to add a third-party sender without breaking DMARC, A field-by-field walk-through of a DMARC aggregate report). In our reporting, each sending source gets its own view with its SPF, DKIM and alignment results, which makes a new platform easy to spot.
Tool types and what usually matters
These are general patterns, not claims about any named product. Put marketing on its own subdomain (Shared domains and multi-service setups) and keep transactional mail apart. A CRM often mixes sending modes, so test each type. Help desk tools need aligned DKIM and often forward inbound mail (Email forwarding, SRS, and ARC). Invoicing tools may send as you or from their own domain; a rejection has a high impact if they send as you. E-commerce, booking, forms and HR tools often show up late in reports.
Keep marketing problems away from invoices
DMARC doesn't care what kind of message it's checking. Mailbox providers do care about reputation, though, and they track it per sending IP and per DKIM domain. A complaint-heavy campaign on the same domain and IPs as your invoices can drag the invoices down with it.
Separating streams limits that damage. Put bulk marketing on its own subdomain, such as news.example.com, keep receipts and invoices on another, and don't put promotions inside receipt or invoice templates. This is reputation hygiene, not a DMARC rule, and it doesn't guarantee inbox placement. How reputation works is in IP and domain reputation, the subdomain trade-offs are in Shared domains and multi-service setups, and the bulk-sender rules are in Google and Yahoo sender requirements and Microsoft and Outlook authentication rules.
When you switch platforms
DKIM and Return-Path records belong to a platform, so a migration needs an overlap:
- Set up and verify the new platform's DKIM, and its Return-Path if it offers one, before cut-over.
- Run old and new side by side until your reports show the old platform has stopped sending (How to inventory sending sources).
- Remove the old platform's include and DKIM records.
Removing the old records too early breaks the last scheduled sends. Leaving them forever wastes SPF lookups and leaves an old vendor authorized to send as you.
Mistakes worth avoiding
- Assuming the CRM sends the way the marketing platform does. It may use connected mailboxes for some messages and its own servers for others.
- Treating a "verified domain" badge as proof. Check headers and reports.
- Assuming invoicing tools are exempt. If the From domain is yours, your DMARC policy applies.
- Letting a setup wizard add a second DMARC record, or replace your record with a sample
p=noneand norua. Receivers ignore a domain's DMARC records when there's more than one. Tags and report addresses are covered in rua, ruf, and report authorization. - Letting each team add its own SPF record or include. That's how domains end up with two SPF records or more than 10 lookups (Two SPF records, The 10-lookup limit and SPF permerror).
- Enforcing before the monthly invoice run has appeared in reports. Irregular senders take a full cycle to show up. The rollout itself is in A safe rollout: p=none to quarantine to reject.
If a platform is already sending and failing alignment, start with Third-party mail fails alignment. Mailbox-platform problems are in Microsoft 365 or Google Workspace setup issues.
Where BIMI fits
BIMI is a domain-level step that comes after DMARC is at enforcement. It isn't a setting in any sending platform. The platform's part is to keep signing aligned DKIM for your From domain. When you get there, What is BIMI, and why DMARC comes first explains why DMARC comes first, and How to move from DMARC enforcement to BIMI covers the move from enforcement to BIMI.
Free DMARC account
Not sure which sender is failing?
Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.
- Every sending source in one dashboard
- SPF, DKIM and alignment results per sender
- No XML files to read
FAQ
Our marketing platform says our domain is authenticated. Are we ready to enforce DMARC?
Only if its mail shows aligned DKIM or aligned SPF passing, both in message headers and in your aggregate reports. The platform's guide shows what to look for.
Should invoices and newsletters come from the same domain?
They can. Separating them by subdomain keeps a marketing reputation problem away from mail customers need. It's a design choice, not a DMARC requirement (Shared domains and multi-service setups).
Our invoicing tool sends from its own domain with our name. Does our DMARC apply?
No. DMARC applies to the domain in the From address. If that's the vendor's domain, the vendor's own authentication is what counts.
We're moving from one marketing platform to another. What breaks?
The old platform's DKIM and Return-Path records don't carry over. Set up the new platform first, overlap the two, and remove the old records once reports show the old platform has stopped.
Where are the HubSpot and Mailchimp steps?
In their own guides: Mailchimp SPF, DKIM and DMARC setup and HubSpot SPF, DKIM and DMARC setup.