Email authentication (SPF, DKIM, DMARC)

DNS records and signatures that let receiving mail servers confirm a message really comes from the domain in its From address.

By Azande PorterUpdated 4 min read

What is email authentication?

Email authentication is a set of DNS records and cryptographic signatures that let a receiving mail server check whether a message really came from the domain it claims, using three standards: SPF, DKIM, and DMARC.

Without it, anyone can put your domain in a From line. With it, a receiving server can tell your newsletter from a forgery and treat each accordingly. Mailbox providers now require it: Gmail asks every sender for SPF or DKIM and asks high-volume senders for all three, as covered in bulk sender requirements.

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

Each answers a different question.

SPF (Sender Policy Framework), defined in RFC 7208, asks: is this server allowed to send for this domain? The domain publishes a DNS record listing the hosts that may send its mail, and the receiver checks the sending server against it. SPF checks the envelope sender (the technical return address), not the From address your readers see. An SPF check is also limited to 10 DNS-querying terms, which matters once several tools send as your domain.

DKIM (DomainKeys Identified Mail), defined in RFC 6376, asks: did this domain sign this message, and is it unchanged? The sender signs selected headers and the body with a private key, and publishes the public key in DNS under a selector, such as s1._domainkey.yourdomain.com. Gmail requires DKIM keys of at least 1024 bits for personal Gmail accounts and recommends 2048.

DMARC, now defined in RFC 9989 (published in May 2026, replacing RFC 7489), asks: does the domain readers see match a domain that passed? It passes when SPF or DKIM passes for a domain aligned with the visible From domain. The DMARC record also states a policy for failures (none, quarantine, or reject) and where to send reports.

What is DMARC alignment?

Alignment means the domain that passed SPF or DKIM matches the domain in the From address. It is the part to check whenever a platform sends on your behalf.

Say your edition comes from hello@yourdomain.com, sent through a newsletter platform. If the platform signs with its own domain and uses its own return address, SPF and DKIM both pass for the platform's domain, but neither aligns with yours, so DMARC fails. Authenticating your custom domain in the platform's settings, usually by adding the DNS records it gives you, makes it sign as yourdomain.com and fixes the mismatch.

Gmail and Yahoo require bulk senders' From domains to align with either the SPF or the DKIM domain, and Yahoo accepts relaxed alignment, where a subdomain such as mail.yourdomain.com counts.

Do newsletter writers need SPF, DKIM, and DMARC?

If you send from your own domain, yes. Gmail, Yahoo, and Microsoft's Outlook.com all accept a DMARC policy of p=none as the minimum for high-volume senders, and Microsoft recommends p=reject.

A practical path:

  1. Authenticate your domain in your newsletter platform before the first send. The platform switching guide puts this ahead of everything else in a move.
  2. Publish a DMARC record at p=none with a reporting address, then read the reports.
  3. List every tool that sends as your domain: the newsletter platform, your work inbox, invoicing, scheduling. Each needs to pass and align.
  4. Move to quarantine or reject only once legitimate mail passes consistently.

Does passing authentication guarantee the inbox?

No. Authentication proves who sent a message, not that recipients want it. Gmail may mark unauthenticated mail as spam or reject it with a 5.7.26 error, and Outlook.com sends non-compliant high-volume mail to Junk, but passing only gets you judged on everything else. Your sender reputation carries over from past sends. Your spam complaint rate reflects how readers react. All of it feeds deliverability, and none of it shows up in a delivered count. The guide to delivered vs sent vs opened explains why.

Forwarding is a known weak spot. A forwarding server is not listed in your SPF record, so SPF can fail even for genuine mail. A DKIM signature survives forwarding as long as the message is not changed, and Microsoft recommends ARC for forwarding services and mailing lists.

Platform details checked

How Distinctful helps

Distinctful never sends email, so authentication is set up between your domain and your newsletter platform, not in Distinctful. What Distinctful does is read what your platform reports: subscribers and editions from beehiiv, Kit, or Ghost, with per-send opens and clicks for beehiiv and Kit. See the Ghost integration.

Related terms

Go deeper

Bring your newsletter numbers together

Connect beehiiv, Kit, or Ghost and review editions beside the posts that promoted them.