These protocols only make sense in order.
DMARC is not a protocol you can learn on its own — it is a decision made on top of SPF and DKIM, and the concept that trips almost everyone is alignment. So this is a path with prerequisites, not an alphabetical glossary. Tell us what you already know and we will show you where to start.
Reference, kept current; dated when revised. Looking for what changed and when? See the Blog. For adoption figures across the top 10,000 domains, read the State of Email Security 2026 report.
Then read Layer 01 in order, all three of them, and stop. They take about fifteen minutes together and everything else on this page depends on them.
The three protocols
Nothing else on this page makes sense without these. SPF and DKIM each prove one thing; DMARC decides what to do when the proof fails.
How DMARC decides
Two concepts do all the work. Alignment is why mail that passes SPF and DKIM can still fail; policy is the choice between watching and blocking.
Reading the evidence
Once the record is published, providers start sending you data. These explain what arrives, what it means, and how to tell a broken forwarder from an attack.
Securing the transport
A separate concern from who sent the message: whether the connection carrying it was encrypted and verified. Useful, and not a prerequisite for enforcement.
Showing the brand
Your logo in the inbox is the visible payoff — but only after your domain is at enforcement. Do not start here, however much marketing wants to.
Not shipped yet
One proposal worth knowing about so you are not surprised when it appears in vendor decks. Nothing here affects what you should do this quarter.