If customers say your quotes and invoices end up in their junk folder, the cause is usually missing or broken email authentication. Gmail, Yahoo and Microsoft now expect senders to prove that mail claiming to be from your domain really is. Three DNS records do that job.
SPF: who is allowed to send
SPF is a single TXT record listing the services allowed to send email as your domain, for example Microsoft 365 plus your invoicing or marketing platform.
- You can have only one SPF record. Two records means SPF fails entirely.
- SPF allows a maximum of 10 DNS lookups. Every
include:counts, and adding too many services quietly breaks it. - End it with
~allor-all, not+all, which allows anyone to send as you.
DKIM: a signature on every message
DKIM adds a cryptographic signature to outgoing mail. In Microsoft 365 you enable it in the Defender portal and publish two CNAME records (selector1 and selector2) in DNS. Each third-party sender (your CRM, your newsletter tool) should sign with DKIM for your domain too.
DMARC: the policy and the reports
DMARC tells receiving servers what to do when a message fails SPF and DKIM, and sends you reports showing who is sending as your domain. Roll it out in stages:
p=nonewith a reporting address: collect reports for two to four weeks and find every legitimate sender.p=quarantine: failing mail goes to spam.p=reject: failing mail is refused. This is what stops criminals spoofing your domain.
Quick self-check
Send an email to a Gmail account, open it, choose "Show original" and look for SPF: PASS, DKIM: PASS and DMARC: PASS. Anything else needs fixing.
We set up and monitor SPF, DKIM and DMARC as part of Microsoft 365 services and cybersecurity.