SPF, DKIM, and DMARC Checklist: Fix Email Authentication in One Pass

SPF, DKIM, and DMARC Checklist: Fix Email Authentication in One Pass

4 min read

spf · dkim · dmarc · email · dns · tools

Authors

PandaONE Team

A practical SPF → DKIM → DMARC checklist for engineers: what each record does, how to verify them, and how email auth ties into broader attack-surface reviews.

Password-reset mail started landing in spam right after a “small” TXT edit. You added a second v=spf1 on the apex. Receivers treat duplicate SPF as permerror — legitimate mail fails alongside spoof attempts.

SPF, DKIM, and DMARC live in DNS. One bad TXT can break delivery overnight. Work through them in order: authorize senders (SPF), sign mail (DKIM), then tell receivers what to do on failure (DMARC).

Quick verify

  1. Open the DMARC / SPF checker.
  2. Enter your apex (for example example.com).
  3. Confirm exactly one usable SPF TXT and that includes stay under the lookup limit.
  4. Confirm DMARC at _dmarc.example.com and that rua / ruf hit a mailbox you read.
  5. Confirm each sending service publishes DKIM for the selector that provider documents.

SPF checklist

CheckPass criteria
One SPF policyExactly one v=spf1 ... TXT on the apex (or the domain that sends mail)
IncludesEvery ESP, MTA, and marketing platform listed via include: or ip4: / ip6:
Soft vs hard failPrefer ~all while onboarding; move to -all only when nothing else sends
Lookup budgetStay under 10 DNS lookups (includes and redirects count)

Typical breaks: duplicate SPF TXT records, a forgotten transactional provider, and include: chains that nest too deep.

DKIM checklist

CheckPass criteria
Selector publishedselector._domainkey.example.com resolves (TXT or CNAME to the vendor)
Signing onProduct, support, and marketing streams all sign
AlignmentDKIM d= aligns with the visible From domain
Key hygieneRotate when vendors ask; delete stale selectors

SPF can fail while DKIM aligns — DMARC may still pass. You want both.

DMARC checklist

CheckPass criteria
Record presentTXT at _dmarc.example.com starting with v=DMARC1
Policy stagedStart p=none; read aggregate reports for days or weeks
Reportingrua= (and optional ruf=) to a monitored mailbox or report service
Alignment modeKnow aspf / adkim (relaxed vs strict) before you tighten
SubdomainsSet sp= when subdomain mail needs a different policy

Jumping to p=quarantine or p=reject without reports is how teams brick billing and password-reset mail.

Order of operations

  1. List every system that sends as @yourdomain (ESP, CRM, helpdesk, CI alerts, workspace mail).
  2. Fix SPF includes and DKIM per source.
  3. Publish DMARC p=none with rua.
  4. Read reports; fix or remove failing sources.
  5. Raise policy: none → quarantine → reject.
  6. Re-run the DMARC / SPF checker after each DNS change.

Subdomains and organizational domains

DMARC on the apex covers the organizational domain. news.example.com that sends on its own needs SPF/DKIM on that subdomain — inventory From domains, not only the corporate apex.

Perfect DMARC on example.com does not stop examp1e.com. Registration hygiene sits beside this DNS work.

Change-management tips

  • Ticket DNS edits; paste pre-change TXT into the ticket
  • Add a new DKIM selector before you retire the old one
  • After ESP migration, drop old include: lines when dual-sending ends
  • Re-check quarterly with the DMARC / SPF checker — forgotten tools accumulate

Email auth is domain hygiene, not a full vulnerability assessment. Spoofed brands, open redirects, and lookalike domains sit outside SPF. For authorized proof on web and email-facing attack surface, AI VAPT only ships findings when impact is demonstrated — not when a scanner labels something informational.

FAQ

Do I need all three?
Receivers increasingly expect all three. SPF or DKIM alone is incomplete; DMARC states policy on failure.

Can I copy a competitor’s SPF?
No. SPF must list your senders. Someone else’s include: lines do not authorize your mail.

Is a green checker enough?
It means DNS looks coherent right now. It does not prove every stream signs or that you are ready for reject.

What does pct do in DMARC?
Applies policy to a percentage of failing mail while you ramp. Use it as a short safety valve — not a substitute for fixing alignment.

Summary

One SPF on the sending domain. DKIM on every production stream. DMARC at p=none with rua before you enforce. Duplicate SPF and policy jumps without reports are the fastest ways to break legitimate mail. Verify after every change with the DMARC / SPF checker.

Featured on ScrollLaunchFeatured on CodeHype