SPF, DKIM, and DMARC Setup: Email Authentication DNS Checklist
SPFDKIMDMARCemail securityDNSdomain authentication

SPF, DKIM, and DMARC Setup: Email Authentication DNS Checklist

TTheHost Cloud Editorial Team
2026-11-16
6 min read

Use this practical SPF, DKIM, and DMARC DNS checklist to authenticate email, handle multiple senders, validate changes, and troubleshoot failures.

SPF, DKIM, and DMARC work together to authenticate messages sent from your domain and make suspicious mail easier to identify. This reusable DNS checklist explains what each record does, how to plan records for multiple senders, how to validate changes, and what to revisit when your email tools or workflows change.

Overview

Email authentication is configured through DNS, but each standard answers a different question. SPF identifies which servers are permitted to send mail for your domain. DKIM adds a cryptographic signature to outgoing messages so a receiving system can check that the message was authorized and not altered in transit. DMARC tells receiving systems how to evaluate SPF and DKIM together, where to send aggregate or forensic-style reports when supported, and what to do when a message fails alignment.

RecordPrimary purposeDNS typeKey planning point
SPFLists authorized sending sourcesTXTPublish one SPF policy per domain and keep every legitimate sender represented.
DKIMVerifies a message signatureTXT or CNAME, depending on providerUse the exact selector and record value supplied by the sending platform.
DMARCDefines handling and reporting for authentication failuresTXTStart with a deliberate monitoring or enforcement plan and verify alignment.

These records do not replace one another. An SPF record alone does not sign messages, and DKIM alone does not provide a policy for messages that fail authentication. Before editing DNS, create an inventory of every system that sends mail using your domain: business mail, website forms, transactional email, newsletters, support platforms, monitoring tools, and applications.

For background on TXT, MX, CNAME, and other DNS record types, see DNS Records Explained: A Practical Guide.

Checklist by scenario

1. One primary mailbox provider

  1. Confirm which platform handles mailboxes and which platforms send automated messages.
  2. Copy the provider's SPF mechanism or include value exactly as documented.
  3. Enable DKIM in the provider's administration area and note the selector and required DNS value.
  4. Publish a DMARC TXT record at _dmarc.example.com, replacing the domain with yours.
  5. Begin with a policy that lets you monitor results while you confirm that legitimate traffic passes.
  6. Send test messages to accounts on more than one receiving service and inspect the authentication results.

2. Multiple sending platforms

  1. List each sender and its purpose, owner, sending domain, and required SPF or DKIM configuration.
  2. Combine authorized SPF sources into one record rather than publishing separate SPF records.
  3. Enable DKIM for each platform where possible. Selectors should distinguish one signing service from another.
  4. Check that the visible From domain aligns with the domain authenticated by SPF or DKIM. A message can pass one technical check while failing DMARC alignment.
  5. Use DMARC reports to find forgotten tools, retired services, or unexpected senders before tightening enforcement.

3. Website forms and application mail

  1. Identify whether the website sends directly from the hosting server or relays through an email provider.
  2. Avoid using a personal mailbox address as the technical sender for automated forms. Use an address on the site’s domain and configure a suitable reply-to address.
  3. Configure the application or relay to use DKIM if the provider supports it.
  4. Confirm that contact-form messages still reach the intended mailbox after DNS and mail changes.
  5. Review the site’s SPF requirement whenever hosting, transactional email, or form software changes.

4. Forwarding and mailing lists

Forwarding can complicate SPF because the receiving system may see the forwarder rather than the original authorized sender. DKIM may survive forwarding if the message is not altered, but modifications can invalidate a signature. If forwarded messages fail, compare the authentication results, examine DMARC reports, and review whether the list or forwarding service supports mechanisms intended to preserve authentication. Do not weaken the entire domain policy to solve one unexamined forwarding path.

5. Domain migration or registrar change

Before transferring a domain or changing DNS hosting, export or document the current SPF, DKIM, and DMARC records. Confirm that the new DNS provider contains the same records and that nameservers are delegated correctly. A domain transfer does not automatically guarantee that DNS records follow the domain. The domain transfer checklist can help you plan the DNS portion of the change.

What to double-check

SPF

  • There is only one TXT record intended to serve as the domain’s SPF policy.
  • Every legitimate sender is included, including less visible systems such as invoicing, support, and application alerts.
  • Provider-specific include values are copied exactly and removed when the service is retired.
  • The record does not contain accidental line breaks, duplicate mechanisms, or an old provider that no longer sends mail.

A generic SPF structure may look like v=spf1 include:sender.example ~all, but the correct include value and final mechanism depend on your provider and policy. Treat examples as syntax illustrations, not values to copy without verification.

DKIM

  • The selector in the DNS hostname matches the selector configured by the sending platform.
  • The public key is placed at the required selector hostname, often in a TXT or CNAME record.
  • The private key remains inside the sending platform or application and is never published in DNS.
  • Each active sender signs with the intended domain rather than an unrelated provider domain.

DMARC

  • The record is published at _dmarc for the correct domain.
  • The policy, alignment mode, and reporting addresses reflect an approved plan.
  • Report recipients are monitored and authorized to receive reports where required by the receiving system.
  • Subdomain behavior is considered separately when the organization uses subdomains for campaigns, applications, or regional sites.

A monitoring-oriented DMARC record might use a policy such as p=none while results are reviewed. Enforcement options such as quarantine or reject should be introduced only after legitimate senders are identified and aligned. The right progression depends on your mail flow, risk tolerance, and ability to analyze reports.

Validation workflow

  1. Lower the DNS record time to live only if your change process requires faster rollback; record the previous values first.
  2. Publish the records through the authoritative DNS control panel, not merely in a hosting panel that does not manage the domain’s nameservers.
  3. Use a DNS lookup tool to confirm that public resolvers return the intended values.
  4. Send controlled test messages from each known platform.
  5. Inspect message headers for SPF, DKIM, and DMARC results, including the authenticated domains and alignment details.
  6. Review aggregate reports over time and update the sender inventory before changing policy.

Common mistakes

  • Publishing two SPF records: Merge authorized mechanisms into one SPF TXT record instead of adding another.
  • Copying a DKIM key incorrectly: Preserve the complete value supplied by the provider and avoid adding spaces or punctuation.
  • Using the wrong DNS zone: Check the domain’s active nameservers before editing records.
  • Enforcing DMARC too quickly: A strict policy can affect legitimate messages from an overlooked sender or forwarding path.
  • Ignoring alignment: Passing SPF for a provider domain is not always enough; the authenticated domain must align with the visible From domain for DMARC.
  • Leaving retired senders active: Remove obsolete SPF includes and DKIM entries according to the provider’s removal guidance.
  • Failing to monitor reports: A reporting address is useful only when someone reviews the results and can investigate anomalies.

When to revisit

Keep this checklist with your domain and DNS change records. Revisit it before seasonal planning cycles, before a major campaign, and whenever workflows or tools change. It is especially useful after adding a newsletter service, replacing a help-desk platform, moving website hosting, changing mailbox providers, launching a new subdomain, or transferring DNS management.

Schedule a periodic review of the sender inventory, SPF contents, DKIM selectors, DMARC reports, and DNS ownership. During the review, ask four practical questions: Which systems currently send mail? Does each sender pass SPF or DKIM with correct alignment? Are any reports showing an unknown source? Is the current DMARC policy still appropriate?

Make one controlled change at a time, preserve the previous records, and allow enough observation time for reports and test messages to reflect the change. If email delivery problems appear, temporarily return to the last known-good configuration while you isolate the affected sender. Email authentication is part of broader domain security and DNS management; pair this review with your website launch, domain transfer, and hosting change procedures.

Related Topics

#SPF#DKIM#DMARC#email security#DNS#domain authentication
T

TheHost Cloud Editorial Team

Technical 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.