SPF Record Checker
Look up a domain's SPF record, see in plain English who it allows to send email, and find the mistakes that send mail to spam.
Free to use. The domains you check are not logged.
SPF lists the servers allowed to send email for your domain
SPF (Sender Policy Framework) is a single TXT record in your domain's DNS. It lists the mail servers and services that are allowed to send email using your domain name, and says what to do with mail from anyone else.
When a message arrives, the receiving mail server looks up the sender's SPF record and checks whether the server that delivered the message is on the list. If it is not, the message is more likely to be marked as spam or refused.
Most SPF problems are small: a second record added by mistake, a service that was never listed, or too many "include" entries. This checker reads the record the way a receiving mail server does and tells you what it finds.
What the SPF checker looks at
One record, written correctly
A domain may only have one SPF record. Two records, or a part that is not valid SPF, makes receiving servers ignore the lot.
The 10 lookup limit
Every include, a, mx and redirect costs a DNS lookup, and so do the includes inside them. Past 10, SPF fails. We follow every include and count them for you.
Who is allowed to send
Each part of the record is explained in plain English, including the servers allowed by the services you include.
How it ends
The "all" at the end decides what happens to everyone else. We flag records that end in +all or ?all, which protect nothing.
Common questions
What should an SPF record look like?
v=spf1, lists the services you send through, and ends with ~all or -all. For example: v=spf1 include:_spf.google.com ~all. Use the include value your email provider gives you; the example only shows the shape.Why does my SPF record fail with "too many DNS lookups"?
include, a, mx, exists and redirect counts as one, and so does every include inside an include. Remove services you no longer send through. ip4 and ip6 entries do not count.Should I use ~all or -all?
~all (soft fail) asks receiving servers to treat mail from unlisted servers as suspicious. -all (fail) asks them to reject it. Start with ~all, and move to -all once you are sure every service that sends for you is listed. With a DMARC policy in place, both work well.Can I have two SPF records?
v=spf1 at the start, all the includes and addresses in the middle, and one all at the end.I changed my SPF record. Why does it still show the old one?
More free tools
- DKIM CheckerFind a domain's DKIM keys and check each one is valid and long enough.
- DMARC CheckerCheck a domain's DMARC record and policy, and see where its reports are sent.
- MX LookupSee which mail servers receive email for a domain, in the order they are tried.
- DNS LookupLook up A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records, with no caching in the way.
- SSL CheckerCheck a website's SSL certificate: who issued it, what it covers and when it expires.
Email hosting with the records done for you
Skyrack email hosting gives you the SPF, DKIM and DMARC records to copy, and checks them for you in your console.
