Spamhaus delisting is free, and for most lists it is fast: check your IP at spamhaus.org (the IP and Domain Reputation Checker), identify which list you are on, fix the underlying cause, then use the self-service removal (PBL, most CSS listings) or open a ticket with the relevant Spamhaus team (SBL). Never pay anyone for Spamhaus removal. Spamhaus itself charges nothing, and paid "delisting services" add no access you don't already have.
Step 1: Confirm the listing and identify the list
Go to check.spamhaus.org and enter your IP or domain. You can also check from the command line, a 127.0.0.x answer means listed:
dig +short 10.113.0.203.zen.spamhaus.org
# 127.0.0.2 → SBL
# 127.0.0.3 → SBL CSS
# 127.0.0.4-7 → XBL
# 127.0.0.10-11 → PBL
# (query is your IP reversed: 203.0.113.10 → 10.113.0.203)
Note: public resolvers like 8.8.8.8 are blocked from querying Spamhaus; use your server's own resolver or the web checker. The return code tells you exactly which playbook to follow.
| List | What it means | Removal route |
|---|---|---|
| PBL | Policy: IP range shouldn't send direct mail | Self-service, instant |
| CSS | Automated: low reputation / compromised / snowshoe | Self-removal after fix, or auto-expiry |
| XBL | Infected: malware, botnet, open proxy | Clean the machine, then self-remove |
| SBL | Manual: verified spam source | Fix cause, ticket to Spamhaus SBL team |
| DBL | Domain (not IP) reputation | Fix cause, domain removal form |
PBL removal: self-service, no investigation
The PBL (Policy Block List) lists IP space that the owning ISP, or Spamhaus on its behalf, has flagged as not intended for direct SMTP. Residential connections and many cheap VPS ranges land here by default.
- Look up your IP at check.spamhaus.org; the PBL entry shows a removal link.
- Confirm you operate a real mail server on a static IP with proper rDNS.
- Complete the self-service form (email verification required). Removal propagates within an hour or so.
If your provider's whole range is PBL-listed by policy and they object to mail servers, removal may be reverted, the real fix is moving to a host that allows SMTP.
CSS removal: stop the cause first
CSS (the SBL's automated component) catches IPs showing spam-like behavior: compromised accounts, weak authentication, snowshoe patterns across many fresh domains, or bursts to spam traps.
- Stop sending immediately. Continued traffic resets the listing.
- Find the cause: compromised webform or account, an unverified purchased list, missing/broken DKIM, or a burst from a cold IP are the usual suspects.
- Fix it, patch the compromise, suppress the bad list, repair authentication.
- Use the self-removal at check.spamhaus.org. CSS listings also auto-expire (typically within days) if the behavior stops.
If you self-remove without fixing the cause, the relisting comes back fast and removals get harder. Spamhaus tracks repeat offenders.
XBL removal: you have an infection
XBL means a machine on your IP is compromised, botnet activity, malware, or an open proxy was observed. This is not about your newsletters.
- Find the infected host. On a single server: audit processes, cron, and outbound connections on port 25. On a NAT'd network: check every device behind the IP.
- Clean or rebuild the machine, and close any open relay/proxy.
- Self-remove via check.spamhaus.org. The XBL re-lists automatically if the infection phones home again, so removal before cleanup is pointless.
SBL removal: the only one requiring human review
SBL listings are added by Spamhaus investigators for verified spam operations, and they can cover ranges, not just single IPs. Each listing has an SBL reference number and a writeup explaining the evidence.
- Read the SBL record carefully, it tells you exactly what Spamhaus observed.
- Fix it completely: terminate the offending customer, kill the spam source, document what changed.
- Contact the SBL team via the link on the listing page, referencing the SBL number. Be factual; explain cause and remediation. Responses usually arrive within 24-48 hours.
- If you are a customer of a listed hosting range, your real fix is pressuring the host, or moving to clean IP space.
Hand-wavy appeals ("we promise to be good") get rejected. Specific remediations get delisted.
While you wait: keep mail moving
A listing on your only IP means your mail is down. This is the operational argument for never running serious volume on a single IP, a pool with headroom routes around a listing while you remediate. We cover that architecture in how to send without getting blacklisted and the IP-count math in our 100K/day infrastructure guide.
Preventing the next listing
- Verify every list before first send; never import lists older than 6 months unverified.
- Warm new IPs properly, cold-IP volume bursts are a classic CSS trigger. Follow a real warm-up schedule.
- Keep complaint rate under 0.1% and hard bounces under 2%.
- Monitor zen.spamhaus.org daily by automation, so you catch listings in hours.
- Lock down webforms, SMTP auth, and WordPress installs, compromise is the #1 source of XBL/CSS surprises for legitimate senders.
How BulkEmailSetup helps
Every BulkEmailSetup server ships on pre-screened clean IPs, with automated Spamhaus/Barracuda/SpamCop monitoring and a team that handles delisting tickets for you when something does get flagged. If you would rather never read an SBL record again, see our pricing.
Frequently asked questions
Does Spamhaus charge for delisting?
No. Spamhaus delisting is completely free for every list (SBL, XBL, PBL, CSS, DBL). Any site or service charging money for Spamhaus removal is a scam or an unnecessary middleman.
How long does Spamhaus delisting take?
PBL self-service removal is near-instant. CSS listings auto-expire or can be self-removed after the underlying issue stops. SBL tickets are typically answered within 24-48 hours once you have fixed the cause.
What is the difference between SBL and CSS?
SBL is a manually investigated listing for verified spam sources, often covering whole IP ranges. CSS is an automated sub-list of the SBL that catches low-reputation or compromised hosts, usually single IPs, and it self-resolves faster.
Why is my IP on the Spamhaus PBL if I never sent spam?
The PBL is not an accusation. It lists IP space that ISPs say should not send direct SMTP mail, typically residential or dynamic ranges. If you legitimately run a mail server on the IP, you can self-remove it in minutes.
Will my mail be rejected while listed on Spamhaus?
Very likely. Spamhaus is the most widely used DNSBL in the world; major providers and millions of corporate mail servers reject or spam-folder mail from listed IPs and domains.
