Business email DNS setup is easier to manage when SPF, DKIM, and DMARC are treated as a monitored system rather than three records added once. This checklist explains how to plan the records, publish them safely, test authentication, and review changes over time so legitimate messages have a better chance of reaching the inbox without accidentally rejecting important mail.
Overview
SPF, DKIM, and DMARC solve different parts of the email authentication problem:
- SPF identifies the servers and services authorised to send mail for your domain.
- DKIM adds a cryptographic signature to outgoing messages so receiving systems can check that the message was signed by an authorised sending service and was not changed in transit.
- DMARC tells receiving systems what to do when a message appears to come from your domain but does not pass the required authentication checks. It can also provide reports for investigation.
These records are published in DNS, usually through your domain registrar, DNS host, or hosting control panel. Your business email provider will supply service-specific values, such as SPF mechanisms, DKIM selectors, public keys, and verification tokens. Do not substitute examples from another provider for those values.
Before editing DNS, make an inventory of every legitimate sender. Include your primary business email platform, website contact forms, CRM, marketing platform, help desk, invoicing system, appointment software, and any application that sends mail using your domain. A record can be technically valid yet incomplete if one of these services is omitted.
For background on record types and nameserver changes, see DNS Records Explained: A Practical Guide to A, CNAME, MX, TXT, and Nameserver Changes.
What to track
1. SPF: maintain one authoritative policy
SPF is normally published as a TXT record at the root of the domain. A simplified planning example might look like this:
example.com. TXT "v=spf1 include:mail.example-provider.test include:marketing.example.test ~all"
The domains and mechanisms in this example are placeholders. Replace them with the exact values supplied by your sending services. The final mechanism, such as ~all or -all, expresses how receivers should treat senders that are not listed. Choose it only after you have confirmed that all legitimate sending sources are included.
Keep a written SPF planning table with these columns:
- Sending service or application
- Purpose, such as staff mail, website forms, or newsletters
- Required SPF include or IP mechanism
- Person responsible for the service
- Date last verified
- Status: active, retired, or under review
The most common configuration error is publishing multiple SPF TXT records for the same domain. Combine approved mechanisms into one SPF policy instead of adding a second record that also begins with v=spf1. When a service is removed, remove its SPF reference only after confirming that it no longer sends mail for the domain. Ask the provider about lookup limits and syntax constraints before building a complex policy; excessive or nested lookups can cause validation problems.
2. DKIM: record selectors and key rotation
DKIM uses a selector to identify a particular public key. The provider usually gives you a selector and asks you to publish a TXT or CNAME record at a hostname similar to:
selector1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=PUBLIC_KEY_VALUE"
Some services use a CNAME that points to a provider-managed DKIM hostname instead. Follow the provider's instructions for the record type, hostname, and value. Do not add quotation marks or line breaks manually if your DNS interface formats long TXT values for you.
Track each selector in an inventory. Record which service uses it, when it was created, whether it is active, and what change or rotation procedure applies. During a key rotation, publish the new key before enabling the new selector for outgoing mail. Leave the old selector available for an appropriate transition period defined by your provider and operational needs, then remove it when it is no longer used. This avoids breaking verification for messages signed with the old key that are still being delivered.
Restrict access to the email and DNS accounts that control DKIM. A private DKIM key should remain with the sending service and must never be published in DNS. Only the public key belongs in the DNS record.
3. DMARC: start with visibility, then enforce deliberately
DMARC is published as a TXT record at _dmarc. A monitoring-stage example is:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]; adkim=r; aspf=r"
The p=none setting requests reporting without asking receivers to reject or quarantine failing messages. Once legitimate sources are identified and authentication is aligned, an organisation may choose to test a stricter policy, such as p=quarantine, and eventually p=reject. That progression should be based on observed mail flows, not a calendar alone.
DMARC alignment matters: the domain visible in the From address must align with the authenticated domain used by SPF or DKIM according to the policy's alignment settings. A message can pass SPF for a provider's domain while still failing DMARC if that domain is not aligned with the address recipients see. DKIM alignment can be more durable for third-party sending services when their mail is configured to sign with your domain.
Use a reporting mailbox or reporting service that can receive and process aggregate reports. Confirm that the address is monitored, protected from excessive noise, and suitable for the volume you expect. Keep the DMARC record to one policy at the domain level unless you have a clear subdomain strategy.
Configuration checklist
- Confirm where authoritative DNS is hosted.
- List every system that sends mail using your domain.
- Collect the exact SPF, DKIM, and DMARC values from each provider.
- Check for an existing SPF record before adding one.
- Publish DKIM records and enable signing in each sending service.
- Publish DMARC with monitoring enabled before enforcement.
- Allow for DNS propagation and test from more than one receiving mailbox.
- Document the final records, owners, selectors, and review date.
Cadence and checkpoints
Use a recurring review schedule so authentication does not become dependent on one administrator's memory.
| Cadence | Checkpoint | Evidence to retain |
|---|---|---|
| After every DNS change | Query the public SPF, DKIM, and DMARC records and send controlled test messages. | Record values, test addresses, timestamps, and results. |
| Monthly | Review authentication results, delivery complaints, failed messages, and newly added sending services. | Report summary and unresolved exceptions. |
| Quarterly | Compare the DNS inventory with actual business systems and remove retired services. | Approved sender list and owner sign-off. |
| Before a campaign or migration | Confirm DKIM signing, SPF inclusion, return-path behaviour, and DMARC alignment for the new sender. | Provider setup notes and pre-launch test results. |
| During key rotation | Verify the new selector before retiring the old one. | Selector history and rotation date. |
DNS changes can be affected by caching and record time-to-live settings, so avoid judging a change immediately from one mailbox. Check the record from an independent DNS lookup method and repeat testing after the expected caching period. For a broader launch checklist covering domain, DNS, SSL, and email dependencies, see How to Connect a Domain to Web Hosting: DNS, SSL, and Email Setup Guide.
How to interpret changes
A rise in SPF failures does not always mean SPF syntax is broken. It may indicate a new marketing tool, a forwarded message, an unauthorised sender, or a service sending through an unapproved route. Compare the reporting source with your sender inventory before changing the record.
DKIM failures can result from a missing selector, an incorrect public key, disabled signing, or message changes after signing. If the failure affects one service, check that service's selector and signing status first. If many services fail after a DNS migration, confirm that the authoritative nameservers and complete record values are correct.
DMARC failures should be investigated by separating SPF alignment from DKIM alignment. A message may pass one authentication method but fail DMARC because neither method aligns with the visible From domain. Review the sending service's From address, return-path, DKIM signing domain, and custom-domain settings.
Before moving from p=none to enforcement, classify report sources into three groups: approved senders, retired or unknown senders, and legitimate business systems that still need configuration. Correct the third group, investigate the second, and keep evidence of the decision. If legitimate messages are rejected after enforcement, temporarily reduce the policy while correcting the sender configuration rather than repeatedly adding unverified mechanisms.
Do not treat a passing authentication result as a complete deliverability guarantee. Content, recipient engagement, sending reputation, mailbox rules, and provider-specific filtering can also affect delivery. SPF, DKIM, and DMARC provide an important identity and policy layer, not a promise that every message reaches the inbox.
When to revisit
Revisit this checklist whenever you change email hosting, add a marketing or transactional sender, migrate DNS, register a new sending subdomain, alter the visible From domain, or rotate DKIM keys. Review it monthly while a DMARC policy is in monitoring or transition, then continue at least quarterly once the configuration is stable.
Set an owner for each record and store the inventory with your infrastructure documentation. At each review, answer four practical questions:
- Does every active business system that sends mail appear in the inventory?
- Is there exactly one intended SPF policy for the domain?
- Are all active DKIM selectors published and signing as expected?
- Do DMARC reports show unknown senders, alignment failures, or a change in normal volume?
Finish each review by recording the date, reviewer, changes made, unresolved risks, and next checkpoint. If you are transferring a domain or changing DNS providers, include these records in the migration plan and verify them before switching nameservers. A documented, repeatable review is the safest way to improve email authentication without creating an avoidable outage.