Article
How to Get Delisted from Spamhaus: A Step-by-Step Removal Guide
By Unlimited Verifier Team ·

Summary
To get delisted from Spamhaus, first identify the list (SBL, XBL, PBL or DBL) at check.spamhaus.org, then remove the cause of the listing. Submit a removal request only after the fix is in place, backed by evidence, since Spamhaus makes the final decision and publishes no fixed removal timeline.To get delisted from Spamhaus, first confirm which list you're on (SBL, XBL, PBL or DBL) at check.spamhaus.org, remove the cause of the listing, then submit a removal request that proves the fix. Spamhaus makes the removal decision, so your request is only as strong as the evidence behind it: what caused the listing, what you removed, and what changed.
Spamhaus is a nonprofit anti-spam organisation. Many mail servers and filters query its blocklists, so a listing can block or filter your mail, and the damage often outlasts the original problem. This guide covers how each list works, how to diagnose your listing, a seven-step removal process, a request template, a list-cleaning tutorial, and a worked example with the arithmetic shown. It sits within our broader guide to spam traps and email blacklists.
Quick answer
- Diagnose first. Check your sending IP or domain at check.spamhaus.org and record the list (SBL, XBL, PBL or DBL) and the reason text.
- Fix the source. Stop the bad sending, close compromised accounts or remove malware, and clean the list that produced the bounces and complaints.
- Request removal only after the fix is in place. SBL needs a request backed by evidence. XBL usually clears once the infected host stops. PBL is generally handled by your ISP or network operator.
- Verify before you resend. Export, verify, suppress Invalid addresses and hold back Risky ones, so the next campaign doesn't recreate the listing.
- Expect a wait, and skip paid "delisting services". Spamhaus publishes no fixed removal window, and only Spamhaus can remove its own listings.
What do the Spamhaus lists actually mean?
"Blacklisted" can describe very different situations. Spamhaus runs several separate lists, and each one points to a different owner and a different removal path.
| List | What it covers | Typical trigger | How removal works | Who acts |
|---|---|---|---|---|
| SBL (Spamhaus Block List) | Known spam sources and spam operations, including snowshoe senders | Manual review of spam activity | Removal request, after the source has stopped and the issue is resolved | You, then Spamhaus reviews |
| XBL (Exploits Block List) | IPs of compromised machines: malware-infected hosts, botnet nodes, open proxies | Automated detection | Usually clears once the infected host stops being detected | You clean the machine; the listing clears |
| PBL (Policy Block List) | IP ranges that should not send mail directly, typically dynamic or residential | Range policy, supplied by network operators or added by Spamhaus | Generally handled by the network operator | Your ISP or hosting provider |
| DBL (Domain Block List) | Domains found in spam message content, such as links in email bodies | Domain appears in spam | Domain-level removal after the domain is cleaned up | You, then a domain request |
| ZEN | A combined IP list that merges SBL, XBL and PBL | A hit on any underlying list | Remove the cause on the list that applies | Depends on the underlying list |
Most mail servers and checkers query ZEN, so a ZEN hit tells you that you're listed but not on which list. The return code does. Spamhaus documents codes such as 127.0.0.2 (SBL), 127.0.0.4 (XBL) and 127.0.0.10 or 127.0.0.11 (PBL). Return codes can change, so confirm against Spamhaus's current documentation before you act on one. Our explainer on SBL vs XBL vs PBL goes deeper on the codes.
Bottom line: The list determines the removal path. SBL needs a request, XBL usually needs a clean machine, and PBL usually needs your ISP.
How do you find out which Spamhaus list you're on?
Start with Spamhaus's own lookup, then use other tools only as a cross-check. Enter your sending IP or domain at check.spamhaus.org, read the list name and reason text, and save a timestamped copy. Spamhaus's record is the one that matters for removal.
Other sources answer different questions:
| Source | What it tells you | Limitation |
|---|---|---|
| Spamhaus lookup (check.spamhaus.org) | The authoritative list name, return code and reason | Covers Spamhaus lists only |
| Aggregator blacklist checkers | Many blocklists in one view, useful for a quick second opinion | Results can differ from Spamhaus's own data, so don't use them as your removal record. Our roundup of best email blacklist checker tools compares them. |
| Your own bounce and complaint logs | When failures began and which campaign or segment caused them | Shows symptoms, not which list you're on |
| Paid "delisting services" | A claim to file the request for you | Spamhaus makes the decision, so a fee doesn't change the outcome |
Three diagnostic traps catch many senders:
- Resolver errors. Spamhaus documents responses in the 127.255.255.x range, including 127.255.255.254 and 127.255.255.255, as refused or invalid queries rather than listings. These often appear when you query through a public or open resolver. Rerun the check from your own server or the web lookup before you panic.
- Shared ESP IPs. If your ESP sends from a shared pool, the listing belongs to the pool. The ESP handles the removal, and your job is to show it your list hygiene. A dedicated IP is a different case, and the removal is yours.
- Domain listings you didn't expect. A DBL hit can come from a single compromised landing page, a tracking domain or a URL shortener in your templates. Check every domain that appears in your emails, not just your main one.
For IP-level causes beyond Spamhaus, see our guide to 8 reasons your IP address is blacklisted.
Bottom line: Diagnose from Spamhaus directly, rule out resolver errors and shared-pool listings, and check domains as well as IPs.
Which fix matches which Spamhaus listing?
Match your symptom to the likely list, then take the first action that list requires. Filing a request on every list at once wastes time, because each one needs a different fix.
| What you see | Likely list | First action | Who acts |
|---|---|---|---|
| Dedicated IP listed after spam-trap hits or complaints | SBL (via ZEN) | Stop sending, clean the list, then request removal | You, then Spamhaus reviews |
| Server IP listed that you didn't expect to send mail | XBL | Find the compromised host, remove malware, rotate credentials | You, then automatic clearing |
| Home, office or dynamic IP range listed | PBL | Send through your ISP's or ESP's authenticated SMTP, not direct delivery | Your ISP or network operator |
| Sending domain listed | DBL | Remove the offending link, template or tracking domain | You, then a domain request |
| Listing on a shared ESP pool | SBL or XBL on the pool | Ask the ESP to act and share your list-hygiene evidence | ESP, with your evidence |
Bottom line: The fastest delisting comes from fixing the root cause that matches your list.
Why do legitimate senders end up on Spamhaus lists?
Most listings for legitimate businesses trace back to three sources: a list you didn't build yourself, a signup form with no protection, or a compromised system. These often overlap. One purchased list can produce spam-trap hits, complaints and a bounce spike at the same time, which is a pattern Spamhaus-style listings tend to reflect.
- Purchased or old lists. Abandoned addresses can be recycled into spam traps, and mailing them is one of the most common routes to a listing. The three types of spam traps every sender should know explains how each type gets onto a list.
- Unprotected forms. Bot signups and typo addresses fill your database with junk. How spam traps get on your email list covers the usual entry points.
- Compromised or forgotten systems. A hacked contact form, an abandoned staging server or a former agency's credentials can send spam under your name. XBL and SBL exist to catch exactly this.
One pattern worth noting from appeals: a removal request often fails because the sender describes a sending problem as a list problem. Reviewers look for evidence that the bad sending has stopped, and a request that says "the list was bad" without showing the stop is hard to approve.
Bottom line: Find the entry point that let bad addresses or bad traffic in, and fix that before anything else.
How do you get delisted from Spamhaus, step by step?
Follow these steps in order. Each one produces evidence for the request in step 6.
- Confirm and record the listing. Save the lookup result, list name, reason text and date. This is your baseline.
- Stop the sending. Pause campaigns, automations and transactional flows that use the affected IP or domain. Each send while listed adds fresh evidence against you.
- Find the source. Check your ESP's logs, server mail queue, form submissions and team sending tools. Identify which campaign, segment, server or account caused the problem.
- Remove the bad data. Suppress hard bounces, complaints and unsubscribes, then verify the remaining list and remove invalid addresses. The tutorial below covers how.
- Fix the infrastructure. Confirm SPF, DKIM and DMARC are set up correctly and check reverse DNS. For XBL, scan the machine, remove malware and rotate credentials.
- Submit the removal request through the path linked from the listing lookup. Describe what happened, what you removed, what you changed and when, with numbers. The template is below.
- Monitor and recheck. Rerun the lookup after your request and after each send. If the request is declined, reply with new evidence rather than resubmitting the same text.
Why this order matters: Steps 2 to 5 create the evidence in step 6. A request filed before cleanup is finished is easy to decline, and a second decline makes the next review harder.
Bottom line: Stop, find, clean, fix, then ask. Reversing that order is the most common reason removal drags on.
What should a Spamhaus removal request say?
Spamhaus doesn't publish a fixed template, so keep the request factual, specific and short. Read it as an incident report with counts, a fix and a commitment you can measure:
Subject: Removal request for [IP or domain] ([list name])
On [date], [IP or domain] was listed on [SBL/XBL/PBL/DBL]. The cause was [one sentence, e.g., "a purchased segment of 12,000 contacts that produced repeated spam-trap hits and bounces"].
We stopped all sending from this address on [date]. We removed [N] hard bounces, [N] complaints and [N] invalid addresses, and verified the remaining [N] contacts. We are holding back [N] risky or catch-all addresses.
We have [specific change, e.g., "closed the unprotected signup form, added double opt-in and rotated the affected credentials"].
Our next sends go only to verified contacts who engaged in the last 90 days, with a bounce ceiling of 1%. We will share send-level metrics on request.
Avoid these behaviours, which reviewers tend to read as a sign of a repeat problem:
- Blaming Spamhaus, the ESP or the data vendor.
- Claiming "we never spam" when the listing itself is the evidence against that claim.
- Asking for removal without describing a change.
- Moving the same list to a new IP to escape the listing. This is the "snowshoe" pattern that M3AAWG, the industry anti-abuse body, treats as abusive.
Bottom line: A good request is short, quantified and shows a change that has already happened.
How long does delisting take, and what does it cost?
Spamhaus publishes no fixed timeline, so treat any specific number you see elsewhere as an estimate. In general, XBL listings clear automatically once a host stops being detected. SBL requests depend on the review queue and the evidence. PBL questions go through your network operator. Plan for days to weeks, and longer if the request is declined.
On cost, Spamhaus's public documentation doesn't describe removal as a paid service. Third-party "delisting services" that charge a fee add nothing the official process doesn't offer, and some simply resell a request you could file yourself. Separately, Spamhaus's free public DNS mirrors are meant for limited query volumes. High-volume senders querying the lists directly should check Spamhaus's current terms for their use case.
Does a listing stop every email? No. Only receivers that query the affected list will act on it, so the impact varies by recipient. That's why a listing can look like a small problem for one client and a major one for another. Don't read the lack of complaints as proof you're clear.
Removal and inbox placement are separate. Delisting lifts a blocklist entry, but mailbox providers track their own reputation signals. Google's sender guidelines ask bulk senders to keep user-reported spam below 0.10% and to avoid reaching 0.30% or higher. Some summaries round this to a single 0.3% figure, but 0.3% is the level to stay under, not the target. Use 0.1% as your recovery target. If you also need to budget for verification while you recover, compare email verification pricing by list size and by volume, not just by headline monthly fee.
Bottom line: Delisting can cost nothing and can take weeks. Rebuilding trust with mailbox providers takes longer.
How do you clean a list so the listing doesn't come back?
This tutorial covers step 4 of the removal process using Unlimited Verifier. Verification can't remove a Spamhaus listing, but it targets a common cause of relisting: invalid addresses, dead domains and risky contacts.
- Export the list as a CSV. Include the email column and engagement fields such as last open, last click or signup date. Export bounces and suppressed contacts separately for your records.
- Create an account. Sign up for free, or choose Pro for larger lists. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. Pro is $29 a month, or $25 a month billed annually, and handles lists of up to 25,000 emails each.
- Upload the file. Go to Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Split any file above 25,000 rows into separate uploads before you start.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Disposable and role-based addresses are flagged, and catch-all domains are detected. Standard verification is unlimited on every plan with no per-email fee.
- Read the three buckets.
- Valid: eligible for your first sends.
- Invalid: suppress permanently in your ESP.
- Risky: includes catch-all domains, which accept any address, so the mailbox can't be confirmed. Hold these back. The catch-all email verification page explains how these results are handled.
- Export the results as CSV, Excel or JSON. Save the summary counts, because they go straight into your removal request.
- Re-import only Valid contacts as a new segment, and add Invalid addresses to your ESP's suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this is an export, verify, re-import workflow, or a call to the API from your own scripts.
Choose your plan by the size of each file, not by the total list. The arithmetic makes the difference clear:
| Consideration | Free | Pro |
|---|---|---|
| Lists per month | 25 | Unlimited |
| Max emails per list | 150 | 25,000 |
| Monthly capacity if every list is full | 25 × 150 = 3,750 emails | No list-count limit |
| Deep verifications per month | 750 | 25,000 |
| API access | Not included | 100,000 emails a month |
A 48,000-contact list would need 320 Free lists (48,000 ÷ 150), which is far beyond the 25-list monthly allowance. That's why most full-list cleanups belong on Pro.
Verification has real limits. An SMTP check can't reliably tell a healthy mailbox from a spam trap, and some traps sit on catch-all domains. That's why the Risky bucket stays out of your first sends, and why engagement data matters alongside verification. For a spot-check on one address, the free email checker is quick. To see whether your sending domains appear on public lists, use the free domain blacklist checker.
Bottom line: Export, verify, suppress Invalid, hold Risky, re-import Valid, and keep the counts for your request.
What does a real Spamhaus cleanup look like? A 48,000-contact worked example
This scenario is illustrative. The arithmetic is real, but the post-cleanup results are hypothetical.
The situation: A B2B company has 48,000 contacts: 36,000 opted-in customers and 12,000 addresses purchased last spring. One campaign to all 48,000 produces 1,968 bounces, and the sending IP is listed on Spamhaus SBL shortly after.
Where the problem sits:
Overall: 1,968 ÷ 48,000 = 4.1% bounce rate
Assume the purchased segment produced 1,740 of those bounces: 1,740 ÷ 12,000 = 14.5%
Opted-in segment: 228 ÷ 36,000 = 0.6%
Check: 1,740 + 228 = 1,968 ✓
The purchased segment is the problem, and the opted-in segment is close to healthy. Showing that split in the request is far more persuasive than a single overall rate.
Cleanup on Pro:
- Upload by segment. Pro allows 25,000 emails per list. The opted-in 36,000 becomes two uploads (25,000 and 11,000), both tagged as opted-in. The purchased 12,000 is a third upload, tagged separately. Keeping segments in separate files means each result maps back to its source.
- Run standard verification on all 48,000. This is unlimited on Pro with no per-email fee.
- Run deep verification on the purchased segment. Those 12,000 addresses use 12,000 of the 25,000 monthly deep verifications, leaving 13,000 for re-checks.
- Hypothetical results:
- Valid: 39,840 (83.0%)
- Risky: 3,840 (8.0%)
- Invalid: 4,320 (9.0%)
- Check: 39,840 + 3,840 + 4,320 = 48,000 ✓
- Cost: One Pro month at $29.
Re-entry plan: Send first to the 22,000 most recently engaged Valid contacts. Hold back the 3,840 Risky contacts and the 4,320 Invalid addresses. Set a ceiling of 0.5% bounces on the first send.
Illustrative result: If the first send produces 66 bounces, the rate is 66 ÷ 22,000 = 0.3%, below the ceiling. That result, with the removal counts beside it, is the evidence the request needs. If the purchased segment had shown a similar rate, it would have been a sign to keep it out entirely.
Bottom line: The problem was concentrated in one segment, so the fix was too. Cleaning the purchased list and re-entering on verified contacts turns "we cleaned it" into numbers a reviewer can check.
How do you keep a Spamhaus listing from coming back?
Prevention is cheaper than another removal. Build verification into every point where addresses enter your system.
- At signup. Add real-time email validation to forms, so bad addresses are caught before they reach your database.
- Through the API. The email verification API supports single-email checks and bulk batches of up to 10,000 emails per request. Pro includes API access for 100,000 emails a month. For workflow patterns, see our guide to email verification API and automation.
- On a schedule. Re-verify monthly or quarterly, because lists decay as people change jobs. This matters most for B2B and SaaS, where addresses churn quickly. Our guide to email verification for ecommerce and SaaS covers how to adjust cadence by business model. The email list maintenance best practices guide explains how to set a schedule.
- Before reviving old lists. Don't mail a dormant list without verifying it first. The 5 ways to avoid hitting spam traps guide covers the steps in order.
- Keep consent records. Verification confirms an address works, not that the person agreed to receive mail. The email verification compliance and hygiene guide explains how the two fit together.
If you're comparing vendors, our guides to the best email verification tools and how to choose an email verifier explain what separates them. If your listing is on a different provider's list, the process differs, and removal from Barracuda covers that path. For the wider picture of causes, see 10 common reasons emails get blacklisted.
Bottom line: Verify at signup, at import and on a schedule, and the next listing becomes far less likely.
What mistakes delay or block a Spamhaus delisting?
- Filing a request before cleanup is finished. The reviewer will see the same sending pattern.
- Requesting removal from the wrong list. An XBL problem won't be solved by an SBL request, and a PBL range needs your ISP.
- Deleting only the bounced addresses. Contacts that never received the failed campaign are still untested.
- Mailing a re-engagement campaign to unverified contacts during the listing. It creates fresh bounces while the review is underway.
- Sending to Risky contacts first. Catch-all and disposable addresses belong at the end of your ramp.
- Losing suppression history when you export or migrate. Keep your own copy of bounces and complaints.
- Treating verification as proof of consent. A valid address is not an opted-in address.
- Paying a delisting service for a process you can complete yourself.
Bottom line: Most failed requests come down to timing, the wrong list, or a cleanup that can't be shown.
How we compared (and limitations)
This guide is based on public documentation: Spamhaus's published list descriptions and lookup information, Google's sender guidelines, and M3AAWG's published anti-abuse guidance. We haven't tested Spamhaus's review process directly. Removal timelines, return codes and terms can change without notice, so confirm against Spamhaus's current documentation before you act.
Unlimited Verifier's features and plan details come from the company's own published information. The company states 99.5% accuracy for deep verification. That is the company's figure, not an independent benchmark. The worked example uses hypothetical outcomes. The arithmetic is correct, but the results are not measured data from any campaign.
Verification reduces the causes of listings, but it doesn't remove a listing and can't reliably detect every spam trap. Start with the Spamhaus website for list details, and use check.spamhaus.org to confirm your status before and after each step.
Worked diagnosis example
| Step | Check | Result | Action |
|---|---|---|---|
| 1 | Lookup at check.spamhaus.org | Listed on XBL, code 127.0.0.4 | Treat as compromised host |
| 2 | Scan server for malware | Infected plugin found | Remove plugin, change credentials |
| 3 | Confirm no outbound spam | Queue clear for 48 hours | Ready for recheck |
| 4 | Re-check listing | Listing cleared | Resume sending with verified list |
Frequently asked questions
How long does Spamhaus delisting take?
Spamhaus does not publish a fixed removal window. XBL listings often clear within a short time after the infected host stops, while SBL requests depend on Spamhaus's manual review of your evidence. Submitting a clear, verified fix speeds things up.
Is Spamhaus delisting free?
Yes. Submitting a removal request to Spamhaus costs nothing. Paid delisting services cannot remove a Spamhaus listing, because only Spamhaus can change its own lists. Be wary of any third party that promises guaranteed removal for a fee.
How do I check if my IP is on Spamhaus?
Visit check.spamhaus.org, enter your sending IP address or domain, and the lookup shows whether it appears on SBL, XBL, PBL or DBL. The result includes a reason and return code that tells you which list applies.
What is the difference between SBL and XBL?
SBL covers known spam sources and spam operations, reviewed manually and removed on request. XBL covers compromised machines such as malware-infected hosts and botnet nodes, detected automatically and usually cleared once the infection is removed.
Who should request PBL removal?
PBL listings cover dynamic or residential IP ranges that should not send mail directly. Removal is generally handled by your ISP or hosting provider, since they control the IP range and can change its policy record.
Can I get removed from the DBL list?
Yes. DBL lists domains found in spam message content. Clean up the domain by removing spammy links, compromised pages or abused content, then submit a domain removal request through Spamhaus's process.
Why does my mail still bounce after a Spamhaus delisting?
Mail servers cache DNS results, and some filters update blocklist data on their own schedule. Allow time for caches to expire, then retest your IP at check.spamhaus.org before resending.
Will sending fewer emails get me delisted faster?
Reducing volume helps stop new complaints and bounces, but it does not remove an existing listing. Spamhaus needs to see that the cause is fixed and the sending practices have changed before it clears the listing.
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.