A practical authentication checklist for SPF authorization, DKIM signatures and DMARC alignment.
SPF, DKIM and DMARC solve different parts of email authentication. Passing one does not replace the others, and syntactically valid records may still fail alignment.
Why spf dkim dmarc checklist matters
SPF, DKIM and DMARC solve different parts of email authentication. Passing one does not replace the others, and syntactically valid records may still fail alignment.
Good sending performance comes from several systems working together: a legitimate sender identity, correctly aligned authentication, a reliable connection, controlled volume, relevant recipients and fast action when warning signs appear. This guide is designed to help you review those areas in a logical order instead of changing settings randomly.
Step-by-step process
- Confirm there is only one SPF TXT record — complete this check and record the result before moving to the next stage.
- Authorize every legitimate sending source — complete this check and record the result before moving to the next stage.
- Keep SPF lookup count within protocol limits — complete this check and record the result before moving to the next stage.
- Enable DKIM signing with the correct selector — complete this check and record the result before moving to the next stage.
- Verify the public DKIM key is reachable — complete this check and record the result before moving to the next stage.
- Publish a DMARC record at _dmarc — complete this check and record the result before moving to the next stage.
- Confirm SPF or DKIM aligns with the From domain — complete this check and record the result before moving to the next stage.
- Monitor reports before increasing enforcement — complete this check and record the result before moving to the next stage.
Before you begin
Make sure you control the domain, can edit DNS, can access the sending mailbox or SMTP account, and know which service actually sends the message. Keep a copy of current records before changing anything.
Before you scale
Confirm that authentication passes on real messages, connection errors are resolved, bounces are understood and sending volume is stable. Scale in measured steps rather than moving directly to a provider maximum.
- Identify one measurable problem.
- Change the smallest relevant setting or behaviour.
- Allow enough time for DNS or provider data to update.
- Retest using the same method.
- Keep the change only when the evidence improves.
Use a controlled improvement cycle
Record the date of each test, the domain or mailbox tested, the sending provider and the exact result. This creates a useful baseline for future troubleshooting. When performance changes, compare the new data with the last known-good configuration instead of replacing several records or providers at once.
A single passing check should not be treated as final proof that the entire sending setup is healthy. Authentication results, SMTP responses and reputation indicators should be reviewed together and compared over time. For example, SPF may pass while DKIM is missing, or an SMTP connection may succeed while the chosen From address is not authorized to relay.
How to interpret the results
Read an authentication result without guessing
A DNS record checker confirms what a domain publishes; it does not prove that a specific message authenticated. To investigate a real delivery, send a permitted test message to a mailbox you control, open its original headers, and locate the receiving system's Authentication-Results field. Interpret the results for that message, not just the domain's published records.
SPF asks whether the connecting server is authorized for the envelope sender domain. DKIM asks whether a valid signature covers the message. DMARC asks whether at least one passing SPF or DKIM identity aligns with the visible From domain. A pass on SPF alone is not necessarily a DMARC pass.
Example: SPF passes but DMARC fails
Suppose the visible From address is news@example.com, the envelope sender is bounce@mailer.example.net, and the DKIM signature uses d=example.net. The receiver may report spf=pass for mailer.example.net and dkim=pass for example.net, while dmarc=fail for example.com. The individual mechanisms passed, but neither authenticated domain aligned with the visible From domain.
To fix this, configure your authorized sending service to use an aligned envelope sender or sign with an aligned DKIM domain, then send another test. Do not weaken your DMARC policy merely to hide an alignment problem. Relaxed alignment generally permits subdomains of the same organizational domain; it does not make unrelated domains equivalent.
Decision checklist for the next test
- SPF fails: Check the actual envelope sender domain and the connecting IP. Confirm the sender is legitimately authorized; update the existing SPF record rather than publishing a second SPF record.
- DKIM fails: Compare the signature's
d=domain ands=selector with the published key. Investigate broken keys, wrong selectors, and message changes after signing. - DMARC fails while SPF or DKIM passes: Compare the authenticated domain with the visible From domain. Correct alignment and retest.
- All three pass but messages land in spam: Review recipient consent, complaint and bounce patterns, content, sending consistency and provider-specific reputation signals. Authentication is necessary but does not guarantee inbox placement.
For a broader diagnosis, read why accepted messages may not reach the inbox and common reasons outreach is filtered as spam. Use the SPF checker, DKIM checker and DMARC checker to review published records before comparing them with a real message header.
What to monitor after setup
Continue reviewing the following signals after the initial configuration. A correct setup can still deteriorate when passwords change, DNS is edited, contact quality drops or campaign volume increases too quickly.
- SPF, DKIM and DMARC results on real sent messages
- SMTP rejection, deferral and authentication responses
- Hard bounces, repeated soft bounces and invalid recipients
- Complaint and unsubscribe trends
- Changes in hourly and daily sending volume
- Provider-specific feedback and reputation data where available
- Meaningful replies and recipient engagement, not only open tracking
Common mistakes to avoid
- Creating separate SPF records for each provider
- Copying DKIM values from another domain
- Publishing DMARC at the root instead of _dmarc
- Using p=reject before all legitimate sources are aligned
- Assuming a green syntax check proves real messages pass
A practical SPF, DKIM and DMARC verification walkthrough
DNS records describe what your domain authorizes, but the message headers reveal what the receiving provider actually checked. Use both views. Before changing anything, list every system that sends mail using your domain: your business mailbox, transactional email service, CRM, support desk, newsletter platform and any approved SMTP relay. Record the visible From domain and the return-path domain for each service.
1. Check SPF authorization without creating duplicates
Look up TXT records at the domain used by the SMTP envelope sender (also called the return path or MAIL FROM domain). An SPF record begins with v=spf1. Keep only one SPF record per hostname: adding a second record can cause a permanent SPF error. When a legitimate provider requires an include: mechanism, merge it into the existing record after checking the provider's instructions and the DNS lookup budget. SPF evaluation has a limit of ten DNS-querying mechanisms or modifiers; exceeding it can produce a permerror.
Example only, not a record to copy into production: v=spf1 include:_spf.example.net -all. Replace the illustrative include with the exact value supplied by your authorized sending provider. A hostname used for the visible From address may differ from the SPF-authenticated return-path hostname.
2. Verify DKIM on an actual message
In your sending platform, find the DKIM selector and public-key DNS record. The TXT hostname typically follows selector._domainkey.example.com, although providers may use CNAME delegation instead. After DNS propagation, send a message to a mailbox you control. Open its original message or full headers and check for a DKIM-Signature and a dkim=pass result in Authentication-Results. Confirm that the signing domain (d=) aligns with the visible From domain if you expect DKIM to satisfy DMARC. Merely finding a DKIM DNS record does not prove the message was signed correctly.
3. Roll out DMARC deliberately
Publish a DMARC TXT record at _dmarc.example.com. For a first inventory, a monitoring policy such as v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com can help you discover which services are authenticating and aligning. The reporting address must be controlled by your organization; replace the example address and follow any external-reporting authorization requirements. DMARC passes when at least one of SPF or DKIM both passes authentication and aligns with the visible From domain. It does not require both to pass.
Review aggregate reports and representative real-message headers before moving to p=quarantine or p=reject. A stricter policy can disrupt legitimate traffic from a forgotten service, forwarding arrangement or third-party sender. DMARC alignment can be relaxed or strict depending on aspf and adkim; the defaults are relaxed.
4. Record evidence before increasing volume
- DNS evidence: hostname, record type, returned value and timestamp for SPF, DKIM and DMARC.
- Message evidence: visible From, return path, DKIM signing domain and the receiver's SPF, DKIM and DMARC results.
- Delivery evidence: accepted versus rejected SMTP messages, bounces, complaints and any provider feedback available to your account.
- Change log: who edited DNS, what changed, when it propagated and which test passed afterward.
If SPF passes but DMARC fails, inspect whether the SPF-authenticated return-path domain aligns with the From domain; then inspect DKIM signing and alignment. If DKIM fails, verify the selector, key and whether an intermediate system modified the signed message. If authentication passes but mail still lands in spam, investigate complaint rates, list consent, content, volume changes and sending history rather than repeatedly editing DNS.
Next step: run the SPF checker, DKIM checker and DMARC checker, then validate with a real test message. These checks are diagnostic aids, not guarantees of inbox placement.
Useful tools for this guide
Related Inbox Warmup solutions
Frequently asked questions
Do I need all three?
For modern business sending, using SPF, DKIM and DMARC together provides stronger authentication and reporting.
Can SPF pass while DMARC fails?
Yes. SPF may authenticate a return-path domain that does not align with the visible From domain.
How do I verify DKIM?
Send a controlled message and inspect the DKIM signature and authentication results, not only the DNS record.
Recommended next step
Use the checks above to document the current state of your domain and mailbox. Fix authentication and connection errors first, then begin controlled warmup and monitor real results before increasing campaign volume.