Spamhaus listing removal starts with the list family, because the family decides who can repair the cause and which procedure applies. A rejection mentioning Spamhaus tells you very little on its own. Before anyone requests removal, line up three things: the outbound IP the message actually left from, the domain or hostname the rejection names, and the time of the failure. Keep that rejection together with whatever transaction logs your sending provider can supply. Look the object up in the official Spamhaus Checker and save the list family, the stated reason, and current instructions. If all the provider passed on was the word “Spamhaus”, the essential evidence is missing; ask for the complete response before choosing a removal path.
An IP flagged in a content check may belong to a server that hosts a linked resource, not the server that sent the email. SBL and XBL can evaluate those resource IPs, and Spamhaus’s dataset documentation distinguishes the two uses. Either way, receiving providers decide how to treat reputation data: being listed does not mean your mail is blocked everywhere, nor does delisting guarantee inbox delivery. Spamhaus’s own CSS guidance on provider decisions describes that discretion.
Which Spamhaus list is it: SBL, CSS, XBL, PBL, ZEN, DBL or ZRD?
SBL lists IPs and ranges tied to spam or other abuse, including the infrastructure supporting it. An informational SBL entry warns about behavior without being an active blocking recommendation: investigate it, but confirm any actual rejection separately, because another listing or rule may be in play. SBL scope and informational listings
CSS lists IPs automatically when associated with low-reputation SMTP traffic, which includes some compromised senders. CSS scope
XBL points to evidence of compromise, and the compromised machine can sit behind the public IP; the listing does not identify the device for you. For IPv6, a finding can cover a /64 or larger range. XBL scope and IPv6 handling
PBL identifies address space whose policy rules out unauthenticated delivery straight to third-party MX servers. Both static and dynamic addresses can appear there, and inclusion is not evidence of abuse. PBL policy
ZEN combines SBL, CSS, XBL, and PBL IP data. Read every reported component and instruction, not only the first one; ZEN does not check domain reputation. ZEN components
DBL lists domains or hostnames wherever they appear: in SMTP identities, headers, or message links. It does not list IPs or full URL paths, and the listed object need not match the visible From domain. Its abused-legit category can identify a compromised legitimate site, which does not establish deliberate abuse by the site’s owner. SPF, DKIM, and DMARC records can coexist with a DBL listing; they do not prove removal or guarantee an inbox result. DBL objects and qualifications
ZRD records domains first observed within the preceding 24 hours. First observation is not necessarily registration time, and this age signal alone does not prove abuse (ZRD technical definition). Listings expire automatically after 24 hours, and Spamhaus does not accept delisting requests for ZRD. Expiry does not guarantee any outcome at the receiving provider. ZRD expiry rules
Who can request Spamhaus removal for each list?
Once you know the object, hand it to someone who controls it. The sender can coordinate the case even when it does not own the resource that needs repair. The table shows where each kind of evidence should go.
| Evidence in the case | What to hand over | Who is responsible | Question to answer |
|---|---|---|---|
| Rejection names SBL and an IP | The listed IP or range and the record | The network or hosting owner, reached through the ISP or ESP | Has the cause been resolved under the SBL procedure? |
| Mail client failure names PBL | The access IP and the client connection details | The submission administrator; the network owner for policy | Does authenticated relay submission work under the PBL guidance? |
| Content report names a DBL hostname | The hostname and its place in the message | The domain or site owner, coordinated with the sender | Is this an abused legitimate site that needs the DBL repair path? |
For SBL, the responsible network or hosting company handles removal after resolving the cause; an end user should involve their administrator, ISP, or ESP. Follow the procedure in the current record. The SBL administrator instructions assign this to the provider, while the general request guidance directs owners to Checker tickets, so do not replace the record-specific route with an assumed universal channel. If a shared IP has low reputation, review what to do when a shared IP has low reputation and the ESP cannot remediate it.
For CSS, an operator with authority over the IP must correct the cause before following Checker’s removal steps. Self-removals are limited, and continued detection can trigger immediate relisting. CSS removal conditions
For XBL, the system or network owner should contain and repair the compromise, looking at devices behind the IP where relevant, and then follow Checker. Blocking abusive outbound connections alone does not disinfect a device, and a renewed listing calls for a renewed investigation. XBL repair and removal
For a PBL client failure, check authenticated submission through the provider’s relay with its current settings. SMTP AUTH is the client’s relay login, which is separate from SPF, DKIM, and DMARC. A server exclusion through Checker requires several things at once:
- permission under network policy,
- a static IP assigned to the requester,
- an outbound mail server,
- appropriate forward and reverse DNS,
- outbound port 25 restricted to that server.
Ordinary access-device IPs don’t meet these conditions, and range policy belongs to the network owner (PBL submission and exclusion conditions).
For an abused-legit DBL finding, the website or server owner should repair the compromise and secure the hosting before following Checker, coordinating with the domain owner if that is someone else. Removal is not guaranteed, and renewed activity can cause relisting. DBL cleanup and removal
If the object is still unidentified, you lack the authority to act on it, or the repair is incomplete, stop there and obtain the missing evidence or involve the provider before going further. When a removal request does apply, prepare the cause, the repairs completed, when they were completed, and what will prevent a repeat. Request preparation
Checking recovery on the affected path
Synthetic example with reserved domains and invented observations; no lookup or send was performed. Suppose a message from notices@example.com leaves via 192.0.2.44 with a link to https://portal.example.net/statement. If the bounce cites DBL for portal.example.net, but the outbound IP itself is clean, those two observations concern different objects: the hostname evidence goes to the site or domain owner and the rejection stays with the sender’s provider. Nobody should request removal of the unlisted IP.
After a removal, check current status and the affected delivery path as two separate questions. Submitting a request does not guarantee removal, and delisting does not mean every mailbox provider will immediately accept your mail. If rejection persists, keep the new response: failures at particular destinations go to their receiving administrators; if mail keeps failing at many destinations, add that to the removal ticket. A clean lookup now does not reconstruct an earlier rejection. Recovery and escalation guidance
Documentation was verified on 12 and 14 September 2026. On 14 September, the Checker’s processing notice warned of delays after approval. Recheck that notice before relying on timing; no turnaround was measured here.
Use the blocklist incident runbook for the wider investigation. When escalating or parsing responses, use the provider escalation checklist and the guide to reading bounce evidence.
Frequently asked questions
Which Spamhaus lists are there, and what does each one list?
SBL lists IPs and ranges tied to spam or abuse infrastructure, CSS lists IPs automatically when associated with low-reputation SMTP traffic, XBL flags compromised machines and exploits, and PBL identifies IP space restricted from unauthenticated MX delivery. ZEN combines SBL, CSS, XBL, and PBL data, DBL catalogs domains and hostnames, and ZRD records newly observed domains during their first 24 hours.
Who can request removal from the Spamhaus SBL?
The responsible network or hosting company handles removal after it has resolved the cause. An end user should involve their administrator, ISP or ESP and follow the procedure in the current record.
Can a Spamhaus ZRD listing be removed on request?
No. Spamhaus accepts no manual removal requests for ZRD. Listings expire after 24 hours of listing, and expiry does not guarantee any outcome at the receiving provider.
Does a Spamhaus listing mean your mail is rejected everywhere?
No. Receiving mail providers decide independently how to interpret and enforce Spamhaus reputation signals.
Do SPF, DKIM and DMARC records remove a DBL listing?
No. SPF, DKIM, and DMARC records can coexist with a DBL listing; they do not prove removal or guarantee an inbox result.


