On This Page
- Why Email Authentication Matters
- SPF, DKIM and DMARC at a Glance
- SPF (Sender Policy Framework)
- DKIM (DomainKeys Identified Mail)
- DMARC (Domain-based Message Authentication, Reporting and Conformance)
- How to Set Up SPF, DKIM and DMARC
- How to Check Your Authentication
- Common Authentication Mistakes
- What Is BIMI?
- Authentication for Gmail, Yahoo and Outlook
- Authentication FAQs
Why Email Authentication Matters
Anyone can type any address into the "From" line of an email. Email authentication lets receiving servers check whether a message really came from the domain it claims to come from. Without it, spammers could impersonate your brand, and inbox providers have little reason to trust your emails.
Three standards work together: SPF, DKIM and DMARC. Since 2024, Gmail and Yahoo have required bulk senders to use all three. Even small senders benefit, because authenticated mail is more likely to reach the inbox. For the wider picture, see our email deliverability guide.
SPF, DKIM and DMARC at a Glance
| Standard | What It Does | Analogy | Where It Lives |
|---|---|---|---|
| SPF | Lists the servers allowed to send email for your domain | A guest list at the door | A DNS TXT record |
| DKIM | Adds a digital signature proving the email was not altered and was authorized by your domain | A tamper-proof wax seal | A DNS TXT or CNAME record with a public key |
| DMARC | Tells receivers what to do if SPF or DKIM fail and alignment does not match, and sends you reports | The house rules for the doorman | A DNS TXT record at _dmarc.yourdomain.com |
SPF (Sender Policy Framework)
SPF is a DNS record that lists which servers and services are allowed to send email using your domain. When an email arrives, the receiving server checks whether the sending server is on that list.
An SPF record looks something like v=spf1 include:_spf.example.com ~all. Each "include" authorizes a sending service. You should have only one SPF record per domain, combining all your senders.
Common SPF Mistakes
- Creating two SPF records instead of one combined record.
- Exceeding the limit of DNS lookups by adding too many includes.
- Forgetting to add a new email service after switching platforms.
DKIM (DomainKeys Identified Mail)
DKIM adds a cryptographic signature to every email you send. Your email platform signs messages with a private key, and you publish the matching public key in your DNS. Receiving servers use it to confirm that the email was authorized by your domain and was not changed in transit.
Most email marketing platforms provide the exact DKIM records to add, often as CNAME records that point to keys the platform manages.
DMARC (Domain-based Message Authentication, Reporting and Conformance)
DMARC builds on SPF and DKIM. It checks that the domain in your visible From address aligns with the domain authenticated by SPF or DKIM, and it tells receiving servers what to do with emails that fail: nothing (p=none), send to spam (p=quarantine) or reject (p=reject). It can also send you reports showing who is sending email using your domain.
| DMARC Policy | What Happens to Failing Email | When to Use |
|---|---|---|
| p=none | Delivered normally; you receive reports | Starting out and monitoring |
| p=quarantine | Treated as suspicious, often sent to spam | Once legitimate senders are authenticated |
| p=reject | Rejected outright | Strongest protection once fully confident |
Gmail and Yahoo require bulk senders to publish a DMARC record; a policy of p=none meets the minimum.
Authentication Without the Headache
AWeber walks you through connecting your domain, and its 24/7 support team can help.
Our #1 Autoresponder PickOn a tighter budget? See Moosend, our #2 pickHow to Set Up SPF, DKIM and DMARC
- List every service that sends email for your domain: your email marketing platform, your inbox provider, your store or CRM.
- Get the records from your email platform. Look for "domain authentication" or "sender authentication" in its settings.
- Log in to your DNS provider (for example, Cloudflare or your domain registrar).
- Add or update your SPF record so it includes all your senders in a single record.
- Add the DKIM records exactly as provided.
- Publish a DMARC record, starting with
v=DMARC1; p=none; rua=mailto:[email protected]. - Verify in your email platform that authentication passes.
- Review DMARC reports over time, then consider moving to quarantine or reject.
DNS changes can take time to propagate. If verification fails, wait and recheck, and confirm there are no typos or duplicate records.
How to Check Your Authentication
- Use your email platform's domain verification status.
- Send a test email to a Gmail account, open it, and choose "Show original" to see SPF, DKIM and DMARC results.
- Use a DNS lookup tool to confirm the records are published correctly.
Common Authentication Mistakes
| Mistake | What Happens | Fix |
|---|---|---|
| Two separate SPF records | SPF fails, because a domain may publish only one | Merge all senders into a single SPF record |
| Too many DNS lookups in SPF | SPF evaluation stops after 10 lookups and returns an error | Remove unused services; avoid nesting many includes |
| Forgetting a sending service | Emails from that tool (for example, your help desk) fail | List every service that sends as your domain |
| DKIM record copied with line breaks | Signature cannot be verified | Paste the key exactly as your platform provides it |
| Jumping straight to p=reject | Legitimate mail from a forgotten service is blocked | Start at p=none, read reports, then tighten |
| Sending from a free mailbox address | From domains such as gmail.com cannot be authenticated by you | Send from your own domain |
What Is BIMI?
BIMI (Brand Indicators for Message Identification) lets supporting inboxes display your logo next to authenticated emails. It builds on DMARC: your domain needs a DMARC policy of quarantine or reject, plus a correctly formatted logo file, and some inboxes, including Gmail, also require a verified mark certificate. BIMI is optional and mainly useful for established brands; get SPF, DKIM and DMARC working first.
Authentication for Gmail, Yahoo and Outlook
All three major consumer inbox providers now expect bulk senders to authenticate. Gmail and Yahoo require SPF, DKIM and a DMARC record for senders of roughly 5,000 or more messages a day, and Microsoft has required the same from senders of 5,000 or more daily emails to Outlook, Hotmail and Live addresses since May 2025. Details are in our Gmail and Yahoo sender requirements guide.
Authentication FAQs
Do I Need SPF, DKIM and DMARC?
Yes, if you send marketing email. Gmail and Yahoo require all three for bulk senders, and they help every sender's deliverability.
What Is the Difference Between SPF and DKIM?
SPF checks whether the sending server is authorized for your domain. DKIM checks a digital signature to confirm the email was authorized and not altered.
Which DMARC Policy Is Best to Start?
Start with p=none to collect reports without affecting delivery, then move to quarantine or reject once all legitimate senders pass.
Can I Have More Than One SPF Record?
No. A domain should have a single SPF record that includes all authorized senders.
Authenticate Your Domain the Easy Way
AWeber guides you through domain authentication and offers 24/7 support if you get stuck.
Our #1 Autoresponder Pick