SPF, DKIM, and DMARC Setup Guide: Audit Domain Email Authentication and Fix Delivery Issues
email authenticationSPFDKIMDMARCemail deliverability

SPF, DKIM, and DMARC Setup Guide: Audit Domain Email Authentication and Fix Delivery Issues

BBestWebsite.biz Editorial Team
2026-11-21
7 min read

Learn how to configure SPF, DKIM, and DMARC, audit legitimate senders, read reports, and safely improve domain email delivery.

SPF, DKIM, and DMARC give a domain owner a practical way to verify legitimate email, reduce impersonation risk, and investigate delivery problems. This guide explains how to inventory senders, publish the right DNS records, monitor authentication results, and change policy safely as your website, newsletter, or business email setup evolves.

Overview

Email authentication is a DNS and mail-server configuration task, not a single setting in your hosting control panel. SPF identifies the servers permitted to send mail for a domain. DKIM adds a cryptographic signature to outgoing messages. DMARC tells receiving mail systems how to evaluate those signals against the visible From address and how to report results back to the domain owner.

The three standards work together, but they solve different problems:

  • SPF: publishes an approved list of sending services or servers for a domain.
  • DKIM: lets a receiving system verify that a message was signed by an authorized sender and was not altered in transit.
  • DMARC: applies a policy to messages that fail authentication alignment and provides reporting options.

A reliable setup begins with an inventory rather than with copying records from a random example. List every service that sends mail using your domain, including employee mailboxes, website forms, ecommerce or payment notifications, newsletters, customer relationship tools, support platforms, appointment systems, and monitoring software. Record the sending domain, the provider's required SPF mechanism, the DKIM selector or setup instructions, and whether the service uses your domain in the visible From address.

Keep this inventory with your DNS documentation. It is especially useful during a platform migration or when a message begins going to spam. If your website or store is hosted separately from your email provider, remember that web hosting does not automatically authenticate every application that sends mail.

What to track

SPF records and sender changes

Publish one SPF record for each domain or subdomain that sends mail. Combining several separate SPF TXT records for the same name is not a safe substitute for one coordinated record. Start with the sending services you can verify, then follow each provider's current instructions for the required include, IP address, or other mechanism.

Review the record whenever you add or remove a sender. Avoid adding broad, undocumented mechanisms merely to make a test pass. A long chain of third-party lookups can also make an SPF design harder to maintain, so remove obsolete services and use subdomains where separate sending streams need separate administration. For example, a marketing platform might send from a dedicated subdomain while employee mail uses the primary domain.

DKIM keys and selectors

For DKIM, enable signing in each sending platform and publish the public key at the selector and domain name supplied by that platform. The private key should remain with the sender; it should not be placed in a public DNS record or shared in a support ticket.

Track the selector, provider, signing domain, and key-rotation procedure. Multiple selectors can coexist, which allows a provider to introduce a new key before retiring an old one. Do not delete an old selector until messages using it have stopped and any transition period required by the provider has passed.

DMARC policy and reports

DMARC is published as a TXT record at _dmarc.example.com. Its settings commonly include a policy such as p=none, p=quarantine, or p=reject, an aggregate reporting address, and alignment preferences. Use the exact syntax recommended by your DNS host and reporting provider; small punctuation errors can invalidate a record.

Begin by collecting reports with a monitoring policy while you identify legitimate senders. After the inventory is complete and authentication is passing consistently, consider a staged move toward enforcement. A quarantine or reject policy should be treated as an operational change: it can affect legitimate messages from forgotten forms, old platforms, forwarded mail, or regional systems.

Authentication results

Track more than a headline pass rate. For each source in aggregate reports, note the sending IP or provider, the header From domain, SPF result, DKIM result, DMARC result, and alignment outcome. Investigate new sources, unexpected countries or networks, sudden volume changes, and messages that pass SPF or DKIM but fail alignment.

Forwarding can change the path of a message and cause SPF to fail. DKIM may survive if the message is not altered, but forwarding services and mailing lists can modify content or headers. Treat these results as clues to investigate rather than as proof that a legitimate sender is malicious.

Cadence and checkpoints

Use a simple recurring schedule so email authentication does not depend on memory:

  • After every sender change: test the new platform, confirm SPF and DKIM are enabled, and check that the visible From domain aligns with the authenticated domain.
  • Weekly during a rollout: review reports for new sources, failures, and unexpected volume. Keep the DMARC policy conservative while unknown legitimate systems are being identified.
  • Monthly: compare the sender inventory with DNS records, provider accounts, website plugins, and business tools. Remove records for services that are no longer used.
  • Quarterly: review DMARC policy, reporting destinations, DKIM selectors, SPF complexity, subdomains, and access to DNS. Confirm that a former employee, discontinued campaign, or replaced platform has not left an active sender behind.
  • After a delivery incident: preserve a sample message and its full authentication headers, then compare the result with aggregate reports before changing policy.

Test from the actual applications that send mail. A successful message from an employee mailbox does not prove that a website contact form or order notification is configured correctly. If DNS changes are not visible immediately, allow for DNS caching and recheck using the authoritative record rather than assuming the first lookup is definitive.

How to interpret changes

A new SPF failure can mean an unapproved sender, a forwarding path, a missing provider include, or a message that uses a different envelope-from domain than expected. A DKIM failure can indicate that signing is disabled, the selector is missing, the key is wrong, or a message was modified after signing. A DMARC failure means the message did not satisfy the required combination of authentication and alignment; it does not, by itself, identify the cause.

Compare timing and volume. A small number of failures immediately after adding a known platform may point to setup or alignment work. A sudden increase from an unfamiliar source deserves closer review, especially if it uses your brand in the visible From field. Do not respond to a single report by adding every unfamiliar IP address to SPF. First establish whether that source is yours and whether the message should be allowed.

When moving from monitoring to enforcement, change one variable at a time where possible. Confirm all legitimate streams, communicate the change to people responsible for newsletters and transactional systems, and retain a rollback plan. If legitimate mail is affected, temporarily return to monitoring or narrow the change while correcting the underlying sender configuration. For broader website security work, pair this review with a website SSL and security checklist rather than treating email authentication as the entire security program.

When to revisit

Revisit this guide whenever you add a newsletter provider, change business email, install a new contact-form or ecommerce integration, migrate hosting, launch a subdomain, or investigate spam placement. Also schedule a monthly review during active changes and a quarterly audit once the setup is stable.

At each review, take these practical actions:

  1. Export or read the latest DMARC aggregate reports.
  2. Compare every sending source with your current inventory.
  3. Test representative messages from employee, website, marketing, and transactional systems.
  4. Check SPF for duplicate records, obsolete services, and unnecessary mechanisms.
  5. Confirm DKIM selectors still resolve and that active platforms are signing.
  6. Review DMARC policy, alignment, reporting addresses, and subdomain treatment.
  7. Document the change, the test result, and the person responsible for the next review.

Keep DNS access, email-provider access, and recovery details current. Domain administration is part of this process: an expired domain or poorly documented DNS account can interrupt both website and mail operations. If you are changing hosting or email providers, use a staged migration approach similar to the testing discipline described in this WordPress staging site guide. A short, maintained sender inventory and regular report review will make future authentication changes safer and make delivery issues easier to diagnose.

Related Topics

#email authentication#SPF#DKIM#DMARC#email deliverability
B

BestWebsite.biz Editorial Team

Site Operations 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.