Email blacklists: check and delist

A blacklist listing is the one infrastructure problem that can zero out a campaign on day one with perfect copy and a clean list. It is also the one most teams never check before launch, because the domain sends fine from the sender’s side. This guide covers which lists matter, how listings happen, how to check, and how delisting actually works. For the launch-day story of how domains end up listed, see why your cold email domain landed on a blacklist.

What a blacklist is

A blacklist (also called an RBL or DNSBL) is a published, DNS-queryable list of IPs or domains flagged for spam-associated behavior. Receiving mail servers query these lists in real time during delivery. A hit on a high-confidence list means the message is rejected, throttled, or filtered before any human sees it.

Two kinds matter for cold email:

• IP lists flag the sending server’s address. When you send through Google Workspace or Microsoft 365, the IPs belong to the provider and are shared with thousands of senders, so individual IP listings are mostly out of your control and usually transient.
• Domain lists flag your domain itself, in the return-path, the From, or the links in the body. These follow you across any IP and any provider. For cold email, domain listings are the ones that hurt.

The lists that matter

• Spamhaus is the one with real teeth. ZEN aggregates its IP lists; DBL is the domain list. Spamhaus is consulted by most major mail infrastructure, and a DBL listing suppresses delivery almost everywhere.
• SpamCop lists IPs based on user spam reports and spam-trap hits. Widely queried, listings age out fast, typically within 24 to 48 hours of the reports stopping.
• Barracuda feeds Barracuda’s security appliances, common in mid-size and enterprise inboxes. Relevant when your targets are companies behind corporate filters.
• SURBL and URIBL list domains found inside message bodies. Your sending domain can be clean while a tracking or link domain in the message is listed, which is one reason tracking domains get their own checks.

Hundreds of other lists exist. Most have near-zero real-world query volume, so a listing on an obscure RBL is noise. Weight your response by whether the list is actually consulted.

How listings happen

1. Spam traps. Addresses that never belonged to a real prospect, seeded to catch senders with scraped or purchased lists. One trap hit on a pristine list operator like Spamhaus can list a domain immediately.
2. Complaint volume. Enough recipients clicking “report spam” feeds complaint-driven lists and provider filtering at once.
3. Sudden volume from a new domain. The burn pattern described in the domain warmup guide. New registration plus instant bulk volume is a listing trigger on its own.
4. Bad list hygiene. High hard-bounce rates signal a scraped list, and scraped lists contain traps.
5. Inherited history. Expired domains carry their past. A domain that spammed under its previous owner can be listed before you send message one.
6. Shared infrastructure. Another tenant on the same sending IP misbehaves. Annoying, mostly self-healing, and a reason to judge IP listings calmly.

How to check

Check at three moments: before buying inboxes on a domain, before every launch, and daily while campaigns run.

A manual check means querying each list’s lookup form one at a time. The email blacklist checker runs the domain and its resolved mail-server IPs against the major domain and IP lists in one pass, in the browser. For a wider readiness view including age and authentication, use the domain reputation checker.

An agency running multiple client workspaces should not rely on a human remembering this. OutboundQA checks current blacklist status as one launch signal and rechecks daily during monitoring, so a listing that appears mid-campaign raises an alert instead of a mystery.

Current status vs. history

A current lookup answers whether the sender is listed right now. Historical reputation answers a different launch question: did this domain, IP, shared pool, or nearby network recently produce abuse signals?

That history matters because a sender can be unlisted today and still deserve review:

• a listing cleared yesterday after repeated incidents;
• the sending IP sits in a contaminated shared pool;
• the SMTP egress IP has recent abuse reports;
• a domain was cleanly delisted but the cause was never fixed.

Treat current high-confidence listings as launch blockers. Treat recent abuse history, repeated historical listings, and IP abuse signals as reasons to slow down, move infrastructure, or get a deliverability owner to review before volume starts.

How to delist

First, stop sending from the listed domain. Delisting while the behavior continues gets you relisted with less goodwill.

Second, find and fix the cause: verify the list, remove the scraped segment, fix the volume ramp. Every serious delisting form asks what changed.

Then, per list:

• Spamhaus: look up the domain or IP at spamhaus.org. Listings link to a reason code and a removal path. DBL removal requires explaining the cause and the fix; low-quality requests are ignored. Turnaround is hours to a couple of days for a credible request.
• SpamCop: listings expire automatically about 24 hours after reports stop. There is an expedited self-service delist, but if the cause remains you will bounce back on.
• Barracuda: removal request at barracudacentral.org, asks for contact details and a reason. Usually processed within 12 to 24 hours.
• SURBL / URIBL: each has its own lookup and removal form for listed body domains.

Never pay for delisting. Legitimate lists do not charge, and paid “delisting services” submit the same free forms you can.

If a Spamhaus DBL listing will not clear, or the domain has repeat listings, retire it. Days of a stalled campaign cost more than a replacement domain, and a domain with listing history stays fragile.

Common mistakes

1. Checking once at setup and never again. Listings appear mid-campaign. Day 9 is as dangerous as day 1.
2. Panicking over obscure lists. A hit on a list nobody queries changes nothing. A Spamhaus DBL hit changes everything. Triage by list weight.
3. Delisting without fixing the cause. Relisting after removal is scored worse than the original listing.
4. Ignoring link and tracking domains. SURBL-class lists look inside the message. A listed tracking domain filters mail from a clean sending domain.
5. Buying aged domains without history checks. Check before purchase; the previous owner’s spam is your problem now.

FAQ

How do I know if the listing is domain or IP? The lookup result names the list, and each list is one or the other. Domain listings (Spamhaus DBL, SURBL) are yours to fix. Shared-provider IP listings usually resolve without you.

How long does delisting take? SpamCop, about a day on its own. Barracuda, 12 to 24 hours after a request. Spamhaus, hours to days depending on the case you make.

Will a listing definitely block my mail? It depends on which receivers consult that list. Spamhaus coverage is broad enough to treat as universal. Minor lists may affect almost nobody.

Can a brand-new domain already be listed? Yes, if it existed before you owned it, and occasionally new domains get swept into pattern-based listings. Check before you build on it.

Blacklist status and sender-history risk are part of what OutboundQA checks before a launch and rechecks after it. Run the email blacklist checker on a sending domain now.