Threat Intel · 06 Oct 2026

SPF, DKIM and DMARC: a field guide

Three DNS records decide whether anyone can send email as your domain. What each one does, the common mistakes, and a safe rollout path.

← Threat Intel / Email

Email was designed without sender verification. SPF, DKIM and DMARC bolt it on through DNS, and together they decide whether a criminal can send mail that appears to come from your domain.

SPF — who may send

SPF is a TXT record listing the servers allowed to send mail for your domain.

example.com.  TXT  "v=spf1 include:spf.protection.outlook.com -all"

Common mistakes:

  • More than 10 DNS lookups. Every include, a, mx, ptr, exists and redirect counts, including nested ones. Exceeding 10 causes a permerror and SPF fails entirely.
  • Multiple SPF records. Only one v=spf1 record is allowed per name.
  • Ending in +all or ?all, which authorises the whole internet.

DKIM — was the message altered

DKIM signs outgoing messages with a private key; the public key is published at selector._domainkey.example.com. Microsoft 365 uses selector1 and selector2; Google Workspace uses google by default.

DMARC — what to do on failure

DMARC ties SPF and DKIM to the visible From domain (alignment) and tells receivers what to do when both fail.

_dmarc.example.com.  TXT  "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"

A safe rollout path

  1. Publish p=none with a rua address and collect aggregate reports for a few weeks.
  2. Fix every legitimate sender that fails alignment.
  3. Move to p=quarantine, optionally with pct to ramp up.
  4. Finish at p=reject.

Run our free Email security check to grade your domain in seconds.