Last updated: July 2026

In short: Spamhaus operates the world’s most authoritative DNS blocklists for email infrastructure. While the SBL blocks active spam sources, the PBL restricts consumer and dynamic IP ranges that lack direct sending authorization. Delisting from Spamhaus is always free; any third-party paid removal offer is a scam.

If your outbound messages are rejected with bounce reports mentioning zen.spamhaus.org, sbl.spamhaus.org, or pbl.spamhaus.org, your mail server is facing immediate network blockages. Spamhaus serves as the global benchmark among DNS-based blocklists (DNSBLs): when an IP address appears in its databases, major email providers across the globe terminate inbound SMTP connections at the network edge.

What is Spamhaus and how do its lists differ?

The Spamhaus Project maintains real-time threat intelligence databases designed to protect the internet against unsolicited bulk email, malware, and phishing. For email administrators, the two most critical zones are the SBL and the PBL:

1. Spamhaus Block List (SBL)

In official documentation, the core mandate of the SBL is explicitly outlined: The Spamhaus Block List (SBL) is a realtime database of IP addresses of spam sources, including known spammers, spam gangs, spam operations and spam support services.

An SBL listing confirms that spam broadcasts, honeypot hits, or malicious automated scripts have been traced directly back to your IP address or its surrounding subnet.

2. Policy Blocklist (PBL)

Unlike the SBL, the PBL does not track active spam behavior. Instead, it identifies IP ranges whose Internet Service Providers (ISPs) have designated them as unauthorized for direct-to-destination SMTP transmission: The Policy Blocklist (PBL) lists IP space that should not be sending email directly to the Internet/direct-to-mx: often these are IP ranges assigned by ISPs to broadband or dial-up customers, but the PBL does include other types of IP space.

If you run an email server on a residential broadband connection or dynamic cloud IP allocation, your IP resides on the PBL by default to prevent compromised consumer endpoints from broadcasting direct spam.

Why was your IP listed?

  • For SBL listings: Compromised web applications, outdated CMS plugins, breached email accounts on your server, or broadcasting marketing campaigns to uncleaned subscriber lists containing active honeypots.
  • For PBL listings: Attempting to send mail directly (direct-to-MX) over TCP port 25 from a consumer ISP address space or dynamic cloud instance instead of routing through an authenticated smarthost relay.

Checking Your Status and Requesting Delisting

To check whether your IP address or sending domain appears on any Spamhaus zone, navigate to the free lookup portal at check.spamhaus.org. Enter your mail server’s public IPv4 or IPv6 address to retrieve full diagnostic details.

Critical scam warning regarding removal fees

Spamhaus explicitly warns administrators against fraudulent third-party services that demand payment in exchange for expedited delisting. Official policy mandates: any charge or fee associated with removing any Spamhaus listing. Any offer from anyone to remove any Spamhaus listing for a fee is a scam. Spamhaus has no affiliation with anyone offering any ‘blocklist removal’ service, nor can any third party influence or expedite removals from any Spamhaus database.

Furthermore, all delisting workflows are processed strictly through standard project guidelines: The criteria for removal from the SBL is explained on the Spamhaus Blocklist page. Removals of Spamhaus listings are governed by our removals policy only.

Delisting workflows:

  1. SBL Delisting: First, identify and resolve the underlying security exploit on your server. Next, look up your IP on check.spamhaus.org, open the specific SBL ticket ID, and follow the instructions to submit a free removal request. Once the Spamhaus team verifies that the vulnerability is patched, unblocking usually completes within a few hours.
  2. PBL Delisting: If you operate a dedicated business server with a static IP address and are incorrectly listed on the PBL, you can authenticate via the lookup portal and claim single-IP removal. For dynamic consumer connections, you must configure your mail server to relay outbound traffic over port 587 (Submission) through your provider’s smarthost.

Honest Verdict: Should You Care?

YES — highest possible priority! Unlike low-impact or controversial blocklists, a listing on Spamhaus (specifically the SBL) is critical. Major global email ecosystems—including Google Workspace, Microsoft 365, Apple iCloud, and Tier-1 ISPs—rely on Spamhaus directly at their network firewalls. As long as an SBL listing remains active, your domain’s email communication is effectively halted worldwide. Address the root cause and request delisting immediately.

Verifying your configuration

To confirm that your mail server infrastructure is fully secured after delisting and complies with industry authentication rules (SPF, DKIM, and DMARC), audit your setup instantly using the free MXAudit scanner.

Further reading