Skip to content

SPF void lookup limit exceeded

More than 2 lookups in your SPF record come back empty, so receivers return permerror until you remove or correct the terms that point at nothing.

Last updated:

What the checker reports

Critical spf.void_limit_exceeded

SPF has more than 2 void lookups; the limit is 2

A void lookup is a DNS query from the record that returns no records at all. The standard tells receivers to allow at most 2 and to return permerror past that, so SPF fails.

How to fix: Remove the terms listed in the evidence, or correct their domain names. They usually point at services or hosts that no longer exist.

What this error means #

A void lookup is a DNS query made by one of your SPF terms that comes back with nothing. Either the name doesn’t exist at all (NXDOMAIN), or it exists but holds no records of the type the term asked for. RFC 7208 tells receivers to allow at most 2 of these while they evaluate your record. A third one gives permerror, and SPF fails.

A common cause is a record that outlived what it pointed at. An a term names a host that was deleted. An mx term names a domain whose mail setup was removed. Each one a receiver reaches adds a void lookup, and two are tolerated, so the record can sit broken until a third dead term tips it over.

An include is a special case. If the included name publishes no SPF record, the standard gives permerror at once (RFC 7208 §5.2), without waiting for a third void lookup. That case has its own page: SPF include has no SPF record.

Evaluation goes from left to right and stops at the first term that matches (RFC 7208 §4.6.2). A message from a server matched early in the record never reaches the dead terms, so a test from your main server can look fine while mail from a service listed further right fails. That’s why this error tends to show up as scattered failures rather than all of your mail.

The limit is worded as a recommendation, and an implementation may make it configurable, with 2 as the recommended default. Receivers can therefore differ. Don’t count on a lenient one: fix the record so every term points at something that answers.

How receivers treat it #

Standard: RFC 7208 §4.6.4

SPF implementations SHOULD limit “void lookups” to two. An implementation MAY choose to make such a limit configurable. In this case, a default of two is RECOMMENDED. Exceeding the limit produces a “permerror” result.

A permerror means the domain’s published records couldn’t be correctly interpreted, and RFC 7208 §2.6.7 says it signals an error that definitely requires DNS operator intervention. What a receiver does next is its own local policy (§4.2). If it rejects the message during the SMTP conversation, §8.7 says it should use reply code 550 with, if supported, the enhanced status code 5.5.2.

For DMARC, a permerror is not an SPF pass. RFC 9989, which replaced RFC 7489 in May 2026, only treats a domain as an SPF-authenticated identifier when SPF passes (§4.10.2), so there’s nothing for DMARC to align. Mail can still pass DMARC through an aligned DKIM signature (§5.3.5).

Broken and fixed record #

void-lookups.zone
example.com.  TXT  "v=spf1 ip4:192.0.2.10 a:old-shop.example.com mx:legacy.example.net a:crm-retired.example.com include:spf.mailer.example ~all"

Three terms in this record point at nothing. old-shop.example.com and crm-retired.example.com were deleted from DNS, so those lookups return NXDOMAIN. legacy.example.net exists, but it has no MX records, so that lookup returns an empty answer. That’s 3 void lookups against a limit of 2. Mail from 192.0.2.10 still passes, because the ip4 term on the left matches before any lookup happens, which is how a record like this can go unnoticed.

The fixed record drops the three dead terms and keeps what still answers:

no-void-lookups.zone
example.com.  TXT  "v=spf1 ip4:192.0.2.10 include:spf.mailer.example ~all"

If one of the three names was a typo for a host that does exist, correct the name instead of deleting the term.

How to fix it #

  1. Run the SPF Record Checker on your domain. It lists the terms behind the void lookups.
  2. Look up each listed name with any DNS lookup tool. For an a term ask for its address records, for an mx term ask for its MX records. An empty answer or an NXDOMAIN confirms the term is void.
  3. Decide what each dead term was for. If the host moved or the name has a typo, correct the name. If the host or the service is gone, delete the term.
  4. Check any service you still use against its own setup guide, in case it changed the name of its include or host.
  5. Publish the corrected record. Keep it as the only SPF record at that name.
  6. Run the SPF Record Checker again and confirm the report shows no void lookups.

Check your domain

Records look right? Check the list next.

Kavik.email checks every address on your list, so what you send reaches real inboxes.