If your mail is bouncing or landing in spam, a blocklisted sending IP is a likely cause. To check, you test the address against the major DNS blocklists and read which, if any, have flagged it. The IP blacklist checker queries eight at once, but the result is only useful if you know how to read it.
What a DNSBL actually is
A DNSBL, or DNS-based blocklist, is a list of IP addresses with a poor sending reputation, published over DNS. Mail servers query these lists in real time to decide whether to accept a connection. The clever part is that the check is just a DNS lookup.
To test an address, its octets are reversed and prepended to the list zone. So checking 198.51.100.4 against zen.spamhaus.org means looking up:
4.100.51.198.zen.spamhaus.orgIf the list returns an answer — an address in the 127.0.0.0/8 range — the IP is listed, and the exact code often says why. If the lookup returns no record (NXDOMAIN), the address is not listed. That is the whole mechanism, and it is why a blocklist check is fast and cheap.
The honest caveat: not every list will answer
This is the part most checkers gloss over, so read it carefully. Several major blocklists deliberately refuse queries that arrive through large public DNS resolvers. Spamhaus is the well-known example. They do this to protect their service from the huge query volume that public resolvers generate.
The IP blacklist checker runs in your browser and queries over a public resolver, so for those lists you will often see an Unknown verdict rather than Listed or Clean. That is expected. It does not mean the address is fine, and it does not mean it is listed — it means the list could not be reached from here. To get a definitive answer on those lists, you need to query them from your own mail server resolver, which is the environment they are designed to serve.
Treat Unknown as “no answer”, not as a verdict. The lists that do answer still give you a real, useful signal.
Reading the result
When you run a check, you get three possible verdicts per list:
- Listed — the IP is on that blocklist. The detail column shows the return code, which on many lists encodes the reason.
- Clean — the list answered and the address is not on it.
- Unknown — the list did not return a usable answer, usually because it refuses public-resolver queries.
A clean run across the lists that answered is reassuring. A single listing is worth investigating; multiple listings usually point to a real reputation problem rather than a one-off.
What to do if you are listed
Being listed is not the end of the world, but it needs prompt attention because it actively hurts delivery.
- Find out why. Open the listing on the blocklist that flagged you. Most lists have a lookup page that explains the reason — spam complaints, an open relay, malware traffic, or simply a new IP with no sending history.
- Fix the cause. Common causes are a compromised mailbox sending spam, a misconfigured server acting as an open relay, or poor list hygiene generating complaints. Listing the IP again after delisting without fixing the cause just gets you relisted.
- Request delisting. Each list handles this differently. Some have a self-service removal form; others clear automatically a set time after the bad behaviour stops. Delisting is per-list, so you may need to do it in a few places.
Reverse DNS goes hand in hand
Many of the same receivers that check blocklists also check reverse DNS. A sending IP with no PTR record, or one whose hostname does not forward-confirm, gets treated with suspicion even when it is not on any list. If you are cleaning up a sending IP, check its reverse DNS at the same time and confirm the MX records for the domain are sane.
Running the check
Enter an IPv4 address into the IP blacklist checker and it queries eight major DNSBL zones in parallel over secure DNS, then shows a per-list table with the verdict and return code. Nothing you enter is stored. Read the Unknown rows for what they are — lists that declined to answer — and act on the lists that gave a real result.