emailrules.today
In forceHygieneIn force 1 Aug 2026

Fix the cause before requesting blocklist removal

What do Spamhaus SBL, CSS and DBL listings mean, and who removes one on a shared ESP IP?

Global

In one sentence

A blocklist hit is a signal, not a fine — fix the cause first; paid delisting without that is theatre.

Plain English

Spamhaus and similar lists are data receivers may use. problems often belong with your ticket queue. Your domain on a domain blocklist is usually your list hygiene, traps, or compromised form. Stop the behaviour, then request delisting. Paying a middleman first rarely sticks.

Why it matters. Teams burn budget on delist services while the signup form still feeds traps every night.

Dotted words open definitions. Full glossary.

What to do

Your move — not a lecture

Part platform, part you

The platform covers the mechanical bit. The judgement is still yours.

On shared IPs the or upstream network owns the SBL removal channel and the IP's neighbour risk.

Your part: List practices, complaint rates, trap hygiene, and any branded domain or tracking domain that got listed.

What to do first

Run sending IPs, From/ domains and tracking domains through check.spamhaus.org. Build an owner table: → ticket; domain listing → your and list practices.

You can skip this if: You send no email and expose no domain in email .

Who this applies to

Anyone whose IP or domain shows on Spamhaus check tools, and anyone buying or renting lists.

Checklist

  • 01Identify whether the listing is IP (SBL/CSS) or domain (DBL) before acting.
  • 02Fix acquisition, complaint and trap causes first; then request removal through the correct owner.
  • 03Do not publish "Spamhaus means all mail is blocked". Test the receivers you care about.
  • 04Treat purchased lists as a first-party Spamhaus risk signal, not a grey-area growth hack.

That’s enough to act. Sources and exact wording are below for counsel, bosses, or AI tools that need a citation. Not legal advice.

Proof

Exact position, enforcement, sources

For records and people who will check you. Skip if Monday’s move is already clear.

The exact position

Spamhaus SBL, CSS and DBL are reputation datasets, not a court order and not a universal "email is blocked" switch. Each mailbox or gateway operator decides how to treat a listed IP or domain. Shared sending IPs are remediated by the network or that owns them; branded domains on DBL are the marketer's. Purchased lists are a documented path to traps, complaints and listings. Removal without fixing the cause is how you reappear.

What happens if you do not

Spamhaus does not levy marketing fines. Receivers choose reject, defer, tag or ignore. Impact ranges from nothing at one provider to widespread filtering at others.

Sources

Related

History of this page

  • Added from Spamhaus policy pages.

FAQ

Awkward questions

Who is this actually for?

People who ship email and are too busy to re-read every PDF: week-one marketers, lifecycle/CRM, deliverability, multi-country ops, DTC brands, agencies — on Klaviyo, Mailchimp, Braze, HubSpot, SFMC, or something else. Pick your tool and geos so product-specific pages only appear when they match. EU and UK are first-class filters. Not for people who sell tools about email and need a fake score to demo.

Why only ~40 rules? Isn’t that… thin?

On purpose. A wall of 400 undated “best practices” is how you look busy and still get burned. Every page needs a primary source we actually read. Thin and checkable beats fat and folklore. Europe, bulk inbox rules, measurement honesty, and protocol topics like BIMI/DMARC policy are on the shelf when we can cite them — not every Member State and not every vendor myth. Coverage map lists what we still refuse to invent.

Is this legal advice?

No. If it were, you’d have a billable hour and a longer PDF. This is a dated operator reference written by an email geek. Confirm anything high-stakes with counsel who knows your facts. Same for “will this make me compliant?” — no tool does that. Lawyers and judges do. We say what the sources say and what to do first on Monday.

Why no trust score out of 100?

Because we refuse to invent a number you can’t audit. Fake scores sell seed tests and panic. You get findings, dates, and links. If that feels less exciting than a red dial, good — you’re not the red-dial customer.

Why should I trust you more than my ESP’s blog?

ESPs sell seats. Seed-score vendors sell fear. AI invents citations when nobody watches. We sell nothing today — no pixels, no placement scores, no affiliate — so we can say when a tool is the problem. A human verifies, dates, and corrects in public. Tools may help draft; they do not ship unsourced claims. Check the primary links. Fail that test and leave.

Do I need an account?

No. Filters live in this browser and the URL. Share the link. That’s it. Accounts come later only if they earn it — not so we can nurture you about email.

I’m an agency. Where’s multi-client mode?

We tried a client-name CRM on the setup card. It made the product feel like work before it felt useful. Role filters + copy link + one-page brief (optional PDF title) is enough for now. Complexity comes back when the free shelf is habit, not before.

Is the quiet changelog a bug?

No. Quiet means nothing material moved. We don’t invent urgency so the homepage looks “alive.” Sticky risks still show what usually needs a person when the market is still.