Email Deliverability Explained: SPF, DKIM and DMARC

Email deliverability determines whether emails successfully reach recipients’ inboxes rather than being rejected, blocked, or placed in spam folders. For businesses that depend on email marketing, customer communication, newsletters, or transactional notifications, maintaining good deliverability is essential for reaching the intended audience.

One of the most important parts of email deliverability is authentication. Email providers need a way to determine whether a message is genuinely authorized by the domain shown in its sender address. Three technologies help establish this trust: SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance).

Although these technologies work together, each performs a different function. SPF identifies authorized sending servers, DKIM uses digital signatures to verify message integrity and domain responsibility, and DMARC checks whether SPF or DKIM authentication aligns with the domain displayed in the sender’s address.

Understanding how these protocols work makes it easier to configure business email, protect domains against impersonation, troubleshoot authentication failures, and improve the reliability of legitimate email communication.

What Is Email Deliverability?

Email deliverability refers to the ability of an email message to reach its intended destination, particularly the recipient’s inbox.

It is different from email delivery. Delivery generally indicates that a receiving mail server accepted the message, while deliverability focuses on whether the message reaches the inbox rather than the spam or junk folder.

For example, suppose a company sends a promotional email to 5,000 subscribers. Its email platform may report that 4,800 messages were successfully delivered. However, some of these messages might have reached spam folders instead of the primary inbox.

This means a high delivery rate does not necessarily indicate strong inbox placement.

Several factors influence email deliverability:

  • Sender domain and IP reputation.
  • SPF, DKIM, and DMARC authentication.
  • Recipient engagement and spam complaints.
  • Email list quality and permission practices.
  • Sending frequency and volume.
  • Message content and sending patterns.
  • DNS configuration and mail server infrastructure.

Email authentication is an important foundation because it helps receiving servers evaluate whether messages are authorized. However, passing authentication does not guarantee inbox placement.

Understanding SPF, DKIM, and DMARC

SPF, DKIM, and DMARC are email authentication protocols designed to reduce domain spoofing, impersonation, and unauthorized email activity.

They work at different levels of the email authentication process.

ProtocolFull formMain purpose
SPFSender Policy FrameworkIdentifies authorized email sending servers
DKIMDomainKeys Identified MailUses digital signatures to verify message integrity and signing-domain responsibility
DMARCDomain-based Message Authentication, Reporting, and ConformanceChecks authentication alignment and communicates the domain owner’s handling preference for failures

These three protocols should be configured together for stronger protection.

What Is SPF (Sender Policy Framework)?

SPF is an email authentication protocol that allows a domain owner to specify which mail servers are authorized to send messages using that domain’s email sending identity.

The domain publishes an SPF policy in its DNS records. When a receiving server gets an email, it can check the sending server’s IP address against that policy.

For example, a company might send email through Google Workspace, Microsoft 365, and an email marketing platform. Its SPF configuration should account for the legitimate services that send email on its behalf.

If an unauthorized server attempts to send email using the company’s domain in the SPF-checked identity, the SPF evaluation may fail.

How SPF works

The process generally follows these steps:

  1. A business publishes an SPF TXT record in its domain’s DNS configuration.
  2. The SPF record identifies authorized sending sources.
  3. A receiving email server examines the sending server’s IP address.
  4. It retrieves the SPF policy for the relevant SMTP envelope sender domain.
  5. It checks whether the sending IP address is authorized.
  6. The SPF evaluation produces a result such as pass, fail, softfail, or neutral.

An important technical detail is that SPF normally authenticates the domain in the SMTP MAIL FROM identity, also known as the envelope sender. It does not independently verify the visible From address that recipients see in their inbox.

This distinction becomes important when configuring DMARC.

Example of an SPF record

A simplified illustrative SPF TXT record might look like this:

v=spf1 ip4:192.0.2.10 include:spf.example.net ~all

This example contains several components:

SPF componentMeaning
v=spf1Identifies the SPF version
ip4:192.0.2.10Authorizes the specified IPv4 address
include:spf.example.netIncludes an external domain’s SPF authorization policy
~allMarks other unmatched sources as softfail

The IP address and domain in this example are placeholders. A real SPF record must use the exact sending addresses and mechanisms supplied by the email providers being used.

Important SPF configuration rules

SPF has technical restrictions that administrators must consider.

First, a domain or hostname should have only one SPF record. Multiple SPF TXT records beginning with v=spf1 at the same DNS name can cause authentication errors.

Second, SPF has a limit of 10 DNS-querying terms during an evaluation. Mechanisms such as include, a, mx, ptr, and exists, as well as the redirect modifier, contribute to this limit. Exceeding it can produce a permanent SPF error.

Businesses using several third-party email services should therefore consolidate their authorized senders into one properly constructed SPF record.

What Is DKIM (DomainKeys Identified Mail)?

DKIM is an email authentication method that uses cryptographic digital signatures to help receiving servers verify that a message was signed by a domain-authorized system and that the signed parts of the message have not been modified in a way that invalidates the signature.

Unlike SPF, which checks sending infrastructure, DKIM verifies a digital signature associated with the message.

When a company sends an email, its outgoing mail system signs selected message headers and the message body using a private cryptographic key.

The corresponding public key is published in the domain’s DNS records. Receiving servers use this public key to verify the signature.

A valid DKIM signature helps establish responsibility by the signing domain and protects the integrity of the signed message content.

How DKIM works

The process includes the following steps:

  1. The sending email service generates a public and private cryptographic key pair.
  2. The private key is used to create a digital signature for outgoing messages.
  3. The message includes a DKIM-Signature header.
  4. The receiving server reads the signing domain and selector from that header.
  5. It looks up the corresponding public key in DNS.
  6. The receiving server uses the public key to verify the signature.
  7. The message receives a DKIM authentication result.

Two important values are included in a DKIM signature:

  • d= Identifies the signing domain.
  • s= Identifies the selector used to locate the public key.

For example, a signing system might use the selector mail2026 and the signing domain example.com.

The public key would then be published under a DNS name similar to:

mail2026._domainkey.example.com

Why DKIM matters for email deliverability

DKIM provides additional verification beyond checking the sending server.

A valid DKIM signature can remain verifiable when a message passes through forwarding servers, provided the signed content and headers are not modified in a way that invalidates the signature.

This is useful because forwarding can change the IP address involved in SPF authentication.

However, changes introduced by mailing lists, email gateways, or other intermediaries can sometimes invalidate DKIM signatures.

Businesses should configure DKIM through their email provider and follow the exact DNS values supplied by that service.

Where supported, a 2,048-bit RSA key is a sensible choice for stronger key security. Google recommends this key length when supported for messages sent to personal Gmail accounts.

What Is DMARC (Domain-based Message Authentication, Reporting, and Conformance)?

DMARC is an email authentication protocol that builds on SPF and DKIM.

Its primary purpose is to help domain owners protect their visible From domain against unauthorized use and impersonation.

SPF and DKIM can both pass authentication without proving that the authenticated domain is related to the domain displayed in the sender’s address.

DMARC addresses this issue through a concept called alignment.

It checks whether at least one successful SPF or DKIM authentication result is aligned with the domain in the visible From address.

A DMARC policy also communicates the domain owner’s preference for handling messages that fail DMARC authentication.

How DMARC works

The process generally follows these steps:

  1. A business publishes a DMARC TXT record in DNS.
  2. An email arrives displaying the business’s domain in its From address.
  3. The receiving server evaluates SPF and DKIM.
  4. It checks whether the authenticated SPF or DKIM domain aligns with the visible From domain.
  5. If at least one authenticated identifier passes and aligns, DMARC passes.
  6. If neither mechanism produces an aligned pass, DMARC fails.
  7. The receiving server uses the published DMARC policy to inform its handling decision and can send requested authentication reports.

Example of a DMARC record

A basic monitoring record might look like this:

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

Its components are:

ComponentMeaning
v=DMARC1Identifies the DMARC version
p=noneRequests monitoring without a DMARC-specific enforcement action
rua=mailto:[email protected]Specifies where aggregate DMARC reports can be sent

The DMARC record is normally published as a TXT record at:

_dmarc.example.com

The example uses a placeholder domain and reporting mailbox. Replace them with the organization’s actual domain and a mailbox configured to receive and process reports.

Understanding DMARC policies

DMARC supports three main policy values.

PolicyPurposeTypical use
NoneRequests no DMARC-specific enforcement actionInitial monitoring
QuarantineRequests suspicious handling of messages that fail DMARCGradual enforcement
RejectRequests rejection of messages that fail DMARCStronger domain protection

A company should generally begin with monitoring, inspect authentication reports, correct problems involving legitimate sending systems, and then consider moving toward quarantine or reject.

A p=none policy does not block spoofed messages by itself. It helps the domain owner observe authentication results without requesting DMARC-based rejection or quarantine.

The receiving provider can still apply its own spam and security filtering.

How SPF, DKIM, and DMARC Work Together

Although each protocol performs a different function, the strongest email authentication setup uses all three.

Consider a company sending an invoice notification from:

[email protected]

Its email service sends the message using an authorized mail server and signs the message with DKIM.

The recipient’s email server checks the following:

SPF verification: Is the sending server authorized by the relevant SPF domain?

DKIM verification: Does the message contain a valid digital signature associated with the signing domain?

DMARC verification: Does at least one successful authentication result align with example.com, the domain shown in the visible From address?

The distinction between authentication and alignment is particularly important.

For example, an email might pass SPF for provider-mail.com and pass DKIM for provider-mail.com, but display [email protected] as its sender address.

Both individual authentication mechanisms may pass, but neither authenticated domain aligns with example.com. In that situation, DMARC fails.

This is why businesses using external email marketing, CRM, invoicing, and customer support platforms should configure custom-domain authentication correctly.

SPF, DKIM, and DMARC comparison

FeatureSPFDKIMDMARC
Checks authorized sending sourcesYesNoUses SPF results
Uses cryptographic signaturesNoYesNo
Checks message integrityNoYesIndirectly through DKIM
Provides domain alignmentNoNoYes
Publishes policy through DNSYesPublic key through DNSYes
Supports reportingNo native reportingNo native reportingYes

A useful way to remember the relationship is that SPF checks the sending source, DKIM verifies the signed message, and DMARC connects the authentication results to the visible sender domain.

How to Set Up SPF, DKIM, and DMARC for Your Domain

Setting up email authentication requires access to your domain’s DNS settings and the administration tools of the services that send email for your business.

The exact records vary depending on your email provider, so administrators should always use provider-generated values rather than copying generic DNS examples.

Step 1: Identify Every Service That Sends Email

Before changing DNS settings, prepare a list of all services that send email using your domain.

These may include:

  • Google Workspace or Microsoft 365.
  • Email marketing platforms.
  • CRM applications.
  • Customer support systems.
  • Billing and invoicing software.
  • Website contact forms.
  • Automated notification services.

This step is important because an overlooked sending service can cause authentication failures after the domain’s policies are tightened.

Step 2: Configure the SPF Record

Log in to your domain registrar or DNS hosting provider and locate the DNS management section.

Check whether an SPF record already exists.

If one is present, update it rather than creating another independent SPF record.

Add the authorized sending mechanisms provided by your email services. Check the complete record for incorrect entries and DNS lookup-limit issues.

Once published, allow DNS changes to propagate and test messages from each legitimate sending service.

Step 3: Generate and Publish DKIM Records

Open your email provider’s administration console and locate its DKIM authentication settings.

The provider will generally generate a selector and corresponding DNS record.

Depending on the service, you may need to publish a TXT or CNAME record.

After publishing the record, enable DKIM signing in the provider’s administration interface.

Send a test email and inspect its authentication results to confirm that DKIM passes.

Step 4: Configure a DMARC Record

After SPF and DKIM are working, create a dedicated email address or group for receiving DMARC aggregate reports.

Publish the initial DMARC record using a monitoring policy:

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

This allows the business to receive reports about messages using its domain.

DMARC aggregate reports generally contain XML data showing which sources sent mail using the domain, how many messages were evaluated, and their authentication results.

They can help identify legitimate services that are not configured correctly and unauthorized use of the domain.

Step 5: Review Reports and Strengthen the Policy

Do not move immediately to a reject policy without checking every legitimate sending source.

Review the reports to identify:

  • Authorized email services.
  • Unknown sending IP addresses.
  • SPF failures.
  • DKIM failures.
  • Domain alignment problems.
  • Unexpected sending activity.

Correct legitimate authentication problems before moving to a stronger policy.

Once all important mail streams are properly authenticated, consider moving from p=none to p=quarantine and eventually p=reject, depending on the organization’s requirements.

The transition should be based on actual authentication results rather than an arbitrary deadline.

Step 6: Test Email Authentication

Send test messages through every important sending service to different recipient providers.

For example, test delivery to Gmail and Outlook accounts.

Inspect the message headers or authentication details. A successfully authenticated message should generally display results similar to:

Authentication-Results:

    spf=pass

    dkim=pass

    dmarc=pass

Check the domains associated with each authentication result, not just the pass or fail status.

A passing SPF result and a passing DKIM result do not automatically mean DMARC will pass unless the necessary alignment exists.

Common SPF, DKIM, and DMARC Errors

Incorrect authentication records can cause legitimate messages to fail verification or create opportunities for domain impersonation.

Multiple SPF Records

Publishing separate SPF records for different email providers is a common configuration error.

Instead of creating multiple records, consolidate all authorized sending sources into a single valid SPF record for the relevant domain.

Exceeding the SPF DNS Lookup Limit

Adding too many third-party include statements can cause an SPF evaluation error.

The SPF standard limits DNS-querying terms to 10 during evaluation. Administrators should review nested DNS references and remove unnecessary mechanisms.

Incorrect DKIM DNS Records

A DKIM record may fail when the selector is incorrect, the public key is missing, or the DNS value has been entered improperly.

Always use the exact record generated by the email provider.

Missing Third-Party Email Authentication

Businesses often configure their primary mailbox provider correctly but forget about email marketing platforms, CRM applications, or website notification services.

Every legitimate service sending mail using the company’s domain should be considered when configuring authentication.

DMARC Alignment Failures

An email can pass SPF and DKIM individually but still fail DMARC because the authenticated domains do not align with the visible From domain.

The solution may involve configuring a custom return-path domain for SPF alignment or enabling DKIM signing with the company’s own domain.

Enforcing DMARC Too Early

Moving directly to p=reject without reviewing legitimate email sources can cause important business messages to be rejected.

This is particularly risky when different departments use separate email platforms.

Monitoring and gradual enforcement help reduce this risk.

Email Authentication Does Not Guarantee Inbox Placement

Passing SPF, DKIM, and DMARC is important, but these protocols do not guarantee that an email will reach the primary inbox.

Receiving providers also consider sender reputation, recipient complaints, sending volume, content, and engagement patterns.

Businesses should therefore maintain good email practices alongside authentication.

Maintain a permission-based mailing list. Send promotional messages to recipients who have an appropriate basis to receive them. Avoid purchased or poorly sourced email lists.

Monitor bounce rates. Repeated attempts to deliver messages to invalid addresses can damage sender reputation.

Control sending frequency. Unexpected increases in sending volume can create deliverability problems, particularly for domains with little sending history.

Monitor spam complaints. High complaint rates can affect how receiving systems classify messages.

Maintain consistent sending practices. Use recognizable sender names, relevant content, and clear communication about why recipients receive messages.

Make unsubscribing straightforward. Honor opt-out requests and meet the unsubscribe requirements applicable to your messages and recipient providers.

Google’s current sender guidelines require SPF or DKIM for all senders to personal Gmail accounts. Senders exceeding 5,000 messages per day to Gmail accounts must configure both SPF and DKIM, publish DMARC, and meet additional requirements, including DMARC alignment and one-click unsubscribe for marketing and subscribed messages.

Google recommends keeping the spam rate reported in Postmaster Tools below 0.10% and avoiding a rate of 0.30% or higher.

These are Gmail-specific requirements and recommendations, not universal thresholds for every email provider.

Frequently Asked Questions

What is the difference between SPF, DKIM, and DMARC?

SPF identifies authorized sending sources, DKIM uses digital signatures to verify the integrity of signed message content, and DMARC checks whether SPF or DKIM authentication aligns with the visible sender domain. All three work together to protect email domains.

Are SPF, DKIM, and DMARC required for email deliverability?

Requirements depend on the recipient provider and sending volume. Google requires SPF or DKIM for all senders to personal Gmail accounts and SPF, DKIM, and DMARC for qualifying bulk senders. Configuring all three is a strong general practice for business domains.

Can emails be delivered without DMARC?

Yes. A domain can send email without publishing a DMARC record if the receiving provider accepts the message. However, the domain owner loses DMARC’s reporting and policy-based protection against domain impersonation.

What does a DMARC fail result mean?

A DMARC failure means that neither SPF nor DKIM produced an authenticated result aligned with the visible From domain. The receiving server can use the domain’s DMARC policy to inform its handling decision.

Does DKIM encrypt email messages?

No. DKIM uses cryptographic digital signatures to authenticate the signing domain and verify message integrity. It does not encrypt the message body or make its contents confidential.

How long does it take to configure SPF, DKIM, and DMARC?

The DNS setup itself can be relatively quick, but the overall process depends on DNS propagation, provider configuration, and testing. DMARC monitoring may require a longer period because businesses need to identify legitimate sending services before enforcing a stricter policy.

Can I configure SPF, DKIM, and DMARC myself?

Yes, administrators with access to DNS settings and email provider controls can configure these protocols. However, businesses with several sending services, complex DNS configurations, or strict DMARC policies may benefit from assistance from an experienced email administrator.

Conclusion

Email deliverability depends on several technical and operational factors, but SPF, DKIM, and DMARC provide an essential foundation for authenticating business email.

SPF identifies authorized sending sources, DKIM verifies digital signatures, and DMARC connects those authentication results to the visible sender domain while communicating how authentication failures should be handled.

For businesses, implementing these protocols requires more than publishing three DNS records. Administrators should identify every legitimate sending service, configure authentication correctly, monitor reports, resolve alignment problems, and gradually introduce stronger DMARC policies.

When combined with good list management, responsible sending practices, and consistent monitoring, email authentication helps protect brand identity, reduce spoofing risks, and support more reliable email communication.

Must Read This

Customer Retention Emails: Campaign Ideas for Subscription Businesses
Customer Support Email Templates for Common Business Situations
Customer.io vs Klaviyo: Comparing Email Automation Capabilities
Dedicated IP vs Shared IP for Email Sending
Ecommerce Email Marketing Metrics: Revenue, Conversions and Customer Retention
Email Accessibility Standards for Modern Newsletter Design
Email Automation Workflows Every Growing Business Should Consider
Email Blacklists: Causes, Monitoring and Removal Considerations
Email Bounce Rates Explained: Hard Bounces vs Soft Bounces
Email Deliverability Explained: SPF, DKIM and DMARC