Email was designed without any way to check who sent a message. Anyone can put any address in the From line. SPF, DKIM and DMARC are three DNS-based standards that together let receivers tell real mail from forgeries.
SPF: which servers may send
A TXT record on your domain lists the servers allowed to send mail for it. The receiver checks the server that delivered the message against that list. SPF checks the envelope sender (Return-Path), an address the recipient never sees, and it breaks when mail is forwarded. How to set up SPF.
DKIM: a signature on every message
Your mail server signs each message with a private key. The public key sits in your DNS, so any receiver can verify the signature. A valid signature proves the message came from a server holding the key for that domain and wasn't changed on the way. It survives forwarding, as long as nobody edits the message.
DMARC: tying it to the From address
Neither SPF nor DKIM looks at the From address people actually see. DMARC adds that link: a message passes DMARC if SPF or DKIM passes for the same domain as the From address. This is called alignment. Your DMARC record then tells receivers two things:
- What to do with mail that fails: nothing (
p=none), send it to spam (p=quarantine) or refuse it (p=reject). - Where to send reports: daily summaries of every server that sent mail using your domain, and whether it passed (
rua=).
What receivers expect today
Since 2024, Gmail and Yahoo require SPF or DKIM from every sender, and SPF, DKIM and DMARC from anyone sending in bulk. Microsoft followed in 2025. Mail that doesn't meet the bar goes to spam or is rejected. See the sender requirements checklist.
In practice: make sure every service that sends as you passes DKIM with your domain, publish SPF, start DMARC
at p=none with reports, and work towards reject.