Skip to content

SPF, DKIM, and DMARC Explained for Non-Engineers

SPF, DKIM, and DMARC Explained for Non-Engineers

Your emails are landing in spam. Or worse, they’re disappearing entirely, and the only clue is a bounce message full of jargon about “authentication failures” and “policy rejections.” You’ve heard you need to set up SPF, DKIM, and DMARC, but every guide you find assumes you know what a DNS TXT record is and why your sending domain has something called a “selector.”

Here’s the uncomfortable truth: these three standards aren’t optional decoration. Gmail and Yahoo now require them for bulk senders, and mailbox providers use them to decide whether your message reaches the inbox, the spam folder, or the void. But the good news is that you don’t need to be an engineer to understand what they do, why the order matters, and where most setups quietly break.

This is a plain-English walkthrough of the three authentication standards, the sequence you should implement them in, and the misconfigurations that cause the most silent failures. It’s written for marketers, founders, and operations people who own the sending domain but not necessarily the server.

What Authentication Actually Solves

Email was designed without a way to prove who sent a message. Anyone could claim to be anyone. Authentication standards exist to answer a single question for the receiving mailbox provider: did this message really come from the domain it claims to be from, and was it authorized to do so?

There are two distinct problems being solved, and conflating them is the source of most confusion. The first is spoofing: someone impersonating your domain to phish your customers. The second is legitimate deliverability: proving your own genuine mail is genuine so it doesn’t get filtered. SPF and DKIM address the mechanics of proof. DMARC ties them together and tells the receiver what to do when proof fails.

One number worth internalizing: as of early 2024, Google requires authentication for anyone sending 5,000 or more messages per day to Gmail addresses, and the threshold applies to your whole domain, not per campaign. Even below that threshold, unauthenticated mail increasingly gets filtered. Treat these standards as table stakes, not a competitive edge.

SPF: The List of Approved Senders

SPF, or Sender Policy Framework, is a DNS record that publishes a list of servers allowed to send email on behalf of your domain. When a receiving server gets a message claiming to be from yourdomain.com, it looks up your SPF record and checks whether the sending server’s IP address appears on the approved list.

The record is a single TXT entry at your domain root, and it starts with v=spf1. A simple example might authorize your email provider and nothing else. The receiver returns one of several results: pass, fail, softfail, neutral, or none (no record found). Only “pass” is unambiguously good.

The 10-DNS-lookup limit

Here’s the detail that trips up almost everyone: SPF allows a maximum of 10 DNS lookups to resolve your record. Mechanisms like include:, a, mx, and ptr each trigger lookups, and include: chains count toward the total recursively. If you exceed 10, you get a permerror, and many receivers treat that as a failure. A marketing team that has accumulated five different sending tools over three years can easily blow past the limit without realizing it.

Two practical consequences. First, audit your record whenever you add a sending vendor. Second, some vendors’ own include: statements are lookup-hungry, so a single vendor can consume several of your ten. There are flattening services that resolve includes into static IPs, but they require maintenance because vendor IP ranges change. That trade-off is real: flattening buys you headroom at the cost of ongoing upkeep.

The forwarding problem

SPF breaks when mail is forwarded. If a recipient auto-forwards your message to another address, the forwarding server becomes the sender, and its IP isn’t in your SPF record. The result is a fail at the final destination even though your original send was perfectly legitimate. This is why SPF alone is insufficient and why DKIM exists. It’s also why you should never rely on SPF as your only authentication method.

DKIM: The Cryptographic Signature

DKIM, or DomainKeys Identified Mail, attaches a cryptographic signature to each outgoing message. Your sending server signs selected headers and the body with a private key, and publishes the matching public key in DNS. The receiver verifies the signature. If the message was altered in transit, or signed by someone without the private key, verification fails.

The elegance here is that DKIM survives forwarding. Because the signature travels with the message and doesn’t depend on the sending IP, a forwarded email can still verify at its final destination. That’s the gap SPF leaves open.

Selectors and rotation

DKIM public keys live at a specific address built from a selector, something like selector1._domainkey.yourdomain.com. The selector is just a label that lets you have multiple active keys at once, which matters for rotation. When you rotate keys, you publish the new key under a new selector, start signing with it, and keep the old key live until old messages have expired from queues. Skipping this sequencing causes a spike in failures during the transition.

Key length is another decision point. 1024-bit keys are still common but increasingly considered weak; 2048-bit is the current recommendation and is what most major providers now use by default. If a vendor only offers 1024-bit, ask why.

Where DKIM silently fails

DKIM breaks in subtle ways. If your sending platform modifies the message after signing (adding a footer, injecting a tracking pixel, rewriting a link), the body hash no longer matches and the signature fails. Many ESPs handle this by signing after modification, but some configurations don’t. If your open rates look fine but authentication reports show DKIM failures, suspect post-signing modification first.

A second trap: alignment. A valid DKIM signature only helps DMARC if the signing domain aligns with your From domain. If your ESP signs with its own domain rather than yours, the signature verifies but doesn’t count toward DMARC alignment. You need to configure your ESP to sign with your domain, which usually means adding DNS records they provide.

Where to host the site behind the list

None of the tactics in this article matter if the infrastructure behind them is slow,
poorly configured, or capped at a mailbox size you outgrow in a month. If you are setting up
a site, a landing page, or a sending domain from scratch, Hostinger is a sensible starting point: entry plans are cheap enough to
experiment with, the control panel exposes DNS records for SPF, DKIM and DMARC without a support
ticket, and the VPS tier is there when you outgrow shared hosting. What matters more than the
headline price is that it scales predictably as the list grows.

DMARC: The Policy That Ties It Together

DMARC, or Domain-based Message Authentication, Reporting and Conformance, is the layer that tells receivers what to do based on SPF and DKIM results. It requires that at least one of them passes and aligns with the From domain. Alignment means the domain that passed matches the domain the recipient sees, either exactly (strict) or as an organizational domain (relaxed).

The DMARC record lives at _dmarc.yourdomain.com and specifies a policy: none (monitor only), quarantine (send failures to spam), or reject (block failures outright). It also specifies where to send aggregate reports, which are XML files summarizing authentication results.

Start at p=none, always

The single most common mistake is publishing p=reject on day one. If any legitimate mail stream fails authentication, you’ve just blocked it. Start at p=none with a reporting address, collect aggregate reports for at least two to four weeks, and identify every source sending mail as your domain. Only move to quarantine and then reject once you’ve confirmed all legitimate sources pass.

The reporting is the point. DMARC aggregate reports tell you which IPs are sending as your domain, which pass, which fail, and why. That data is how you find the forgotten marketing tool, the legacy contact form, or the spoofing attempt. Reading raw XML is unpleasant; use a DMARC reporting service or parser. This is the one place I’d spend money early rather than build a spreadsheet.

Policy progression and the pct tag

You don’t have to jump straight from none to reject. The pct tag lets you apply a policy to a percentage of failing mail, so p=quarantine; pct=25 quarantines a quarter of failures. This staged rollout catches problems without a full outage. Move in steps: none, then quarantine at partial pct, then full quarantine, then reject. Each step gets a week or two of monitoring.

One contested point: how long to stay at p=none. Vendors selling DMARC tools will tell you to move fast; practitioners who’ve been burned will tell you to wait for clean reports. The honest answer is that it depends on how many unknown senders exist. A company with a decade of accumulated tools should budget months, not days.

The Setup Order That Actually Works

Sequence matters because each standard depends on the previous one being correct. Doing them out of order means debugging against a moving target.

  1. Inventory your senders. Before touching DNS, list every system that sends email as your domain: ESP, CRM, transactional provider, helpdesk, invoicing tool, website contact form, calendar invites. You cannot authenticate what you don’t know exists.
  2. Publish SPF. Build one record covering all verified senders. Keep it under 10 lookups. Test with a checker before and after.
  3. Configure DKIM per sender. Each sending platform issues its own selector and keys. Add the DNS records, enable signing with your domain, and send a test to a Gmail address to confirm the signature verifies.
  4. Publish DMARC at p=none. Add a reporting address. Wait for reports to accumulate.
  5. Reconcile reports against your inventory. Every sending IP in the reports should map to a known system that passes. Unknown senders are either forgotten tools to authenticate or spoofers to block.
  6. Progress the policy. none to quarantine to reject, with monitoring at each step.

Do not skip step one. Teams that start with DNS records and work backward spend weeks chasing failures caused by senders they forgot to authorize.

Common Misconfigurations Worth Checking Today

Most authentication failures aren’t exotic. They’re the same handful of mistakes repeated across organizations.

  • Multiple SPF records. You may only have one SPF record per domain. Two TXT records starting with v=spf1 produce a permerror. Merge them into one.
  • Missing the root vs. subdomain distinction. SPF and DMARC records on the root domain don’t automatically cover subdomains like mail.yourdomain.com or news.yourdomain.com. If you send from subdomains, they need their own records or a DMARC record with a sp= tag.
  • DKIM signing with the ESP’s domain. The signature verifies but doesn’t align, so DMARC still fails. Configure signing with your own domain.
  • Post-signing modification. Footers, tracking rewrites, or content filters applied after signing break the body hash. Check with your ESP.
  • SPF include bloat. Years of accumulated vendors push you over 10 lookups. Audit and prune.
  • DMARC reports going nowhere. An address that bounces or a mailbox nobody reads means you’re flying blind. Confirm reports actually arrive.
  • Jumping to reject too early. The classic self-inflicted outage. Stage it.

What Good Looks Like, and What to Measure

Once everything is in place, you should see SPF pass, DKIM pass with alignment, and DMARC pass on your legitimate mail. Your DMARC aggregate reports should show near-zero failures from known senders. If you’re running a custom domain with a DMARC policy at quarantine or reject, you’ve also closed the door on most direct domain spoofing, which is the security payoff.

Track three things monthly: the percentage of your mail passing DMARC, the count of unknown sending sources in reports, and any change in inbox placement. A sudden drop in pass rate usually means a new tool was added without authentication, or a vendor changed its infrastructure. The reports will tell you which within a day if you’re reading them.

One honest caveat: authentication improves deliverability but doesn’t guarantee it. Content, engagement, list hygiene, and sending reputation still matter. Authentication removes a category of failure; it doesn’t manufacture a good sender reputation on its own.

Related reading

Conclusion

SPF tells receivers which servers may send for your domain. DKIM proves the message wasn’t altered and survives forwarding. DMARC ties the two together, enforces a policy, and gives you the reporting that makes the whole system observable. Implement them in that order, start DMARC at p=none, and don’t advance the policy until your reports are clean.

The work isn’t glamorous, and the failure modes are quiet. But authentication is the foundation everything else in email rests on. Get it right once, monitor it monthly, and you can stop worrying about whether your mail is being rejected for reasons you can’t see.

Disclosure: this article contains an affiliate link. If you buy through it we may earn a commission at no extra cost to you. We only link to services we would recommend on merit.

Leave a Reply

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