# SPF, DKIM and DMARC Done Right: A Field Guide

> A field guide to SPF, DKIM and DMARC, the three records that decide whether your mail reaches the inbox, and the failure modes that silently break them.

Canonical: https://www.cresca.xyz/blog/email-deliverability-spf-dkim-dmarc-done-right
Author: Lalit Kumar Jangid
Published: 2026-09-26
Last updated: 2026-10-26

Most deliverability advice tells you to "set up SPF, DKIM and DMARC" and stops there. The records themselves are a few lines of DNS. What actually determines whether your mail lands is whether those records are correct under real conditions: forwarded messages, third-party senders, subdomains and the gradual rollout of enforcement that turns a misconfiguration from a warning into a silent outage.

## What do SPF, DKIM and DMARC each actually prove?

SPF proves a message came from a server the domain owner authorised, checked against the envelope sender rather than the visible From header. DKIM proves the sending server signed selected headers and the body with its private key, and it survives forwarding. DMARC authenticates nothing itself; it checks that SPF or DKIM aligns with the visible From domain.

SPF answers a narrow question: did this message originate from a server that the domain owner authorised? It is a list of IP addresses and includes, evaluated in order, capped at ten DNS lookups. It authenticates the envelope sender, not the visible From header, which is the detail most teams miss. When a message is forwarded by a mailing list, the envelope sender is often rewritten, so SPF fails even though nothing is wrong.

DKIM ([RFC 6376](https://datatracker.ietf.org/doc/html/rfc6376)) takes a different approach. The sending server signs selected headers and the body with a private key, and publishes the public key in DNS at a selector you choose. Because the signature travels with the message, it survives forwarding intact. This is why DKIM is the record that matters most in practice, and why a message can fail SPF and still pass authentication overall.

DMARC ([RFC 7489](https://datatracker.ietf.org/doc/html/rfc7489)) does not authenticate anything itself. It tells receiving servers what to do when SPF and DKIM disagree with the visible From domain, and where to send reports. That alignment requirement is the point: DMARC closes the gap where a message passes SPF for one domain while claiming to be from another.

## The failure modes that do not show up in a checker

An online DNS checker will happily report all three records present and green while your mail still fails. The common reasons:

- **Two SPF records.** [RFC 7208](https://datatracker.ietf.org/doc/html/rfc7208) permits exactly one. A second record causes a permanent error rather than a merge, and many DNS panels allow you to create it without complaint.
- **Lookup limit exceeded.** Includes are counted recursively. A record with several third-party includes can exceed ten lookups, at which point SPF returns a permanent error and fails outright.
- **DKIM selector mismatch.** Providers rotate keys and expect you to publish the new selector. If you only add, never remove, you accumulate stale selectors that some receivers still try to use.
- **DMARC on the wrong host.** The DMARC record is a TXT record published at `_dmarc.yourdomain`, not at the domain itself. Subdomains without their own `_dmarc` record fall back to the organisational domain's record, where the `sp` tag sets the policy that applies to them.
- **Alignment failure.** A third-party sender may pass SPF for its own domain and pass DKIM, yet still fail DMARC because neither aligns with your From domain.

## How do you roll out DMARC without losing mail?

Start at `p=none` with a reporting address and collect aggregate reports for at least two weeks. Authenticate every legitimate source the reports reveal, then move to `p=quarantine` at a percentage below 100 and watch the effect. Move to `p=reject` only once the reports show full alignment for a sustained period.

Do not begin at enforcement. Start at `p=none` with a reporting address, and collect aggregate reports for at least two weeks. The reports are XML and unreadable raw; use a parser. What you are looking for is every source sending mail as your domain, including ones you have forgotten about: an old marketing tool, an invoice system, a developer's laptop using a local SMTP relay.

Once the legitimate sources are all authenticating, move to `p=quarantine` with a percentage below 100 so you can watch the effect before it applies broadly. Only then move to `p=reject`. Teams that skip straight to reject frequently discover an unmonitored sending source the hard way, when transactional mail stops arriving and customers notice before the engineering team does.

## How this looks inside Cresca

Cresca sends from your own verified sending domain. Its domain setup handles the SPF and DKIM records through Cloudflare DNS and verifies them before the domain is used for sending. DMARC is a policy for your whole domain, so check whether a record already exists and roll it out as described above. Sending runs through a queue rather than synchronously, so a campaign is paced within your plan's limits instead of being fired in one burst.

Hard bounces and complaints are suppressed automatically, and sending pauses when bounce or complaint rates get too high. That matters alongside authentication work because repeat delivery attempts to addresses that no longer exist are one of the fastest ways to damage a sending reputation, however well your records are configured.

## Should you use a separate sending subdomain?

A separate sending subdomain is usually worth the setup. It isolates your marketing reputation from your transactional reputation, so a complaint spike on a campaign does not affect password resets. It also gives you a clean reputation history to warm without dragging in whatever the root domain accumulated from previous tools.

The tradeoff is that a new subdomain starts with no history at all, which means slow ramp-up. If you already send marketing from the root domain and it has good standing, moving can temporarily reduce placement. Decide once and commit: switching sending domains repeatedly resets the clock each time.

## A worked rollout order

The sequence matters, because each step depends on the previous one being verified.

1. Publish DKIM first. It survives forwarding, so it is the record that does the most work.
2. Fix SPF to exactly one record, and count the lookups to confirm you are under ten.
3. Send a test and read the headers. Confirm DKIM passes with the selector you published.
4. Publish DMARC at `p=none` with a reporting address and wait two weeks.
5. Work through the reports and authenticate every legitimate source you find.
6. Move to `p=quarantine;pct=25`, watch for a week, then raise the percentage.
7. Move to `p=reject` only once aggregate reports show full alignment for a sustained period.

If you send through multiple systems, repeat the SPF, DKIM and DMARC steps for each one. A single unauthenticated path is enough to fail DMARC for messages that look identical to your authenticated ones.

## How do you verify that SPF, DKIM and DMARC actually work?

Send to a seed address at each major provider and read the full headers. Look for `Authentication-Results` and confirm three outcomes: `spf=pass`, `dkim=pass` with the selector you expect, and `dmarc=pass`. A result of `dmarc=pass` via SPF only, with DKIM failing, means forwarding will break your alignment and you should fix DKIM before you enforce.

Repeat this after any change to DNS, any provider migration and any new sending service. Authentication is not a one-time setup; it is a property that quietly decays as infrastructure changes around it.

## Pricing

Cresca starts with a Free plan that runs for 30 days with no credit card required, and paid plans raise the limits as you grow; see [current plans and limits](https://www.cresca.xyz/pricing).

## The short version

Publish exactly one SPF record and keep it under ten lookups. Publish DKIM and keep selectors current. Roll DMARC from `p=none` through quarantine, at partial percentage, to reject, with reporting active the whole way. Verify with real headers rather than a DNS checker, and re-verify after every infrastructure change. None of this SPF, DKIM and DMARC work is complicated, but all of it is easy to leave half-finished in a way that only becomes visible when mail stops arriving.
