Three records work together:
– SPF lists the servers allowed to send email for your domain.
– DKIM adds a cryptographic signature to each message, which receivers check against a public key published in your DNS.
– DMARC tells receivers what to do with messages that fail (none, quarantine or reject), requires the visible From domain to align with SPF or DKIM, and sends you reports.
Since 2024, Gmail has required senders of about 5,000 or more messages a day to Gmail addresses to use SPF, DKIM and DMARC (a policy of p=none is the minimum), align the From domain, offer one-click unsubscribe and keep spam complaint rates below 0.3%. Yahoo introduced similar rules. Since May 2025, Microsoft has applied comparable SPF, DKIM and DMARC requirements to domains sending more than 5,000 emails a day to Outlook.com, Hotmail and Live addresses.
Why it matters for eCommerce
A store that fails authentication sees campaigns and flows filtered to spam or rejected outright. Email revenue drops quietly, and nothing in your ESP dashboard explains why.
How it works in practice
- Send from your own domain or a subdomain authenticated in your ESP, using the DNS records the ESP provides.
- Include every service that sends as your domain in one SPF record, such as your ESP, helpdesk and Google Workspace, and stay within SPF’s limit of 10 DNS lookups.
- Start DMARC at p=none with reporting, fix what the reports reveal, then move toward quarantine or reject.
- Monitor spam rates in Google Postmaster Tools.
Common mistakes
- Publishing more than one SPF record on a domain, which breaks SPF.
- Jumping to p=reject before every sender is authenticated, which blocks legitimate mail such as order confirmations.
- Forgetting apps outside the ESP, such as review or helpdesk tools, that send as your domain.