Free tool · SPF checker

Check your SPF record

Enter a domain to read its SPF record from DNS, count every lookup it costs against the limit of 10, and see what to fix. DKIM, DMARC and MX are checked too, right below.

01What it checks

One record, ten lookups, one ending.

SPF lists the servers allowed to send mail for your domain. Receivers evaluate it on every message, and a few rules decide whether it works at all.

Lookups

The 10-lookup limit

Each include:, a, mx, ptr, exists and redirect= costs a DNS lookup, and so do the ones inside every include. RFC 7208 caps the total at 10. Past it, SPF returns a permanent error. The checker follows each include and counts them all.

Record

Only one SPF record

A domain may publish exactly one TXT record starting with v=spf1. With two, receivers return a permanent error and SPF fails for every email, even if each record is fine on its own.

all

~all, -all, ?all, +all

The last mechanism says what to do with servers not listed. ~all soft-fails them, -all fails them, ?all says nothing, and +all lets any server on the internet send as you. The checker flags ?all, +all and a missing all.

Includes

Every include must resolve

An include: that points at a name with no SPF record, or with two, breaks evaluation for that branch. The checker lists every included name it could not read as valid SPF.

Read more: SPF, DKIM and DMARC explained · SPF record generator

02Questions

What people ask.

What does “SPF permerror: too many DNS lookups” mean?
Your record, with everything it includes, needs more than 10 DNS lookups to evaluate. Receivers stop and treat SPF as a permanent error, which counts as a fail for DMARC. Remove includes for services you no longer send through, or move a sending service (a newsletter tool, a CRM) to a subdomain with its own SPF record. ip4: and ip6: cost no lookup.
Can a domain have two SPF records?
No. RFC 7208 allows one v=spf1 record per name; with two, the result is a permanent error. Merge them into a single record that carries every include: you need, for example: v=spf1 include:_spf.google.com include:amazonses.com ~all.
Should SPF end in ~all or -all?
Both are valid. -all tells receivers to fail mail from unlisted servers; ~all marks it as a soft fail. With DMARC in place, the DMARC policy decides what happens to failing mail, so ~all is the common choice and avoids rejections when a message is forwarded. Never use +all.
Do subdomains inherit the SPF record?
No. SPF is checked on the exact domain in the envelope sender (the Return-Path) and the HELO name. A subdomain that sends mail, like news.example.com, needs its own SPF record. DMARC, on the other hand, does fall back to the parent domain's policy.
Is SPF flattening a good idea?
Flattening replaces include: entries with the IP addresses they currently resolve to, which brings the lookup count down. The catch: when your provider changes its IPs, your record goes stale and real mail starts to fail. Only flatten with a tool that refreshes the record automatically; removing unused includes is usually the better fix.
03Go further

Related pages.

04Free tools

More free tools.

Deliverability, handled

Records right. Domain warmed. Then send.

Mailbase writes SPF, DKIM, DMARC and the reply MX when you add or buy a domain, then raises its volume only while real bounces and complaints stay low.