SPF, DKIM, and DMARC Explained: A Business Email Authentication Guide

By Dave TanguayPublished Updated Editorial draft

Quick Answer

SPF checks whether a sending server is authorized for an envelope-sender domain. DKIM verifies a message signature associated with a signing domain. DMARC checks whether a passing SPF or DKIM identity aligns with the From domain your recipient sees. Configure and test every legitimate sending service, including website and store notifications. Correct authentication helps receivers evaluate mail, but it does not guarantee delivery to the inbox.

Your employees’ mailboxes may send only part of your business email. Contact forms, order notifications, appointment reminders, invoices, newsletters, and support software can use the same From domain through different sending systems. A record that works for employee mail does not establish that those other systems work.

A useful review follows an actual message from its source to the receiving provider. It combines DNS inspection with the authentication results on received messages and a record of the services your business uses.

What do SPF, DKIM, and DMARC check?

Scroll horizontally to see all columns.

The different jobs of the three authentication mechanisms
Mechanism Question it answers Identity and DNS location What a pass does not prove
SPF Is this server authorized to send for the checked envelope domain? Usually the SMTP MAIL FROM domain; its SPF TXT policy. That the visible From domain matches, or that a recipient wants the message.
DKIM Does this signature verify using the signing domain’s published key? The signature’s d= domain and s= selector; a selector-specific DNS lookup. That the signing domain matches the visible From domain, or that the content is safe.
DMARC Does a passing SPF or DKIM path align with the visible From domain? The message’s From domain and its applicable DMARC policy, normally found through a _dmarc TXT lookup. That the message will reach the inbox or that every impersonation technique is blocked.

Start with the SPF record guide for authorized senders and lookup errors, the DKIM guide for signatures and selectors, and the DMARC guide for alignment, reports, and policies. Each explains the corresponding DNS record and the checks needed after publication.

Recognize the three domains on a message

The address a person sees in the From field is not necessarily the address used for delivery errors. A sending provider can also sign mail using a different domain. Reading the three identities separately prevents a common mistake: assuming that any SPF or DKIM pass proves authentication for your business’s visible address.

Visible From
The address presented to the recipient, such as billing@example.com. DMARC evaluates alignment against this domain.
Envelope sender
The SMTP MAIL FROM identity used during transfer. It commonly appears as Return-Path in the final received message. SPF normally checks its domain. Special cases, including a null MAIL FROM, have additional SPF rules.
DKIM signing domain
The d= value in a DKIM signature. The s= value identifies the selector used to locate its public key.

For a synthetic example, imagine a message with From billing@example.com, an envelope domain of bounces.example.net, and a passing DKIM signature using d=example.com. The SPF path can pass for bounces.example.net while remaining unaligned with example.com. The aligned DKIM pass can still allow DMARC to pass.

If both passing identities instead belong to example.net, neither aligns with the visible example.com domain. Separate SPF and DKIM passes would not produce a DMARC pass in that example. These domains illustrate identity relationships; they are not configuration values to paste into DNS.

Follow the message through its actual sending path

An employee may send through a mailbox provider, while a website sends an inquiry alert through an application, local mail server, or separate delivery service. A store can use another service for order updates. Each path has its own credentials, sender settings, and evidence.

For website mail, distinguish the form submission from the notification it creates. A visitor’s successful submission does not establish that the sending service accepted the notification or that the recipient received it. Our website form delivery guide traces those handoffs.

For store or marketing mail, ask which service actually sent the message rather than assuming that the website host sent it. Check the relevant platform’s current domain-authentication instructions and the resulting message. Installing another WordPress email plugin does not configure a separate newsletter provider automatically.

Build a sender inventory before editing records

List employee mail, website forms, account notifications, store receipts, booking systems, newsletters, invoicing tools, and support software. Include low-volume systems that send only monthly or after an unusual event. An inventory based only on today’s messages can miss a legitimate sender.

A worksheet for each legitimate sending service
Field What to record
Service and owner The system, its business purpose, and the person who maintains it.
Message types The events that generate mail and whether each follows the same route.
Identities Visible From domain, envelope domain, and DKIM signing domain/selector from a received sample.
Provider instructions The current account-specific DNS and sender-configuration requirements.
DNS authority Where public DNS is actually managed and who can approve an edit.
Verification and recovery A test reference, time and time zone, observed results, and the preserved configuration needed for recovery.

Keep credentials and private message contents in approved restricted systems. The inventory should describe the route without becoming a public copy of your customers’ communications.

Configure and verify one sending path at a time

  1. Preserve the before-state. Save the relevant DNS values, sender configuration, and owners. Identify the authoritative DNS provider before choosing an editing screen.
  2. Reconcile SPF requirements. Review all legitimate senders together. A DNS name must not publish multiple selected SPF policies. Check syntax and lookup behavior rather than appending a second provider’s instructions blindly.
  3. Configure DKIM at the sender and in DNS. Obtain the exact selector and TXT or CNAME values from the service. Then confirm that outgoing mail uses the intended signature. Publishing a key does not, by itself, enable signing in every service.
  4. Send an authorized test through the real route. Trigger the relevant form, notification, or mailbox action using non-sensitive content. Inspect the message at a controlled receiving account. Record SPF, DKIM, and DMARC results with the checked domains.
  5. Review the policy and reports. A monitoring DMARC policy can help reveal unexpected sources. Resolve legitimate failures and examine indirect mail flows before choosing stronger treatment.
  6. Repeat when something changes. Recheck after adding a sender, moving DNS, changing a mail provider, or modifying the website’s sending route. Keep old selectors and other dependencies until the responsible provider confirms they can be retired.

The SPF standard defines SPF’s DNS policy and evaluation rules. The DKIM standard defines signature verification. The current DMARC specification connects authenticated identities with the visible From domain and describes policy considerations.

DMARC enforcement needs a decision about the domain’s actual use. General-purpose correspondence can pass through forwarding services and mailing lists that complicate authentication. Do not treat p=reject as an automatic destination for every domain. The detailed DMARC guide covers the current specification, implementation differences, and the evidence needed for that decision.

Separate protocol results from receiver requirements

DMARC can pass through one aligned authentication path. A receiving provider can still require your sending setup to support both SPF and DKIM, along with other controls.

Gmail’s sender guidelines distinguish general senders from bulk senders and include requirements beyond authentication. Use the requirements for the destinations and sending patterns your business actually has. A policy accepted by one provider is not evidence of universal acceptance.

Check the account’s current provider documentation when implementing a change. Requirements, user interfaces, and deployed support for newer DMARC behavior can change while older setup examples remain online.

Why can authenticated email still go to spam?

Authentication does not answer whether the recipient requested a campaign, whether the sending pattern looks abusive, or whether a receiving organization’s policy permits an attachment. Those questions require separate evidence.

A monitoring DMARC policy does not switch off spam filtering. It means that the domain has not requested quarantine or rejection for a DMARC failure. A receiver can still reject, filter, or quarantine a message under its own controls.

When a message is missing, first establish whether the sending system rejected it, deferred it, obtained receiving-server acceptance, or never attempted it. For accepted mail, check recipient-side handling. Our business email spam troubleshooting guide follows that investigation without treating a DNS edit as the answer to every symptom.

Where do cPanel and Cloudflare fit?

A cPanel account can host the website or mailboxes while Cloudflare hosts the authoritative DNS zone. Publishing a record in cPanel’s local zone does not necessarily publish it to the internet. Confirm which provider supplies the public answers.

Use the cPanel and Cloudflare authentication walkthrough for that setup. If you are changing nameservers as well, start with our broader cPanel-to-Cloudflare DNS migration guide and preserve existing email services through the transition.

Key Takeaways

  • Inventory every sending service, including website and third-party messages.
  • SPF, DKIM, and DMARC check different identities and relationships.
  • Verify the actual received message after publishing DNS and configuring the sender.
  • Review legitimate sending paths and indirect delivery before changing DMARC enforcement.
  • Keep authentication results separate from inbox placement and receiver requirements.

Frequently Asked Questions

Do I need both SPF and DKIM to pass DMARC?

DMARC requires at least one passing authentication path that aligns with the visible From domain. Receiving providers may separately require both SPF and DKIM for your sending pattern. Configure and test both where supported.

Can my mailbox and newsletter provider have separate SPF records?

They cannot publish competing SPF policies at the same DNS name. Review their requirements together in one valid policy for that name. A deliberately configured sending subdomain can have its own policy.

Does DMARC stop all phishing?

No. It addresses the use of a domain in the visible From identity through alignment and policy. It does not prevent all lookalike domains, misleading display names, malicious content, or abuse of legitimate accounts.

Will moving DNS to Cloudflare fix email delivery?

A change of DNS provider does not automatically correct the sending configuration, authentication, reputation, or receiving rules. Preserve the required records and test the actual services before and after a migration.

Can a contact form use the visitor’s email address as its From address?

Use the sending provider’s supported, authenticated sender identity. Put the visitor’s address in Reply-To where the form and provider support it, then verify that replies go to the intended visitor. An unrelated visitor domain is not yours to authenticate.

Bring the sending details to a focused review

If the problem involves your website or hosting, contact Interactive Online with the sending service, approximate time and time zone, affected message type, and non-sensitive error details. We can review the website-related scope and identify the questions that belong with your mail or DNS provider. See ongoing website development for form and integration work, and cPanel hosting for the available website and business-email hosting options.

Archives