Article
Spamhaus SBL vs XBL vs PBL: What Each List Means and How to Fix It
By Unlimited Verifier Team ·

Summary
The Spamhaus SBL lists confirmed spam sources, the XBL lists compromised machines and open proxies, and the PBL lists dynamic end-user IP ranges that should not send mail directly to other servers. The ZEN return code shows which list matched, and that code determines the fix.The Spamhaus SBL (Spamhaus Block List) lists sources of spam operations, the XBL (Exploits Block List) lists compromised machines and open proxies, and the PBL (Policy Block List) lists dynamic or end-user IP ranges that should not send mail directly to other servers. The return code from a ZEN lookup shows which list matched, and each one needs a different fix.
For the wider context, see our pillar guide on spam traps and email blacklists. This article covers the three Spamhaus lists, how to read their codes, and how to choose the right fix.
Quick answer
- SBL covers confirmed spam sources, and Spamhaus staff curate its entries. Removal goes through a manual Spamhaus review, and no timeline is guaranteed.
- XBL covers compromised machines, bots and open proxies, and it detects them automatically. Listings usually lift once the behaviour stops, but a live compromise gets relisted.
- PBL is a policy list of ranges that should not deliver directly to mail servers. Being listed does not mean you sent spam.
- ZEN is the combined lookup. Its return code tells you which list matched, and that code determines the fix.
- Diagnose first. Verifying your recipient list does not clear any of these lists, because they track IPs and networks, not email addresses.
What is the difference between the Spamhaus SBL, XBL and PBL?
Each list answers a different question, which is why each needs a different fix. The SBL asks whether an IP is tied to spam operations, the XBL asks whether a machine is compromised, and the PBL asks whether an IP should be delivering mail to other servers at all.
| SBL | XBL | PBL | |
|---|---|---|---|
| What it targets | Spam operations, spam-support services and netblocks used for spam | Infected PCs, trojan- and bot-driven hosts, open proxies and relays | Dynamic, residential, dial-up and DSL ranges |
| How entries are created | Curated by Spamhaus staff | Automated detection, drawing on Spamhaus's Composite Blocking List (CBL) data | Submitted by ISPs and network owners, or added by Spamhaus |
| Does your own list cause it? | Rarely on its own | Rarely | No. The cause is the network type your IP sits in |
| Typical removal path | Spamhaus review after the source has stopped | Automatic once the behaviour stops, after you clean up | Ask the ISP (ISP-maintained) or use Spamhaus's PBL process (Spamhaus-maintained), after moving to a static, correctly named IP |
| Main risk to a legitimate sender | Scope: a listing can cover a netblock, and removal is slow | Relisting if the compromise is not closed | Day-one blocking for new senders on dynamic infrastructure |
Two details decide most real cases. First, SBL listings can cover whole netblocks, so a clean IP inside a listed range can be affected. Second, PBL entries reflect configuration, so a sender with clean content and no complaints can still be caught.
Bottom line: Treat the lists as three different problems: a source problem (SBL), an infection problem (XBL), and a configuration problem (PBL).
How does the Spamhaus SBL work, and why is it hard to leave?
The SBL targets the operations and infrastructure behind spam, not ordinary businesses with messy contact lists. A poor contact list rarely produces an SBL entry by itself. The SBL is hard to leave because its scope can extend past your own address, and removal depends on evidence that the source has stopped.
Check range history before you commit to an IP. Ask your provider whether the range was recently reassigned, and look up the address on Spamhaus's website. A recycled range can carry the previous tenant's reputation, and you inherit it the day you start sending.
If you are listed, stop sending from that IP and document what changed in the source. Submit one removal request through Spamhaus's process. Repeated resubmissions do not speed up a manual review. No average review time is published, so plan for a slow process and route volume elsewhere while you wait.
Bottom line: SBL listings concern the source of mail, so check range history before buying an IP and expect a slow, evidence-based removal.
What does the Spamhaus XBL detect, and how do you get off it?
The XBL catches machines that behave like part of a spam botnet: infected PCs, trojan-driven hosts, bots, and open proxies or relays that let outsiders send mail through them. Business senders usually trigger it through an abused contact form, an outdated CMS plugin or a forgotten SMTP login, not through deliberate spamming.
Removal is generally automatic once the detected behaviour stops, but that is not a fix. If the compromise remains, the machine gets relisted. Work through this sequence:
- Check mail logs for authentication from accounts you do not recognise, and for unexpected connections on port 25.
- Rotate SMTP and API credentials, and close any open relay.
- Scan the host and remove malware and unauthorised scripts, including plugins that accept form input.
- Watch the lookup status for several days before you return to normal volume.
Bottom line: XBL clears itself, but relisting follows any unresolved compromise, so closing the hole is the real cure.
What is the Spamhaus PBL, and why do legitimate senders end up on it?
The PBL is a policy list of IP ranges, usually residential, dial-up, DSL or dynamically assigned, that should not deliver mail directly to another mail server. Legitimate mail is expected to go out through an authenticated submission server, so a direct connection from an end-user range looks like a warning sign. You can be listed with perfect content and zero complaints.
The PBL has two maintenance types, and they change your removal route. Return code 127.0.0.10 marks an ISP-maintained entry, where the network owner supplied the range, so the ISP is the party to ask. Return code 127.0.0.11 marks a Spamhaus-maintained entry, which goes through Spamhaus's PBL removal process.
New senders hit the PBL most often because they send from a VPS or a home-office connection. Check the reverse DNS name of your sending IP with dig -x. Names containing "dynamic" or "dsl" are a warning sign, though not proof of a listing. Then fix the cause:
- Use a static IP with matching reverse DNS. The reverse name should match your sending hostname.
- Relay through an authenticated submission service. Sending through a provider's SMTP or API server avoids direct delivery from your own address.
- Ask the network owner. If your IP is static and correctly named but still listed, the ISP can request correction of the range.
Receivers vary. Some only score a PBL hit, while others reject the message outright, so plan for the strict case.
Bottom line: PBL concerns how you send, not what you send, so the fix is infrastructure rather than list cleaning.
How does Spamhaus ZEN combine the lists?
ZEN is a single DNS query at zen.spamhaus.org that covers the SBL, CSS (Spamhaus's snowshoe-spam list), XBL and PBL. Many receiving systems query ZEN rather than each list separately, so one response tells you which list matched. Based on Spamhaus's published return-code information, the mapping is:
| Return code | List | Practical meaning |
|---|---|---|
| 127.0.0.2 | SBL | Linked to a spam source |
| 127.0.0.3 | CSS | Snowshoe-style sending across several IPs |
| 127.0.0.4 to 127.0.0.7 | XBL | Compromised host or open proxy |
| 127.0.0.10 | PBL, ISP-maintained | Dynamic range supplied by the network owner |
| 127.0.0.11 | PBL, Spamhaus-maintained | Dynamic or end-user range added by Spamhaus |
| 127.255.255.254 | None (refusal) | Your resolver was blocked, so the lookup is invalid |
Confirm these codes against Spamhaus's current documentation before you automate alerts, because codes can change.
Two operational rules follow. First, Spamhaus refuses queries sent through many public resolvers and answers them with 127.255.255.254. That code means your lookup was refused, not that you are listed, so repeat the query from your own server. Second, Spamhaus's usage terms separate free use from commercial or high-volume use, which generally requires its Data Query Service. Read the terms before you wire ZEN into a sending platform. The DBL checks domains rather than IPs, so it is covered separately in our guide to the Spamhaus DBL.
Bottom line: One ZEN response names the list that hit you, but only if you query from a resolver Spamhaus accepts.
How do you check whether your sending IP is listed?
Run the check yourself. A dashboard that says "blacklisted" without a code does not tell you which fix applies. Follow these steps:
- Find the sending IP. Open the
Received:headers of a message that went out, or ask your ESP or server administrator for the outbound address. - Reverse the octets. For 203.0.113.25, the reversed form is 25.113.0.203.
- Query ZEN. Run
dig +short 25.113.0.203.zen.spamhaus.org. A response in 127.0.0.0/8 means a listing. NXDOMAIN means no listing. - Read the code. Match the response to the table above. If you get 127.255.255.254, your resolver was refused, so repeat the query from your own server.
- Check reverse DNS. Run
dig -x 203.0.113.25 +shortand compare the name with your sending hostname. - Check other lists. A clean ZEN result does not mean you are clean everywhere. Run your IP through a blacklist checker to cover the other lists receivers consult.
- Log the result. Record the IP, date, time and return code. Removal requests move faster with a timeline attached.
Bottom line: The return code, not the colour of a dashboard, tells you what to fix, so record it before you act.
Which list is causing your bounces, and what should you do?
Use this table to match a symptom to a cause. Rejection text often includes the list name or a 5.7.1 enhanced status code, which RFC 3463 defines as "Delivery not authorized, message refused". Use that code as a clue, then confirm with ZEN.
| What you see | Likely cause | What it means | First action |
|---|---|---|---|
| Rejection names Spamhaus SBL, or ZEN returns 127.0.0.2 | SBL | Your IP or netblock is linked to a spam source | Stop sending from the IP, check range history, submit one removal request |
| ZEN returns 127.0.0.3 | CSS | Snowshoe-style pattern across IPs | Lower volume per IP, consolidate sending, review list sources |
| ZEN returns 127.0.0.4 to 127.0.0.7 | XBL | Compromised host or open proxy | Clean the host, rotate credentials, close relays |
| ZEN returns 127.0.0.10 or 127.0.0.11 | PBL | Mail is leaving a dynamic or end-user range | Move to a static IP with matching reverse DNS, or relay through an authenticated submission server |
| Rejections cite bad addresses, not IPs | Not a Spamhaus listing | Your list has invalid or risky recipients | Verify the list, suppress invalid addresses, then re-send |
The last row is where verification helps. Hard bounces and spam-trap hits rarely create a Spamhaus listing directly, but they damage the reputation signals receivers use, and that damage can surface in filtering decisions and other blocklists.
Bottom line: Match the code to the cause first, because a PBL fix (infrastructure) is nothing like a bounce fix (list hygiene).
How do you get delisted, step by step?
Use this sequence for any Spamhaus listing. Each step produces evidence a reviewer or network owner can check.
- Record the code and scope. Note the list, return code, IP, and whether neighbouring IPs in the same range are also listed.
- Stop the sending that triggered it. Pause the affected IP and move volume to a clean one. Continued sending slows the review.
- Fix the root cause. For SBL, document the change at the source. For XBL, show the clean-up. For PBL, show the static IP and matching reverse DNS.
- Request removal through the correct route. For SBL and XBL, use Spamhaus's process. For ISP-maintained PBL entries, work with the network owner. Send one clear request rather than several.
- Re-enter gradually. Start with your most engaged recipients and watch rejections and bounces on every batch.
- Monitor for relisting. Check ZEN daily for two weeks after restoration.
For other lists, the sequence is similar. Our guide to removal from the Barracuda blacklist covers that list specifically, and 8 reasons your IP address is blacklisted lists the common causes beyond these three.
Bottom line: Delisting is an evidence exercise: pause, fix, document, request once, then re-enter slowly.
Where does email verification fit in?
Email verification does not clear or prevent SBL, XBL or PBL listings, because those lists describe IPs and networks, and a verifier checks addresses. Be clear about this with clients and colleagues. Verification reduces the bounces and spam-trap hits that erode your reputation with receivers, which matters even when no Spamhaus list is involved. If you are comparing best email verification tools, look for per-address categories and exports, not only a headline price. The buyer's checklist for choosing a verifier covers what to check.
Unlimited Verifier handles the list side. You can upload and verify a list as a CSV or Excel file up to 10MB, and the email column is detected automatically. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged. Results are sorted into Valid, Risky and Invalid, and you can export them as CSV, Excel or JSON. For one address, the free email checker works without setting up a list. Its checks cover recipient addresses, not your sending IP, so pair it with a blacklist checker for that step.
Here is the workflow for a database that is also producing rejections:
- Export the contact list from your ESP as a CSV.
- Verify it and keep the Valid contacts.
- Suppress Invalid addresses in your ESP.
- Hold Risky contacts, including catch-all domains, out of your first sends. The catch-all email verification page explains how those results are handled.
- Re-import only the Valid contacts. If you want checks inside your own systems, use the Email verification API or read about automated checks.
Export your results promptly. Pro keeps results for 30 days, and the Free plan keeps them for 24 hours, so save files to your own storage before the window closes. For ongoing practice, the list maintenance schedule guide covers cadence, and validating at signup explains how to stop bad addresses entering the list. This is the core of email verification compliance and hygiene. Teams running email verification for ecommerce and saas signup flows will also want the spam traps basics, because trap hits are harder to remove than bounces.
Bottom line: Verification protects the list and your reputation signals, but it cannot clear an IP listing.
What does a worked diagnosis look like with real numbers?
The rejection and list figures are illustrative. The arithmetic and plan limits are real.
Diagnosis. A team sends 20,000 messages from a new VPS, and 1,400 are rejected:
1,400 ÷ 20,000 = 7.0% rejection rate
The rejection text cites Spamhaus. ZEN returns 127.0.0.10, which is an ISP-maintained PBL entry, and the reverse DNS name includes "dynamic". The problem is infrastructure. The team asks its ISP to correct the range, moves sending to a static IP with matching reverse DNS, and routes volume through an authenticated submission server.
Result. The next 20,000-message batch shows 40 rejections:
40 ÷ 20,000 = 0.2% rejection rate
No list cleaning was needed for this problem. Had the rejections been bounces, verification would have been the fix.
List work. The same team now has a 40,000-row contact list to verify. Pro allows up to 25,000 emails per list, so the file is split before upload:
25,000 + 15,000 = 40,000 rows across two lists
Standard verification is included on every plan, with no per-email fees. Deep verifications are a separate allowance: Pro includes 25,000 a month. Running deep checks on all 40,000 rows would exceed that by 15,000, so prioritise the Risky segment and recently imported contacts for deep checks. Email verification pricing on Pro is $29/month, or $25/month billed annually, and it includes 100,000 API emails a month.
Bottom line: Diagnose the code before you spend time or money, because a PBL fix would not have been solved by cleaning the list.
What mistakes make Spamhaus listings last longer?
- Treating a PBL hit as a spam accusation. A PBL entry describes your IP's network type. Changing your content will not clear it.
- Reading 127.255.255.254 as a listing. That code means a public resolver was refused. Query from your own server.
- Buying an IP without checking its history. A clean-looking address inside a listed range can be affected.
- Clearing one list and assuming you are clean. Check ZEN and the other lists receivers consult.
- Sending removal requests repeatedly. Multiple requests before the root cause is fixed slow the review.
- Blaming the verifier for an IP listing. Address verification and IP reputation are separate problems.
- Restarting full volume after delisting. Re-enter with your most engaged recipients first.
Bottom line: Most mistakes come from fixing the wrong layer, so match the list to the layer before you act.
How we compared (and limitations)
This guide is based on public documentation: Spamhaus's published list descriptions and return-code information, RFC 5782 on DNS blacklists, RFC 3463 on enhanced status codes, and Google's sender guidelines. Google asks bulk senders to keep user-reported spam below 0.10% and never let it reach 0.30%. Other guidance often cites 0.3% as the ceiling. Where sources differ, we recommend 0.10% as the working target, because it leaves room before any line is crossed. We have not submitted removal requests to Spamhaus or tested any list's review process. Return codes, usage terms and removal procedures change, so confirm them against current documentation before you automate alerts.
Unlimited Verifier details come from the company's published plan facts. The company states 99.5% accuracy for deep verification, which is its own figure rather than an independent benchmark. The worked-example figures are illustrative.
Bottom line: Use these codes and workflows as a starting point, then confirm them against Spamhaus's current documentation before you act.
Return code to fix mapping
Use this framework after a ZEN lookup:
- Read the return code.
- Match it to the list.
- Apply the fix for that list.
| Return code range | List | Likely cause | Fix |
|---|---|---|---|
| 127.0.0.2, 127.0.0.3 | SBL | Source tied to spam operations | Stop the source, then request Spamhaus review |
| 127.0.0.4 to 127.0.0.7 | XBL | Compromised host or open proxy | Clean the machine, close the open relay, wait for auto-expiry |
| 127.0.0.10, 127.0.0.11 | PBL | Dynamic or end-user IP range | Move to a static IP with proper reverse DNS, or contact the ISP |
Do not start with list cleaning. Identify the code first, because the fix depends on it.
Frequently asked questions
What does the Spamhaus SBL list?
The SBL lists confirmed spam sources, including spam operations, spam-support services and netblocks used for spam. Spamhaus staff curate its entries. Because listings can cover whole netblocks, a clean IP inside a listed range can be affected. Removal requires a review by Spamhaus after the source has stopped sending spam.
What does the Spamhaus XBL list?
The XBL lists IP addresses that appear compromised, such as machines infected with trojans or bots, and open proxies or relays. Detection is automated and draws on Spamhaus's CBL data. Listings usually lift once the malicious behaviour stops, but a machine that is still compromised will be relisted.
What does the Spamhaus PBL list?
The PBL is a policy list of IP ranges that should not deliver mail directly to other mail servers, typically dynamic, residential, dial-up and DSL addresses. Being on the PBL does not mean you sent spam. ISPs or network owners maintain most entries, and the fix is usually to use a static, properly named IP or to request removal through the appropriate process.
How do I tell which Spamhaus list I am on?
Run a lookup against the ZEN combined list and read the return code. Codes in the 127.0.0.2 and 127.0.0.3 range indicate the SBL, 127.0.0.4 through 127.0.0.7 indicate the XBL, and 127.0.0.10 or 127.0.0.11 indicate the PBL. Check the current Spamhaus documentation for the full code set, since codes can be extended over time.
Does verifying my email list remove me from Spamhaus?
No. Spamhaus lists track IP addresses and networks, not email addresses, so cleaning or verifying a recipient list does not clear a listing. You need to identify the list, fix the underlying cause, and then request removal where the list allows it.
How long does Spamhaus removal take?
Spamhaus does not guarantee a timeline. XBL listings often lift on their own after the infection is cleaned and the behaviour stops, while SBL removal requires a manual review and can take longer. Some PBL removals depend on the ISP or on a configuration change, so the time to resolve varies by case.
Can a Spamhaus listing affect IPs I do not own?
Yes, in some cases. SBL listings can cover entire netblocks, so a clean IP sitting inside a listed range may be affected even though it has never sent spam. Checking the netblock ownership and the listing scope helps confirm whether the problem is your address or the wider range.
Should I use the ZEN lookup or check each list separately?
Use ZEN for routine checks because it combines the lists in one query and returns a code that identifies the match. Checking individual lists is useful when you need to see the specific policy or listing details. Either way, the return code is what tells you which fix applies.
Is a PBL listing the same as being blacklisted for spam?
No. A PBL listing is a policy statement about the type of IP address, not a judgement about your mail content. A sender with clean content and no complaints can still hit a PBL block if the server sits on dynamic or end-user infrastructure, so the fix is a configuration change rather than a content change.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.