Skip to content
YHP DMARC

Understanding DMARC

What is SPF?

SPF lists the servers allowed to send mail for a domain. What it checks, what it misses, and its 10-lookup limit.

SPF (Sender Policy Framework) is a TXT record on your domain that lists the servers allowed to send mail for it. When a message arrives, the receiver checks whether the sending server's IP address is on that list.

v=spf1 include:_spf.google.com include:sendgrid.net ip4:203.0.113.10 -all

This record says: Google Workspace, SendGrid and one specific server may send for this domain, and everything else should fail.

What SPF actually checks

SPF checks the envelope sender (also called the Return-Path or MAIL FROM), not the From address people see. Many services, such as newsletter platforms, use their own envelope domain for bounces. Their mail can pass SPF for their domain while saying nothing about yours. DMARC fixes this with alignment.

The rules that catch people out

  • One record only. Two v=spf1 records on the same name make SPF fail with a permanent error. Merge them.
  • Ten DNS lookups. Each include, a, mx, exists, ptr and redirect costs a lookup, including the ones nested inside includes. Over 10, SPF fails for every message. Use the SPF surveyor to count yours.
  • Forwarding breaks SPF. When mail is forwarded, the forwarding server is not on your list. DKIM survives forwarding, which is why you want both. See forwarding.
  • Ending matters. -all fails unlisted servers, ~all soft-fails them. With DMARC enforcing, ~all is fine and is the most common choice. Never use +all.

The full syntax is in SPF record syntax.

See it on your own domain.

Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.

Start free