SPF, DKIM and DMARC setup guide for small business email
What SPF, DKIM and DMARC do, the exact DNS records to publish, how to combine several senders, and how to move DMARC from monitoring to enforcement.
When business email starts landing in spam, or customers receive invoices "from you" that you never sent, the cause is almost always the same: the domain is missing one of three DNS records called SPF, DKIM and DMARC. Together they let receiving mail servers check that a message claiming to be from your domain really is. Large mailbox providers now expect them from every serious sender, and setting them up correctly takes about an hour plus a few weeks of watching reports.
Disclosure: some links in this guide are partner links. If you buy through them, MMIX may earn a commission; your price stays the same.
Marketing MIX has configured email authentication for client domains since 2012. This is the order we follow, and the mistakes we see most often when we audit a domain.
What each record does
Record
Where it lives
What it proves
SPF
TXT at the root (@)
Which servers may send mail for the domain
DKIM
TXT or CNAME at selector._domainkey
That the message was signed by an authorised sender and arrived unchanged
DMARC
TXT at _dmarc
Which policy receivers apply when SPF and DKIM fail to match the From address, and where to send reports
Alignment, and why receivers now insist on it
The key idea is alignment. A spammer can pass SPF for their own domain while showing your domain in the From line. DMARC closes that gap by requiring that the domain checked by SPF or DKIM matches the domain the reader sees.
Since 2024, Gmail and Yahoo require SPF, DKIM and DMARC from senders of large volumes of mail, and Microsoft added similar rules for Outlook.com in 2025. Smaller senders benefit from the same records, because receivers use them to judge every message.
Step-by-step: setting up SPF, DKIM and DMARC
Step 1: List every service that sends mail as your domain
Before you write any records, list every system that sends mail with your domain in the From address:
your mailbox provider (Google Workspace, Microsoft 365, Namecheap Private Email or another host);
newsletter and marketing tools;
CRM, helpdesk and booking systems;
invoicing and accounting software;
the website itself, for contact forms and order confirmations.
Each service publishes its SPF include and DKIM instructions in its help centre. Missing a sender here is the reason most DMARC rollouts break something.
Step 2: Publish a single SPF record
SPF is a TXT record at the root of the domain. A domain with Google Workspace and one newsletter tool might publish:
One SPF record per domain. Two records starting with v=spf1 make SPF fail. When a new service asks you to "add an SPF record", add its include to the existing one.
Ten DNS lookups at most. Each include, a, mx and redirect counts, and includes can contain more includes. Tools like MxToolbox show the total.
End with ~all or -all. Avoid +all, which allows anyone to send as you.
If your DNS is at Namecheap, records go in the Advanced DNS tab; with Cloudflare, in the DNS section of the zone. Our DNS records guide explains how to find the right panel.
Step 3: Turn on DKIM for each sender
DKIM uses a key pair. The sending service keeps the private key and signs each message; you publish the public key in DNS so receivers can check the signature.
In practice:
Open the email authentication or DKIM section in the service's admin panel.
Generate the key. Choose 2048-bit where the service offers a choice.
Publish the record exactly as given. Google Workspace uses a TXT record at google._domainkey; Microsoft 365 uses two CNAME records at selector1._domainkey and selector2._domainkey; other services use their own selector names.
Return to the panel and click "start authentication" or "verify".
Repeat for each newsletter tool, CRM and helpdesk. DKIM signed with your own domain is what lets those tools pass DMARC.
p=none means receivers deliver mail as usual and only report what they see.
rua is where aggregate reports go. Use a dedicated mailbox or a DMARC reporting service, because reports arrive as compressed XML files every day.
Optional tags: adkim and aspf for strict alignment, pct for a gradual rollout.
Step 5: Test and read the reports
Send a message from each service to a Gmail address, open it and choose "Show original". You want to see SPF: PASS, DKIM: PASS and DMARC: PASS. A test at mail-tester.com gives a score and flags problems in plain language.
Then watch the DMARC reports for two to four weeks. They list every server that sent mail claiming your domain and whether it passed. Each failing source is one of three things: a service you forgot in Step 1, a service with DKIM still off, or someone spoofing you.
Step 6: Move DMARC to quarantine, then reject
When every legitimate source passes, tighten the policy:
Change to p=quarantine, so failing mail goes to spam. Optionally start with pct=25 and raise it.
After another couple of weeks of clean reports, change to p=reject, so failing mail is refused.
Keep the reports coming after you reach reject. New tools get added to companies all the time, and the reports show you when one of them sends without authentication.
What to check and common mistakes
Two SPF records after a new tool was added. Merge them.
SPF over ten lookups. Remove services you no longer use.
DKIM published with the wrong host. Some panels add the domain automatically, so google._domainkey.yourdomain.com entered in full becomes doubled. Enter only google._domainkey.
Jumping straight to p=reject. Without the monitoring period you will block your own invoices or newsletters.
Forgetting parked domains. A domain that never sends mail should publish v=spf1 -all and v=DMARC1; p=reject so nobody can use it for phishing.
Ignoring the website. Contact form mail sent directly from the web server fails SPF and DKIM. Send it through your mailbox provider or a transactional service with DKIM on your domain.
Email authentication touches every tool that sends on your behalf, and one wrong record can quietly send invoices to spam. If you have more than a few senders, several brands, or reports you cannot read, we can audit the domain, fix the records, run the monitoring period and move you to enforcement.
Prefer to hand it off? MMIX sets up domain, hosting, email and DNS for you — since 2012. Tell us about your project and we will reply with a plan.
Send your site address. We look at the site, your ads and your search presence and send back what to fix first and a one-month plan. Ads management is quoted after the review.