{"id":5208,"date":"2026-08-11T09:41:12","date_gmt":"2026-08-11T09:41:12","guid":{"rendered":"https:\/\/www.mailercloud.com\/blog\/?p=5208"},"modified":"2026-09-08T04:44:05","modified_gmt":"2026-09-08T04:44:05","slug":"spamhaus-delisting","status":"publish","type":"post","link":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting","title":{"rendered":"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Your campaign goes out, and within minutes your bounce log fills with something like this:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><em>550 5.7.1 Service unavailable; Client host [203.0.113.45] blocked using zen.spamhaus.org; https:\/\/check.spamhaus.org\/query\/ip\/203.0.113.45<\/em><\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Spamhaus data sits in front of a large share of the world&#8217;s mailboxes, so a single listing can take your delivery to near zero across many receivers at once. <a href=\"https:\/\/www.mailercloud.com\/blog\/microsoft-outlook-sender-requirements\">Microsoft enforces Spamhaus listings as OU-001<\/a>, for instance. It is also the blocklist senders handle worst \u2014 mostly because they never work out <em>which<\/em> Spamhaus list they are on, and request removal from the wrong one.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_88 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#What_Spamhaus_Is_and_Why_It_Blocked_You\" >What Spamhaus Is and Why It Blocked You<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#How_to_Confirm_This_Is_Your_Problem_%E2%80%94_and_Which_Zone\" >How to Confirm This Is Your Problem \u2014 and Which Zone<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#The_Zone_Reference_Table\" >The Zone Reference Table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#The_4_Most_Common_Reasons_Senders_Get_Listed\" >The 4 Most Common Reasons Senders Get Listed<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#How_to_Fix_It_Step_by_Step\" >How to Fix It: Step by Step<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#Paste-Ready_Removal_Request_Template\" >Paste-Ready Removal Request Template<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#How_to_Prevent_Spamhaus_Listings\" >How to Prevent Spamhaus Listings<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#Shared_IP_vs_Dedicated_IP_Who_Fixes_What\" >Shared IP vs. Dedicated IP: Who Fixes What<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#How_Mailercloud_Handles_Spamhaus_Listings\" >How Mailercloud Handles Spamhaus Listings<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\/#FAQ_Spamhaus_Delisting\" >FAQ: Spamhaus Delisting<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Spamhaus_Is_and_Why_It_Blocked_You\"><\/span>What Spamhaus Is and Why It Blocked You<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Spamhaus is not one list. It publishes several separate datasets, and the one that matters for a blocked sending IP is usually <strong>ZEN<\/strong> \u2014 a combined zone that bundles the three IP-based blocklists (SBL \u2014 which includes CSS \u2014 XBL, and PBL) into a single query. When a receiving mail server says you are &#8220;blocked using zen.spamhaus.org,&#8221; it is telling you that you are on <em>at least one<\/em> of those, but not which. Spamhaus carries far more delivery weight than lighter lists like <a href=\"https:\/\/www.mailercloud.com\/blog\/barracuda-brbl-delisting\">Barracuda&#8217;s BRBL<\/a> \u2014 see <a href=\"https:\/\/www.mailercloud.com\/blog\/uceprotect-sorbs-listings\">how Spamhaus compares to lower-impact lists<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That distinction is the whole game. <strong>SBL<\/strong> is manually curated and human-reviewed. <strong>CSS<\/strong> is automated reputation detection; in our experience it is the dataset most legitimate ESP senders hit, though Spamhaus publishes no breakdown confirming that. CSS is not a standalone zone \u2014 it is published inside the SBL and ZEN zones, so a CSS listing is always cited as SBL or ZEN. <strong>XBL<\/strong> means a compromised host. <strong>PBL<\/strong> is not a spam list at all \u2014 it is a policy statement that a range should not send direct-to-MX. <strong>DBL<\/strong> sits outside ZEN entirely and lists domains, not IPs. Different triggers, different owners, different removal paths \u2014 the reference table below maps all of them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One thing worth stating plainly: <strong>Spamhaus never charges to remove a listing.<\/strong> Any service offering paid removal is a scam.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_Confirm_This_Is_Your_Problem_%E2%80%94_and_Which_Zone\"><\/span>How to Confirm This Is Your Problem \u2014 and Which Zone<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A <a href=\"https:\/\/www.mailercloud.com\/blog\/smtp-5-7-x-bounce-codes-explained\">550 5.7.1 with a named blocklist<\/a> in the SMTP response is the confirmation. Start with your bounce logs and grep for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>zen.spamhaus.org<\/code> \u2014 you are on one of the IP zones<\/li>\n\n\n\n<li><code>sbl.spamhaus.org<\/code> \/ <code>xbl.spamhaus.org<\/code> \/ <code>pbl.spamhaus.org<\/code> \u2014 the receiver queried a single zone and told you exactly which. There is no <code>css.spamhaus.org<\/code>: CSS is published inside the SBL and ZEN zones, never as its own zone, so a CSS listing is cited as SBL or ZEN.<\/li>\n\n\n\n<li><code>dbl.spamhaus.org<\/code> \u2014 a <em>domain<\/em> listing, not an IP one<\/li>\n\n\n\n<li><code>check.spamhaus.org<\/code> in the bounce text \u2014 Spamhaus is the source, regardless of zone<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the bounce only says &#8220;zen,&#8221; do the lookup yourself. Reverse the octets of your sending IP and query the zone. For <code>203.0.113.45<\/code>:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>dig +short 45.113.0.203.zen.spamhaus.org<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The answer comes back as one or more <code>127.0.0.x<\/code> codes, one per dataset you are listed on:<\/p>\n\n\n\n<!-- Spamhaus return-code table (small). Paste into a WP Custom HTML block. Inline styles, no scroll. -->\n<div style=\"border:1px solid #EAECEF;border-radius:8px;overflow:hidden;margin:24px 0;\">\n  <table style=\"width:100%;border-collapse:collapse;table-layout:fixed;font-family:inherit;\">\n    <colgroup><col style=\"width:34%;\"><col style=\"width:66%;\"><\/colgroup>\n    <thead><tr>\n      <th style=\"background:#1F3A5C;color:#fff;text-align:left;font-weight:700;font-size:13px;padding:12px 12px;font-family:inherit;\">Return code<\/th>\n      <th style=\"background:#1F3A5C;color:#fff;text-align:left;font-weight:700;font-size:13px;padding:12px 12px;font-family:inherit;\">Zone<\/th>\n    <\/tr><\/thead>\n    <tbody>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#C0392B;\">127.0.0.2<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">SBL<\/td>\n      <\/tr>\n      <tr style=\"background:#F5F6F7;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#C0392B;\">127.0.0.3<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">CSS<\/td>\n      <\/tr>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#C0392B;\">127.0.0.4<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">XBL<\/td>\n      <\/tr>\n      <tr style=\"background:#F5F6F7;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#C0392B;\">127.0.0.9<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">SBL DROP (returned alongside the SBL code)<\/td>\n      <\/tr>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#B7791F;\">127.0.0.10<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">PBL &mdash; range declared by the ISP<\/td>\n      <\/tr>\n      <tr style=\"background:#F5F6F7;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#B7791F;\">127.0.0.11<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">PBL &mdash; Spamhaus-maintained<\/td>\n      <\/tr>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#6B7280;\">127.255.255.252<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\"><strong style=\"color:#6B7280;\">Error<\/strong> &mdash; typing error in the query, or the query was truncated. Not a listing<\/td>\n      <\/tr>\n      <tr style=\"background:#F5F6F7;\">\n        <td style=\"padding:12px 12px;vertical-align:top;border-bottom:1px solid #EAECEF;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#6B7280;\">127.255.255.254<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\"><strong style=\"color:#6B7280;\">Error<\/strong> &mdash; query came from an open or public resolver. Not a listing<\/td>\n      <\/tr>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:12px 12px;vertical-align:top;\"><code style=\"font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12.5px;font-weight:700;color:#6B7280;\">127.255.255.255<\/code><\/td>\n        <td style=\"padding:12px 12px;vertical-align:top;font-size:13px;line-height:1.5;color:#24262B;font-family:inherit;overflow-wrap:anywhere;\"><strong style=\"color:#6B7280;\">Error<\/strong> &mdash; query volume exceeded the free-use limit. Not a listing<\/td>\n      <\/tr>\n    <\/tbody>\n  <\/table>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Read the return code carefully before you act on it.<\/strong> Public resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, OpenDNS) return <code>127.255.255.254<\/code> for every query \u2014 an error code meaning &#8220;open resolver&#8221;, not a listing. Treat any answer in <code>127.255.255.x<\/code> as a failed query, not a result. Naive tooling reads that positive <code>127.x<\/code> answer as LISTED and will tell you every IP you own is blocked. Use a resolver that queries Spamhaus directly, or the web checker at <a href=\"https:\/\/check.spamhaus.org\" rel=\"nofollow\">check.spamhaus.org<\/a>, which returns the zone and the removal link together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One caveat on the resolver route: Spamhaus states that the free public query service &#8220;still exists but is being deprecated&#8221; in favour of its free Data Query Service, and self-hosted resolvers querying above fair-use volume are cut off. If you check listings regularly, register for a free DQS key at <a href=\"https:\/\/www.spamhaus.org\/free-trial\/sign-up-for-a-free-data-query-service-account\/\" rel=\"nofollow\">spamhaus.org<\/a> and query your DQS zones instead of the public ones.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Zone_Reference_Table\"><\/span>The Zone Reference Table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is the table to bookmark. Find your zone, and you know who fixes it and where.<\/p>\n\n\n\n<!-- Spamhaus zone reference table. Paste into a WP Custom HTML block. Inline styles, no scroll.\n     Zone links point to check.spamhaus.org \/ portal.spamhaus.org \u2014 keep them as-is. -->\n<div style=\"border:1px solid #EAECEF;border-radius:8px;overflow:hidden;margin:24px 0;\">\n  <table style=\"width:100%;border-collapse:collapse;table-layout:fixed;font-family:inherit;\">\n    <colgroup><col style=\"width:8%;\"><col style=\"width:26%;\"><col style=\"width:24%;\"><col style=\"width:19%;\"><col style=\"width:23%;\"><\/colgroup>\n    <thead><tr>\n      <th style=\"background:#1F3A5C;color:#fff;text-align:left;font-weight:700;font-size:12.5px;padding:12px 11px;font-family:inherit;\">Zone<\/th>\n      <th style=\"background:#1F3A5C;color:#fff;text-align:left;font-weight:700;font-size:12.5px;padding:12px 11px;font-family:inherit;\">What triggers it<\/th>\n      <th style=\"background:#1F3A5C;color:#fff;text-align:left;font-weight:700;font-size:12.5px;padding:12px 11px;font-family:inherit;\">Who can request removal<\/th>\n      <th style=\"background:#1F3A5C;color:#fff;text-align:left;font-weight:700;font-size:12.5px;padding:12px 11px;font-family:inherit;\">Typical resolution<\/th>\n      <th style=\"background:#1F3A5C;color:#fff;text-align:left;font-weight:700;font-size:12.5px;padding:12px 11px;font-family:inherit;\">Where<\/th>\n    <\/tr><\/thead>\n    <tbody>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:13px;border-bottom:1px solid #EAECEF;font-family:inherit;\"><strong style=\"color:#C0392B;\">SBL<\/strong><\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Manual, evidence-backed listing: spam sources, snowshoe configurations, spam-support services, malware\/phishing hosting<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">The ISP or network operator responsible for the IP &mdash; not usually the end sender<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Human review; not automatic and not instant<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\"><a href=\"https:\/\/check.spamhaus.org\" style=\"color:#1F6FEB;\" rel=\"nofollow\">check.spamhaus.org<\/a> &rarr; the SBL listing detail page<\/td>\n      <\/tr>\n      <tr style=\"background:#F5F6F7;\">\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:13px;border-bottom:1px solid #EAECEF;font-family:inherit;\"><strong style=\"color:#C0392B;\">CSS<\/strong><\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Automated reputation detection: spam trap hits, poor list hygiene, unsolicited-looking mail, compromised or misconfigured servers<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">The IP administrator &mdash; self-service, within limits<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Auto-expires ~3 days after last detection; longer for chronic abuse<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\"><a href=\"https:\/\/check.spamhaus.org\" style=\"color:#1F6FEB;\" rel=\"nofollow\">check.spamhaus.org<\/a> &mdash; the only place CSS removals are handled<\/td>\n      <\/tr>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:13px;border-bottom:1px solid #EAECEF;font-family:inherit;\"><strong style=\"color:#C0392B;\">XBL<\/strong><\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Signs of compromise: malware infection, botnet participation, open proxy, brute-force activity, illegitimate credentials used to relay mail<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Whoever controls the host &mdash; after the compromise is actually cleaned<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Auto-expires once the malicious behavior stops being detected<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\"><a href=\"https:\/\/check.spamhaus.org\" style=\"color:#1F6FEB;\" rel=\"nofollow\">check.spamhaus.org<\/a> &mdash; the only place XBL removals are handled<\/td>\n      <\/tr>\n      <tr style=\"background:#F5F6F7;\">\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:13px;border-bottom:1px solid #EAECEF;font-family:inherit;\"><strong style=\"color:#C0392B;\">PBL<\/strong><\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">IP space that should not send direct-to-MX &mdash; usually dynamic\/consumer ranges. Not an accusation of spamming<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">The ISP via its PBL account; or an end user for a <em>single static<\/em> IP running a real mail server<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">Usually quick once the removal is accepted, though Spamhaus publishes no propagation time<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;border-bottom:1px solid #EAECEF;font-family:inherit;overflow-wrap:anywhere;\">End users: <a href=\"https:\/\/check.spamhaus.org\" style=\"color:#1F6FEB;\" rel=\"nofollow\">check.spamhaus.org<\/a>. ISPs: <a href=\"https:\/\/portal.spamhaus.org\/isp\/start\/\" style=\"color:#1F6FEB;\" rel=\"nofollow\">portal.spamhaus.org\/isp\/start\/<\/a><\/td>\n      <\/tr>\n      <tr style=\"background:#FFFFFF;\">\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:13px;font-family:inherit;\"><strong style=\"color:#C0392B;\">DBL<\/strong><\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;font-family:inherit;overflow-wrap:anywhere;\">Domain reputation: spam domains, phishing, malware, botnet C&amp;C, snowshoe throwaway domains, and abused-legitimate domains<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;font-family:inherit;overflow-wrap:anywhere;\">The domain owner<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;font-family:inherit;overflow-wrap:anywhere;\">Minutes to 24 hours in most cases; expires automatically when abuse stops<\/td>\n        <td style=\"padding:11px 11px;vertical-align:top;font-size:12px;line-height:1.5;color:#24262B;font-family:inherit;overflow-wrap:anywhere;\"><a href=\"https:\/\/check.spamhaus.org\" style=\"color:#1F6FEB;\" rel=\"nofollow\">check.spamhaus.org<\/a><\/td>\n      <\/tr>\n    <\/tbody>\n  <\/table>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">One behaviour worth knowing: Spamhaus lists at the <strong>hostname<\/strong> level for abused-legitimate cases in the DBL rather than always listing the entire registered domain. A compromised subdomain no longer automatically takes your primary sending domain with it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_4_Most_Common_Reasons_Senders_Get_Listed\"><\/span>The 4 Most Common Reasons Senders Get Listed<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Spam traps (the dominant trigger for SBL and CSS)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Spamhaus operates a very large trap network, and in our experience trap hits are the most common reason a legitimate sender ends up on CSS or SBL \u2014 Spamhaus does not publish a breakdown of listing causes, so treat that as a practitioner observation rather than a published statistic. Two kinds matter. <strong>Pristine traps<\/strong> are addresses that were never valid and never opted in anywhere \u2014 hitting one means your data came from scraping or a purchase, and it is treated as strong evidence, enough to support a manual SBL listing. <strong>Recycled traps<\/strong> are real addresses that were abandoned, hard-bounced for months, then reactivated by the provider as traps. Recycled traps are what catch honest senders: the address was legitimately collected years ago and simply never removed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. No sunset policy<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you mail contacts who have not opened or clicked in a year, you are mailing addresses that have had ample time to turn into recycled traps. This is the mechanism behind most surprise CSS listings at otherwise clean senders.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Snowshoe-shaped sending patterns<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Thin volume spread across many IPs, rotating subdomains, fresh domains with sparse WHOIS, and inconsistent identification across the fleet. CSS is built specifically to detect this. Well-meaning senders trip it by over-fragmenting their infrastructure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. A compromised host or misconfigured relay<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An open relay, a compromised CMS sending through your MTA, a leaked SMTP credential, or a form without rate limiting. This usually lands you on XBL rather than CSS \u2014 and the listing will keep returning until the actual hole is closed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_Fix_It_Step_by_Step\"><\/span>How to Fix It: Step by Step<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The order below matters more than any individual step. Most senders start at the last step, and it costs them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Identify the zone \u2192 stop the traffic \u2192 fix the root cause \u2192 verify \u2192 request removal.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why requesting removal first backfires<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">CSS and XBL both re-list immediately if the triggering behavior is still detected, so delisting mid-campaign buys you hours. Spamhaus is unusually strict about that pattern: self-service removal is explicitly limited \u2014 Spamhaus describes &#8220;fast, no-questions-asked removals \u2013 within limits&#8221; \u2014 and the reasonable inference is that repeatedly delisting the same IP without fixing the cause exhausts those limits and leaves you without self-service. You have then converted a three-day automatic expiry into a manual case a human must review. For SBL it is simpler still \u2014 a request submitted while the spam is still flowing shows you have not diagnosed anything, and it costs you credibility on every future request.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Identify the exact zone<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Run the ZEN lookup or use check.spamhaus.org. Do not proceed until you know whether this is SBL, CSS, XBL, PBL, or DBL. If you are on more than one, our recommended triage order is SBL first, then XBL and CSS, then PBL. Spamhaus does not document an official ordering \u2014 this is our practitioner advice, based on which listing costs you the most while it stands.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Stop the triggering traffic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pause sending from the listed IP entirely. Not &#8220;reduce&#8221; \u2014 stop. CSS listings expire roughly three days after the last detection, so every campaign you push through the block resets that clock. A large share of CSS listings resolve with no request at all if you simply stop sending.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Fix the root cause<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>CSS or SBL:<\/strong> isolate which campaign and segment triggered it. Suppress every contact with no engagement in 90 days, delete any purchased, appended, or scraped data outright, and verify what remains.<\/li>\n\n\n\n<li><strong>XBL:<\/strong> treat it as a security incident. Audit for open relay, rotate all SMTP credentials, patch the application layer, and check outbound logs for mail you did not send.<\/li>\n\n\n\n<li><strong>PBL:<\/strong> confirm the IP is static with matching forward and reverse DNS and a real outbound mail server behind it. If it is genuinely dynamic broadband space, the fix is not delisting \u2014 it is relaying through a smarthost or an ESP.<\/li>\n\n\n\n<li><strong>DBL:<\/strong> remove the offending content or compromised subdomain before touching the removal form.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Verify before you request<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Re-check the IP at check.spamhaus.org \u2014 sometimes the listing has already expired and you need to do nothing. Confirm sending is still paused and no automation is scheduled to resume.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Submit the removal request, then re-warm<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Everything runs through <a href=\"https:\/\/check.spamhaus.org\" rel=\"nofollow\">check.spamhaus.org<\/a>. Look up the IP or domain, open the listing details, and follow the removal link for that zone. There is no separate sender portal, no email address to write to, and no paid fast-track. Once you are clear, do not resume at full volume: start at 10\u201325% of normal, mail only contacts who engaged in the last 30 days, and increase gradually. A relisting days after a delisting is much harder to resolve than the original listing was.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Paste-Ready_Removal_Request_Template\"><\/span>Paste-Ready Removal Request Template<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When the removal form gives you a free-text field, this is the shape that gets processed. Specific, verifiable, no excuses, no volume of adjectives. Replace the bracketed values.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><em>IP: [203.0.113.45] &nbsp;|&nbsp; Listing: [CSS \/ SBL ref SBL123456] &nbsp;|&nbsp; Organization: [Company], [website]<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>What we send:<\/strong> Opt-in [marketing \/ transactional] email for [Company]. This IP sends only for our own [domain.com] mail, at roughly [X] messages per day.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>What caused the listing:<\/strong> On [date] we sent a campaign to a segment of [N] contacts that had not engaged since [date]. That segment included addresses collected in [year] that we had never sunset, and we believe it contained recycled spam traps.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>What we have done:<\/strong> (1) Stopped all sending from this IP on [date\/time UTC]. (2) Permanently suppressed [N] contacts with no opens or clicks in 90 days. (3) Deleted [N] contacts from [source] entirely. (4) Ran the remaining [N] addresses through verification and removed [N] invalid. (5) Implemented an automatic 90-day sunset rule so this segment cannot be rebuilt.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>What we will do next:<\/strong> Resume at [X]% of prior volume to 30-day-engaged recipients only, ramping over [N] weeks.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Technical contact: [name], [role], [email at your sending domain].<\/em><\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Two rules for using it. Use a contact address at your own sending domain, not a free mailbox. And do not claim a fix you have not actually made \u2014 Spamhaus can see whether the traffic pattern changed, and a request contradicted by the data is worse than no request.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_Prevent_Spamhaus_Listings\"><\/span>How to Prevent Spamhaus Listings<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Sunset aggressively and bounce strictly<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A 90-day engagement window for most senders, and no longer than 180 days for anyone. Suppress hard bounces permanently and immediately \u2014 a hard-bouncing address you keep mailing is a recycled trap in waiting. The whole recycled-trap problem lives in the gap between &#8220;stopped engaging&#8221; and &#8220;still on the list.&#8221;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Use confirmed opt-in on risky acquisition sources, and never buy data<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Paid lead-gen, co-registration, offline collection, and unvalidated form fills are where pristine traps enter. Confirmed opt-in eliminates them at the door. Purchased, rented, and appended data has no clean version \u2014 not for a pilot, not for one campaign.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Monitor the zones on a schedule<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check your sending IPs and domains weekly, not after the bounces start. CSS listings expire in about three days, so a weekly check can miss one entirely while your delivery quietly suffers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Consolidate rather than fragment infrastructure<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Concentrated, consistently identified sending looks legitimate. Volume thinly spread across many IPs and rotating subdomains looks like snowshoe, whatever your intent.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Shared_IP_vs_Dedicated_IP_Who_Fixes_What\"><\/span>Shared IP vs. Dedicated IP: Who Fixes What<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On a <strong>shared IP pool<\/strong>, the listing is your provider&#8217;s to resolve \u2014 they own the IP and only they can act on it. Your job is to identify and stop your contribution, because your provider will isolate the sender that caused it. A CSS listing on a shared pool usually means one tenant mailed a stale list.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a <strong>dedicated IP<\/strong>, everything above is yours: you own the reputation, submit the removal, and set the re-warm pace.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PBL is the exception to both \u2014 it is almost always the ISP&#8217;s record about their own address space. If you are on PBL as a legitimate sender, either claim the single static IP through the checker or stop sending direct-to-MX.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_Mailercloud_Handles_Spamhaus_Listings\"><\/span>How Mailercloud Handles Spamhaus Listings<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Mailercloud delivers over a billion emails a month, so Spamhaus zone monitoring is continuous rather than reactive. Our deliverability team watches trap feedback and reputation signals across all shared pools, isolates a sender before a pattern becomes a listing, and owns the full stop-fix-verify-delist-rewarm cycle when one does occur. Customers on dedicated IPs get the same diagnosis and the same re-warm plan, applied to infrastructure they control.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you are looking at a &#8220;blocked using zen.spamhaus.org&#8221; bounce right now, <a href=\"https:\/\/www.mailercloud.com\/contact\">talk to our deliverability team<\/a> \u2014 or <a href=\"https:\/\/app.mailercloud.com\/register\">start free with Mailercloud<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAQ_Spamhaus_Delisting\"><\/span>FAQ: Spamhaus Delisting<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">How long does a Spamhaus CSS listing last?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">CSS listings normally expire about three days after the last detection, and in cases of chronic abuse they last longer. If you stop the triggering traffic and change nothing else, many CSS listings clear on their own without any request.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I remove myself from the SBL?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Usually not directly. SBL removals are meant to come from the ISP or network operator responsible for the IP, and they are human-reviewed rather than automatic. If you are on a shared pool, this is your provider&#8217;s request to make. If you control the network yourself, work through the listing detail page at check.spamhaus.org.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What happens if I keep requesting delisting?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Self-service removals are limited by design. Repeatedly delisting the same IP without correcting the underlying problem gets your self-service access revoked, which turns a fast automatic expiry into a slow manual case. Fix first, request once.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does my IP get relisted immediately after removal?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Because the triggering behavior is still being detected. CSS and XBL both re-list on detection, so a delisting that happens while your campaign is still running buys you hours at most. Stop the sending completely before you request anything.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">I am listed on more than one zone. Which do I fix first?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Spamhaus does not publish a prescribed order, so this is our own triage advice: SBL, then XBL and CSS, then PBL. PBL goes last, because it is a policy statement about the address space rather than a reputation problem, and clearing it while you are still emitting low-reputation mail achieves nothing. And note that removal is free in every case \u2014 any third party offering paid removal is running a scam.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What does &#8220;blocked using zen.spamhaus.org&#8221; mean?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Your sending IP is on at least one of Spamhaus&#8217;s IP blocklists \u2014 but the ZEN response alone doesn&#8217;t say which. ZEN bundles SBL, CSS, XBL, and PBL into one query, so the fix is to look up the IP at check.spamhaus.org (or <code>dig<\/code> the zone) and read the <code>127.0.0.x<\/code> code: <code>.2<\/code> is SBL, <code>.3<\/code> is CSS, <code>.4<\/code> is XBL, <code>.10<\/code>\/<code>.11<\/code> is PBL. Each has a different owner and removal path, so identifying the zone is the whole first step.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Blocked with &#8220;listed in zen.spamhaus.org&#8221;? Learn the difference between SBL, CSS, XBL and PBL, how to check your IP, and how to get delisted the right way.<\/p>\n","protected":false},"author":19,"featured_media":5318,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28],"tags":[56,45,47,57,55],"class_list":["post-5208","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-delivery","tag-blocklists","tag-deliverability","tag-sender-reputation","tag-spam-traps","tag-spamhaus"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)<\/title>\n<meta name=\"description\" content=\"Blocked using zen.spamhaus.org? How to tell SBL,CSS,XBL,PBL and DBL apart, fix the real cause and delist the right way without paying anyone\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)\" \/>\n<meta property=\"og:description\" content=\"Blocked using zen.spamhaus.org? How to tell SBL,CSS,XBL,PBL and DBL apart, fix the real cause and delist the right way without paying anyone\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting\" \/>\n<meta property=\"og:site_name\" content=\"Mailercloud Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/mailercloud\" \/>\n<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/cherikkapoyil.amar\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-11T09:41:12+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-08T04:44:05+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/07\/Spamhaus-Delisting.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"760\" \/>\n\t<meta property=\"og:image:height\" content=\"380\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Amar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@mailercloud\" \/>\n<meta name=\"twitter:site\" content=\"@mailercloud\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Amar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting\"},\"author\":{\"name\":\"Amar\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#\\\/schema\\\/person\\\/0f3151b32a261b5f5df0a7968fa64945\"},\"headline\":\"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)\",\"datePublished\":\"2026-08-11T09:41:12+00:00\",\"dateModified\":\"2026-09-08T04:44:05+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting\"},\"wordCount\":2772,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Spamhaus-Delisting.jpg\",\"keywords\":[\"blocklists\",\"deliverability\",\"sender reputation\",\"spam traps\",\"spamhaus\"],\"articleSection\":[\"Email Delivery\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting\",\"url\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting\",\"name\":\"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Spamhaus-Delisting.jpg\",\"datePublished\":\"2026-08-11T09:41:12+00:00\",\"dateModified\":\"2026-09-08T04:44:05+00:00\",\"description\":\"Blocked using zen.spamhaus.org? How to tell SBL,CSS,XBL,PBL and DBL apart, fix the real cause and delist the right way without paying anyone\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#primaryimage\",\"url\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Spamhaus-Delisting.jpg\",\"contentUrl\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Spamhaus-Delisting.jpg\",\"width\":760,\"height\":380,\"caption\":\"Spamhaus Delisting: How to Fix SBL and CSS Listings\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/spamhaus-delisting#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/\",\"name\":\"Mailercloud Blog\",\"description\":\"Create And Implement Email Marketing Campaigns\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#organization\",\"name\":\"Mailercloud Blog\",\"url\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/footer_logo.png\",\"contentUrl\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/footer_logo.png\",\"width\":141,\"height\":30,\"caption\":\"Mailercloud Blog\"},\"image\":{\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/mailercloud\",\"https:\\\/\\\/x.com\\\/mailercloud\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/mailercloud\\\/\",\"https:\\\/\\\/www.instagram.com\\\/mailercloud\\\/\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UCslSwv-TECN8rLvFM8wRlog\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/#\\\/schema\\\/person\\\/0f3151b32a261b5f5df0a7968fa64945\",\"name\":\"Amar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/1547012193070-150x150.jpeg\",\"url\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/1547012193070-150x150.jpeg\",\"contentUrl\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/1547012193070-150x150.jpeg\",\"caption\":\"Amar\"},\"description\":\"Amar CP is the Co-Founder and Sales Director at Mailercloud, where he leads partnerships, alliances, and customer growth. With over a decade of experience in application development, database architecture, and scaling web systems, Amar brings a rare blend of engineering depth and go-to-market expertise to email marketing. He writes about email deliverability, marketing automation, and helping small businesses grow smarter with data-driven campaigns.\",\"sameAs\":[\"http:\\\/\\\/www.mailercloud.com\",\"https:\\\/\\\/www.facebook.com\\\/cherikkapoyil.amar\",\"https:\\\/\\\/www.instagram.com\\\/amar.cp\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/amarcp\\\/\"],\"url\":\"https:\\\/\\\/www.mailercloud.com\\\/blog\\\/author\\\/amarmailercloud-com\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)","description":"Blocked using zen.spamhaus.org? How to tell SBL,CSS,XBL,PBL and DBL apart, fix the real cause and delist the right way without paying anyone","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting","og_locale":"en_US","og_type":"article","og_title":"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)","og_description":"Blocked using zen.spamhaus.org? How to tell SBL,CSS,XBL,PBL and DBL apart, fix the real cause and delist the right way without paying anyone","og_url":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting","og_site_name":"Mailercloud Blog","article_publisher":"https:\/\/www.facebook.com\/mailercloud","article_author":"https:\/\/www.facebook.com\/cherikkapoyil.amar","article_published_time":"2026-08-11T09:41:12+00:00","article_modified_time":"2026-09-08T04:44:05+00:00","og_image":[{"width":760,"height":380,"url":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/07\/Spamhaus-Delisting.jpg","type":"image\/jpeg"}],"author":"Amar","twitter_card":"summary_large_image","twitter_creator":"@mailercloud","twitter_site":"@mailercloud","twitter_misc":{"Written by":"Amar","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#article","isPartOf":{"@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting"},"author":{"name":"Amar","@id":"https:\/\/www.mailercloud.com\/blog\/#\/schema\/person\/0f3151b32a261b5f5df0a7968fa64945"},"headline":"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)","datePublished":"2026-08-11T09:41:12+00:00","dateModified":"2026-09-08T04:44:05+00:00","mainEntityOfPage":{"@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting"},"wordCount":2772,"commentCount":0,"publisher":{"@id":"https:\/\/www.mailercloud.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#primaryimage"},"thumbnailUrl":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/07\/Spamhaus-Delisting.jpg","keywords":["blocklists","deliverability","sender reputation","spam traps","spamhaus"],"articleSection":["Email Delivery"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting","url":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting","name":"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)","isPartOf":{"@id":"https:\/\/www.mailercloud.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#primaryimage"},"image":{"@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#primaryimage"},"thumbnailUrl":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/07\/Spamhaus-Delisting.jpg","datePublished":"2026-08-11T09:41:12+00:00","dateModified":"2026-09-08T04:44:05+00:00","description":"Blocked using zen.spamhaus.org? How to tell SBL,CSS,XBL,PBL and DBL apart, fix the real cause and delist the right way without paying anyone","breadcrumb":{"@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#primaryimage","url":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/07\/Spamhaus-Delisting.jpg","contentUrl":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/07\/Spamhaus-Delisting.jpg","width":760,"height":380,"caption":"Spamhaus Delisting: How to Fix SBL and CSS Listings"},{"@type":"BreadcrumbList","@id":"https:\/\/www.mailercloud.com\/blog\/spamhaus-delisting#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.mailercloud.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Spamhaus Delisting: How to Fix SBL and CSS Listings (2026)"}]},{"@type":"WebSite","@id":"https:\/\/www.mailercloud.com\/blog\/#website","url":"https:\/\/www.mailercloud.com\/blog\/","name":"Mailercloud Blog","description":"Create And Implement Email Marketing Campaigns","publisher":{"@id":"https:\/\/www.mailercloud.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.mailercloud.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.mailercloud.com\/blog\/#organization","name":"Mailercloud Blog","url":"https:\/\/www.mailercloud.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.mailercloud.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2025\/02\/footer_logo.png","contentUrl":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2025\/02\/footer_logo.png","width":141,"height":30,"caption":"Mailercloud Blog"},"image":{"@id":"https:\/\/www.mailercloud.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/mailercloud","https:\/\/x.com\/mailercloud","https:\/\/www.linkedin.com\/company\/mailercloud\/","https:\/\/www.instagram.com\/mailercloud\/","https:\/\/www.youtube.com\/channel\/UCslSwv-TECN8rLvFM8wRlog"]},{"@type":"Person","@id":"https:\/\/www.mailercloud.com\/blog\/#\/schema\/person\/0f3151b32a261b5f5df0a7968fa64945","name":"Amar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/04\/1547012193070-150x150.jpeg","url":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/04\/1547012193070-150x150.jpeg","contentUrl":"https:\/\/www.mailercloud.com\/blog\/wp-content\/uploads\/2026\/04\/1547012193070-150x150.jpeg","caption":"Amar"},"description":"Amar CP is the Co-Founder and Sales Director at Mailercloud, where he leads partnerships, alliances, and customer growth. With over a decade of experience in application development, database architecture, and scaling web systems, Amar brings a rare blend of engineering depth and go-to-market expertise to email marketing. He writes about email deliverability, marketing automation, and helping small businesses grow smarter with data-driven campaigns.","sameAs":["http:\/\/www.mailercloud.com","https:\/\/www.facebook.com\/cherikkapoyil.amar","https:\/\/www.instagram.com\/amar.cp\/","https:\/\/www.linkedin.com\/in\/amarcp\/"],"url":"https:\/\/www.mailercloud.com\/blog\/author\/amarmailercloud-com"}]}},"_links":{"self":[{"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/posts\/5208","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/comments?post=5208"}],"version-history":[{"count":5,"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/posts\/5208\/revisions"}],"predecessor-version":[{"id":5576,"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/posts\/5208\/revisions\/5576"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/media\/5318"}],"wp:attachment":[{"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/media?parent=5208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/categories?post=5208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mailercloud.com\/blog\/wp-json\/wp\/v2\/tags?post=5208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}