OOmnistu

Blog / Web Fundamentals

Web Fundamentals

SPF, DKIM and DMARC explained: what each one proves and how to roll them out

Three standards, three questions: DKIM's key-pair signatures, SPF's sender list, DMARC's alignment policy and reports - plus a rollout order that does not break your own mail.

OOmnistu
Reviewed 2026-11-19 · 3 min read

SPF, DKIM and DMARC get named in one breath so often that they blur into one thing. They are three different mechanisms that answer three different questions, and setting them up is mostly DNS work plus one switch at your email provider. This guide explains what each one proves and how to roll them out without breaking your own sending.

For what Google specifically requires of senders to Gmail accounts (thresholds, unsubscribe rules, spam-rate limits), see our companion piece on Google's sender guidelines; this article covers the standards themselves. DKIM mechanics below follow Google Workspace's official setup documentation, checked 19 November 2026.

DKIM: a signature receivers can verify

DKIM (DomainKeys Identified Mail) works on a key pair, as Google's documentation describes it. A private key on your sending server adds a cryptographic signature to the header of each outgoing message; the matching public key lives in a DNS TXT record on your domain. A receiving server fetches the public key from DNS and verifies the signature - proving the message came from your infrastructure and was not altered in transit.

For Google Workspace, setup is three steps: generate the key pair in the Admin console, publish the public key as a DNS record, then turn on DKIM signing and verify. Two practical caveats from the same docs: outbound gateways that modify messages (for example, appending footers) can invalidate signatures, and some domains already have DKIM configured - check before generating a new key.

SPF: the guest list for your domain

SPF (Sender Policy Framework) is a DNS record listing which servers may send mail for your domain. Where DKIM answers "is this message authentically ours and unaltered?", SPF answers "was this server allowed to send for this domain?". Both matter because neither covers every path: forwarded mail can break SPF while the DKIM signature survives, and a message can pass SPF on a bounce address while the visible From: domain is something else.

DMARC: alignment, policy and reports

DMARC adds the missing link between the visible From: domain and what SPF and DKIM checked - alignment - and then answers "what should a receiver do when checks fail?": monitor, quarantine or reject. Its most immediately useful feature is reporting: receivers send you XML reports of who is sending mail as your domain, which is how most teams discover a forgotten legacy service or a marketing tool nobody told engineering about.

A rollout order that does not break your own mail

Sources

Drafted with AI assistance from these sources. Provider setup steps change; follow your email provider's current documentation for exact key generation and record formats.