Email blacklist check: which lists matter in 2026 and how to get off them
There are over a hundred public blocklists. Two of them can hurt you. Here is how to check the right ones and what to do if you are on them.
Most public email blacklists cannot keep your mail out of anyone's inbox. Spamhaus can. An email blacklist check is only useful if you know which result actually predicts blocked mail and which is a red icon on a scanner that nobody's mail server consults.
This distinction saves you real money, because an industry of "blacklist removal services" exists to charge you for the scary-looking results. Blacklists are one input into the reputation system covered in our email deliverability handbook; this article is the practical piece: what to check, how, and what delisting honestly involves.
Which blacklists matter in 2026
A blacklist (DNSBL, if you want the technical term) is a DNS zone that answers "is this IP or domain a known spam source?" Receiving mail servers query these lists during the SMTP conversation and can reject or filter on the answer. The catch: each mail operator chooses which lists to consult, and in practice the market has consolidated hard.
| List | What it covers | Does a listing block real mail? |
|---|---|---|
| Spamhaus ZEN | IP addresses (combines their SBL, XBL, PBL zones) | Yes. Widely consulted by mailbox providers and corporate filters |
| Spamhaus DBL | Domains seen in spam | Yes, and this is the one small senders actually hit |
| Barracuda BRBL | IPs, consulted by Barracuda appliances | Sometimes, at companies running Barracuda gear |
| UCEPROTECT Level 3 | Entire providers and subnets | Rarely. Lists whole networks by design; treat as noise |
| SORBS | Nothing anymore | No. Proofpoint shut SORBS down in June 2024; its zones are empty |
The pattern to internalize: Spamhaus results are actionable, most other red marks are not. SORBS is the cautionary tale here. It ran for two decades, appeared on every scanner, and when Proofpoint decommissioned it in June 2024 (announced June 5) the practical effect on global email was close to zero. Many of the lists on a 100-item scan are in that category while still alive.
UCEPROTECT Level 3 deserves its own sentence because it frightens people on purpose. It lists entire subnets and providers, not senders, so being on it says nothing about you. Their own site states that removal requests from end customers at Level 3 are futile. If your check shows only UCEPROTECT, close the tab.
How to run the check
You need two inputs: your sending domain and your sending IP. If you send through an ESP or relay (Mailchimp, Resend, SES, anything where you did not rent the server yourself), the IP belongs to a shared pool the provider manages. Find it by sending yourself a message and reading the Received: headers in "Show original", or from your provider's dashboard.
Then, in order:
- Go to check.spamhaus.org. Enter your domain, then run it again with the IP. This is the authoritative source for the only listings that reliably matter, and it tells you which specific zone (SBL, XBL, PBL, DBL) flagged you and why.
- Go to mxtoolbox.com/blacklists. Enter the same domain and IP. This sweeps roughly a hundred lists at once. Expect a couple of hits on obscure lists even on perfectly healthy senders; read the names before reacting.
- If you run your own server, you can query a DNSBL directly with dig. Reverse the IP's octets and prepend them to the zone:
dig +short 2.0.0.127.zen.spamhaus.org
A 127.0.0.x answer means listed (the x tells you which zone); no answer means clean. One trap: Spamhaus refuses queries arriving through large public resolvers like 8.8.8.8, so an empty dig result on a machine using Google DNS proves nothing. When in doubt, trust the check.spamhaus.org web result over your own dig.
At LetterDuck we send from a shared relay pool, so the pool operator carries the IP reputation and we carry the domain's. That split is the norm now, and it is why the domain check matters more than the IP check for most senders reading this: your domain is the reputation asset you actually own, and DBL is the list that tracks it.
Delisting, honestly
Here is the part the removal-service industry does not want written down: Spamhaus delisting is free, self-service, and usually fast once the cause is gone. Their listing pages link directly to the removal process, and for common cases (PBL listings on dynamic IPs, XBL listings from a since-cleaned infection) removal is close to immediate after you attest the fix.
The honest general formula for every legitimate list is time plus fix. You identify why you were listed, you stop the behavior, you request removal, and the listing ages out. There is no lever a paid third party can pull that you cannot, because reputable blocklist operators do not sell placement or removal.
Which makes paid "express delisting" a reliable tell. If a service offers guaranteed removal from many lists for a fee, you are funding a business model, not fixing your email. UCEPROTECT is the famous example: a standard waiting period with a paid express option, for a list that barely affects delivery in the first place. Paying it does nothing for your inbox placement and marks you as someone willing to pay.
One more honesty checkpoint: if you are listed on Spamhaus SBL or DBL specifically, take it seriously and read their evidence. Those listings are researched, and arguing with the listing instead of fixing the cause extends your stay.
The listing is the symptom
Every listing has an upstream cause, and delisting without finding it schedules your next listing. The usual suspects, in the order we would check them:
A compromised asset. A hacked WordPress plugin, an open contact form, or leaked SMTP credentials quietly sending spam from your infrastructure. Check your outbound logs for volume you do not recognize.
A bought or scraped list. Purchased addresses contain spam traps, and traps feed blocklists directly. If you imported a list you did not build, that is probably your answer, and your bounce rate usually spiked at the same time.
Sustained complaints. Real subscribers hitting "report spam" because unsubscribing was harder. Your spam complaint rate is the metric to pull first; above 0.3% with Gmail you have a bigger problem than any blacklist.
Our own setup is built on the assumption that prevention beats delisting. Hard bounces are suppressed permanently and automatically, every send checks the suppression list first, and the send path pauses itself at 2% bounces or 0.3% complaints. None of that is heroic; it is exactly the behavior that keeps a domain off DBL in the first place.
What to do this week
Run your domain and sending IP through check.spamhaus.org today, and again after any incident. Ignore scanner hits on lists you cannot name. If you find a Spamhaus listing, fix the cause before you file the removal request, and never pay anyone to do either. Then put your energy where the signal is: Google Postmaster Tools and your own bounce and complaint numbers will warn you about most problems before any blacklist does.