About Spamhaus PBL
The Spamhaus Policy Block List (PBL) is a list of IP ranges that should NOT be sending email directly to mail servers — typically residential broadband ranges, dynamic IPs, mobile carrier ranges, and any address space where the ISP has declared (or Spamhaus has determined) that end users should send mail via the ISP's authenticated mail relay, not directly. PBL is a policy list, not a 'bad behaviour' list — you're not listed because you spammed, you're listed because of where your IP sits. PBL is included in zen.spamhaus.org.
Gmail, Microsoft 365, Yahoo, iCloud, Fastmail, and most enterprise mail servers using Spamhaus integration. PBL is the most-checked zone in ZEN because it's a fast policy filter — receivers can reject before any deeper inspection. Mail from PBL-listed IPs is typically rejected at SMTP-time with a clear PBL reference in the bounce.
The IP is part of an address range declared by the ISP (via Spamhaus's SBL-Datafeed program or the PBL self-declaration system) as not authorized for direct mail sending, OR Spamhaus has automatically classified the range as dynamic/end-user based on rDNS patterns, network ownership, and historical sending behaviour. PBL is the catch-all default for residential broadband: cable, DSL, FTTH, 4G/5G, etc.
How To Get Delisted From Spamhaus PBL
- 1
Determine whether removal is actually appropriate
PBL exists for a good reason — most IPs on it genuinely shouldn't be sending mail directly. Before requesting removal, confirm you have a legitimate reason: you operate a mail server on a static commercial IP that was mis-classified, or your ISP has authorized your specific IP for outbound mail. If you're trying to send cold email from a residential or dynamic IP, PBL removal is not your fix — you need to move to a hosted mail-sending IP entirely.
Note: Many self-removal requests are denied because the IP is genuinely dynamic. PBL is not a punishment list.
- 2
Run the Spamhaus lookup and click the PBL link
Open https://check.spamhaus.org and enter the listed IP. PBL listings always include a direct link to the appropriate removal path: either 'Submit to your ISP' (if the ISP controls the listing) or 'Self-Service Removal' (if Spamhaus's automatic classification can be overridden by the operator).
Note: PBL listings managed by the ISP via SBL-Datafeed cannot be self-removed — you have to contact the ISP.
- 3
Complete the Self-Service Removal form
If self-service removal is available, the form asks for your IP, a contact email on a non-listed domain, and confirmation that the IP is authorized to send mail directly. You agree that the IP has a static assignment, that you operate a real mail server (with proper SMTP responses, correct rDNS, and matching forward DNS), and that you'll be responsible for any abuse from the IP. The form completes instantly if your responses pass automated validation.
Note: Setting up proper forward and reverse DNS for the IP BEFORE submitting the form is required. The form's validation rejects IPs with generic-looking rDNS (e.g. dynamic-203-0-113-1.cable.example.net).
- 4
Verify removal propagates to ZEN
PBL self-service removal is typically instant — the entry is updated within minutes and ZEN reflects it within an hour as receivers refresh their DNSBL caches. Re-run https://check.spamhaus.org to confirm. If you're still seeing rejections after 2-3 hours, check whether your IP is also on XBL or SBL — receivers cite the first match they find.
Note: Some receivers use longer DNSBL caches (up to 24 hours). Don't panic if SMTP rejections continue overnight.
- 5
Keep the IP off PBL by maintaining sender hygiene
PBL self-removal is one-shot — if you re-list (because rDNS changed, the IP is reassigned, or Spamhaus's classifier re-evaluates), the second removal goes through a slower manual review. Maintain static rDNS that matches forward DNS, maintain proper SPF/DKIM/DMARC, and don't let the IP be assigned to a residential subscriber by your hosting provider.
Note: If your provider does dynamic IP assignment, you cannot stay off PBL long-term. Move to a provider that gives you a permanent static commercial IP.
Operational Details
Instant to 1 hour for self-service removal. ISP-managed listings depend on the ISP's response time (typically 24-72 hours). ZEN cache propagation adds up to 24 hours at slow receivers.
rDNS changes back to dynamic-looking patterns, IP reassignment by your hosting provider, the ISP re-classifying the range, or repeated abuse reports tying the IP to behaviour inconsistent with a legitimate static commercial sender.
ISP-managed listings: contact the ISP that owns the IP range. Self-service queries: use the per-listing form at check.spamhaus.org.
Spamhaus PBL And Cold Email
PBL is the listing that catches DIY cold senders — people who try to send outbound mail from their home broadband, a developer VPS that's actually in a residential-classified range, or a cloud instance where the cloud provider hasn't requested a PBL exception for that range. The correct fix is never 'request PBL removal'; it's 'send from infrastructure designed for outbound mail'. ColdRelay's mailboxes run on Microsoft 365 infrastructure, where the M365 SMTP outbound IPs are explicitly classified as authorized mail-sending IPs and are never on PBL. Each customer also gets dedicated IPs that come pre-configured with proper rDNS, SPF, DKIM, and DMARC — so the PBL category doesn't apply.
Frequently Asked Questions
Why is my IP on PBL even though I haven't sent any spam?
PBL is a policy list, not a behaviour list. The listing means Spamhaus or your ISP has classified your IP range as not authorized to send mail directly — usually because it's a residential broadband, mobile, or dynamic range. It has nothing to do with what you've actually sent.
How fast is Spamhaus PBL self-removal?
Instant to about an hour for the actual delisting via the Self-Service Removal form. ZEN cache propagation across receivers adds another hour for most, up to 24 hours for slow-caching receivers.
Can I get a PBL exemption for sending cold email from my home internet?
Technically yes via self-service removal, but PBL exists for a reason — residential and dynamic IPs lack the reputation history, rDNS infrastructure, and abuse-handling that mail receivers expect. Even after PBL removal, mail from residential IPs typically lands in spam at Gmail and is rejected by Microsoft. The real fix is sending from purpose-built outbound infrastructure.
Will Microsoft 365 mailboxes ever be on PBL?
No. Microsoft's outbound SMTP IPs are explicitly classified as authorized mail-sending IPs by Spamhaus and other DNSBL operators. ColdRelay provisions M365 mailboxes on dedicated Azure tenants, and those outbound IPs are never on PBL by design.
What if my ISP put my IP on PBL and refuses to remove it?
The ISP's classification is binding for ISP-managed listings — you cannot self-override it via the Spamhaus form. If the ISP refuses, the practical path is moving your sending to a different network (cloud-hosted mail provider, dedicated mail hosting, or a different ISP's static commercial range). Spamhaus does not arbitrate ISP policy.
How do I check whether my IP is on PBL specifically vs ZEN as a whole?
Use https://check.spamhaus.org — the result page breaks down which sub-zone (SBL, XBL, PBL, CSS, DBL) the listing is on. If only PBL is flagged, the others are clean and self-removal will fully clear ZEN. If SBL or XBL is also flagged, you need to resolve those separately first.