Every email platform has its own screens and its own names for things, but the job underneath is always the same. You’re proving to Gmail, Outlook and Yahoo that the email really comes from you, using three DNS records: SPF, DKIM and DMARC.
This guide walks through that job step by step. It works whether you send from Mailchimp, Brevo, HubSpot, Klaviyo, Google Workspace, Microsoft 365 or something else entirely. Where a platform does things differently, I’ll point it out.
Before you start: list everything that sends as you
This is the step most people skip, and it’s why so many setups fail later. Make a list of every service that sends email from your domain, not just your marketing platform. Typically that’s:
- Your mailbox provider (Google Workspace or Microsoft 365)
- Your marketing platform
- Your CRM or sales tools
- Your help desk or support system
- Invoicing, booking or ecommerce systems
- Your website’s contact forms
Every one of these needs to pass authentication. Miss one, and when you turn DMARC up later, its emails will start going to spam or bouncing.
You’ll also need access to your DNS. That’s usually wherever you bought your domain, or Cloudflare if you use it.
Step 1: Authenticate your domain in each platform
Every decent email platform has a setting for this, though the name varies: domain authentication, sending domain, branded domain or verified domain. Find it, add your domain, and the platform will give you a set of DNS records to publish. Usually these are CNAME or TXT records.
Do this for every platform on your list. It’s what lets the platform sign your email with your own domain instead of its own.
Step 2: Publish the DKIM records
Most of the records your platform gives you are for DKIM. Copy them into your DNS exactly as shown. A few things to watch:
- Some DNS panels add your domain to the end of the name automatically, so you end up with selector._domainkey.yourdomain.co.uk.yourdomain.co.uk. Check what your panel expects.
- Long DKIM keys sometimes get split or cut off when pasted. If your platform offers a 2048-bit key, use it, and check the whole value went in.
- Some platforms, like Microsoft 365, need you to switch DKIM on after the records are published. Publishing them isn’t enough.
Then go back to the platform and click verify. DNS changes can take a few minutes to a few hours to show up.
Step 3: Sort out SPF, but only where it’s needed
This is where most people go wrong. Not every platform needs adding to your SPF record. SPF checks the bounce (Return-Path) domain, and many marketing platforms use their own bounce domain unless you set up a custom one. If yours does, adding it to your SPF record does nothing.
Add a platform to SPF when it tells you to, or when you’ve set up a custom bounce domain on your own domain. Your mailbox provider (Google Workspace or Microsoft 365) always needs to be in there.
Two rules matter more than anything else:
- Only one SPF record per domain. If a platform tells you to add a new one, merge it into the one you have. Here’s how to merge two SPF records.
- No more than 10 DNS lookups. Every include: counts. Go over and SPF breaks completely, which is explained in SPF PermError: too many DNS lookups.
Step 4: Check alignment
DMARC doesn’t just want SPF or DKIM to pass. It wants them to pass for the same domain your subscribers see in the From address. That’s called alignment.
In practice, DKIM alignment is the one that matters most. If step 2 is done properly, DKIM will be signed with your domain and will align. SPF only aligns if the platform uses a custom bounce domain on your domain. If you’re seeing SPF pass but DMARC fail, DMARC alignment explained covers why.
Step 5: Add a DMARC record
Once your senders are authenticating, publish a DMARC record. Start in monitoring mode:
v=DMARC1; p=none; rua=mailto:[email protected]
It goes in a TXT record at _dmarc.yourdomain.co.uk. The p=none part means nothing gets blocked yet. The rua part asks mailbox providers to send you daily reports showing every service sending as your domain and whether it passed. Those reports are how you find the senders you missed. Here’s how to read a DMARC aggregate report.
Step 6: Test it
Send a test email from each platform and check it passes. The quickest way is our free email spam test, which checks SPF, DKIM and DMARC along with your spam score. You can also open the email in Gmail, choose “Show original” and look for SPF, DKIM and DMARC all showing PASS.
Step 7: Move to enforcement
p=none is a starting point, not a finish line. Once your reports show all your real email passing, move to p=quarantine and then p=reject. That’s what actually stops someone sending email pretending to be you, and it’s needed for BIMI. A few weeks is typical to get there. DMARC p=none: what it means and how to move to enforcement safely walks through it.
Notes for the most common platforms
- Google Workspace: DKIM is generated in the Admin console and has to be switched on after you publish it. Full walkthrough: DMARC for Google Workspace.
- Microsoft 365: your own domain isn’t DKIM-signed until you switch it on. Full walkthrough: How to set up DKIM in Microsoft 365.
- Mailchimp, Brevo, HubSpot and Klaviyo: each has a domain authentication setting that gives you the records to publish. Step-by-step guides: Mailchimp, Brevo, HubSpot and Klaviyo.
- Anything else: look for “domain authentication” or “sending domain” in the settings. If you can’t find it, or the platform can’t sign with your domain at all, that’s worth knowing before you move DMARC to enforcement.
Common mistakes
- Adding a second SPF record instead of merging into the first
- Publishing DKIM records but never clicking verify or switching DKIM on
- Forgetting the services outside marketing, like invoicing or your help desk
- Adding a DMARC record with no rua address, so you never get the reports
- Staying on p=none forever, which leaves your domain open to spoofing
Want it done for you?
I’ve set up SPF, DKIM and DMARC on most email platforms over 16 years, and it can often be done within an hour. See SPF, DKIM & DMARC setup, or run the free email spam test first to see where you stand.
