Skip to content
BlacklistMonitoring

Spamhaus Blacklist Check for Business Senders

· 8 min read

Checks run by DNS only. Nothing is sent from or to your domain.

A Spamhaus blacklist check means looking up your IP or domain on the Spamhaus lists, mainly ZEN for IPs and DBL for domains, through the Spamhaus web lookup or a DNS query. A listing returns a code in the 127.0.0.x range that names the list. The two traps that catch business senders are querying through a public resolver such as 8.8.8.8, which Spamhaus refuses and which looks like a clean result, and checking once instead of continuously. A listing that appears at 2 a.m. costs you a day of bounced mail if nobody is watching.

This article is for people who send email for a living, hosting providers, agencies, SaaS companies and in-house teams. It covers how to read a Spamhaus result, what each list means for delivery, a worked example with real return codes, and when it makes sense to automate the check. We sell a monitor, so we say plainly where a manual lookup is enough.

What the Spamhaus lists cover

Spamhaus runs several lists, and a listing on each one means something different. ZEN is the combined list for IP addresses. It merges SBL, CSS, XBL and PBL into one query, so most checks start there. The domain list is DBL.

ListWhat it containsReturn codeWhat to do
SBLIPs that Spamhaus has seen send spam or host spam operations127.0.0.2Find the cause, fix it, then open a removal ticket on the Spamhaus lookup page
CSSLow reputation sending, including snowshoe spam across many IPs127.0.0.3Review the whole range, not one IP, and fix the sending behavior
XBLHosts with exploits or malware, infected machines and hijacked servers127.0.0.4 to 127.0.0.7Clean the machine or mailbox, then request delisting
PBLIP ranges that should not send mail directly, mostly dynamic consumer addresses127.0.0.10 and 127.0.0.11Send through your provider, or ask the range owner to remove the IP if it is yours to send from
DBLDomains seen in spam, phishing or malware, queried by domain not IP127.0.1.2 and upRemove the offending content, then request delisting

The code tells you which problem you have before you read anything else. A PBL code on a new server means the IP was never meant to send mail, which is a hosting setup problem, not a reputation problem. An XBL code means something on that IP was compromised. An SBL or CSS code means Spamhaus has judged the sending to be spam. The official definitions live on spamhaus.org, and they are the source to read before filing a request.

A worked example with real return codes

Take the documentation address 203.0.113.10. A DNS check reverses the octets and appends the list zone. The query is 10.113.0.203.zen.spamhaus.org. If the IP is not listed, the lookup returns no answer (NXDOMAIN). If it is listed, you get one or more addresses back.

  • 127.0.0.2 means the IP is on the SBL. Mail to many receivers will be rejected, and the bounce usually names Spamhaus.
  • 127.0.0.4 means the IP is on the XBL. Treat it as a security incident first, a deliverability incident second.
  • 127.0.0.10 means the IP is on the PBL. Your provider's IP range is flagged as end-user space.
  • 127.255.255.254 means the query came from a resolver Spamhaus does not answer for. This is not a listing and not a clean result. It is an error that many scripts misread as clean.
  • 127.255.255.255 means you exceeded the free query limit.

That last pair is where most home-built checks quietly fail. Spamhaus gives free DNS lookups to low volume users who query from their own resolver. Queries sent through public DNS services such as Google or Cloudflare resolvers, or through the shared resolver of a large cloud provider, get an error answer instead of a verdict. A script that treats "no 127.0.0.2 found" as clean will report your listed IP as fine. Spamhaus documents the volume limits and its commercial data query service on its site, and a monitor that checks thousands of assets every few minutes needs to use a proper channel, not a free one.

How to check an IP or domain manually

For a one-off, the web lookup on Spamhaus is the safest option because it removes the resolver problem. Enter the IP, domain or URL, and the result states whether it is on SBL, CSS, XBL, PBL or DBL and why. If you run your own DNS resolver, the command line check also works. Replace the octets and keep the order reversed.

Two further habits save time. First, check the domain as well as the IP, because a clean IP sending links to a listed domain can still be rejected. Second, check the IP your mail actually leaves from, which is the one in the message headers, not the one on your website. A marketing platform or an SMTP relay often uses a different address from the one you assume.

Why a single check is not enough

A Spamhaus listing does not announce itself. The first sign is usually a bounce, a customer reporting that mail did not arrive, or a drop in opens. By then the listing may be a day old. The costs of finding it late are concrete, and they scale with your sending volume.

Consider an agency sending 40,000 messages a day for clients from a pool of IPs. A listing that starts at midnight and is found at 9 a.m. has already blocked every message to receivers that query Spamhaus during those nine hours. If the cause is a compromised mailbox, the sending continues until someone stops it, and every further message makes the listing harder to remove. Finding it in 5 or 15 minutes instead of 9 hours is the difference between one pause and a lost day.

The same logic applies to hosting providers. One customer's compromised website sending from a shared IP gets that IP onto the XBL or SBL, and every other customer on the address pays for it. The IP range blacklist check exists for exactly this case, watching entire customer subnets.

What a monitor adds over a manual lookup

TaskManual Spamhaus lookupMonitor with alerts
Detect a new listingWhen you remember to lookWithin 5 to 60 minutes, depending on plan
Cover many IPs and domainsOne at a time10 to 5,000 assets per workspace
Know which list and whyYou read the resultThe alert names the list and links to the removal page
Confirm delistingCheck again by handA second alert when the list returns clean
Catch relistingNot at allAlert the moment it returns
Other 100 plus listsSeparate lookups109 lists in the same check

BlacklistMonitoring checks each domain and IP on 109 DNS blacklists, including Spamhaus, every 60, 15 or 5 minutes depending on the plan, and alerts by email, Slack, Teams or webhook the moment a listing appears or clears. Starter costs $49 a month for 10 domains and IPs, Business $149 for 100, Agency $499 for 500 and Scale $1,499 for 5,000. Full details are on the blacklist monitoring page and the pricing page.

For Microsoft mailboxes, a Spamhaus result is only half the picture. An IP can be clean on every list and still be junked at Outlook.com. Business and higher plans read your Microsoft SNDS data and alert on complaint rate, which is covered on the Microsoft SNDS monitoring page.

When a manual check is enough

If you send from one or two IPs, send a few hundred messages a week and tolerate a day of delay, a monthly lookup on the Spamhaus site is reasonable. If a listing would stop revenue, trigger customer tickets or breach an SLA, a monitor is cheaper than one incident. A single mid-sized campaign blocked for a day is usually worth more than a year of Starter.

The honest limit of any monitor, ours included, is that it detects and guides. It cannot delist you. Spamhaus and every other list owner require the request from the party that controls the IP or domain, and they want to see that the cause is fixed. If you are in that position now, how to get off an email blacklist and the blacklist removal workflow walk through the order that gets requests accepted.

What to do in the first hour after a Spamhaus alert

  1. Read the return code or list name. It tells you whether you face a configuration problem (PBL), a compromise (XBL) or a reputation judgment (SBL, CSS, DBL).
  2. Stop the sending that caused it. A request filed while the same mail still flows out is rejected.
  3. Find the cause. Check for a hijacked mailbox, an abused web form, a purchased list or a customer on a shared IP. Your DMARC reports show which system sent mail as your domain, see DMARC monitoring.
  4. File the removal request with a short, specific statement of what changed.
  5. Keep the IP on 5 or 15 minute checks for a week to catch relisting.

Frequently asked questions

What is a Spamhaus blacklist check?

It is a lookup of an IP address or domain on Spamhaus lists such as ZEN and DBL to see whether it is listed. You can do it through the Spamhaus web lookup or a DNS query. A listing returns a code in the 127.0.0.x range that identifies the list and the reason.

How do I check if my IP is on Spamhaus?

Use the lookup on the Spamhaus website, or query the reversed IP against zen.spamhaus.org from your own resolver. No answer means not listed. A 127.0.0.x answer names the list. Do not use public resolvers, because Spamhaus answers them with an error that looks like a clean result.

What does 127.255.255.254 mean on Spamhaus?

It means the query came through a resolver Spamhaus does not serve, usually a public DNS service. It is not a listing and not a clean result. Rerun the check from your own resolver or use the Spamhaus web lookup for a real verdict.

How long does Spamhaus removal take?

PBL entries are often cleared within the hour if the IP is allowed to send. SBL and DBL requests commonly take hours to a few days, longer if the cause is not fixed. The time depends on proof of the fix, and a repeat offense extends it.

Can I monitor Spamhaus automatically?

Yes. A blacklist monitor checks your IPs and domains on Spamhaus and other lists every 5 to 60 minutes and alerts you when a status changes. BlacklistMonitoring starts at $49 a month for 10 domains and IPs.

Is a Spamhaus listing the same as being blocked by Gmail or Outlook?

No. Gmail and Microsoft keep their own reputation systems, and a clean Spamhaus result does not guarantee inbox delivery. Spamhaus is used by many receivers and filters, so a listing hurts widely, but you should also track inbox placement and provider data such as Microsoft SNDS.

More guides