What are the criteria for removing IPs from the Policy Blocklist (PBL)?

1. The IP will operate a mail server. 2. Proper forward DNS (A record) and reverse DNS (rDNS) configurations are in place. 3. Port 25 outbound is restricted to the mail server, preventing use by any other device.

What Is the Spamhaus Policy Blocklist (PBL)?

The Policy Blocklist (PBL) helps minimize the risk of spam and malware distribution, thereby protecting the integrity of email communication networks.

The Spamhaus Policy Blocklist (PBL) is a specialized email filtering tool aimed at preventing abusive email practices by blocking outbound email sent from dynamic or residential IP addresses. These IP ranges are typically not intended for direct mail delivery without proper authentication.

By enforcing this policy, the PBL helps minimize the risk of spam and malware distribution, thereby protecting the integrity of email communication networks. Internet Service Providers (ISPs) and mail server administrators can leverage the PBL to ensure that only authenticated and properly configured email servers are allowed to send mail, enhancing overall email security and reliability.

PBL: About the Data

The Policy Blocklist (PBL) is a vital dataset that identifies end-user IP ranges that should never directly send emails to their final destination. Primarily composed of IPv4 addresses, with some IPv6 ranges, it is formatted in Classless Inter-Domain Routing (CIDR).

How the Spamhaus Policy Blocklist Works

The PBL designates end-user IP ranges that must not send unauthenticated SMTP emails directly to Internet mail servers. Emails originating from IPs listed in the PBL should be routed through an SMTP server with authentication before being delivered. This SMTP server can be provided by the ISP or an external mail service.

The PBL includes both dynamic and static IP addresses that, according to policy (either the block owner’s or Spamhaus’ in the absence of one), should not send emails directly to third-party MX servers. It aids networks in enforcing their Acceptable Use Policies (AUP) for dynamic and non-MTA customer IP ranges.

End users can request to have their IP excluded from the PBL if it aligns with their network’s policy. Visit this link, input your IP, and follow the provided instructions.

Benefits of using the PBL Dataset

IPs in this dataset are not inherently “bad”; they simply should not send emails directly. Many ranges are added and maintained by networks, ensuring high data accuracy. Spamhaus’ researchers also identify end-user IP spaces with high concentrations of “botnet zombies,” which are major spam sources. This dataset covers over 1.4 billion IPv4 addresses, nearly 40% of routable IPv4 space, and is actively maintained and expanding.

Email administrators can utilize this real-time DNSBL to reduce spam and malicious emails from residential addresses. User-generated exclusions help prevent legitimate mail from being rejected, ensuring industry-leading catch rates with minimal false positives. This reduces security risks, email infrastructure costs, and human resource requirements.

How to Use the Policy Blocklist Dataset

To maximize the benefits of Spamhaus’ data, integrate blocklists at critical stages in the email filtering process. The PBL is specifically designed to be used against the connecting IP during the initial SMTP connection.

Spamhaus Blocklists Work Well Because They Are Free

Each blocklist targets a distinct type of behavior. Relying on a single blocklist limits the effectiveness of the data. Spamhaus offers three other IP-based blocklists for free:

Spamhaus Blocklist (SBL)
Combined Spam Sources blocklist (CSS)(included in the SBL DNSBL zone)
Exploits Blocklist (XBL)

These IP blocklists can be accessed via ZEN, which consolidates these datasets for easier and faster querying. While most malicious emails are intercepted at the SMTP transaction stage, some sophisticated actors invest significantly to evade IP detection. To enhance your catch rates, also employ domain and hash blocklists to filter emails post-acceptance. Spamhaus offers the Domain Blocklist (DBL) for free for this purpose.

Technical Information

You can utilize the data through SMTP server configuration for connection and transaction checks, and use open-source tools like SpamAssassin and Rspamd for content analysis. Plugins for these tools are readily available to reduce configuration time for users of Spamhaus Technology’s free Data Query Service.

How to Access the PBL Dataset

Spamhaus DNSBLs are available at no cost for low-volume, non-commercial users. Unsure if you qualify? Review our DNSBL usage criteria. Free accounts can be acquired through our partner, Spamhaus Technology. Sign up for data access via the Data Query Service.

Best Practices for Maintaining Positive IP Reputation

Spamhaus data protects billions of mailboxes worldwide. To avoid being listed and ensure uninterrupted email service, adhere to these best practices:

Restrict Outbound SMTP Traffic – Configure your firewall to allow outbound SMTP traffic (port 25) only from your mail server’s internal IP.
Segment Your Network – Isolate your email infrastructure from the rest of your network’s IP space.
Verify Infrastructure Providers – Ensure your internet infrastructure providers, such as ISPs, are reputable.
Implement Double Opt-In – Avoid spam traps by ensuring emails are sent only to real, interested recipients.
Ensure Proper Configuration – Match your hostname with your HELO and ensure your reverse DNS (PTR record) points to the same hostname.

Note: These actions may require coordination with network administrators and deliverability specialists.

Removal from Policy Blocklist

IPs in this dataset aren’t inherently “bad.” If your IP is mistakenly listed on the Policy Blocklist, visit https://check.spamhaus.org for more information and PBL removals.

How to Use Policy Blocklist (PBL) Ranges

Network owners and ISPs can manage their IP space by submitting PBL ranges. Modify IP ranges to implement specific policies, including allowing or disallowing removals.

Spamhaus PBL FAQ:

What is the Policy Blocklist (PBL)?

The Policy Blocklist (PBL) contains IP addresses that should not send emails directly to the Internet or direct-to-MX servers. Typically assigned by ISPs to broadband or dial-up customers, these IP ranges may include other types. All IP addresses not meant for direct email sending should be listed in the PBL. Notably, PBL listings don’t block email sending unless the user’s email client fails to authenticate properly when connecting to their ISP or company mail server.

What do I do if my IP is on the PBL?

If you’re using an email client like Apple Mail, Thunderbird, or Outlook and facing issues due to a PBL listing, ensure SMTP Authentication is enabled and functioning correctly. This adjustment should promptly resolve the issue. For more details, refer to our guide on Enabling SMTP Authentication.

What if my mail server runs on PBL-listed IPs?

For dynamic IPs, use your ISP’s outgoing mail relay as a smarthost. If unavailable, numerous affordable commercial smarthost providers are accessible through a web search or by consulting your ISP or hosting company.

How do I remove a Single IP from the PBL?

Mail server administrators can delist their static IP addresses from a PBL Zone Listing by following these steps:

Use the IP and Domain Reputation Checker to look up the IP.

Click “show details.”
Follow the instructions for removal.
Allow approximately 15 minutes for DNS changes to propagate.

Before removal, ensure the IP address meets these criteria:

Static (not dynamic)
Serves as an outbound mail server
Configured with appropriate forward (A record) and reverse DNS (rDNS)
Assigned to the individual or company performing the removal

Criteria for Removing IPs from the Policy Blocklist (PBL)

IPs should be removed from the PBL only if:

The IP will operate a mail server.
Proper forward DNS (A record) and reverse DNS (rDNS) configurations are in place.
Port 25 outbound is restricted to the mail server, preventing use by any other device.

Does the Policy Block List (PBL) Only Contain Dynamic IP Ranges?

The PBL lists IP addresses that should not send emails directly to the Internet or direct-to-MX servers, usually assigned by ISPs to broadband or dial-up customers. However, it also includes other types of IP addresses. Essentially, any IP space that shouldn’t be sending email directly to the Internet should be listed in the PBL.

Can I nominate IP addresses for inclusion in the PBL?

Third-party nominations to the PBL are not accepted. Only Spamhaus and authorized ISP PBL Accounts can make changes to the PBL database.

How often is the Policy Blocklist (PBL) updated?

The PBL DNSBL zone is refreshed every 15 minutes, around the clock. To maintain high redundancy, Spamhaus operates over 100 public DNSBL mirror servers worldwide, each functioning autonomously to provide real-time responses to public queries.

Can the PBL to block access to web servers?

The PBL should not be used to restrict access to web servers, forums, journals, or similar platforms.

A PBL listing is NOT a result of any actions taken by end users. The Spamhaus PBL is a registry of IP spaces that should not send emails directly to MX servers, often including IP ranges assigned by ISPs to broadband or dial-up customers. Most legitimate connections to web servers come from IPs listed in the PBL and should NOT be blocked due to their PBL inclusion.