Marketing

SPF, DKIM and DMARC: 10 Essential Checks for Better Email

SPF, DKIM and DMARC – Email Deliverability: SPF, DKIM and DMARC in Plain English

In this guide: SPF, DKIM and DMARC explained in plain English: what each record does, how to set them up, and how to check your email deliverability.

You send an important email — a proposal, an invoice, an order confirmation — and it lands in spam or disappears. Often, the reason is missing email authentication. SPF, DKIM and DMARC provide different authentication and policy signals. They do not prove the content is trustworthy or guarantee inbox placement.

Why deliverability matters

  • Business communication: clients must receive your emails.
  • Website emails: contact forms, password resets, and order confirmations must arrive.
  • Marketing: newsletters in spam don’t get read.
  • Brand protection: without authentication, scammers can more easily send emails pretending to be your domain.

Major providers like Gmail and Yahoo now require authentication for bulk senders, and all senders benefit from proper setup.

Think of it like a letter:

  • SPF = a list of approved post offices that may send letters for you.
  • DKIM = a digital signature covering selected message elements on each letter.
  • DMARC = your instructions for what to do with letters that fail the checks — plus reports about them.

SPF explained

SPF (Sender Policy Framework) is a DNS TXT record listing which servers are allowed to send email for your domain.

Example:

v=spf1 include:_spf.google.com include:sendgrid.net ~all
  • v=spf1 — this is an SPF record.
  • include: — authorizes a service’s sending servers (here, Google Workspace and SendGrid).
  • ~all — soft fail for anything else (mark as suspicious). -all expresses fail; the receiver still decides how to handle the message.

Rules:

  • Only one SPF record per domain. If you use multiple services, combine them into one record.
  • SPF has a limit of 10 lookup-causing terms during evaluation, including recursive evaluation — too many include: statements can break it.
  • Add every service that sends as your domain: business email, website/SMTP service, marketing platform, CRM, and helpdesk.

DKIM explained

DKIM (DomainKeys Identified Mail) adds a digital signature to each email. The sending server signs messages with a private key; receiving servers verify it using a public key published in your DNS.

  • Verifies the signed elements according to the signing and validation rules; it is not a guarantee about every aspect of the message.
  • Associates a valid signature with a signing domain; DMARC additionally evaluates alignment with the visible author domain.

Setup:

  1. In your email service’s admin panel, generate DKIM keys.
  2. Add the provided DNS record (usually TXT or CNAME) with a selector name, e.g., google._domainkey.yourdomain.com.
  3. Activate DKIM signing in the service.

Each sending service (Google Workspace, Microsoft 365, your transactional email provider, your newsletter platform) should have its own DKIM record.

DMARC explained

DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receiving servers what to do if an email fails SPF and DKIM checks — and sends you reports.

DMARC also checks alignment: the domain in the visible “From” address must match the domain authenticated by SPF or DKIM.

Example DNS TXT record at _dmarc.yourdomain.com:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com

Policies:

  • p=none — monitoring preference; inspect an existing policy before changing it.
  • p=quarantine — send failing emails to spam.
  • p=reject — block failing emails entirely.

Recommended path:

  1. Inventory the existing policy and legitimate mail streams; do not weaken current enforcement merely to follow a tutorial.
  2. Fix any legitimate services that fail (add them to SPF, set up DKIM).
  3. Move to p=quarantine, then eventually p=reject for strong protection against spoofing.

DMARC reports are XML files; free and paid DMARC report analyzers make them readable.

Checking your setup

  1. Send an email to Gmail and open “Show original.” You should see SPF: PASS, DKIM: PASS, DMARC: PASS.
  2. Use online DNS/email authentication checkers to look up your SPF, DKIM, and DMARC records and find errors.
  3. Use a mail tester service for an overall deliverability score.
  4. Review DMARC reports to discover unknown services sending as your domain.
  5. Check blacklists if emails still land in spam.

Beyond authentication:

  • Send only to people who opted in.
  • Include easy unsubscribe links in marketing emails.
  • Keep spam complaint rates low.
  • Warm up new domains and IPs gradually for bulk sending.
  • Avoid spammy content and misleading subject lines.

For WordPress sites, pair these records with proper SMTP — see How to Set Up SMTP in WordPress.

Further reading: RFC 9989: current DMARC specification

Key Takeaways: SPF, DKIM and DMARC

  • SPF lists who may send for your domain — one record, combined services.
  • DKIM signs each email to prove authenticity.
  • DMARC connects authentication with author-domain alignment, policy preferences and reporting; plan changes against the actual deployment.
  • Check headers for PASS results and monitor DMARC reports.

1. Inventory the mail streams before changing SPF

List the services that send business, application and campaign messages. Record the responsible owner, visible sender, envelope arrangement and signing configuration where available. A business mailbox, website notification service and newsletter platform may use different identities even when the recipient sees the same brand.

Do not assume that every account containing the domain name needs the same DNS change. Inspect the provider’s current instructions for the specific sending arrangement. An unused legacy service and an active order-notification route require different decisions. Keep unknown sources marked for investigation rather than immediately authorizing them.

Our email versus web hosting guide explains the operational distinction. A correct inventory makes authentication work easier to review and reduces the risk of breaking a legitimate sender during cleanup.

2. Understand the identity SPF actually checks

RFC 7208 describes SPF around the MAIL FROM and HELO identities. Do not assume the check directly validates the address a reader sees in the From header. That distinction matters when a service uses a provider-controlled return path.

Record the relevant domain for a controlled test message and compare it with the service configuration. The task is to understand the actual route, not to paste every vendor include into the root domain indiscriminately. Keep the provider’s documentation and the observed header evidence together.

An SPF pass can be useful evidence without establishing author-domain alignment or recipient inbox placement. State what the check demonstrates and leave other questions for the corresponding evidence. This avoids treating one positive result as a complete deliverability diagnosis.

3. Review SPF complexity before merging services

The protocol limits lookup-causing terms during evaluation, including nested processing. Counting only the visible include statements is not a complete assessment. Avoid publishing a universal record for readers to copy into unrelated domains.

Use an appropriate validation process and current provider instructions. Do not flatten provider-managed ranges manually without a maintenance plan; an apparently successful snapshot can become outdated when a service changes its infrastructure. Record who owns the record and how future changes will be reviewed.

Preserve the approved previous configuration and a change record. DNS editing affects real mail flows. A tutorial example should remain an example, with placeholder domains and explicit limitations, rather than being presented as a production-ready answer for every business.

4. Verify DKIM at the sending service

Publishing a key-related DNS record is only one part of an operational configuration. Confirm that the intended service is signing the actual message stream and inspect the relevant signing domain and selector in a controlled received message. Follow the provider’s supported activation and rotation process.

Do not expose private keys or administrative credentials in screenshots or support requests. A public DNS key and the private signing material have different purposes. The issue register should record which configuration was checked without becoming a repository of secrets.

Our email header guide provides complementary interpretation questions. A valid signature is not a testimonial about the sender’s honesty or the content’s safety. Authentication evidence and message trustworthiness remain distinct.

5. Evaluate DMARC alignment separately from SPF pass

The current DMARC specification, RFC 9989, was published in May 2026 and obsoletes RFC 7489 and RFC 9091. DMARC passing requires a passing SPF or DKIM result with the relevant identifier aligned to the author domain. Strict and relaxed alignment are different modes.

A message can therefore pass an authentication check for a domain without satisfying the intended author-domain relationship. Inspect the actual identifiers and results instead of looking only for the word pass. Do not assume that two similar-looking addresses are aligned under every configuration.

Keep the current standard and the receiving provider’s requirements distinct. A beginner explanation does not replace reviewing the full deployment requirements, particularly for an enforcement policy. Have the responsible mail administrator evaluate the actual streams and applicable behaviour before changing production.

6. Preserve existing policy while investigating

Do not automatically change an established DMARC enforcement policy to monitoring because an article says start here. First identify the current arrangement, the legitimate sources and the reason for the reported failure. A troubleshooting shortcut can reduce an existing protection without solving the underlying identity problem.

Plan any authorized policy change with evidence, ownership and a recovery route. An enforcement preference should not be described as a promise that every receiver will take one identical action. Keep the provider’s actual response separate from the domain owner’s published preference.

When the configuration is complex, obtain appropriate specialist review. This article is an educational workflow and does not certify a domain as protected or compliant. Record unresolved questions rather than announcing a complete solution based on one test.

7. Apply recipient requirements to the actual sender

Gmail’s sender guidance distinguishes requirements for all senders and bulk senders. It also describes authentication and alignment expectations. Do not copy a requirement from one provider and present it as a universal rule for every receiving system.

Review the applicable sender category, message type and provider guidance. Marketing permission, complaint handling and unsubscribe behaviour are separate operating responsibilities. An authentication pass does not grant permission to send a campaign to acquired or scraped addresses.

Our campaign platform guide helps distinguish newsletter operations from ordinary mailboxes. Keep current limits and requirements attached to the service and date checked, rather than assuming that an old plan comparison remains accurate.

8. Test the whole application path

Use controlled test recipients and sample content. Confirm that the original application event generated the intended message, then examine transport and recipient evidence. A successful plugin test button does not necessarily establish that order confirmations or password-reset journeys use the same route.

Our SMTP troubleshooting guide separates application submission, provider acceptance and recipient handling. Do not repeatedly replay live orders or payments to produce test messages. Use the supported safe test process for the application involved.

Record timestamps, message type and redacted evidence. Never post reset links, tokens or customer records publicly while seeking help. A concise diagnostic record can be useful without retaining the entire contents of every message indefinitely.

9. Review reports with clear limitations

Authentication reports can reveal useful patterns, but their meaning depends on the reporting source and the available data. Keep the report period, source and limitations visible. Do not assume that a missing report proves no mail was sent or that every unfamiliar source is automatically malicious.

Assign an owner to investigate unexplained streams. Compare them with the inventory, application changes and provider documentation. A report is an input to a decision, not an instruction to authorize every observed source or to remove every source you do not immediately recognize.

Consider privacy and access when choosing a report-processing arrangement. Explain which service receives information and who can review it. Do not send sensitive diagnostic material to an unrelated tool merely because it promises a simple score.

10. Maintain SPF and authentication ownership

Recheck the relevant configuration when a service is added, replaced or retired. A one-time setup can become outdated after a provider migration or a change in application sending. Keep the domain administrator and application owner aligned on the intended behaviour.

Use the DNS and email troubleshooting guide for supporting checks. Preserve a dated change record and compare controlled messages after material changes. Do not treat the presence of three DNS records as evidence that every message stream works.

Separate completion from impact. A corrected SPF configuration is a technical acceptance result, not proof of increased revenue or a guaranteed inbox percentage. Continue investigating content, recipient handling and operational problems when authentication is working but the intended outcome remains absent.

Relevant professional email support

Promotional recommendation: KAWEDMA professional email is an option to consider for business mailboxes. Ask about the specific authentication setup, supported sending uses and administration responsibilities before changing a live domain. This recommendation does not guarantee inbox placement or establish that every campaign or application can use the same mailbox service.

KAWEDMA also offers development and hosting services through its main site. Request a written scope when seeking help with a WordPress sending integration. A hosting purchase is not a substitute for a correct sender inventory or a permission-based marketing process.

SPF and identity
SPF and identity. Original explanatory diagram.
Authentication evidence
Authentication evidence. Original explanatory diagram.
Authentication maintenance
Authentication maintenance. Original explanatory diagram.

A hypothetical SPF and sender-inventory exercise

Consider a fictional business using a mailbox service, a website notification provider and a newsletter platform. The team wants to understand why one controlled message failed an authentication check. This is an educational scenario, not a diagnosis of this website or evidence that any real domain is misconfigured.

The investigator begins with the exact message stream and timestamp. They identify the visible sender, the relevant envelope domain and the signing domain from appropriate evidence. They do not assume that the website’s domain is automatically the identity checked by SPF. Unknown values remain unknown until the application or provider configuration establishes them.

Next, the investigator compares the stream with current provider instructions and the approved inventory. An old service that no longer sends is recorded for a separate authorized cleanup decision. A new legitimate application needs its actual supported configuration, not a copied include value from an unrelated tutorial. The existing policy remains in place while the evidence is reviewed.

The team then writes an acceptance check for the proposed correction. A controlled message should demonstrate the intended authentication and alignment results under the chosen configuration. The record explains what that observation proves and what it does not. It does not claim that one successful message guarantees future inbox placement or validates the entire marketing process.

If a recipient still cannot find the message, the investigation continues through the relevant transport and handling evidence. The team does not repeatedly resend real invoices or reset links merely to generate more samples. Test data and redacted diagnostic details are used through an appropriate support route.

Finally, another authorized colleague reviews the decision record. They should understand which source was checked, who approved the change and which mail stream was tested. If the evidence is incomplete, the item remains open. A readable worksheet is more useful than an unexplained collection of green scores from several unrelated checking tools.

Keep this exercise separate from production configuration. Do not publish private keys, account credentials or customer message contents with the example. Review the inventory again when services or responsibilities change, and maintain a clear distinction between a technical authentication result, a provider’s handling decision and a business outcome.

A practical closeout note names the corrected configuration, test conditions, observed result and next review owner. It should also preserve any remaining uncertainty so future administrators do not interpret a narrow successful test as a complete audit.

Z
zasma171

Writes for Hostreta about the topics covered in this article.

Comments (0)

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

Ad
Affiliate links
Tools we recommend
Protect Your Website with Automated Daily Backups
$2.09
Get it
the easiest way to manage all of your social media accounts
$29
Get it
Starter Website Get online, properly
$249
Get it
google workspace Business Starter
$3.75
Get it
Nord Vpn Cybersecurity. Built for Everyday Use
$8.99
Get it
More hosting options · affiliate
AI SiteBuilder
View plans
AI Application Hosting
View plans
Shared Hosting
View plans
Reseller Hosting
View plans
Managed WordPress · Rocket.net
View plans
Unmanaged VPS Hosting
View plans
Managed VPS Hosting
View plans
Virtual Dedicated Servers
View plans

We may earn a commission on purchases made through these links, at no extra cost to you.

Ad
Ad

$ top hosting picks

affiliate
★★★★★

KAWEDMA Website Services

See optionsCheck current plans and terms
  • Explore website setup services
  • Choose a scope that fits your project
  • Confirm features with KAWEDMA
Explore KAWEDMA →
affiliate link · we may earn a commission
★★★★★

Managed WordPress Hosting

See plansCurrent terms on provider website
  • Managed hosting for WordPress
  • Powered by Rocket.net
  • Compare current plan specifications
View WordPress plans →
affiliate link · we may earn a commission
★★★★★

AI SiteBuilder

See plansCheck current offer and renewal terms
  • Explore AI-assisted website creation
  • Review included tools and features
  • Choose a plan for your project
Explore SiteBuilder →
affiliate link · we may earn a commission

Never miss a new article

Join thousands of developers and builders getting a weekly digest of the best tech articles.