SPF Checker
See every include in your SPF record, count its DNS lookups against the limit of 10 and find the errors that break it.

More checks
Subject: Updated bank details
| Receiver | What its documentation says |
|---|
This email passes DMARC, so no DMARC policy applies to it.
The DNS lookups were blocked
Try another network, or turn off the blocker for this page.
Everything this checker flags
Each problem the check can report about SPF, and why it matters. Where a guide explains the fix, the row links to it.
Your domain has a valid SPF record
Receivers can read which servers may send mail for your domain, and the record stays within the lookup limits.
Your domain has no SPF record
Receivers cannot tell which servers may send mail for your domain. Gmail asks every sender for SPF or DKIM, and asks anyone who sends more than 5,000 messages a day for both.
Two or more SPF records sit on the same name
Receivers treat more than one SPF record as an error and stop checking. Every message from your domain then gets an SPF error.
An SPF record has a syntax error
One malformed term makes receivers stop reading the whole record. Every message from your domain then gets an SPF error.
Your SPF record needs more than 10 DNS lookups
Receivers stop after 10 lookups and return an error. Every message from your domain then gets an SPF error.
Your SPF record has more than 2 lookups that find nothing
Receivers may allow only 2 lookups that come back empty. Past that, they return an error and every message from your domain gets an SPF error.
An mx term in your SPF points to more than 10 mail servers
SPF allows at most 10 mail servers behind each mx term. With more, receivers return an error for that term and mail from your domain gets an SPF error.
An include points to a domain with no SPF record
Receivers treat an include without a record as an error. Every message from your domain then gets an SPF error.
The redirect in your SPF points to a domain with no SPF record
Receivers treat a redirect without a record as an error. Every message from your domain then gets an SPF error.
An SPF record repeats redirect= or exp=
Each of these may appear once per record. A second copy makes receivers return an error, so every message from your domain gets an SPF error.
Your SPF lets any server on the internet send as your domain
An SPF record in your chain ends in +all, which approves every server. Anyone can pass SPF for your domain, and DMARC then accepts their forged mail.
Your SPF approves servers that anyone can use
The record has one of these: a term that covers every IPv4 or IPv6 address (ip4:0.0.0.0/0, ip6:::/0 or a/0), a range wider than /16 that takes in Amazon EC2 or Google Cloud addresses anyone can rent, or an exists term that always resolves. It lets those servers pass SPF for your domain, and DMARC then accepts forged mail that passes SPF.
Your SPF approves a very large block of addresses
An ip4 range wider than /16 or an ip6 range wider than /32 covers a huge number of machines, whether it is written as an ip4 or ip6 term or as a prefix on a or mx. Anyone who controls one of them can pass SPF for your domain.
Your SPF record does not say what to do with other servers
It ends in ?all or has no all term, so servers you did not list get a neutral result. Receivers must treat neutral the same as having no SPF.
Your SPF record uses the ptr mechanism
The SPF standard says ptr should not be published. It is slow, it fails when DNS has trouble, and it costs a lookup.
Part of your SPF record comes after the all term
Receivers stop reading at the all term, so anything after it is never checked. Servers listed there do not pass SPF.
Your SPF record is longer than 450 characters
Answers that large may not fit in one DNS packet, and some receivers then fail to read the record at all. SPF for your domain can break without warning.
Your SPF record uses macros that change with each message
Some terms hold macros, written with a percent sign, that depend on the sender or the connection. This check cannot follow them, so the lookup count shown here may be lower than what receivers see.
Your SPF includes a service, which no other record mentions
No MX record or DKIM key found here points to a service. Does it still send mail for your domain?