Skip to content
Writing
DeliverabilityDNSSPFDKIMDMARC

The Complete Guide to SPF, DKIM, and DMARC Alignment in 2026

Everything you need to know about SPF, DKIM, and DMARC in 2026: syntax rules, the 10-lookup SPF limit, strict vs relaxed alignment, and debugging with dig.

Tayyab MughalFounder & AI Chief9 min read

Why authentication is mandatory in 2026

In 2024, Google and Yahoo introduced strict authentication requirements for all bulk senders. In 2026, these rules apply universally: any domain sending transactional or automated mail without valid SPF, DKIM, and DMARC records faces immediate throttling, spam folder placement, or outright 550 SMTP rejections.

Understanding how the authentication triad works together is essential for keeping transactional mail out of the spam folder.

1. Sender Policy Framework (SPF)

SPF is a DNS TXT record that publishes which IP addresses and services are authorized to send mail on behalf of your domain (`Return-Path` / `Mail From`).

Crucial limitation: The RFC 7208 specification limits SPF evaluation to **10 DNS lookups**. Exceeding 10 lookups causes SPF `permerror`, resulting in authentication failure.

// Recommended SPF Record for SadaSend:
yourdomain.com.  TXT  "v=spf1 include:_spf.sadasend.com ~all"

2. DomainKeys Identified Mail (DKIM)

DKIM provides cryptographic tamper protection. Your sending server signs the email headers and body with a private key, and mailbox providers verify the signature against the public key published in your DNS under a specific selector (`s1._domainkey.yourdomain.com`).

SadaSend generates high-security 2048-bit RSA key pairs for every verified domain with automated selector rotation.

3. DMARC: Policy and Alignment

DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties SPF and DKIM together. It specifies what receiving servers should do with unauthenticated emails (`none`, `quarantine`, or `reject`) and requires **domain alignment**.

Alignment means that the domain in the visible `From:` header matches the authenticated SPF domain and/or the DKIM signing domain.

// Recommended DMARC Record:
_dmarc.yourdomain.com.  TXT  "v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com; pct=100; sp=reject"

Verification Cheat Sheet with dig

You can inspect and verify your DNS records directly from your terminal:

# 1. Check SPF record:
dig +short TXT yourdomain.com | grep "v=spf1"

# 2. Check DKIM selector:
dig +short TXT s1._domainkey.yourdomain.com

# 3. Check DMARC policy:
dig +short TXT _dmarc.yourdomain.com