An email blacklist (now usually called a blocklist or DNSBL) is a public list of IP addresses or domains that have been linked to spam, compromised machines, or poor sending practices. Receiving mail servers look up the sender’s IP or domain against these lists in real time and may reject, filter, or score the message based on the result. To run an email blacklist check, look up your sending IP and your domains at the list operators’ own tools (such as Spamhaus’s checker) or a multi-list lookup service, then read the reason for any listing before you try to get removed.

This post explains how blocklists work under the hood, which ones matter, and how to check them yourself. If you’re already listed and need the step-by-step removal order, our post Listed on a blocklist: what to do, in order picks up from there.

How email blocklists work

Most blocklists are published over DNS, which is why they’re called DNSBLs (DNS-based blocklists). The mechanics are defined in RFC 5782:

The receiving server takes the connecting IP, say 192.0.2.99.
It reverses the octets: 99.2.0.192.
It appends the list’s zone and does a DNS lookup: 99.2.0.192.bl.example.org.
If the IP is listed, the lookup returns an A record in the 127.0.0.0/8 range, conventionally 127.0.0.2. If it’s not listed, there’s no record.
An optional TXT record explains the listing, often with a URL. Servers frequently paste that text into their rejection message.

Lists that cover several categories return different 127.0.0.x values to say which sub-list matched. RFC 5782 also requires every list to answer for the test address 127.0.0.2 and never for 127.0.0.1, so mail admins can confirm a list is working.

Domain-based lists (sometimes called URI or RHS lists) work the same way, but you query a domain name instead of a reversed IP. These are used to check the sender’s domain and the domains linked in the message body.

What happens when you’re on a blocklist

It depends entirely on who is using the list and how.

Outright rejection. Many mail servers reject during the SMTP conversation. You’ll get a bounce like:

550 5.7.1 Service unavailable; Client host [203.0.113.25] blocked
using zen.spamhaus.org; https://www.spamhaus.org/query/ip/203.0.113.25

Spam folder. Some filters treat a listing as one negative score among many, so mail is accepted but filtered.
No effect. Many lists are used by few or no large providers. A listing on a minor list might not change anything you can measure.

Large consumer mailbox providers like Gmail mostly rely on their own internal reputation data. Blocklists matter most for mail going to businesses, universities, ISPs, and anyone running their own filtering.

Which email blocklists matter?

There are dozens of public lists. A few carry most of the weight.

List	What it lists	Removal
Spamhaus SBL	Network ranges tied to spam or malicious activity	Via the ISP’s abuse team
Spamhaus CSS	IPs associated with spam emission	Request through the Spamhaus checker after fixing the cause
Spamhaus XBL	Compromised IPs	Request through the Spamhaus checker after cleaning the host (one request covers XBL and CSS)
Spamhaus PBL	IP ranges that shouldn’t send mail directly (e.g., residential)	Only if the IP really runs a mail server
Spamhaus DBL	Domains with poor reputation	Only through the Spamhaus checker; many listings expire once the activity stops
Spamhaus ZEN	Combined SBL, XBL, and PBL lookup	Depends on the underlying list
SpamCop (SCBL)	IPs reported by users for spam	Expires automatically
Barracuda (BRBL)	IPs flagged by Barracuda’s automated systems	Removal request form

Sources: the Spamhaus blocklist overview, the DBL page, Spamhaus’s notes on the reputation checker and removal order, SpamCop’s FAQ, and Barracuda’s removal page.

A few details from those sources worth knowing:

Spamhaus shows listings in the order they must be removed. If an IP is on the SBL, that has to be cleared, by the ISP’s abuse team, before anything else.
A PBL listing is normal for residential and dynamic IP ranges. It doesn’t mean you did anything wrong; it means that IP isn’t supposed to send mail directly to the internet.
SpamCop says IPs are automatically delisted after 24 hours with no new spam reports, and asks admins not to request early removal.
Barracuda says removal requests are typically processed within 12 hours if they include a valid explanation, and that duplicate requests are ignored.

How to do an email blacklist check

Step 1: Identify what to check

You need to check more than one thing:

Your sending IP addresses. Find them in the Received: headers of a message you sent, or in your ESP’s settings. On a shared ESP pool, your ESP is responsible for these, but it’s still worth knowing.
Your sending domains. The From: domain, the DKIM d= domain, and the Return-Path domain.
Your link and image domains. Including any click-tracking domain. A blocklisted link domain can sink a message from a perfectly clean IP.

Step 2: Use the list operators’ own tools

Spamhaus IP and Domain Reputation Checker accepts IPs, domains, and email addresses in one search box, and explains why something is listed.
Barracuda and SpamCop each have lookup pages on their sites.

Step 3: Use a multi-list lookup for breadth

Multi-RBL tools (MXToolbox is a well-known example) check your IP against many lists at once. They’re good for spotting listings, but they include many obscure lists. Before acting, look at who actually uses a list. A listing on a list nobody queries isn’t worth panic.

Step 4: Query a DNSBL directly (for developers)

You can check a list yourself from the command line:

# Is 203.0.113.25 on Spamhaus ZEN?
dig +short 25.113.0.203.zen.spamhaus.org A
dig +short 25.113.0.203.zen.spamhaus.org TXT

# Is example.com on the Spamhaus DBL?
dig +short example.com.dbl.spamhaus.org A

An answer like 127.0.0.2 means listed. Check the specific return code against the list’s documentation to see which sub-list matched.

Be careful with automated checks: Spamhaus refuses queries sent through public or open resolvers and returns error codes such as 127.255.255.254. Those are errors, not listings. If your mail server treats them as listings, it can end up rejecting all incoming mail. Spamhaus points heavy users to its free Data Query Service instead of the public mirrors.

Step 5: Set up monitoring

A one-time check tells you about today. Set up a scheduled check (many monitoring services do this) and alert on new listings for your IPs and domains, so you hear about problems before customers do.

Why IPs and domains get blocklisted

Listings almost always come from one of these:

Spam trap hits. Mailing purchased, scraped, or very old lists that contain trap addresses. See spam traps: how to avoid them.
Spam complaints from recipients who didn’t ask for your mail.
Compromised accounts or servers. A hacked website form, a leaked SMTP password, or malware sending spam from your network.
Sending from residential or dynamic IPs that sit on policy lists like the PBL.
Shared infrastructure. Another customer on your ESP’s shared IP, or a shared link-shortening domain, got listed.
Sudden volume from a new source, especially combined with any of the above.

What to do before requesting delisting

Requesting removal without fixing the cause usually leads to a quick relisting, and some operators treat repeat listings more harshly. The general order:

Read the listing reason. Most operators tell you what they saw: trap hits, a botnet signature, a policy listing.
Fix the source. Secure compromised accounts, stop the offending campaign, remove the list segment that caused it, or move mail off a residential IP.
Clean your list. Remove hard bounces, complainers, and long-term inactive contacts. Run older or imported data through our free email verifier to drop malformed addresses, domains without MX records, disposable domains, and common typos before you send again. It checks the address and domain, not the mailbox itself, so pair it with your own bounce history.
Request removal through the operator’s official process, once.
Watch for relisting after you resume sending.

The detailed, list-by-list sequence is in our post on blocklist delisting. Avoid paid “delisting services” that promise removal from major lists. Spamhaus says removal never costs anything and that fee-based removal offers are a scam.

How blocklists relate to your overall reputation

A blocklist listing is a symptom, not a separate problem. The same behaviors that get you listed (bad data, complaints, compromised sending) also damage your reputation inside Gmail, Yahoo, and Microsoft, which don’t publish their lists. Fixing the listing without fixing the cause leaves the bigger problem in place. For the broader picture, see sender reputation explained and why are my emails going to spam.

FAQ

What’s the difference between an email blacklist and a blocklist?

They’re the same thing. “Blocklist” is the term most operators, including Spamhaus, use now. You’ll still see “blacklist” in tools, error messages, and search queries.

How do I know if my email is blacklisted?

Look for bounces that name a list (for example, “blocked using zen.spamhaus.org”), then check your sending IP and domains at the list operator’s site, such as the Spamhaus checker. A multi-list lookup can show listings on smaller lists too.

How long does it take to get delisted?

It depends on the list. SpamCop listings expire automatically 24 hours after the last report, and Barracuda says it typically processes valid requests within 12 hours. Spamhaus says approved DBL removals usually take effect within minutes, with some systems lagging up to 24 hours, while SBL listings must go through your ISP.

Can I be blacklisted on a shared IP because of someone else?

Yes. On a shared IP, another sender’s behavior can get the IP listed. Your ESP is responsible for handling that, so contact them. Authenticating with your own domain helps keep your domain reputation separate from the IP’s.

Will verifying my email list prevent blacklisting?

It reduces one major risk: sending to invalid or abandoned addresses that bounce or turn into spam traps. It doesn’t prevent listings caused by complaints, compromised accounts, or sending without consent, so it should be one part of a broader hygiene routine.

Email Blacklists (Blocklists): How to Check Them and Get Delisted