SPF, DKIM, and DMARC Setup Guide: Email Authentication Records and Ongoing Deliverability Audits
DNSemail-authenticationSPFDKIMDMARCdeliverability

SPF, DKIM, and DMARC Setup Guide: Email Authentication Records and Ongoing Deliverability Audits

wwhata.cloud Editorial Team
2026-11-20
7 min read

A practical SPF, DKIM, and DMARC setup checklist covering DNS records, multiple senders, key rotation, reports, and recurring audits.

SPF, DKIM, and DMARC work together to show receiving mail systems that your domain is authorized to send email. This provider-neutral checklist explains how to plan the records, publish them through DNS management, test alignment, interpret reports, and keep authentication accurate when your sending tools change.

Overview

Email authentication is a DNS and domain-management task, not a single switch in your mailbox settings. SPF identifies approved sending infrastructure, DKIM adds a cryptographic signature to messages, and DMARC tells receiving systems what to do when a message does not authenticate or does not align with your domain.

  • SPF (Sender Policy Framework): A TXT record that lists the services allowed to send mail for your domain. A receiving system checks the sending server against that policy.
  • DKIM (DomainKeys Identified Mail): A sending service signs outgoing messages with a private key. The matching public key is published in DNS at a selector-based hostname.
  • DMARC (Domain-based Message Authentication, Reporting, and Conformance): A TXT record that defines a handling policy and can request aggregate or failure reports. It also requires alignment between the visible From domain and an authenticated domain.

Authentication does not replace good list hygiene, accurate mail configuration, or monitoring. It does, however, give your organization a controlled way to document legitimate senders and investigate unauthorized use of a domain.

DNS record reference

RecordTypical hostPurposeWhat to confirm
SPF@ or the sending subdomainAuthorizes sending servicesThere is one effective SPF record and every legitimate sender is represented.
DKIMselector._domainkeyPublishes a public signing keyThe selector and key match the sending provider's configuration.
DMARC_dmarcSets policy and reporting instructionsThe policy, alignment mode, and reporting destinations match your rollout plan.

Record names vary slightly between DNS control panels. Follow the panel's host-field convention, and do not assume that entering the full domain name is correct when the panel automatically appends the zone name.

Checklist by scenario

Before adding a new sender

  1. List every system that sends mail using the domain or one of its subdomains. Include employee mail, transactional application mail, support tools, marketing platforms, contact forms, monitoring systems, and development environments that can reach external recipients.
  2. Record the visible From domain, envelope or return-path domain, DKIM signing domain, and the provider's required DNS records. These domains may differ, so document each one rather than copying a record from another service.
  3. Decide whether the service should send from your primary domain or a dedicated subdomain. A separate subdomain can make ownership and troubleshooting clearer, but it still requires deliberate DNS and monitoring.
  4. Confirm that the service supports DKIM and DMARC alignment. If it supplies SPF instructions, determine whether it expects an include:, an IP address, or another mechanism.
  5. Set a change owner and keep a record of the provider, selector, purpose, date added, and removal procedure.

SPF planning for multiple email services

Start with one inventory, then build one policy for each domain that actually sends mail. Do not publish a separate SPF TXT record for every provider at the same hostname. Multiple SPF records can create an invalid or unpredictable result. Instead, combine the authorized mechanisms into a single record, using the syntax supplied by each provider.

A planning template might look like this:

v=spf1 include:mail-service.example include:transactional-service.example ~all

This is only a planning example. Replace the mechanisms with the values documented by your sending services, and choose the final policy qualifier after testing. Remove services that no longer send mail. Review nested lookups and provider guidance when the list grows, because SPF evaluation has operational limits and a long chain of includes can become difficult to maintain.

After publishing, verify that the record is visible publicly and that it contains no accidental line breaks, quotation marks copied from a documentation page, or unrelated mechanisms. Never create an SPF record for a service solely because it appears in an old setup note; confirm that the service is still active and authorized.

DKIM setup and key rotation

  1. Generate or request a DKIM key pair through the sending service. Keep the private key inside that service or your controlled secret-management process; it belongs in DNS only as a public key.
  2. Publish the TXT or CNAME record at the exact selector hostname supplied by the provider. A selector is part of the DKIM identity, so a copied selector or missing subdomain can cause verification to fail.
  3. Enable signing in the provider's dashboard only after the DNS record is available, if the provider requires that order.
  4. Send a test message to a mailbox you control and inspect the authentication results. Confirm that DKIM passes and that the signing domain aligns with the visible From domain under your DMARC plan.
  5. For rotation, publish the new selector before retiring the old one. Keep the old public key available while messages signed with it could still be processed, then remove it after the provider's documented transition window.

DMARC rollout

Begin by publishing a monitoring policy so you can see which systems send mail and whether SPF or DKIM aligns. A generic structure is:

v=DMARC1; p=none; rua=mailto:[email protected]

Use a mailbox or reporting service intended for aggregate reports rather than a normal employee inbox if the volume is substantial. Confirm that the reporting address is monitored and that access to reports is restricted appropriately. Once legitimate senders pass consistently and unauthorized sources are understood, consider a staged move toward a stricter policy, such as quarantine or reject, according to your organization's risk tolerance and operational evidence.

Do not treat a passing SPF result alone as proof that DMARC passes. DMARC also evaluates alignment. A message can pass SPF for a return-path domain while failing to align with the visible From domain. DKIM can provide alignment when SPF does not, so configure and test both paths where possible.

What to double-check

  • Authoritative DNS: Make changes at the DNS provider serving the domain's active nameservers. A record added at a registrar or an old provider may have no effect.
  • Host formatting: Check whether the DNS interface expects _dmarc, selector._domainkey, or a fully qualified name. Search for duplicate records at the same name.
  • Propagation and caching: Allow for DNS caching and the record's TTL. Test from more than one resolver when a change seems inconsistent.
  • Subdomains: Decide whether a subdomain inherits the organizational DMARC policy or has its own record. Document exceptions for application, marketing, or regional sending domains.
  • Third-party reporting: Verify that reporting destinations are trusted, valid, and able to receive the expected format. Avoid placing sensitive report addresses in public documentation.
  • Message identity: Inspect the actual From, Return-Path, and DKIM signing domains in a delivered message. Configuration screens do not always show the identity recipients see.
  • Operational ownership: Keep a current inventory of records, vendors, selectors, and renewal or contract owners. DNS management becomes fragile when nobody knows why a record exists.

For a broader DNS inventory, compare this process with a DNS records cheat sheet and editable zone-file template. If DNS changes are part of a larger move, use an authoritative DNS provider migration checklist before switching nameservers.

Common mistakes

  • Publishing two SPF records: Consolidate authorized mechanisms into one policy at a hostname instead of adding a new TXT record for each vendor.
  • Leaving former senders authorized: Remove old platforms after confirming that no application, alias, or automated workflow still uses them.
  • Copying DKIM records between environments: Selectors and keys are provider- and environment-specific. Use the exact values for the account that sends the message.
  • Moving directly to a strict DMARC policy: A strict policy without an inventory can affect legitimate mail. Monitor first, correct alignment, and stage enforcement.
  • Ignoring forwarded or automated mail: Forwarding and intermediary services can change authentication results. Investigate patterns in reports rather than assuming every failure is domain abuse.
  • Testing only the website domain: Email authentication applies to the domain identities used by mail. A working website, SSL certificate, or MX record does not prove SPF, DKIM, or DMARC is correct.

When to revisit

Make email authentication part of routine domain operations rather than a one-time launch task. Revisit the records before seasonal planning cycles, before a major campaign, and whenever a provider, application, mailbox platform, or DNS host changes. Also review them after a domain transfer, nameserver change, cloud migration, or security incident.

Recurring email-authentication audit checklist

  1. Export or review the current DNS records for SPF, DKIM, DMARC, MX, and relevant sending subdomains.
  2. Compare every authorized sender with an active business owner and current contract or configuration.
  3. Review DMARC aggregate reports for new sources, repeated alignment failures, unexpected geographies, and volume changes.
  4. Check that DKIM selectors are documented and that retired selectors can be removed safely after key rotation.
  5. Send controlled test messages and inspect authentication results from the receiving mailbox.
  6. Confirm that monitoring addresses, report-processing tools, and escalation contacts still work.
  7. Record the review date, findings, changes, and next review trigger.

Keep this checklist with your domain inventory and website launch documentation. For related operations, see the website launch checklist and the domain transfer checklist. The goal is not to collect records for their own sake; it is to ensure that every legitimate sender remains identifiable, every change has an owner, and authentication evidence informs the next DNS decision.

Related Topics

#DNS#email-authentication#SPF#DKIM#DMARC#deliverability
w

whata.cloud Editorial Team

Technical SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.