Skip to content
AdminKit

How to get delisted from Spamhaus

AdminKit's guide to Spamhaus delisting starts with identifying which list flagged you: SBL, XBL, PBL and CSS each have a distinct cause and a distinct public removal procedure, and knowing which one applies determines what to fix before requesting removal. This covers the public procedure only; neither Spamhaus nor AdminKit can guarantee removal time or success.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • Spamhaus runs several lists, and each has its own cause and removal path. Find out which one names your IP or domain before you change anything.
  • Every removal starts at the Spamhaus IP and Domain Reputation Checker (the lookup page). Spamhaus says it does not handle removal requests sent through other channels, such as email.
  • A PBL listing is a policy entry, not an abuse report. Most mail clients fix it by turning on SMTP Authentication; only a static mail server IP is eligible for self-removal.
  • SBL, XBL and CSS listings mean Spamhaus saw real abuse from the address. Fix the cause first, because these lists re-list quickly if it recurs.
  • Removal is free. Spamhaus states there is never a fee for removing any listing, and that no third party can expedite one.

What does this guide 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. Spamhaus’s own FAQ says the same: submitting a removal request does not guarantee that removal will be granted.

It’s one of several delisting and authentication guides in AdminKit’s email authentication cluster. Every fact about a list below comes from that list’s own page on spamhaus.org.

Which Spamhaus list flagged you?

The lookup result names the list, and that name decides everything after it. Spamhaus runs several separate lists, per its own blocklists overview, and the removal path differs by list:

ListWhat it coversTypical causeWhat to do
SBL (Spamhaus Blocklist)IPs and ranges that appear to be controlled by or available to spammers and abusersSpam operations, snowshoe ranges, spam or malware hosting, botnet controllers, phishingEnd users ask their ISP or ESP; the ISP requests removal after ending the abuse
CSS (Combined Spam Sources)IPv4 addresses and IPv6 /64s sending low-reputation mail, found automaticallyUnsolicited mail, poor list hygiene, a compromised or misconfigured serverFix the cause, then self-remove at the checker; listings expire 3 days after last detection
XBL (Exploits Blocklist)Individual IPv4 and IPv6 addresses of legitimate devices hijacked by third-party exploitsMalware, bots, compromised servers or devices behind a NAT gatewayClean the devices, restrict port 25, then use the checker
PBL (Policy Blocklist)IP space that should not send mail directly to the internetA mail client sending without SMTP Authentication, or a mail server on a residential IPTurn on SMTP AUTH, or self-remove a qualifying static server IP
DBL (Domain Blocklist)Domains with poor reputation, never IPsDomains used in spam, phishing or malware, or abused legitimate domainsFix the abuse; most listings expire automatically, or request removal at the checker

ZEN is not a separate list. The ZEN page describes it as one zone combining the SBL, CSS, XBL and PBL, so a rejection that says “zen.spamhaus.org” still means one of those four. CSS data is published inside the SBL zone too, per the CSS page.

AdminKit’s blacklist check page explains how a DNSBL lookup works; for this list, start at Spamhaus’s own lookup and removal tool with the specific IP in question — the result names which list (or lists) currently include it. Spamhaus also asks you to check related domains there, because domain and IP reputations affect each other.

A rejection caused by one of these lists is usually also surfaced to your own sending server as a 5xx SMTP reply carrying a standard enhanced status code such as 5.7.1 (“delivery not authorized”), defined in IANA’s SMTP Enhanced Status Codes registry — the free-text wording alongside that code usually names Spamhaus directly, which is a fast way to confirm it’s this blocklist rather than another cause. AdminKit’s SMTP status code decoder explains a pasted bounce line in plain words. If the result instead names the Barracuda Reputation Block List, see how to get delisted from Barracuda for that list’s separate, independently-run removal procedure.

How does a Spamhaus DNSBL lookup work?

A receiving server asks DNS whether a name built from your IP exists in the list’s zone. RFC 5782 defines the format: reverse the octets of the IPv4 address and append the list’s domain. An A record means listed; no record (NXDOMAIN) means not listed. The A record holds a code such as 127.0.0.2, and the RFC says it must not be used as an address.

The illustrative query below uses the documentation address 192.0.2.10. The answer lines are not a real result; they show what a listing would look like using return codes Spamhaus documents:

; Illustrative only: documentation IP 192.0.2.10 checked against ZEN
; Reversed octets:  10.2.0.192
; Query name:       10.2.0.192.zen.spamhaus.org.   IN A

; Example answer if the address were in the XBL and the ISP-maintained PBL:
10.2.0.192.zen.spamhaus.org.   A   127.0.0.4
10.2.0.192.zen.spamhaus.org.   A   127.0.0.10

; Not listed in any ZEN component:
status: NXDOMAIN

The ZEN page says one query can return several answers, one per component list. Spamhaus’s DNSBL usage FAQ documents what each code means:

Return codeZoneMeaning per Spamhaus
127.0.0.2SBLSpamhaus SBL data
127.0.0.3SBLSpamhaus CSS data
127.0.0.4XBLCBL data (the XBL’s detection source)
127.0.0.10 / 127.0.0.11PBLISP-maintained / Spamhaus-maintained entry
127.255.255.252, .254, .255AnyErrors, not listings: typing error in the zone name, query via a public or open resolver, excessive number of queries

The error codes matter when you read a bounce. If a receiving server treats 127.255.255.254 as a listing, the problem is that server’s DNS setup, not your IP. Domain lookups against the DBL use a separate 127.0.1.0/24 range, listed on the DBL page.

What should you fix before requesting removal?

Fix whatever the named list reacts to. Requesting removal without fixing the underlying issue is the most common reason a removal doesn’t stick. Each list’s page names the causes it looks for:

Listed inCause Spamhaus describesWhat to fix
PBLMail client sending without SMTP AuthenticationEnable SMTP AUTH and use port 587 or 465, not 25
PBLMail server on a dynamic IPRelay through your ISP’s smarthost, or move to a static IP with forward and reverse DNS
XBLA device on or behind the IP is insecure, compromised or infectedClean or rebuild it; close outbound port 25 except from your mail server; check NAT gateways, VPNs and guest Wi-Fi
XBL / CSSPlesk sending with domain names in the SMTP greeting from a shared IPUse the Plesk outgoing mail mode Spamhaus recommends: send from domain IPs, or from specified IPs
CSSSnowshoe patterns, compromised websites or CMS, bots, misconfigured appsCheck technical settings first, then logs, role accounts and feedback loops
SBLSpam operations, spam hosting or other abuse on the rangeThe ISP terminates the abuse, then requests removal
  • 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 PBL page says a listing does not stop email unless your email program is not authenticating to its outgoing server.
  • 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.

For a mail server, also check that the IP has matching forward and reverse DNS, which the PBL page lists as a removal condition. Large mailbox providers expect the same: Gmail’s email sender guidelines say a sending server’s public IP must have a PTR record that resolves to a hostname, and that hostname must have an A or AAAA record resolving back to the same IP. AdminKit’s reverse DNS lookup shows the PTR record your address currently returns.

What should you have ready before you request removal?

Have proof that you own the address and a short account of the fix. Spamhaus’s general FAQ sets out who may ask and what to include:

RequirementWhat Spamhaus says
OwnershipRequests must come from the registered owner of the IP or domain; otherwise ask your service provider
Where you submit fromAn IP address that can be associated with the listed IP or domain, not a VPN
The explanationWhat caused the spam issue, what action you took, when you solved it (time and date), and what you did to prevent it recurring
Contact address (PBL)An address at a domain matching the mail server; free email addresses such as Gmail, Hotmail or Yahoo are not accepted
ChannelThe checker only; requests through other channels, such as email, are not handled

How do you request removal from each list?

Start every request at 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. The list pages add these specifics:

  • CSS: removals are “fast, no-questions-asked” within limits, and self-removals are limited. CSS re-lists immediately if the problem is still detected.
  • XBL: removals are handled only at the checker. The XBL page says an unresolved IP will re-list the next time it connects to Spamhaus.
  • PBL: a mail server administrator can exclude a single static IP by clicking “show details” in the checker. The IP must be static, run an outbound mail server, have forward and reverse DNS, and be assigned to you. Allow about 15 minutes for DNS propagation. Exclusions expire after one year and are reversed if spam is detected.
  • SBL: the SBL page says the ISP requests removal once the abuse has ended, using the “contact the SBL Team” link on the SBL listing page. The SBL FAQ tells end users to contact their administrator, ISP or ESP.
  • DBL: once a removal is approved it is processed immediately, though some networks may take up to 24 hours to catch up.

Spamhaus does not publish a single fixed turnaround time. Some listings clear on their own once the underlying bad traffic stops being observed: CSS listings normally expire three days after the last detection, and XBL listings expire automatically once the behavior is no longer detected.

If you are still blocked after a removal, the general FAQ says some networks take longer to sync. It suggests waiting 1–2 hours, and checking whether the problem affects all receiving networks or just one or two. If only one or two, contact them.

How do you avoid being listed again?

Keep the cause fixed, because detection is ongoing. The XBL page says an IP that keeps being re-listed means the detected problem has not been corrected, and CSS warns that it re-lists IPs quickly on re-detection. Spamhaus also warns that excessive removers may be blocked from the removal form, and that people who remove many PBL entries may lose removal access.

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.

Spamhaus’s SBL page also lists habits that keep a reputation clean: protect web forms with a captcha or similar check, enforce an acceptable use policy, and allow outbound port 25 only from your mail server. Its role accounts and feedback loops advice applies to every list: if nobody reads abuse reports, you learn about problems from the next listing.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Which Spamhaus list is most common for a home or small-office IP?

The PBL (Policy Blocklist) most often applies to residential and dynamic IP ranges. It isn't a report of abuse at all: Spamhaus describes it as a list of IP space that should not be sending email directly to the internet, often ranges that ISPs assign to broadband or dial-up customers. Entries are maintained either by the ISP or by Spamhaus, and Spamhaus's DNSBL FAQ gives each its own return code. If an email program's sending fails because of a PBL listing, Spamhaus says the fix is to turn on SMTP Authentication and send through your provider's server on port 587 or 465.

What's the difference between the SBL and the XBL?

The SBL (Spamhaus Blocklist) lists IPs and ranges that appear to Spamhaus to be controlled by or available to spammers and abusers, maintained by Spamhaus's research team. The XBL (Exploits Blocklist) lists individual IPs of legitimate devices hijacked by third-party exploits — infected machines, bots, compromised servers — and Spamhaus adds them automatically when its detectors receive connections directly from the IP.

How long does delisting actually take?

Spamhaus does not publish a single guaranteed timeline; it varies by list. What it does document: CSS listings normally expire three days after the last spam detection; XBL listings expire automatically once the malicious behavior is no longer detected; a PBL self-removal needs about 15 minutes for DNS propagation; an approved DBL removal is processed immediately, though some networks may take up to 24 hours to catch up. Submitting a request does not guarantee removal, and Spamhaus says no third party can expedite it.

Can I get removed if I haven't actually fixed the cause yet?

You can request removal, but if the underlying cause (a compromised device, an open relay, ongoing spam) is still active, Spamhaus's systems are likely to simply re-list the IP once they see the same traffic again. Fixing the cause first makes a request far more likely to stick.

Does Spamhaus charge for delisting?

No. Spamhaus's SBL and DBL pages both state that there is never any charge or fee associated with removing any Spamhaus listing, that any offer to remove a Spamhaus listing for a fee is a scam, and that no third party can influence or expedite removals. Separately, querying the Spamhaus DNSBLs is free only for low-volume, non-commercial users; that is about using the lists, not about getting off them.

Who is allowed to request a Spamhaus removal?

Spamhaus's general FAQ says removal requests must be made by the registered owner of the IP or domain, from an IP address that can be associated with it, and not through a VPN. If you don't own the address, for example on a home connection or a shared server, ask your provider to handle it. SBL removals in particular are requested by the ISP once the abuse has been terminated.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.