What an IP blacklist check can and cannot tell you
Hundreds of DNS blocklists exist. This tool queries a curated nine that matter in practice and tolerate open queries — a deliberate subset, not an exhaustive sweep, and any tool claiming to check "all blacklists" is overselling. The nine cover the lists with real receiver adoption (Spamhaus above all), the aggressive-but-consulted tier (UCEPROTECT, SORBS), and the domain-reputation zones (DBL, SURBL) that IP-only checkers skip.
The bigger caveat: the receivers that matter most consult public lists least. Gmail, Microsoft, and Yahoo run internal reputation systems built from their own signal — spam reports, engagement, authentication history. A clean sweep here removes one class of problem; it does not certify inbox placement. Our methodology is built around that distinction.
How to read each status
- Listed: the zone returned a code in 127.0.0.0/8. For Spamhaus ZEN the code identifies the sub-list — SBL (manual spam listings), XBL (compromised hosts), or PBL (policy: residential/dynamic space that should not send mail directly). A PBL listing on your home IP is normal and harmless; the same listing on your mail server's IP means the reverse zone is misdeclared.
- Clean: no answer from the zone — the IP or domain is not listed there right now. Listings appear and expire constantly, so treat it as a snapshot.
- Unavailable via public DNS: the zone refused the query because it arrived through a shared public resolver. Spamhaus signals this with return codes 127.255.255.252, .254, and .255, and this tool maps those to "unavailable" — never to "listed". Plenty of checkers get this wrong and scare people with phantom Spamhaus listings.
- Timeout: no answer within 4 seconds. Some volunteer-run zones are slow or intermittently down; a timeout is an unknown, not a verdict.
Listed — now what?
Diagnose before delisting. A listing is a symptom: a compromised account or web form sending spam, a purchased list triggering traps, an open relay, or shared-IP neighbors if you send through a provider. Delisting without fixing the cause buys you days at most — most operators escalate repeat listings.
The order of operations that works: stop the bleeding (pause sending from the affected IP if you can), find the source (check your message logs around the listing date), fix it, then request removal via the list's own process. XBL/CBL removals are self-service and near-instant once the compromise is closed. SpamCop expires on its own. Never pay for delisting — the lists worth caring about do not charge, and the ones that charge are not worth caring about.
If you send through an email platform, the platform owns IP reputation and you own domain reputation. A DBL or SURBL listing of your domain follows you across any provider, which makes it the more serious finding — and the reason domain input mode checks those zones first.
Keep the rest of the stack clean
Blocklists judge past behavior; authentication decides how much benefit of the doubt you get going forward. A domain with enforced DMARC and clean SPF recovers from incidents faster because receivers can tell its real mail from a spoofer's. Run the full email DNS check to see authentication, MX, and reverse DNS in one report, and the reverse DNS checker for the FCrDNS state of your sending IP specifically.
Frequently asked questions
How does an email blacklist check work?
Each blocklist is a DNS zone. To check 203.0.113.10 against SpamCop, the tool queries 10.113.0.203.bl.spamcop.net: an answer in 127.0.0.0/8 means listed, no answer means clean. Domain lists work the same way with the domain prepended. This tool runs those queries in parallel against 7 IP zones and 2 domain zones, with a 4-second budget per list.
Why does Spamhaus show as 'unavailable via public DNS'?
Spamhaus blocks queries arriving through large public resolvers (like 8.8.8.8 or 1.1.1.1) and signals it with special return codes in the 127.255.255.x range. Those codes mean 'query refused', not 'listed' — a tool that reports them as listings is wrong. When you see 'unavailable', verify directly at spamhaus.org or query from a network running its own resolver.
I'm listed — how do I get delisted?
Fix the cause first, then request removal at the list operator's site. Each list has its own process: Spamhaus and CBL have self-service lookups with removal flows, SpamCop listings expire on their own within about 24 hours of the last spam report, Barracuda has a removal form, UCEPROTECT Level 1 expires after 7 clean days (ignore their paid 'express' delisting). Delisting without fixing the cause means relisting within days.
Does a listing on a small blocklist actually hurt deliverability?
It depends entirely on who consults the list. Spamhaus ZEN is used by a large share of the world's mail servers, so a listing there is an emergency. SORBS or UCEPROTECT listings affect the minority of receivers that subscribe to them. Gmail and Microsoft rely mostly on internal reputation systems — you can be clean on every public list and still land in spam there, and occasionally the reverse.
Why check a domain and not just an IP?
Modern filtering weighs domain reputation at least as heavily as IP reputation, and some lists track domains directly: Spamhaus DBL and SURBL list domains that appear in spam, independent of any IP. Entering a domain here checks those domain zones plus the IPs behind the domain's A record and MX hosts.