Skip to content
MailVet
Free tool

SPF record checker

Check a domain's SPF record: every mechanism explained, DNS lookups counted against the limit of 10, and the common mistakes flagged.

Results appear here. Lookups run in your browser through public DNS-over-HTTPS.

What is SPF?

SPF (Sender Policy Framework) is a TXT record that lists the servers allowed to send email for a domain. Receiving servers compare the sending IP with that list. Since 2024, Gmail and Yahoo require SPF or DKIM from every sender, and both plus DMARC from bulk senders.

A domain should have exactly one SPF record, it must stay within 10 DNS lookups including nested includes, and it should end with ~all or -all. More in /glossary/spf-record.

A typical SPF record

DNS TXT record
example.com.  TXT  "v=spf1 include:_spf.google.com include:sendgrid.net ip4:203.0.113.10 ~all"

Common SPF problems

  • ✓One record per domain, starting with v=spf1
  • ✓Ten DNS lookups or fewer, includes counted
  • ✓Ends with ~all while you test, -all once you're sure
  • ✓Every service that sends for you is included
  • ×Two or more v=spf1 records (an automatic PermError)
  • ×+all, which lets anyone send as you
  • ×ptr mechanisms, which are deprecated
  • ×Forgotten includes for old tools that still send
FAQ

SPF questions

What is the SPF 10 lookup limit?

SPF evaluation may trigger at most 10 DNS lookups. include, a, mx, ptr, exists and redirect each count, including those inside included records. Over 10, SPF fails with a PermError.

Should I use ~all or -all?

~all (soft fail) is the common, safe default. -all (fail) is stricter and fine once you're sure every sending service is listed. Pair either with DMARC for real enforcement.

Does SPF affect email verification?

No. SPF is about whether you may send as a domain. Email verification checks whether a recipient's mailbox exists. Both matter for deliverability.

Authentication done? Clean the list next.