include: _spf. google. cominclude: mail. zendesk. cominclude: mailgun. orginclude: servers. mcsv. netEnter your domain. We read its SPF record from public DNS, follow every include and redirect, count the DNS lookups against the limit of 10, and explain what to fix first.
include: _spf. google. cominclude: mail. zendesk. cominclude: mailgun. orginclude: servers. mcsv. netOne record from public DNS, everything it points to, and the one thing a domain name cannot tell us.
yourdomain.comThe TXT record that starts v=spf1 at the domain itself. Two or more of them is an error: receivers return permerror and treat the record as broken.
include:_spf.example.comEach one is fetched and read the same way, up to 8 levels deep. Each costs one of the 10 lookups, as does every a, mx, ptr and exists term. ip4, ip6 and all cost nothing.
203.0.113.7Receivers evaluate SPF for one message from one server and may stop early. We count every term the record can reach, so the number here is the most a receiver could spend. Paste a message into the header analyzer to see one real result.
What the count, the score and the words on this page mean.
Every include, a, mx, ptr, exists and redirect costs one, in the record and in every record it includes. ip4, ip6 and all cost nothing.
RFC 7208 section 4.6.4 lets a receiver make at most 10 DNS lookups while evaluating SPF. Past that it returns permerror, and your mail fails SPF for that message. Counting your SPF lookups.
One record with fewer than 8 lookups, no ptr and a -all catch-all scores 100. Each finding takes points off: over the limit 45, more than one record 35, +all 60, ?all 15, no all 12, 8 to 10 lookups 12, ptr 8, and ~all 3. A walk we could not finish caps the score at 75. 90 and above reads Strong, 70 to 89 Decent, 40 to 69 Needs work, below 40 Weak. No record, no score.
~all or -all?-all asks receivers to fail mail from any server you did not list. ~all asks for a soft fail and leaves the decision to them. Move to -all once every sender is in the record. Softfail, hardfail, and which to use.
No. We count that the tool ran and which kind of result it gave, so we can see what people run into. The domain and the record are not kept.
Ten an hour from one network. The limit keeps the tool fast for everyone.
The reading behind each finding, and the checks this page leaves to a sibling tool.