SPF, DKIM and DMARC in Plain English
Anyone can type any address into the From line of an email, a bit like writing any return address on an envelope. That's how scammers pretend to be your bank. SPF, DKIM and DMARC are three small records that let the receiving server check whether an email really came from the domain it claims.
Since 2024, Gmail and Yahoo require them, and Outlook.com does too for high-volume senders. You don't need to be technical to understand them. Here's what each one does.
First, where these records live
All three are entries in your domain's DNS, the public settings for your domain name. You (or whoever manages your domain) add them where you bought the domain or wherever its DNS is hosted. Your email platform usually tells you exactly what to paste in.
The one-minute version
| Record | The question it answers | Everyday comparison |
|---|---|---|
| SPF | Is this server allowed to send mail for this domain? | A guest list at the door |
| DKIM | Was this message signed by this domain, and is it unchanged? | A tamper-proof wax seal |
| DMARC | Does the visible From address match what passed, and what should happen if it doesn't? | The rulebook for the bouncer |
SPF: the guest list
SPF (Sender Policy Framework) lets you publish a list of the servers and services allowed to send email using your domain. When a message arrives, the receiving server checks whether it came from somewhere on your list.
A few details that trip people up:
- It checks a hidden address. SPF checks the behind-the-scenes return address that bounces go back to, plus the name the sending server introduces itself with. It doesn't check the From address your reader sees. That gap is why DMARC exists.
- Only one SPF record per domain. The standard says multiple SPF records for the same name are not permitted, and having two produces an error. When you add a new email tool, add it to your existing record instead of creating a second one.
- There's a limit of 10 lookups. Each service you add to the record (with an "include") makes the receiving server look up more records, and the standard caps those lookups at 10. Go over and SPF returns an error, so remove services you no longer use.
- The ending matters. A record ending in -all says "anything not listed is not allowed." One ending in ~all (a "softfail") is a weaker "probably not allowed," and the standard says receivers shouldn't reject mail based on a softfail alone.
A simple SPF record looks like this: v=spf1 include:mail.example.net -all
DKIM: the tamper-proof seal
DKIM (DomainKeys Identified Mail) adds a hidden digital signature to every message. The matching public "key" (a long string of characters your email platform gives you) is published in your DNS under a name ending in ._domainkey.yourdomain.com. The receiving server looks up that key and checks the signature.
If the signature checks out, two things are confirmed: the signing domain takes responsibility for the message, and the message wasn't altered on the way. Because the signature travels with the message, it usually survives being passed between servers, although a system that changes the message along the way can break it.
Key length matters a little: Google requires a DKIM key of at least 1024 bits for mail to personal Gmail accounts and recommends 2048 bits. Yahoo also lists 1024 bits as the minimum.
DMARC: the rulebook that ties them together
Here's the catch with SPF and DKIM on their own: both can pass for a domain that's different from the one in the From line. A scammer could pass SPF for their own domain while showing your name to the reader.
DMARC (Domain-based Message Authentication, Reporting and Conformance) closes that gap with alignment. A message passes DMARC only if SPF or DKIM passes and the domain that passed matches the domain in the visible From address.
A DMARC record is published at _dmarc.yourdomain.com and starts with v=DMARC1. It tells receivers what to do with mail that fails, using one of three policies:
- p=none: take no special action, just monitor.
- p=quarantine: treat failing mail as suspicious, for example by putting it in spam.
- p=reject: refuse failing mail.
DMARC also gives you reports. Add an rua address and receiving servers send you regular summary reports of who is sending mail using your domain and whether it passed. They're hard to read raw, so many people use a DMARC report viewer to make sense of them. A starter record might look like: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
One more setting you may see: alignment can be "relaxed" (mail signed by example.com lines up with an address at news.example.com) or "strict" (exact match only). Relaxed is the default. Older guides also mention a pct setting for applying a policy to only part of your mail; the updated DMARC standard published in 2026 (RFC 9989) removed it.
Check a list from $1.49
What Gmail, Yahoo and Outlook.com require
- Every sender to Gmail and Yahoo needs at least SPF or DKIM.
- Bulk senders (Google says close to 5,000 messages or more a day to personal Gmail accounts) need SPF and DKIM, plus a DMARC record of at least p=none, with the From domain aligned to SPF or DKIM.
- Outlook.com requires SPF and DKIM to pass and DMARC of at least p=none, aligned, for domains sending more than 5,000 emails a day to its consumer addresses.
Full details are in our guide to Gmail and Yahoo sender requirements.
A safe order to set them up
- SPF first. List every service that sends mail as you: your mailbox provider, newsletter tool, booking or invoicing software.
- Turn on DKIM for each of those services, using the records they give you.
- Add DMARC at p=none with a reporting address, and watch the reports for a few weeks.
- Fix anything legitimate that fails, such as a forgotten tool sending as your domain.
- Tighten the policy to quarantine, then reject, if you want stronger protection against spoofing. Only move on once your reports show all your legitimate mail passing.
Authentication isn't the whole story
The DMARC standard itself notes that a DMARC pass, on its own, doesn't mean a message is safe or wanted in the inbox. Passing all three proves the mail is yours; it doesn't prove people want it. Spam complaints, bounces and sending to bad addresses still count against you. See why emails go to spam for the rest of the picture.
Frequently asked questions
Do I need SPF, DKIM and DMARC?
Every sender to Gmail and Yahoo needs at least SPF or DKIM. Bulk senders need all three: SPF, DKIM and a DMARC record of at least p=none. Setting up all three is the safer choice even for small senders.
Can I have two SPF records?
No. The SPF standard says multiple SPF records for the same domain are not permitted, and having two causes an error. Combine everything into one record.
What DMARC policy should I start with?
Start with p=none and a reporting address. It takes no action on failing mail, meets the Gmail and Yahoo minimum for bulk senders, and lets you see who is sending as your domain before you tighten it.
Will DMARC get my emails into the inbox?
Not by itself. The DMARC standard notes that a pass on its own doesn't mean a message is safe or wanted in the inbox. It proves the mail is yours; inbox placement still depends on complaints, bounces and list quality.
Sources
- RFC 7208: Sender Policy Framework (SPF)
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC)
- Google: Email sender guidelines
- Yahoo Sender Hub: Sender best practices
- Microsoft Tech Community: Outlook's new requirements for high-volume senders