Deliverability

SPF, DKIM & DMARC Explained

Three DNS records stand between your emails and the inbox. Here's what each one actually proves, and what happens when one's missing.

Short answer: SPF lists the servers allowed to send for your domain, DKIM signs each email so receivers can check it wasn't changed, and DMARC tells receivers what to do when an email fails those checks. DMARC passes when SPF or DKIM passes and matches your From domain.

Why this matters before we go record by record

Anyone can put any "From" address on an email — SMTP doesn't stop that. SPF, DKIM, and DMARC exist so the receiving mail server can check whether a message claiming to be from your domain actually came from someone authorized to send on your behalf. Fail that check often enough and providers start routing your mail to spam.

SPF — Sender Policy Framework

SPF is a DNS record listing which mail servers are allowed to send email for your domain. The receiving server checks the connecting server's IP against that list.

TXT yourdomain.com "v=spf1 include:spf.sendcorex.com ~all"

~all means "soft-fail anything not listed" — flag it, don't necessarily reject it. -all is the strict version: hard-fail.

SPF's limitation

SPF only checks the sending server's IP, and it breaks when a message is forwarded (the forwarding server isn't in your SPF list). That's part of why DKIM exists too.

DKIM — DomainKeys Identified Mail

DKIM adds a cryptographic signature to each outgoing message, generated with a private key. The receiving server fetches your public key from DNS and verifies the signature — proving the message wasn't altered in transit and really came from a server holding your private key.

TXT selector1._domainkey.yourdomain.com "v=DKIM1; k=rsa; p=MIGfMA0GCSq..."

Unlike SPF, DKIM survives forwarding, since the signature travels with the message content rather than depending on which server made the connection.

DMARC — the policy layer on top

DMARC tells receiving servers what to do when a message fails SPF and/or DKIM, and gives you visibility via aggregate reports. It also enforces alignment — that the domain in SPF/DKIM actually matches the visible "From" domain.

TXT _dmarc.yourdomain.com "v=DMARC1; p=quarantine; rua=mailto:reports@yourdomain.com"

p= is the policy: none (monitor only), quarantine (send to spam), or reject (bounce it outright). Most teams start at none, watch the reports, then tighten once confident nothing legitimate is failing.

How the three fit together

RecordProvesSurvives forwarding?
SPFThis IP is allowed to send for this domainNo
DKIMThis message wasn't altered and is signed by this domainYes
DMARCWhat to do if SPF/DKIM fail, plus alignment & reporting—

What happens if you skip one

No SPF or DKIM: major providers like Gmail and Yahoo now require both for bulk senders, and will bounce or bin mail that's missing them. No DMARC: you have no visibility into who else might be spoofing your domain, and no enforcement even if SPF and DKIM are set up correctly.

Frequently asked questions

What are SPF, DKIM and DMARC?

Three DNS records that authenticate your email. SPF says which servers may send for your domain, DKIM adds a cryptographic signature to each message, and DMARC sets the policy (none, quarantine or reject) for email that fails and sends you reports.

Does DMARC require DKIM?

No. DMARC passes if SPF or DKIM passes and is aligned with your From domain. In practice you should set up DKIM anyway: SPF breaks when email is forwarded, and Gmail, Outlook and Yahoo require DKIM for bulk senders.

Do SPF, DKIM and DMARC stop my email from going to spam?

No. They prove who you are, but they don't make you trusted. Inbox placement depends on your domain and IP reputation, engagement and complaint rate. Authentication is the minimum requirement, not a guarantee.

Sendcorex checks this for you

Domain setup in Sendcorex walks you through SPF and DKIM records per sending domain, with real-time verification — free up to 3,000 emails a month.

No credit card required