Free SPF Record Checker

Enter a domain to read its SPF record, follow every include, and count the DNS lookups a receiving server has to make before it can decide.

Lookup limit checked
10 per RFC 7208

Expanding the record...

What an SPF Checker Tells You

An SPF record is a TXT record at your domain that lists the servers allowed to send mail as you. A receiving server reads it, follows any include: it names, and checks whether the sending IP is on the list.

Two things break SPF without any visible error: publishing two records, and going over the limit of ten DNS lookups. This SPF checker reads the record the way a receiver does, expands each include, and totals the lookups. To build a new record, use the SPF record generator; to see the raw TXT set, use the TXT record lookup.

How to check an SPF record
  1. Enter the domain you send mail from, without "www".
  2. We read its TXT records through a public resolver and pick out the SPF record.
  3. We follow each include and redirect, and count every term that costs a DNS lookup.
  4. Read the verdict, then the lookup count and the include tree.

What this check settles

  • Whether receivers can evaluate it: two records, a broken include or more than ten lookups all end in a permanent error.
  • How much room is left: the lookup count shows whether one more sending service will push you over.
  • What happens to everyone else: the final all term decides how receivers treat a server that is not on the list.

SPF all Qualifiers Explained

The all term at the end of the record decides what happens to mail from any server not listed before it.

Term Result for others What it means Protection
-all Fail Unlisted servers fail SPF. Receivers may reject the message, and DMARC sees a clear failure. Strongest
~all Soft fail Unlisted servers soft fail. Most receivers accept the mail and let DMARC decide. A common choice while senders are still being added. Good with DMARC
?all Neutral The record takes no position on unlisted servers. A missing all term means the same thing. None
+all Pass Every server passes SPF, including one run by someone spoofing you. Never publish this. Harmful

How to Read the Result

The verdict comes first, then the parts a receiver works through to reach it.

The verdict

The headline

Whether receivers can evaluate the record at all, and if they can, how firmly it rejects servers that are not listed.

SPF record and all term

The policy

The record as published, and its final all term. If the record hands off with redirect=, the all term comes from the target.

DNS lookups and void lookups

The budget

Every include, a, mx, ptr, exists and redirect costs one lookup, counted through every nested include. The limit is ten. A void lookup is one that returns no records, and the limit is two.

Each name the record hands off to, indented under the record that names it, with its own lookups and any reason it could not be followed.

What Is the SPF 10 Lookup Limit?

RFC 7208 caps SPF evaluation at ten DNS lookups. Every include, a, mx, ptr, exists and redirect term counts, and so does every such term inside the records those includes point to. Go over ten and the receiver returns a permanent error, so SPF fails for all of your mail, not just some of it.

The ip4, ip6 and all terms cost nothing. The count is easy to exceed because each sending service controls its own include, and some use several lookups of their own.

How to Get Under 10 Lookups

Start with the senders you no longer use. Then look at what each remaining include costs.

The usual fixes:

  • Remove includes for services you have stopped sending through.
  • Drop a and mx terms when those hosts do not send mail.
  • Replace ptr, which is slow and discouraged by the standard.
  • Move a high-volume sender to a subdomain with its own SPF record.
  • Replace an include with ip4 and ip6 ranges only if the provider publishes fixed ranges, and check them when the provider changes them.

SPF Record Checker or SPF Lookup?

An SPF lookup reads the TXT record at a domain and shows it. An SPF record checker goes further: it follows each include, totals the DNS lookups and tells you whether a receiver can evaluate the result. This tool does both, so the record and the verdict sit side by side.

What Does a Valid SPF Record Look Like?

A valid SPF record is one TXT record that starts with v=spf1, lists the senders, and ends with an all term, for example v=spf1 include:_spf.google.com ~all. It must be the only record at that name that starts with v=spf1.

A TXT string holds at most 255 characters. A longer record is split into several strings that receivers join back together, which your DNS host normally does for you.

Where SPF Records Go Wrong

Most failures come from changes made one at a time, each harmless on its own:

  • Adding a second v=spf1 record for a new sender instead of adding an include to the first one.
  • A provider expanding its own include, so your count crosses ten with no change on your side.
  • Keeping includes for services you stopped using, which still cost lookups.
  • Publishing SPF on the apex but sending from a subdomain, which needs a record of its own.
  • Treating SPF as enough on its own. It checks the envelope sender, not the From address people see; DMARC connects the two.

Why Check Your SPF Record

01

Limit who sends as you

A record that ends in -all or ~all, with the right senders listed, gives receivers a reason to doubt mail from anywhere else.

02

Catch silent failures

A duplicate record or an eleventh lookup fails SPF for every message, and nothing in your DNS host warns you.

03

Make DMARC work

DMARC passes on an aligned SPF or DKIM result. A broken SPF record leaves DKIM as the only path.

04

Keep senders delivering

A sending service missing from the record can see its mail soft fail or fail, depending on your all term and your DMARC policy.

Who Checks SPF Records

The same read answers a different question depending on who runs it.

Mail Admins

Confirm the lookup count before adding a new sending service, not after its mail starts failing.

For DNS monitoring

Security Teams

Check that the record ends in -all or ~all, and that no one has widened it to +all.

For brand protection

Email Marketers

Make sure a newsletter or CRM platform is included before a campaign goes out.

For publishers

Agencies

Audit a client's record during onboarding, when old senders and duplicate records usually turn up.

For agencies

Related Email Tools

SPF is one of three checks receivers run. These cover the other two.

01

Check DKIM

DKIM signs each message, so it survives forwarding where SPF does not.

DKIM checker
02

Check DMARC

DMARC tells receivers what to do when SPF and DKIM both fail.

DMARC checker
03

Build a new record

Pick your mail senders and get one valid SPF record to publish.

SPF record generator
04

Monitor SPF, DKIM and DMARC

Get an alert when one of your email records breaks or weakens.

Email authentication monitoring
Start Today

Start Monitoring & Catching Domains Today

Join founders, agencies, and domainers already protecting their portfolio. Your first 3 domains are free.

Create Free Account

No credit card required • Cancel anytime

Frequently Asked Questions

Common questions about SPF records, lookups and how to check them.

What is an SPF record?

A TXT record, defined in RFC 7208, that lists the servers allowed to send mail for a domain. It starts with v=spf1 and ends with an all term. Receivers compare the sending server's IP address with the list and record a pass, fail, soft fail or neutral result.

How do I check my SPF record?

Enter your domain in the checker above. It reads the TXT record that starts with v=spf1, follows every include and redirect, counts the DNS lookups against the limit of ten, and shows the verdict next to the record.

What is the SPF 10 DNS lookup limit?

Receivers stop after ten DNS lookups while evaluating SPF and return a permanent error. The include, a, mx, ptr, exists and redirect terms each count, including those inside nested includes. The ip4, ip6 and all terms do not count.

Can a domain have two SPF records?

No. If more than one TXT record at a name starts with v=spf1, receivers must return a permanent error and SPF fails for every message. Merge the senders into a single record with one all term.

Should I use -all or ~all?

Use ~all while you are still confirming every sender, then -all once the list is complete. With DMARC at quarantine or reject, the practical difference is small, because DMARC decides what happens to failing mail.

What is a void lookup?

A DNS lookup made during SPF evaluation that returns no records, usually an include pointing at a name that no longer exists. RFC 7208 lets receivers stop with a permanent error after two of them.

Why does my record show more lookups than includes?

Each include points to another record, and that record can contain its own includes and a or mx terms. Every one of them counts toward the same limit of ten, so a single include can cost several lookups.

Does SPF stop spoofing on its own?

No. SPF checks the envelope sender, which people never see, not the From address in their mail client. DMARC ties the visible From address to an SPF or DKIM pass, so publish all three.

Does SPF work for subdomains?

Each name needs its own SPF record. A record at example.com says nothing about mail sent as news.example.com. Publish a record at every subdomain that sends mail, and consider v=spf1 -all on names that never do.

Does this tool send a test email?

No. It reads public DNS only. It does not connect to your mail servers or test a specific sending IP, so it tells you whether the record is valid and how strict it is, not whether one particular message passed.

Your first 3 domains are monitored free

No credit card. Upgrade or cancel any time.

Start free