Blocklists
Why Blocklist Checks Give Wrong Answers (Spamhaus DQS and Public DNS Resolvers)
Spamhaus blocks queries sent via public DNS resolvers and answers with error codes, not listings. Checkers that misread them report listings that don't exist.
On this page
Blocklist checks give wrong answers mostly because of how they query. Spamhaus refuses lookups that arrive through public DNS resolvers like Google's 8.8.8.8, and answers them with an error code (or nothing at all) instead of real data. A checker or mail server that doesn't recognize those error codes can report "listed" when you're clean, or "clean" when you're listed.
The authoritative answer for Spamhaus is always check.spamhaus.org. If a third-party tool disagrees with it, believe Spamhaus.
How a blocklist lookup works (and where it goes wrong)
A DNS-based blocklist (DNSBL) is queried like any other DNS name. To check 203.0.113.7 against Spamhaus ZEN, you reverse the IP and look up 7.113.0.203.zen.spamhaus.org. If the IP is listed, the answer is an address in the 127.0.0.x range, and the last number says which list (127.0.0.2 for the SBL, 127.0.0.10 or .11 for the PBL, and so on). If it isn't listed, the answer is "no such name" (NXDOMAIN).
That design has a weak spot: any answer at all is easy to mistake for a listing. Spamhaus added error codes in the same 127.x range, and software that only checks "did I get an answer?" treats an error as a hit.
Spamhaus's error codes
Spamhaus documents three return codes that are not listings:
| Return code | What it actually means |
|---|---|
| 127.255.255.252 | The blocklist name was mistyped (for example xen.spamhaus.org instead of zen) |
| 127.255.255.254 | The query came through a public or open resolver, or from an IP with generic, unattributable reverse DNS. No data returned. |
| 127.255.255.255 | Too many queries from a resolver that doesn't meet Spamhaus's usage terms. No data returned. |
Spamhaus is blunt about it: none of these codes relate to the reputation of the IP being checked. It also warns that software that doesn't parse them correctly can end up treating every response as "listed" or every response as "not listed," and calls that a potentially disastrous outcome.
Spamhaus has also said that some public resolvers simply return NXDOMAIN for its zones. That produces the opposite mistake: a tool that sees nothing and tells you you're clean, whether you are or not.
Why public resolvers get blocked
Spamhaus's free public mirrors are meant for low-volume, non-commercial use: small organizations, schools, non-profits. Commercial users and high query volumes are supposed to pay. Big public resolvers break that model because they hide who is asking. Spamhaus's own words: public recursive name servers "act as an anonymizing service and enable large-scale users to hide behind them."
So queries that arrive from a public resolver get the 127.255.255.254 treatment. Spamhaus has published similar notices for the shared resolvers at some large hosting providers, which means a VPS using its host's default DNS can hit the same wall.
Where you'll see wrong answers
Free online blocklist checkers. A checker that runs its lookups through a public resolver, or queries heavily enough to get rate-limited, gets error codes back. If it treats any 127.x answer as a listing, you'll see a Spamhaus "listing" that check.spamhaus.org doesn't show.
A recipient's mail server. A small company running its own server with a public resolver configured can end up rejecting legitimate mail "because of Spamhaus." The bounce names Spamhaus, but you aren't listed. This is the receiver's misconfiguration, and only the receiver's admin can fix it. Send them Spamhaus's return-code article.
Your own mail server. The same mistake in reverse: if your inbound filtering queries Spamhaus through a public resolver, you're either rejecting good mail or getting no protection at all. Check your logs for 127.255.255.x answers.
Dead and stale lists. Checkers often still query lists that no longer operate. SORBS shut down in June 2024, and checkers and old articles kept reporting SORBS "listings" afterward. A list that's gone can't be blocking you.
Checking the wrong IP. Running your office IP through a checker tells you nothing about mail your ESP sends from its own servers. Check the IP in your bounce or in the Received headers (the header analyzer will find it).
How to get a correct answer
- Start with the bounce. If mail isn't bouncing, a listing on a checker is trivia. If it is bouncing, the bounce usually names the list and often links to the lookup. See how to read a bounce message.
- Check Spamhaus at the source. Use check.spamhaus.org for IPs and domains. It shows which list, if any, and the removal path.
- Check other lists at their own lookup pages (Barracuda, SpamCop and so on) rather than relying on an aggregator.
- If you query DNS yourself, use a resolver you run on your own network, not 8.8.8.8 or 1.1.1.1, and read the actual return code. 127.255.255.254 means "you asked the wrong way," not "you're listed."
- Ignore lists that don't matter. Which blocklists actually matter covers the handful worth watching.
If you run a mail server: DQS
Spamhaus's fix for operators is the Data Query Service (DQS). You sign up, get a personal query key, and put it in the hostname you query. Instead of zen.spamhaus.org, you query:
7.113.0.203.YOURKEY.zen.dq.spamhaus.net
Because the key identifies you, DQS doesn't depend on which resolver you use. Spamhaus offers a free DQS account for users who meet its fair-use terms, and paid access (with a trial) for commercial use. The other option Spamhaus gives is to keep using the public mirrors but query from your own resolver on a dedicated IP with proper forward and reverse DNS.
Whichever you choose, configure your filter so the 127.255.255.x codes are logged as errors and never used to reject mail.
If a recipient keeps rejecting you "for Spamhaus" and check.spamhaus.org says you're clean, tell their admin about 127.255.255.254 and DQS. It's usually a ten-minute fix on their side.
When to get help
If mail is really bouncing and the bounce names a list, but every lookup says you're clean, it's worth having someone read the actual bounces and DNS answers before you chase a listing that may not exist. Get in touch. For real listings, the Spamhaus removal guide and the blocklist playbook cover what to do.
FAQ
What does 127.255.255.254 mean?
It means Spamhaus refused the query because it came through a public or open resolver, or from an IP with generic reverse DNS. It says nothing about the IP being checked.
Why does one checker say I'm on Spamhaus and another says I'm not?
Usually because one of them is reading an error code as a listing, or querying through a resolver Spamhaus blocks. Check at check.spamhaus.org, which is the authoritative source.
Is Spamhaus DQS free?
There's a free DQS account for users who meet Spamhaus's fair-use terms (broadly, non-commercial and modest volume). Commercial users need a paid subscription, which can start with a trial.
Can a recipient block me for a Spamhaus listing I don't have?
Yes, if their server misreads Spamhaus's error codes as listings. That's their configuration problem, and only their admin can fix it.
Sources
- Spamhaus: Using our public mirrors? Check your return codes now
- Spamhaus Technology: Help for Spamhaus public mirror users
- Spamhaus Technology: Successfully accessing Spamhaus's free blocklists using a public DNS
- Spamhaus Technology docs: Public Mirrors to DQS migration
- Spamhaus Technology docs: Available zones and return codes
Related guides
- Barracuda Blocklist (BRBL) Removal and Barracuda Gateway BlocksCheck your IP at barracudacentral.org, fix the cause, then submit one removal request with a real explanation. Not listed? The block is a gateway policy.
- Cloudmark CSI: Why Your IP Is Listed and How to Reset ItCloudmark CSI blocks IPs with poor reputation from traps and spam reports. Fix the cause, then file a reset request at csi.cloudmark.com as the IP's owner.
- Email Blacklists: What They Are, How to Check, and How to Get OffAn email blocklist is a list of IPs or domains receivers refuse mail from. Your bounces tell you which list; fix the cause, then use that list's removal path.
- My ESP's Shared IP Is Blacklisted: What Can I Do?On a shared IP, your ESP owns the delisting, not you. Send them the bounce, check whether your own mail is a cause, and know when a dedicated IP makes sense.
- SpamCop Blocklist (SCBL) RemovalSpamCop listings expire automatically 24 hours after the reports stop. There's no removal form that works faster: find what's generating reports and stop it.
- Spamhaus Blocklist Removal (ZEN, SBL, XBL, CSS, DBL, PBL)How to get off a Spamhaus blocklist: identify whether you're on the SBL, CSS, XBL, PBL or DBL, fix the cause, then use the removal path that list requires.
Still stuck?
Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.