Email Authentication: SPF, DKIM, and DMARC in 2026

A newsletter lands in a subscriber’s spam folder, while a fake message pretending to come from your company reaches someone else’s inbox. Strong email authentication helps address both problems. In this guide, you will learn how email authentication works, how SPF, DKIM, and DMARC fit together, and how to roll them out safely in 2026.

These controls do not guarantee inbox placement, but they give mailbox providers useful evidence about who is allowed to send mail for your domain. You will also see practical DNS examples, a setup walkthrough, common mistakes, and a verification checklist you can use with your marketing or IT team.

Why email authentication matters

Email authentication is like showing identification at the door of an event. SPF identifies approved sending servers, DKIM attaches a tamper-resistant signature to a message, and DMARC tells receiving providers what to do when those checks do not match your domain.

Without these controls, an attacker may impersonate your domain in a phishing message. Legitimate campaigns can also fail authentication when a new newsletter platform, CRM, help desk, or transactional service is added without updating DNS.

Authentication is separate from content quality and sender reputation. A message can pass SPF and DKIM yet still be filtered because of unwanted content, poor list practices, or recipient complaints. Treat authentication as the foundation of email deliverability, not as a complete delivery strategy.

Start with a sender inventory

The safest email authentication project begins with a list of every system that sends mail for your domain. Do not start by copying DNS values from a provider dashboard. First confirm which platforms are active, which addresses appear in the visible From field, and which domain each service uses for its return path.

Record the following details for every sender:

  • The provider or application name, such as a newsletter platform, CRM, support system, or transactional service.
  • The visible From domain and any return-path or envelope-from domain.
  • The SPF instructions, DKIM selector, and required TXT or CNAME records.
  • Whether the service supports a custom authentication domain.
  • Who owns the account and whether the service is still sending messages.

For example, a small retailer may use one platform for weekly promotions, an online store for receipts, and a help desk for ticket replies. All three sources belong in the sender inventory, even if only one team manages the marketing platform. An old application that still sends password resets is easy to miss and can create confusing DMARC reports.

Publish one SPF record per domain

SPF, or Sender Policy Framework, is a DNS-based list of servers and services allowed to send mail for a domain. A receiving provider checks the sending server against the SPF record for the envelope-from domain. An SPF record is published as a TXT record, usually at the root of the sending domain.

A simplified SPF record might look like this:

v=spf1 include:example-esp.com include:transactional.example -all

The domains in this example are placeholders for provider instructions. Replace them with the exact mechanisms documented by your active services. Do not add an include merely because a provider appears in an old setup guide or because another company uses it.

There must be one SPF record for a domain. If your DNS zone already has an SPF TXT record, edit and combine the approved mechanisms instead of publishing a second SPF record. Multiple SPF records can produce an error or an unreliable result.

Also watch SPF’s DNS lookup limit. Includes and some other mechanisms can trigger DNS lookups, so a long list of providers may exceed the limit. Remove abandoned services, ask providers whether they offer a suitable consolidated record, and avoid adding mechanisms you cannot explain.

Use subdomains when your organization wants separate sending streams, such as news.example.com for marketing and receipts.example.com for transactions. Each sending domain still needs a deliberate configuration. Changing the visible From address alone does not automatically authenticate every related domain.

Configure DKIM signing and alignment

DKIM, or DomainKeys Identified Mail, adds a cryptographic signature to outgoing messages. The sending service keeps a private key, while your DNS contains the matching public key. The recipient uses that public key to check that the message was signed by an authorized service and that signed content was not changed in transit.

Your provider normally gives you a selector and a public key record. A selector is a label that lets a domain use more than one DKIM key over time. A record may use a name such as:

news._domainkey.example.com

Some providers ask you to publish the public key as TXT. Others ask for one or more CNAME records that point to the provider’s key. Follow the current instructions for your account and copy the record name and value exactly. Do not add extra quotation marks or line breaks unless your DNS provider handles them automatically.

DKIM alignment is important because DMARC compares the signing domain with the domain visible to the recipient. A provider may report dkim=pass while still failing DMARC alignment if it signs with its own unrelated domain. When available, choose a custom DKIM domain that matches, or is aligned with, your visible From domain.

For example, imagine a campaign appears to come from [email protected]. If the service signs with a domain controlled by the service rather than an aligned example.com domain, the signature may pass but provide less useful evidence for DMARC. Configure the custom domain, publish the key, and send a test message before changing enforcement settings.

Use DMARC monitoring before enforcement

DMARC, or Domain-based Message Authentication, Reporting, and Conformance, uses SPF and DKIM results together with domain alignment. It lets a domain owner request reports and publish a policy for messages that fail the checks.

A cautious starting record is:

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

This monitoring policy does not ask recipients to quarantine or reject failures. It gives your team time to discover legitimate senders, correct SPF records, enable DKIM, and investigate unexpected sources. Use a separate, monitored mailbox for aggregate reports rather than an address that nobody checks.

Review reports for enough sending cycles to capture normal activity, including less frequent transactional messages. Then move gradually:

  1. Start with p=none and collect reports.
  2. Identify every legitimate source and fix authentication or alignment failures.
  3. Test the changes with marketing, transactional, and support messages.
  4. Move to p=quarantine when the remaining failures are understood.
  5. Use p=reject when you are confident that legitimate traffic is covered.

Policy changes affect real mail, so document who approved each change and when it happened. A business that sends receipts only once a month should not decide that its inventory is complete after checking only a busy weekly newsletter.

Practical email authentication walkthrough

Here is a realistic setup for Northwind Studio, a company that sends newsletters through an email service and receipts through its store platform. The team uses news.northwind.example for campaigns and orders.northwind.example for receipts.

  1. List the sources. The team records the newsletter service, store platform, and help desk. It confirms that an old webinar tool no longer sends mail.
  2. Choose the domains. Marketing uses the news subdomain, while receipts use the orders subdomain. This separates streams and makes reports easier to understand.
  3. Publish SPF. Each domain receives one SPF record containing only the mechanisms supplied by its active provider.
  4. Publish DKIM. The team adds the newsletter selector and the store platform’s CNAME records, then enables custom signing in both provider dashboards.
  5. Monitor DMARC. The organization publishes a p=none record for the parent domain and sends reports to a monitored mailbox.
  6. Test real messages. It sends a campaign, receipt, and support reply to test accounts, then checks the authentication results in the message headers.

This example shows why a sender inventory matters. If the team had authenticated only the newsletter service, receipts could still fail alignment or appear as an unknown source in reports. Email authentication works best when it follows the organization’s actual sending map.

When inspecting a test message, look for results such as spf=pass, dkim=pass, and dmarc=pass. A pass result by itself is not enough; confirm that the authenticated domain aligns with the visible From domain. Save a few representative headers so you can compare results after DNS or provider changes.

Common failures and useful fixes

Most problems come from incomplete inventories, copied records, or a mismatch between the technical sender and the visible From domain. Use the symptom as a starting point, not as proof of one specific cause.

Symptom Likely cause Next check
SPF softfail or permerror Missing provider mechanism, multiple records, or too many DNS lookups Inspect all TXT records and simplify the approved sender list
DKIM none The selector is missing, incorrect, or signing is disabled Compare the selector in the message header with the DNS record
DKIM passes but DMARC fails The signing domain is not aligned with the visible From domain Check the d= domain and configure a custom signing domain
Unexpected quarantine An unknown service is sending or a legitimate source is misconfigured Match the source shown in reports to the sender inventory

Do not solve every failure by weakening the policy. First identify the source, confirm whether it is legitimate, and fix its authentication. If a service is no longer approved, removing its access or account may be safer than adding it to SPF.

Provider settings and self-hosted sending

Brevo, SendGrid, Mailchimp, and similar providers publish their own current SPF and DKIM instructions. Their record names and setup screens can change, so use the documentation for your account rather than copying a value from another domain or an old screenshot.

Self-hosted sending requires more than DNS records. You also need to manage reverse DNS, TLS, bounce processing, suppression lists, queue behavior, and sender reputation. A technically valid message can still perform poorly if your server continues sending to addresses that have opted out or bounced.

Keep marketing and transactional mail separate when practical. For example, a promotional campaign should not share the same operational process as password resets. Separate domains or subdomains can make reporting and incident response clearer, but they do not remove the need for accurate authentication on each stream.

Final verification checklist

Before moving from monitoring to enforcement, complete this email authentication checklist:

  • Every legitimate sending platform appears in the sender inventory.
  • Each sending domain has one SPF record with approved mechanisms.
  • Every active platform signs messages with DKIM.
  • DKIM and SPF align with the visible From domain where required by DMARC.
  • DMARC reports go to a monitored mailbox.
  • Test messages cover newsletters, receipts, support replies, and password or account notifications.
  • Unsubscribe, bounce, and suppression processes work as expected.
  • DNS changes and policy changes are documented for future troubleshooting.

Frequently asked questions

Can I publish more than one SPF record?

No. Publish one SPF record for each domain and combine the approved mechanisms in that record. Multiple SPF records can cause an error instead of creating a stronger policy.

Does DMARC replace SPF and DKIM?

No. DMARC relies on SPF and DKIM results, then checks whether at least one authenticated result aligns with the visible From domain. You need working SPF or DKIM before DMARC can provide useful protection.

How long should I monitor DMARC before enforcement?

Monitor long enough to capture every legitimate sending source, including infrequent transactional mail. The right period depends on your sending schedule; do not move to quarantine or reject until the reports and test messages make sense.

Why does DKIM pass while DMARC fails?

DKIM can pass for a provider’s domain while failing DMARC alignment with your visible From domain. Check the signing domain in the message header and ask the provider to enable a custom aligned DKIM domain.

Take the next step

Reliable email authentication starts with knowing who sends mail for your domain. Build the sender inventory, publish one accurate SPF record per domain, enable aligned DKIM signing, and use DMARC monitoring before enforcement.

Start with one test message from each legitimate platform today and record its SPF, DKIM, and DMARC results. For broader delivery guidance, review our email deliverability checklist and the guide to self-hosted email marketing.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *