BP Strategists
Free toolEmail toolsInstant results

SPF record checker

Enter your domain and see whether your SPF record is valid, how many of the ten allowed DNS lookups it uses, and which services it actually authorises to send as you.

SampleDeliverability check · what a report looks like
RecordsSPF DKIM DMARCread live from DNS
Blacklists14checked per run
The part after the @ in your email address. We read its public DNS records. Nothing is sent.
Free, no account to create. Quick score in seconds, full report by email. See a sample report
What you get

A real report, not a summary.

Score, the fixes in order, then every finding with the evidence. This is the actual output of the tool for domain=microsoft.com.

SPF Record Checker sample report showing the score, top fixes and findings
Sample spf record checker report. Yours will show your own site or account.
What this tool checks

Every check, explained.

Record present

Whether a v=spf1 TXT record exists at your domain, and a starting record based on your mail provider if not.

One record only

Two SPF records is a permanent error. Receivers treat it as no SPF at all.

DNS lookup count

Every include, a, mx, ptr, exists and redirect, including the ones nested inside your providers, counted against the limit of ten.

Include tree

Each include expanded up to ten levels deep so you can see which service costs what.

Closing all mechanism

Whether the record ends with ~all or -all, the dangerous +all, or nothing.

Syntax

Unknown mechanisms, bad hostnames and malformed terms that cause a permerror.

Void lookups

Includes that point at domains with no SPF record, usually a service you stopped using.

Deprecated ptr

Flags the ptr mechanism, which the RFC says not to use and many receivers ignore.

Record length

Whether the record is split correctly across strings and stays under the 450-character guidance.

Recognised senders

Names the services your includes authorise: Google Workspace, Microsoft 365, Mailchimp, HubSpot and dozens more.

How it works

Three steps, free to run.

  1. 01Enter your domain

    The domain you send from. Subdomains are fine if you send from one.

  2. 02We fetch and expand the record

    One TXT lookup for your record, then every include it references, counted the way a receiving server counts them.

  3. 03Fix in order

    The top fixes are ranked by impact. Most take one edit in your DNS panel.

Before you run it

The thinking behind the checks.

What SPF does and where it breaks

SPF is a list, published in DNS, of the servers allowed to send email using your domain in the bounce address. When a message arrives, the receiving server looks up that list and checks whether the connecting server is on it. If it is, SPF passes. If not, the message is marked with a soft fail or rejected, depending on how your record ends.

The record rarely breaks in an obvious way. It breaks quietly. Someone adds a CRM, then a newsletter tool, then a helpdesk, each with its own include. Each include drags in the includes of its own provider. One day the total passes ten DNS lookups and every receiver on the internet starts returning permerror, which means your SPF is treated as if it did not exist. Nothing changed on your side, and the record still looks fine in the DNS panel.

What a healthy record looks like

Start with v=spf1, list one include per service that actually sends for you, add ip4 ranges only for servers you control, and end with ~all. Keep it under ten lookups with room to spare, because providers change their own records without telling you. Remove anything for a tool you cancelled.

  • v=spf1 include:_spf.google.com ~all is the whole record for a business on Google Workspace with no other tools.
  • Add include:servers.mcsv.net for Mailchimp, include:sendgrid.net for SendGrid, and so on, one per service.
  • Use -all only once you are certain every legitimate sender is listed. Until then ~all is the safe choice.
  • Never use +all. It authorises the entire internet.

SPF alone is not enough

SPF checks the bounce address, not the From address people see, so a forged From with a legitimate bounce domain passes SPF. It also breaks when mail is forwarded, because the forwarding server is not on your list. That is why DMARC pairs SPF with DKIM and only counts a pass when the domain matches the From address. For cold outreach in particular, receivers weigh all three together. A valid SPF record is the first step, not the finish line. Run the DMARC and DKIM checkers next.

Mistakes this checker catches

The same include listed twice, each counting against the limit. An include for a tool cancelled two years ago that now returns no record at all. A record copied from a forum post that ends in +all. Two records because the DNS host added one automatically and nobody removed the manual one. A ptr mechanism from a setup guide written in 2008. None of these look wrong in a DNS panel, and every one of them has cost a business inbox placement without anyone noticing for months.

FAQ

Questions people ask about this tool.

What is the 10 DNS lookup limit?

RFC 7208 caps the number of DNS queries a receiver will make while evaluating your record at ten. Includes, a, mx, ptr, exists and redirect each count one, including those nested inside your providers. Past ten, the result is permerror and your SPF is ignored.

Should I use ~all or -all?

~all (soft fail) marks unlisted senders as suspicious and is what DMARC expects. -all (hard fail) tells receivers to reject outright. Use -all only when you are certain every sender is listed, because forwarded mail and forgotten tools will bounce.

Why does the tool say permerror when my DNS panel shows the record?

The record exists but a receiver cannot use it: too many lookups, more than one record, or a term it does not understand. Fix the item flagged as critical and the record becomes usable again.

Can I have SPF on a subdomain?

Yes. Each domain or subdomain you send from needs its own record. Many companies put newsletters on a subdomain so a large include list does not eat the main domain's lookup budget.

How long until a change takes effect?

Usually minutes, up to the TTL of the old record, which is often an hour. Run the check again after the change; we read DNS live.

Done reading the report?

Want outbound that actually lands?

We are a London agency that does this for a living. Book a 20 minute call and we will walk through your results with you, no pitch deck.

Free 20-min strategy callBook now →
Hi there! 👋

Got a quick question? Drop us a message on WhatsApp — we usually reply in under 5 minutes.