Blocklist (RBL/DNSBL)
Public lists of IPs and domains known for spam. Mail servers check them in real time and refuse or junk anything that shows up.
See it
What it is
A blocklist (older name: RBL, real-time blackhole list; technically a DNSBL because it is queried over DNS) is a published set of IPs or domains associated with spam. Receiving mail servers look you up at SMTP time and reject or junk the message before your content is ever read. Weight is not a property of the list, it is a property of who queries it. Spamhaus zones (SBL, CSS, XBL, and PBL, usually queried together as ZEN, plus DBL for domains) are consulted very widely, so a listing there tends to turn into visible rejections fast. Barracuda, SpamCop, UCEPROTECT, and others matter in proportion to how many of your recipients' servers actually consult them, and a few small lists exist mainly to sell removal. Rank a listing by the rejections showing up in your logs, not by the name on the page.
You get listed by hitting a spam trap, spiking volume on a cold IP, collecting complaints, sending from a compromised server, or sharing a pool IP with someone who did any of the above. Check with mxtoolbox or Spamhaus directly, and read the rejection message: a real 5xx bounce usually names the list and links the delisting page. Fix the cause first, then request removal. Delisting while the leak is still open just buys you a faster relisting with a worse note attached.
Two things people get wrong. A blocklist is not the same as a bad reputation at Gmail: Gmail leans mostly on its own signals, so you can be spotless on every public list and still sit in the Promotions tab or Spam. And domain listings follow you across providers, so switching sending platforms fixes nothing if the taint is on your domain or your click-tracking domain. Meanwhile a shared-IP listing is often not your doing at all, which is the strongest argument for a dedicated IP once your volume supports one.
Ask AI for it
Build a blocklist monitor for our sending infrastructure. For each sending IP, run reversed-octet DNS A lookups against zen.spamhaus.org, b.barracudacentral.org, and bl.spamcop.net; for our sending domain and click-tracking domain, query dbl.spamhaus.org. Run it hourly, store every result with the returned response code and TXT reason, and open a high priority alert on any new listing that includes the list name, the reason text, and the delisting URL. Also parse bounce messages for SMTP 5xx replies mentioning a blocklist and tag those sends. Show a status page with current listings, listing history, and time to delist. Set severity from evidence rather than from the vendor name: a listing correlated with real rejections in our bounce logs is severity one, a listing with no matching rejections is informational until that changes, and note that a widely queried zone like Spamhaus ZEN will usually produce that evidence within hours.