Skip to content
DMARC Pulse

SPF checker

Check SPF Record: SPF Validator

Enter a domain to check its SPF record, follow every include recursively and see how many of the 10 allowed DNS lookups it uses.

We resolve includes and redirects the same way receivers do (RFC 7208).

Example result

Sample data, not a live check. Run the tool above to see your own result.

Result for

acme.example

Looks good

-all

DNS lookups

Within the limit. Receivers can evaluate your SPF record.

DNS lookups 5 / 10
Void lookups 0 / 2
Authorized IPs 32
Google Workspace SendGrid

Published record

acme.exampleTXT
v=spf1 include:_spf.google.com include:sendgrid.net -all

What we found

  • Your SPF has room for more services (5 of 10 lookups)

    Comfortably within the limit of 10 DNS lookups.

  • Servers outside the list are not allowed (-all)

    Strict and clear. Make sure every service you send with is in the record.

Include tree

Every mechanism, including nested includes. Terms marked with a lookup count towards the limit.

  • acme.example 5 lookups
    • include:_spf.google.com 4 lookups
      • include:_netblocks.google.com 1 lookup
        • 11 IP ranges
          ip4:35.190.247.0/24 ip4:64.233.160.0/19 …

          ip4:35.190.247.0/24 ip4:64.233.160.0/19 ip4:66.102.0.0/20 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:74.125.0.0/16 ip4:108.177.8.0/21 ip4:173.194.0.0/16 ip4:209.85.128.0/17 ip4:216.58.192.0/19 ip4:216.239.32.0/19

      • include:_netblocks2.google.com 1 lookup
        • 6 IP ranges
          ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 …

          ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36

      • include:_netblocks3.google.com 1 lookup
        • 6 IP ranges
          ip4:172.217.0.0/19 ip4:172.217.32.0/20 …

          ip4:172.217.0.0/19 ip4:172.217.32.0/20 ip4:172.217.128.0/19 ip4:108.177.96.0/19 ip4:35.191.0.0/16 ip4:130.211.0.0/22

    • include:sendgrid.net 1 lookup
      • 9 IP ranges
        ip4:167.89.0.0/17 ip4:208.117.48.0/20 …

        ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16

    • -all

What to do with the result

No SPF record was found

We found no TXT record starting with v=spf1. Receivers get the SPF result none and have no list of your servers to check. If the findings also report timed-out lookups, wait 15 minutes and check again before you touch DNS.

  1. List every service that sends as your domain.
  2. Build one record with the SPF Generator. With Google Workspace alone, it is:

    v=spf1 include:_spf.google.com ~all

  3. Publish it as a TXT record at the root of example.com. This page reuses results for 15 minutes, so retest after that.

Start with ~all. With -all, mail from a forgotten service can be rejected. A domain that never sends mail can publish:

v=spf1 -all

The domain has two or more SPF records

SPF allows one record per domain. With more, receivers return permerror, a permanent error that only a DNS fix clears. The count and tree on this page cover just one of the records, so the real total may be higher.

  1. Copy every term from all the records into one line that starts with v=spf1. Miss one and that service keeps failing SPF after the fix.
  2. Keep a single all at the very end, because receivers ignore anything after it. If a record uses redirect=domain, write it as include:domain, because receivers ignore redirect= in a record that has an all.
  3. Publish the merged record and delete the others in the same DNS change.
  4. Check again after 15 minutes, since merging can push the count past 10.

The lookup count is over 10, or close to it

Past 10, the SPF standard requires permerror as soon as a receiver reaches the eleventh lookup. Evaluation stops at the first match, so some servers still pass while others fail. At 8 to 10 the record works, but a provider can add nested includes and push you over. Above 2 void lookups (queries that return no data), receivers can also return permerror.

Start with the include tree branch that uses the most lookups. Confirm a service has stopped sending before you remove it. The SPF Flattening Tool swaps includes for IP addresses, which go stale when a provider changes them. Microsoft advises against flattening include:spf.protection.outlook.com.

A term in the include tree is marked in red

The label beside the term names the cause: no SPF record, several SPF records, loop, invalid range or domain, or unknown. Most of these produce permerror, and one broken term affects the whole record, even inside a provider’s include.

  • Typing mistake: correct the domain or the IP range.
  • Outdated include: copy the current value from the provider’s documentation.
  • Fault in the provider’s own record: open a support ticket with them.
  • Unknown term containing =: receivers ignore it, so include= written for include: leaves that service unlisted.

Remove a term only after you confirm the service no longer sends.

The record works: now check how it ends

~all and -all need no change. +all lets every server pass, so list your senders and replace it. ?all, or no all and no redirect=, gives neutral, which receivers treat like no SPF. A record with redirect= needs no all: adding one makes receivers ignore the redirect. If your list is incomplete, use ~all: -all can get mail refused before DMARC runs, and those messages never reach your reports.

A clean result covers syntax and lookups only. SPF counts for DMARC only when the MAIL FROM domain (the envelope sender) shares an organizational domain with the visible From. If the domain has no DMARC record yet, publish one at p=none (monitoring only) with a rua address for reports, and keep it there at least a month before enforcing.

Explained

What the SPF checker counts: the 10-lookup limit

SPF evaluation may trigger at most 10 DNS lookups (RFC 7208 §4.6.4). include, a, mx, ptr, exists and redirect count — including the ones nested inside your providers’ includes. ip4, ip6 and all don’t. Over the limit, the result is permerror and SPF fails everywhere.

How to fix too many lookups

  • Remove includes of services you no longer use.
  • Replace a and mx with ip4: ranges when your servers are stable.
  • Move marketing tools to a subdomain with its own SPF record.
  • Rely on DKIM: DMARC passes with aligned DKIM even when SPF doesn’t.

Frequently asked questions

How do I validate my SPF record?
Enter your domain above. We find the TXT record starting with v=spf1, check its syntax, resolve every include and report errors and the lookup count.
What does SPF permerror mean?
A permanent error: the record can’t be evaluated, usually because it exceeds 10 lookups, there are two SPF records, or an include points to a domain without SPF. Receivers treat it as a failure.
Should I use ~all or -all?
Both are fine once DMARC is enforced, because DMARC decides what happens to failing mail. ~all is the safer default; -all is stricter.
Can I have two SPF records?
No. Two records cause a permerror. Merge all mechanisms into one record.
Does SPF survive forwarding?
No — forwarding changes the sending server, so SPF fails. That’s why DKIM matters most before moving to p=reject.

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.

Related tools