SPF record checker

Validate your SPF record, follow every include and redirect, and see where your 10 DNS lookups go. DKIM and DMARC are checked at the same time so you get the full picture.

DKIM selector (optional)

The selector is shown in your provider's DKIM settings, or in the s= tag of the DKIM-Signature header of a message you sent. Separate several with commas. Without it, 76 common selectors are tried.

DNS queries are sent to Cloudflare's and Google's public resolvers over HTTPS. Nothing else leaves your browser and no result is stored.

The 10-lookup limit, explained

When a receiver evaluates your record, each mechanism that needs DNS costs one lookup, and included records bring their own lookups with them. A typical business domain with Google Workspace (1 lookup), a CRM (2 to 4) and a marketing platform (1 to 3) is already close to the limit. Past 10, evaluation stops with a permanent error: your SPF fails for every message, including legitimate ones, and DMARC can only rely on DKIM.

The lookup tree in the SPF card shows each include and how many lookups it carries, so you can see which service is expensive.

Common SPF mistakes this checker catches

Two SPF records

Often created when a second provider's instructions say "add this record" instead of "edit your record". Result: permanent error.

+all

Authorises every server on the internet. Spam filters treat it as a red flag.

Include of a domain without SPF

A provider changed its include name or you made a typo. One bad include breaks the whole record.

Terms after all

Everything after -all is ignored, so the service you listed last is not authorised.

ptr mechanism

Deprecated by RFC 7208; slow, and some receivers ignore it.

Void lookups

Mechanisms that point to names with no records. More than two is a permanent error.

Record templates

ProviderSPF record
Google Workspacev=spf1 include:_spf.google.com ~all
Microsoft 365v=spf1 include:spf.protection.outlook.com -all
Google Workspace + a second servicev=spf1 include:_spf.google.com include:<service-include> ~all
Own mail server onlyv=spf1 ip4:203.0.113.10 -all

Replace the placeholders with the include names documented by each service. Publish the record as a TXT record on the bare domain (host @).

Frequently asked questions

What is an SPF record?

SPF (Sender Policy Framework) is a TXT record on your domain that lists the servers allowed to send mail using your domain in the envelope sender. A receiving server looks up the record, checks whether the connecting IP address is listed, and produces a pass, softfail, fail or neutral result that DMARC then uses.

What counts towards the 10-lookup limit?

Each include:, a, mx, ptr, exists: mechanism and each redirect= modifier costs one lookup, and the lookups inside included records count too. ip4:, ip6: and all are free. The MX mechanism may additionally resolve up to 10 MX hosts without counting them.

How do I reduce SPF lookups?

Remove includes for services you no longer use, replace includes that never change with their ip4:/ip6: networks (and re-check them regularly), and move high-volume tools such as marketing platforms to a dedicated subdomain with its own SPF record. Avoid automatic "flattening" services unless you understand that provider IPs change.

~all or -all?

-all tells receivers to fail mail from unlisted servers; ~all asks for a softfail. Once DMARC is enforced the difference is small, because DMARC treats both as "not passing". Many administrators keep ~all to avoid hard rejections of forwarded mail; -all is stricter and fine when every sender is listed.

Can I have two SPF records?

No. Two v=spf1 records are a permanent error, which is the same as having none. Merge the mechanisms into a single record.

Does SPF protect the From address people see?

Not by itself. SPF checks the envelope sender (Return-Path), which can differ from the visible From header. DMARC adds the alignment check that ties the authenticated domain to the From header.