SPF record checker
Enter your domain: the checker reads its SPF record and every record it includes, counts the DNS lookups receivers make against the limit of 10, and checks DKIM and DMARC alongside, since receivers weigh the three together.
Check a domain
SPF
Your SPF record and every record it includes, its DNS lookups against the limit of 10, and its policy for other servers.
DMARC
The DMARC record that applies to your domain, its policy, its reports and where it comes from.
DKIM
Your DKIM keys, under your selectors or 12 common ones, with the type and size of each key.
What an SPF record does
An SPF record lists the servers allowed to send mail for your domain. A receiving server checks the domain of the envelope sender, the address that bounces come back to, against that list, and the last term of the record, such as -all or ~all, says what to make of a server that is not on it.
It is one TXT record at your domain itself, starting with v=spf1. Each include points to another record, often your sending service's, and every include, a, mx, ptr, exists and redirect costs a DNS lookup: past 10 across the whole tree, receivers stop and SPF fails.
SPF alone does not protect the address people see in their inbox: it checks the envelope sender, which your sending service often sets to a domain of its own. DMARC ties the two together, which is why Gmail, Yahoo and Outlook ask bulk senders for SPF, DKIM and DMARC at once.
How the check reads your domain
- Every query goes through PricklyMails' own resolver, never a public one, with at most 32 queries and 8 seconds per check; a section the budget cut short says so.
- SPF follows RFC 7208: one record at the domain, every
includeandredirectfollowed, the lookups counted against 10 and the lookups that find nothing against 2, as receivers count them. - DMARC follows RFC 9989, which replaced RFC 7489 in May 2026: the record at the domain or, without one, the record the DNS walk finds above it, the obsolete
pct,rfandritags noted, and each report address on another domain checked for the authorization RFC 9990 asks for. - DKIM follows RFC 6376, with the key rules of RFC 8301 and RFC 8463: the type of each key, its RSA size, and its flags. Selectors cannot be listed from the DNS, so without yours the check tries 12 common ones.
- The answer is kept 4 minutes, so a second check of the same domain costs no query, then forgotten: no domain is stored, logged or sent to analytics.
- RFC 7208: Sender Policy Framework (SPF) (opens in a new tab)www.rfc-editor.org
- RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC) (opens in a new tab)www.rfc-editor.org
- Email sender guidelines (opens in a new tab)support.google.com
- Sender best practices (opens in a new tab)senders.yahooinc.com
- Outlook's new requirements for high-volume senders (opens in a new tab)techcommunity.microsoft.com
Frequently asked questions
Why does my SPF record fail past 10 DNS lookups?
RFC 7208 caps the DNS lookups one SPF check may make at 10, counting every include, a, mx, ptr, exists and redirect across every record the check reaches, and the lookups that find nothing at 2. Past either limit the result is a permanent error, which DMARC never counts as a pass. Remove the services you no longer send through, or replace an include with the ip4 and ip6 ranges it stands for, which cost no lookup.
- RFC 7208: Sender Policy Framework (SPF) (opens in a new tab)www.rfc-editor.org
Should my SPF record end with -all or ~all?
-all asks receivers to fail mail from any server the record does not list, ~all to accept it but treat it as suspect. With DMARC published, receivers apply your DMARC policy to mail that fails either way, so ~all is a common choice while you confirm that every service you send through is listed. +all lets any server in the world send as you and should never be published.
- RFC 7208: Sender Policy Framework (SPF) (opens in a new tab)www.rfc-editor.org
Can a domain have two SPF records?
No. A domain publishes one SPF record: with two or more, receivers return a permanent error and SPF fails for all your mail. To add a sending service, merge its include into the record you have.
Do Gmail, Yahoo and Outlook require SPF?
Yes. Gmail and Yahoo ask every sender for SPF or DKIM, and bulk senders for both, with DMARC; Gmail counts as bulk a sender of 5,000 messages a day or more to its users. Outlook.com announced the same requirements in April 2025 for senders of more than 5,000 messages a day, with rejection for mail that fails them.
- Email sender guidelines (opens in a new tab)support.google.com
- Sender best practices (opens in a new tab)senders.yahooinc.com
- Outlook's new requirements for high-volume senders (opens in a new tab)techcommunity.microsoft.com
Check your list before your next send.
1,000 tokens free when you sign up, no credit card. After that, you only pay for answers.