Skip to content
BENIBIX Learn

SPF, DKIM and DMARC

Level 4 · Reaching the inbox

The three DNS records that prove an email really came from your domain. What each one checks, and why big mail services now insist on all three.

Course contentsLesson 10 of 11

After this lesson you can

  • Say what SPF, DKIM and DMARC each check
  • Read the three records in DNS
  • Move DMARC from none to reject safely

12 mincovers 4 glossary entries

Worth reading first: Email Deliverability

How SPF, DKIM and DMARC prove who sent an email

Anyone can type any address into the from line of an email. SPF, DKIM and DMARC are three records that let a mail service check the email really came from your domain. All three live in your domain's DNS. That is the public lookup system for names on the internet. Since 2024, Gmail and other big mail services expect all three from anyone sending 5,000 emails a day.

SPF is a list of the servers allowed to send email for your domain. When an email arrives, the mail service checks if the server that sent it is on the list. Every tool that sends for you has to be on it. That means your newsletter tool and your web shop.

DKIM adds a hidden signature to each email. Your email tool signs each message with a secret key, and the matching public key sits in your DNS. The receiver checks the signature. If it matches, the email is real and nobody changed it on the way.

DMARC ties the two together. It is a rule that says what to do when an email fails. None only watches. Quarantine sends it to spam. Reject turns it away. It also asks mail services to send you reports on who sends mail in your name.

Start DMARC on none and read the reports for a few weeks. They show every service sending as your domain, including tools you forgot. Fix those, then move to quarantine, and later to reject.

A marketer rarely types these records in by hand. Your email tool gives you the exact lines, and whoever runs your domain adds them. Your job is to know they are needed, ask for them, and check they pass.

The common mistake is adding a new email tool and forgetting to add it to SPF and DKIM. Its mail fails the checks and lands in spam. Nobody knows why until a customer complains.

dns
example.com.                  TXT  "v=spf1 include:_spf.google.com include:mailgun.org ~all"
sel1._domainkey.example.com.  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
_dmarc.example.com.           TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
The three records for one domain. Your email tool gives you the exact values; the names and shapes look like this.
SPF checks the server. DKIM checks the signature. DMARC decides what happens when either one fails.

Worked example

A charity finds a forgotten sender

A charity sets DMARC to none and reads the reports for a month. They show 2,000 emails a week sent in its name by an old donation tool nobody remembered.

It adds the tool to SPF and turns on DKIM there. Two months later it moves DMARC to reject, and fake emails using its name stop reaching donors.

The words for this lesson4

Check yourself

Why start a new DMARC record on none rather than reject?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.