IP Blacklists vs. Domain Blacklists: Why You're Probably Checking the Wrong One

Every week senders come to us convinced a blacklist is killing their deliverability. They paste their IP into MXToolbox, see a listing, and panic. Or they run a placement test, get bad results, and assume it must be a blacklist.

Here's the thing though: most of the time, the listing they found isn't the one causing the problem. And a lot of the time, they're not even checking the right IP to begin with.

There are two completely different types of blacklists that affect email delivery: IP blacklists and domain blacklists. They work differently, they're checked at different points in the delivery process, and fixing one does absolutely nothing for the other. Add email relays into the mix and most people have been looking at the wrong IP entirely.

Let's break it all down.

Two Types of Blacklists, Two Completely Different Problems

Before getting into specifics, here's the key distinction to understand:

• IP Blacklist: Lists the sending server's IP address. Checked at the SMTP connection, before your message is even accepted. The receiving server sees the IP and immediately decides whether to let the connection through.
• Domain Blacklist: Lists domains found inside your message — including your sending domain, links, and tracking domains. Checked during content scanning, after the message is accepted. A clean IP won't save you here.

This matters because the fix for one is completely different from the fix for the other. You can have a spotless IP but still get filtered because a link in your email is on a domain list. Or vice versa.

IP Blacklists: What They Are and Which Ones Actually Matter

An IP blacklist (also called a DNSBL or RBL) is a published list of IP addresses with poor sending reputations. When a receiving mail server gets a connection from your IP, it can query one of these lists in real time. If your IP is listed, the connection can be rejected before your email even arrives.

Here are the ones worth knowing about:

Spamhaus ZEN — Impact: High

This is the big one. Spamhaus ZEN is a combined zone that bundles all of Spamhaus's IP lists into a single query. It includes the SBL (confirmed spam sources), CSS (high-volume/snowshoe senders), XBL (compromised machines and botnets), and PBL (IP ranges that shouldn't be sending mail directly). Microsoft and most enterprise mail servers actively reference Spamhaus. A ZEN listing has real teeth for B2B cold email.

Barracuda BRBL — Impact: Medium-High

The Barracuda Reputation Block List catches IPs flagged by Barracuda's network of appliances and spam traps. If your recipients are using Barracuda-protected corporate mail servers (common in mid-market and enterprise), this one matters. The good news: Barracuda has a manual delisting form and typically processes it within about 12 hours once the underlying issue is fixed.

SpamCop (SCBL) — Impact: Medium

SpamCop lists IPs based on user complaints and spam traps. The scoring is time-weighted so recent complaints count more and listings auto-expire, usually within 24 hours after the reports stop. There's no delisting form. Stop the spam, and it clears itself.

UCEPROTECT L2 / L3 — Impact: Very Low

UCEPROTECT's secondary and tertiary zones list entire ASNs or netblocks, not individual IPs. Almost no major receiver uses them for delivery decisions, and they will charge you for express delisting. Don't pay. Don't lose sleep over a listing here unless you're using them as a generic "is my IP healthy" signal.

Domain Blacklists: The Ones Most People Forget Exist

Domain blacklists work on a completely different layer. Even if your IP is squeaky clean, a receiving server can scan the contents of your message and reject it because of a domain referenced inside the body or envelope.

Spamhaus DBL — Impact: High

The Spamhaus Domain Block List catches sending domains, From-domains, and any URL host found in the message body. A DBL listing for your primary sending domain is among the most damaging things that can happen to a B2B program — it follows the message no matter which IP you send from.

SURBL — Impact: Medium-High

SURBL flags domains that appear in the body of spam messages. It's used heavily by SpamAssassin-based filters across small and mid-market hosting. If your click-tracking domain, redirect domain, or unsubscribe domain ends up here, expect SpamAssassin scores to spike across a wide swath of inboxes.

URIBL (Black / Multi) — Impact: Medium

Similar to SURBL but maintained independently, URIBL focuses on URI hosts found in message bodies. It's a common second opinion alongside SURBL in commercial filtering stacks.

One practical thing to watch: your custom tracking domain is also at risk. If you're using a CNAME-based click tracking domain and it gets associated with spam campaigns, it can end up on a URI list. That's one reason a lot of experienced senders have moved away from link tracking entirely.

Why Checking "Your IP" Is Probably Useless

This is the part that trips up almost everyone who sends through a relay, a sequencer, or shared sending infrastructure.

When you click "send" in your email tool, the IP that actually delivers the message to Gmail or Outlook is almost never the IP you'd guess. It's not your office IP. It's not your server's public IP. It's not the IP your sequencer's marketing page shows. It's the IP of the outbound MTA that actually handed the message to the receiving mail server — typically a relay your sending platform owns or rents.

That outbound IP is the one a receiving server sees. That outbound IP is the one that can get listed. And that outbound IP is the only one worth checking against Spamhaus, Barracuda, and SpamCop.

If you're pasting your IP into a blacklist checker, you're almost certainly looking at a number that has nothing to do with your actual deliverability.

How to Find the IP That Actually Got You Listed

The real outbound delivery IP is hiding in the email headers of any message you've successfully delivered. Here's how to find it.

Step 1: Send a test to an inbox you control

Use a fresh Gmail or Outlook address. Send from the exact mailbox you're troubleshooting so you get the right relay path.

Step 2: Open the raw email headers

• Gmail: open the message, click the three-dot menu next to the reply button, and select "Show original." The full raw headers open in a new tab.
• Outlook on the web: open the message, click the three-dot "More actions" menu, then View, then "View message source."
• Apple Mail: View → Message → Raw Source (or All Headers).

Step 3: Find the last (bottom-most) Received: header before your test inbox

Received: headers stack chronologically with the most recent on top. Read from the bottom up — the lowest Received: line written by the receiving provider is the one that records the IP that actually delivered to them.

Step 4: Pull the IP out of that line

You're looking for something like from mail.example.com ([203.0.113.42]). The IP in brackets is the real outbound delivery IP.

Step 5: Check that IP (and your domains)

Now run the outbound IP through a multi-list checker like our blacklist checker. Separately, check your sending domain and any link or tracking domains against Spamhaus DBL, SURBL, and URIBL.

Then ask: are you actually seeing bounce errors that name a specific blacklist? If the answer is no, a listing you found might not be causing your problem at all.

Which Blacklists Actually Affect B2B Cold Email?

Here's an honest breakdown of impact for cold email sending to professional inboxes:

List	Impact	Why
Spamhaus ZEN	Very High	Referenced by Microsoft and most enterprise filters
Spamhaus DBL	Very High	Follows your domain across every IP
Barracuda BRBL	High	Common in mid-market and enterprise
SURBL	Medium-High	Heavy use in SpamAssassin stacks
URIBL	Medium	Second opinion alongside SURBL
SpamCop	Medium	Time-weighted, auto-clears
UCEPROTECT L2/L3	Very Low	Almost never used for delivery decisions

How to Actually Fix a Blacklist Problem

01. Find the right IP first. Pull the raw headers from a delivered test email and find the actual outbound delivery IP. Don't check your server IP, your office IP, or the submission hostname.

02. Confirm it's actually the bottleneck. Look at real bounce messages. If receiving servers aren't naming a specific blacklist in the SMTP error, the listing you're staring at probably isn't the cause.

03. Check your domains separately. Run your sending domain, link domains, and tracking domain against Spamhaus DBL, SURBL, and URIBL. A clean IP doesn't help if a URI in the message is listed.

04. Fix the underlying behavior before delisting. Most lists will re-list you within hours if the spam complaints, traps, or volume spikes that caused the listing are still happening. Pause sending, identify the source, then request delisting.

05. Know when to stop. If your spam complaint rate is approaching 0.3%, your bounce rate is above 5%, or you have a confirmed Spamhaus SBL or DBL listing with real bounce evidence — stop sending and remediate before continuing.

Bottom Line

Most deliverability problems blamed on blacklists aren't actually blacklist problems — and the ones that are usually involve a different IP or a different list than the one being checked. Pull your real outbound IP from headers, check both your IP and your domains, and only treat a listing as the cause when bounce evidence actually names it.

MailVitals monitors 34 DNSBLs across your sending IPs and domains, so listings surface the day they happen — against the IP that's actually delivering your mail.

👉 Related: How Do I Know If I'm Blacklisted? · Why Are My Emails Going to Spam?