# SPF Record Checker

Look up a domain's SPF record and check it the way receiving mail servers do: the checker parses every mechanism, follows include and redirect chains, counts the DNS lookups against the limit of 10 from RFC 7208, and warns about multiple records, a missing or permissive all, deprecated ptr and includes that have no SPF record. Fix sender authentication problems before your emails land in spam.

## Frequently asked questions

### What is an SPF record?

Sender Policy Framework is a TXT record in a domain's DNS that lists the servers allowed to send email for that domain. Receiving servers compare the sending server's address with the list and use the result, together with DKIM and DMARC, to decide whether to trust the message.

### What does the checker do?

It reads the TXT records of the domain, finds the record that starts with v=spf1, explains each mechanism and its qualifier, follows include and redirect to the records they point to, counts the DNS lookups the whole chain needs and lists everything that would make receivers treat the record as an error or as too weak.

### Why is there a limit of 10 DNS lookups?

RFC 7208 lets a receiver stop after 10 mechanisms that need a DNS query, which are include, a, mx, ptr, exists and the redirect modifier, counted across all nested includes. Beyond 10 the result is a permanent error, which many receivers treat like a failed check. ip4 and ip6 need no lookup and do not count.

### What do -all, ~all and ?all mean?

The all mechanism at the end decides what happens to servers that are not listed. -all means fail, so unlisted servers should be rejected; ~all means softfail, so mail is accepted but marked; ?all is neutral and says nothing. +all would allow every server on the internet and defeats the purpose of SPF.

### Can a domain have more than one SPF record?

No. A domain must publish exactly one TXT record that starts with v=spf1. With two or more, receivers return a permanent error and SPF fails. Merge the mechanisms into one record instead, for example when adding a new email service.

### How do I reduce the number of lookups?

Remove includes for services you no longer use, replace a and mx with the ip4 or ip6 ranges they resolve to when those are stable, and avoid ptr. Some providers offer a single include that covers all of their ranges, which is cheaper than several.

### Why is ptr flagged?

The ptr mechanism is slow, unreliable and marked as do not use in RFC 7208. Some large receivers ignore it entirely. Replace it with the ip4, ip6 or include mechanisms of the servers you actually send from.

### What does a missing include record mean?

An include points to a domain that has no SPF record. RFC 7208 makes that a permanent error for the whole check, so all of your mail can fail SPF. Usually the provider changed its include domain or the name is misspelled.

### Does a valid SPF record stop spoofing on its own?

No. SPF checks the envelope sender, which users never see, not the From address in their mail program. Only DMARC ties SPF and DKIM to the visible From domain, so publish a DMARC record as well and check it with the DMARC Record Checker.

### Is the lookup cached or rate limited?

The records are looked up live in DNS for every request, so changes appear as soon as your DNS has published them. To keep the service fair, each visitor can run a limited number of checks per minute.

Your ad here?

[Email us](mailto:hi@dennn.is?subject=Advertising%20on%20OneClick%20Pro)

[Ad 433 tools for your AI agents through one MCP server.](https://multitaskai.com/?ref=oneclickpro)
