← Back to blog

Email Blacklists (DNSBL) Explained: What They Are and How to Check Them

How DNS blocklists work, which lists matter for deliverability, and how to scan your mail server IP before a campaign goes out.

By FeedPipeline Team

  • Blacklists
  • DNSBL
  • Deliverability

Email blacklists—also called DNSBLs or RBLs—are DNS-based lists that mark IP addresses or domains associated with spam. If your mail server IP appears on a major list, inbox providers may reject or filter your mail before authentication even matters.

How DNSBL lookups work

Most IP blocklists use a reversed-IP query pattern:

{reversed-ip}.{blacklist-zone}

Example: if your mail server is 93.184.216.34, a lookup might query:

34.216.184.93.zen.spamhaus.org

If the DNS response is 127.0.0.x, the IP is listed. No response usually means not listed.

Blocklists worth checking

FeedPipeline scans these zones during every domain audit:

ZoneOperator
zen.spamhaus.orgSpamhaus (combined ZEN)
sbl.spamhaus.orgSpamhaus SBL
xbl.spamhaus.orgSpamhaus XBL
bl.spamcop.netSpamCop
dnsbl.sorbs.netSORBS
b.barracudacentral.orgBarracuda
dnsbl-1.uceprotect.netUCEPROTECT Level 1
dnsbl-2.uceprotect.netUCEPROTECT Level 2
dnsbl-3.uceprotect.netUCEPROTECT Level 3
cbl.abuseat.orgCBL (Spamhaus)
psbl.surriel.comPSBL

We also check URIBL domain lists (multi.surbl.org, multi.uribl.com) for domain reputation—not just the sending IP.

Where the IP comes from

Blacklist checks use the primary MX host of your domain:

  1. Look up MX records for yourdomain.com
  2. Resolve the first MX hostname to an IPv4 address
  3. Query blocklists against that IP

If you send through a third-party SMTP relay, the listed IP may be the ESP’s—not your website server. That is normal; monitor the IP your mail actually exits from.

What to do if you are listed

  1. Identify the list — each zone has its own delisting process
  2. Stop the cause — compromised form, open relay, bad list purchase, volume spike
  3. Request removal — follow the operator’s delisting portal
  4. Wait for propagation — DNS TTLs mean changes are not instant
  5. Re-scan before resuming campaigns

Listing on Spamhaus ZEN alone can severely limit Gmail and Microsoft delivery.

Blacklists vs authentication

IssueSymptom
Blacklisted IPBlocks at connect or high spam folder rate across many receivers
Bad SPF/DKIMAuthentication fails in headers; more variable by receiver
Low engagementGradual reputation decline—not always a DNSBL listing

Run authentication and blacklist checks together. Our free checker does both in under a minute.

Prevention habits

  • Warm up new domains and IPs gradually
  • Never send from IPs shared with questionable senders unless you trust the pool
  • Monitor blocklists weekly on production sending domains
  • Fix forward DNS (PTR) and authentication before scaling volume

A clean blacklist scan is not a guarantee of inbox placement—but a listed IP is one of the fastest ways to kill deliverability overnight.

Check your domain for free

Run SPF, DKIM, DMARC, MX, and blocklist checks in seconds.

Open domain checker