arrow_backBack to Blog
IndustryMarch 8, 2023

SPF, DKIM, and DMARC: Email Authentication Explained Simply

Demystifying the three pillars of email authentication and how proper configuration protects your domain from spoofing and improves deliverability.

Sarah Chen

Sarah Chen

Email Marketing Specialist

SPF, DKIM, and DMARC: Email Authentication Explained Simply

Email authentication is the foundation of modern email deliverability. Without proper authentication, your emails are significantly more likely to be flagged as spam or rejected by major inbox providers. The three core protocols—SPF, DKIM, and DMARC—work together to verify that your emails are legitimate and have not been tampered with during transit. Understanding each protocol is essential for anyone managing email marketing at scale.

SPF tells receiving servers which IP addresses are authorized to send mail from your domain. When a receiving server gets an email claiming to be from your domain, it checks the SPF record to verify the sending IP is authorized. If the IP is not listed, the email may be rejected. The key to effective SPF is keeping your record up to date as you add or change email service providers, and never exceeding the DNS lookup limit of 10 queries.

DKIM adds a cryptographic signature to each outgoing email. The email is signed with a private key stored on your sending server, and the signature is verified by the receiving server using a public key published in your DNS records. DKIM ensures that the email content has not been modified between sending and receiving. Unlike SPF, DKIM signatures survive email forwarding, making them essential for newsletters that may be forwarded to different addresses.

DMARC ties SPF and DKIM together with a policy that tells receiving servers what to do when authentication fails. A DMARC policy can be set to none, quarantine, or reject. DMARC also generates aggregate reports that show you who is sending email from your domain, giving you visibility into potential spoofing or unauthorized sending. Start with p=none to monitor, then progress to p=quarantine and finally p=reject as you confirm all legitimate senders are authenticating properly.

Implementation follows a phased approach over several weeks. Publish SPF and DKIM records first. Then publish a DMARC policy set to none and analyze the reports to identify all legitimate senders. Once confirmed, move to quarantine, then reject. The final step is implementing BIMI, which displays your verified logo next to authenticated emails in supported inboxes, providing both security and branding benefits.

Deepen your understanding.

Join our monthly dispatch on email marketing strategy.

Share
All Articles
Put this into practice

Want emails like this, done for you?

Our team designs, writes, and ships campaigns that put these ideas to work — across 70+ industries. Here's where to start.