SPF, DKIM, and DMARC Setup Guide for Business Email Domains
DNSbusiness emailSPFDKIMDMARCemail security

SPF, DKIM, and DMARC Setup Guide for Business Email Domains

TTopDomains Editorial Team
2026-11-15
7 min read

Configure SPF, DKIM, and DMARC with a provider-neutral checklist for testing business email and safely strengthening domain security.

SPF, DKIM, and DMARC work together to show receiving mail systems that your business email is authorized and has not been altered or impersonated. This practical checklist explains how to configure each control, test the result, and move from monitoring to enforcement without accidentally disrupting legitimate mail.

Overview

Email authentication is managed through DNS, usually at the registrar, DNS host, or provider that is authoritative for your domain. The three controls have different jobs:

  • SPF identifies the servers and services allowed 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 was not changed in transit.
  • DMARC tells receiving systems what to do when a message fails authentication checks and can send reports about those results.

Authentication is not the same as guaranteed inbox placement. Delivery also depends on message content, recipient engagement, sending practices, reputation, and the receiving provider's own controls. The purpose of this setup is narrower and important: reduce unauthorized use of your domain and create a process for finding legitimate senders that have not been configured correctly.

Before editing DNS, make an inventory of every system that sends as your domain. Include employee mailboxes, website forms, customer support platforms, marketing tools, invoicing systems, appointment software, CRM notifications, and any application that sends from a server or cloud service. If you manage several domains, record them separately. A domain portfolio audit can help identify domains that are active, unused, or still connected to old services: Domain Portfolio Audit Checklist.

Checklist by scenario

1. Preparing a new business email domain

  1. Confirm DNS access. Identify where the domain's nameservers point and confirm that you can create TXT and, where required, CNAME records. The registrar and hosting provider may be different companies, so do not assume the website host controls DNS.
  2. List approved senders. Ask each mail and application provider for its current SPF include, DKIM selector and record value, or equivalent setup instructions. Use provider documentation rather than guessing record contents.
  3. Publish SPF. Create one SPF TXT record at the root of the domain. A simplified example is v=spf1 include:mail.example-provider.test -all. This is only a format example; replace the include with an authorized service and add any other legitimate senders required by your environment.
  4. Enable DKIM. Generate or obtain a DKIM key through each sending provider. The provider normally supplies a selector, such as selector1, and a DNS record. The record may be a TXT record or a CNAME that points to the provider's key. Add it exactly as supplied.
  5. Start DMARC in monitoring mode. Publish a DMARC TXT record at _dmarc.example.com. A basic example is v=DMARC1; p=none; rua=mailto:[email protected]. Use a mailbox or reporting destination that your organization can monitor.

2. Adding a new sending platform

Do not change DMARC policy first. Record the new platform's sending domains, envelope-from domains, SPF requirements, DKIM selector, and alignment behavior. Then:

  • Add the platform's authorized sender to your SPF design, if it uses SPF for your domain.
  • Publish the platform's DKIM record and confirm that signing is enabled.
  • Send a controlled test to a mailbox you can inspect.
  • Check the received message headers for SPF, DKIM, and DMARC results.
  • Review DMARC reports after the platform has sent representative messages.

Keep a change log with the provider name, DNS record, owner, date added, and removal instructions. This makes future provider changes and incident review easier.

3. Moving email providers

Keep the old provider authorized until you are confident that it no longer sends mail. Removing an SPF mechanism or DKIM record too early can cause legitimate messages to fail. During the transition, verify forwarding, aliases, shared mailboxes, automated notifications, and applications that may use the old SMTP credentials. After the migration, remove obsolete records and access, then continue monitoring for unexpected traffic.

4. Moving toward enforcement

DMARC policyPurposeSuitable use
p=noneRequests reporting without asking the receiver to reject or quarantine failing mail.Initial monitoring and discovery.
p=quarantineAsks the receiver to treat failing messages as suspicious.Staged enforcement after legitimate senders are identified.
p=rejectAsks the receiver to reject messages that fail the DMARC requirements.Stronger enforcement when authentication coverage is understood.

Policy handling depends on the receiving system, and a published request is not a guarantee of identical behavior everywhere. Move gradually: monitor, correct legitimate failures, apply a limited enforcement policy where appropriate, review results, and only then consider broader enforcement.

What to double-check

SPF record design

  • There should be one SPF policy for a domain. Multiple separate SPF records can create an invalid or ambiguous configuration.
  • Include every legitimate sending service, but remove services that are no longer used.
  • Do not copy a provider's SPF value into a second record without understanding how it combines with existing authorization.
  • Check that the SPF record is published at the correct hostname. For the main domain, this is commonly the root or host field represented as @ in a DNS dashboard.

DKIM records and alignment

  • Confirm the selector and hostname. DKIM records are normally published under a selector-specific name such as selector1._domainkey.example.com.
  • Copy long TXT values carefully. Unintended spaces, quotation marks, line breaks, or missing characters can invalidate a key.
  • Confirm that the visible From domain is aligned with the authenticated domain used by the provider. A valid DKIM signature alone may not satisfy DMARC if the domains do not align under the provider's configuration.

DMARC reporting

  • Use a monitored reporting address and make sure the responsible person can interpret or process reports.
  • Decide how long reports should be retained and who investigates unfamiliar senders.
  • Protect reporting mailboxes from overflowing or exposing information unnecessarily. Reports may contain technical details about sending activity.
  • Check the complete syntax before publishing. Semicolons separate DMARC tags, and unsupported or misspelled tags may be ignored.

For a broader explanation of TXT, CNAME, MX, and other records, see DNS Records Explained. DNS changes may not appear everywhere immediately, so use a DNS lookup tool or propagation checker and test from more than one network when troubleshooting.

Common mistakes

  • Authorizing only the mailbox provider. A website, CRM, help desk, or accounting system may also send mail and needs its own approved authentication path.
  • Publishing multiple SPF records. Consolidate authorized mechanisms into a single policy instead of adding a new SPF TXT record for every vendor.
  • Turning on reject immediately. Unknown applications, forwarding paths, and regional systems may not be visible until reports are reviewed.
  • Assuming DNS and hosting are the same. The company hosting your website may not control the DNS zone where email records belong. The registrar-versus-hosting decision matrix explains how these responsibilities can be separated: Registrar vs Hosting Provider.
  • Ignoring third-party changes. A vendor may change its sending domain, DKIM selector, or setup instructions. Assign an owner to review authentication whenever a service is added or changed.
  • Testing only the website. A working site and valid SSL certificate do not prove that business email is authenticated. Test actual messages from each important sender.

A useful test message should answer four questions: Did SPF pass? Did DKIM pass? Did DMARC pass? Which domain was authenticated and was it aligned with the visible From address? Inspect the message's authentication-results headers, compare them with the provider's dashboard, and record the result. If results conflict, check the exact DNS zone being queried and whether an old record remains at another DNS provider.

When to revisit

Use this checklist before seasonal planning cycles, during security reviews, and whenever workflows or tools change. Revisit the configuration when you:

  • launch a new domain, brand, subdomain, or regional mail stream;
  • add or replace a marketing, CRM, support, payroll, invoicing, or website form platform;
  • change mailbox providers, DNS providers, nameservers, or domain ownership;
  • receive reports showing unfamiliar sources or a rise in authentication failures;
  • see legitimate mail routed to spam or rejected after a DNS change;
  • prepare to move from monitoring to quarantine or reject;
  • review old domains and discover that they still forward or send mail.

At each review, compare the sender inventory with SPF, DKIM, and DMARC records; test representative messages; remove obsolete authorization; and confirm that someone owns report review. Provider-specific record formats and recommendations can change, so check the relevant documentation before copying a new value. A technical review every six months is a practical baseline, with an additional review after any major mail-platform or DNS change. For related domain hygiene, see the Domain Renewal Checklist so authentication records, ownership, and renewal controls are considered together.

Action plan: inventory senders today, publish or verify SPF and DKIM, start DMARC with a reporting workflow, review results over a representative period, and make enforcement changes one step at a time. Keep the final records and test evidence with your domain documentation so the next provider migration does not begin from scratch.

Related Topics

#DNS#business email#SPF#DKIM#DMARC#email security
T

TopDomains Editorial Team

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.