whohostsitCheck your
SPF record.
Validate the SPF record, follow every include, and count DNS lookups
against the limit of 10.
Every include, followed.
The SPF result, lookup count, errors, and the full include tree appear here.
PUBLIC DATA. ONE SIMPLE LOOKUP.Why SPF records break
SPF lists the servers allowed to send email for your domain. Each include, a, mx, ptr, exists, and redirect costs a DNS lookup, and includes can contain more includes. Receivers stop at 10 lookups and treat anything over the limit as a permanent error, so SPF fails for all your mail.
WhoHostsIt follows every include and redirect through DNS, counts the lookups, and flags the common mistakes: more than one SPF record, includes that don’t exist, +all, and records with no all at the end.
Common questions
How do I fix too many DNS lookups in SPF?
Remove services that no longer send mail for you, replace a and mx with ip4 and ip6 ranges where they’re stable, or move some senders to a subdomain with its own SPF record.
Should I use ~all or -all?
~all (softfail) marks unlisted senders as suspicious, while -all (fail) asks receivers to reject them. With DMARC in place either works; -all is stricter once you’re sure every legitimate sender is listed.
Can I have two SPF records?
No. A domain must publish exactly one TXT record starting v=spf1. Merge the mechanisms from both into a single record.