How to get delisted from Spamhaus

What this guide does and doesn’t cover

This is the public, factual removal procedure for Spamhaus’s blocklists — not a guarantee of outcome or timeline. Spamhaus’s own process decides whether and when an IP is removed; neither AdminKit nor any third party controls that decision.

Step 1: find out which list flagged you, and which one it is

Spamhaus runs several separate lists, per its own blocklists overview, and the removal path differs by list:

• SBL (Spamhaus Block List) — IPs and ranges tied to spam operations, generally identified through Spamhaus’s own investigation.
• XBL (Exploits Block List) — IPs showing automated signs of compromise: open proxies, worms, trojans, or other malware sending mail without the owner’s knowledge.
• PBL (Policy Block List) — IP ranges that ISPs themselves ask Spamhaus to list as “should not send mail directly” — typically residential and dynamic address space. A PBL listing is not a report of abuse; it reflects the ISP’s own policy about which of its IP ranges are expected to send mail through a relay rather than directly.
• CSS (Combined Spam Sources) — a fast-moving, automated list capturing active spam sources in real time, often with shorter-lived listings than the SBL.

Start at AdminKit’s blacklist check or Spamhaus’s own lookup and removal tool with the specific IP in question — the result names which list (or lists) currently include it.

Step 2: fix the cause before requesting removal

Requesting removal without fixing the underlying issue is the most common reason a removal doesn’t stick:

• SBL/XBL/CSS listings usually mean something on your network is actively sending spam or shows signs of compromise. Check for a compromised device, an open relay, or malware before requesting removal — see our IP blacklist guide for how to find the cause.
• PBL listings are different: there’s typically nothing to “fix” on your side if you’re a home or small-office user not intentionally running a mail server directly — the listing reflects your ISP’s own policy for that IP range, and removal (if applicable) usually means confirming with your ISP or Spamhaus that your use case is legitimate (e.g., you run a properly configured, authenticated mail server that should be allowed to send directly).
• Confirm your IP isn’t shared (CGNAT, hosting) before assuming the cause is something you personally did — see what is my IP for shared-address indicators.

Step 3: use the public removal procedure

Once the cause is addressed:

• Go to Spamhaus’s own lookup and removal tool, enter the IP, and follow the list-specific removal instructions shown for whichever list(s) currently include it.
• Each list’s removal form may ask for details about what was fixed — having specifics ready (what was compromised, what was changed) makes the request easier to evaluate.
• Spamhaus does not publish a fixed turnaround time, and some listings (especially automated ones like parts of the XBL and CSS) can clear on their own once the underlying bad traffic stops being observed, sometimes faster than a manual request is reviewed.

Avoid re-listing

A request that succeeds without the root cause actually being fixed tends to result in the same IP being re-listed within days, since Spamhaus’s detection is ongoing, not a one-time check. If the cause was a shared IP (CGNAT, hosting, a VPS range), understand that the same abuse from a different customer on that address can re-trigger a listing regardless of anything you personally did — in that case, the durable fix is usually a dedicated IP from your provider, not repeated removal requests on a shared one.