A list of IPs or domains flagged for sending spam. Being listed can block or filter your emails. Good sending practices help avoid it.
Some blocklists are managed by ISPs while other blocklists are operated independently and are sometimes referred to by ISPs to filter out bad actors.
It's important to note that not all blocklists carry weight in the decision-making of ISPs. Some blocklist operators even accept compensation to remove a sender from their list, even if that listing is not materially impacting deliverability. Not all blocklists are created equal!
A blocklist (still called a blacklist by many tools) is a database of IP addresses or domains that an operator believes are sending spam. Mailbox providers and corporate spam filters query these lists in real time when a message arrives. If your sending IP address, your from domain, or a domain used in your links appears on a list they trust, the message can be rejected outright, sent to spam, or quietly dropped.
Listings are triggered by evidence, not opinion. Common causes are hitting spam traps, a spike in complaints from recipients marking mail as spam, sending to a large number of invalid addresses, and compromised accounts or servers relaying unwanted mail. Each list has its own rules for what gets you on and how long you stay.
The lists with the most influence on delivery are the ones major providers and filtering vendors consult. Spamhaus runs the most widely used ones: the SBL for known spam sources, the XBL for compromised machines, the PBL for IP ranges that should not send mail directly, and the DBL for domains. Spamhaus listings can stop mail at a large share of mailbox providers, so they deserve immediate attention. Other lists that filtering products reference include Barracuda, SpamCop, and SURBL and URIBL for link domains.
Beyond the public lists, every large mailbox provider runs its own internal reputation system. Gmail, Microsoft, and Yahoo do not publish these and you cannot request removal from them. Their internal scoring, driven by engagement and complaint rates, matters more to day-to-day deliverability than most public blocklists.
Not every list carries weight. Some small operators list aggressively and charge for removal. If a listing is not appearing in your bounce messages, it is probably not affecting your delivery, and paying to be delisted is never necessary on a reputable list.
Most reputable lists remove entries automatically once the problem stops, or accept a removal request through a form. Before requesting removal, fix the root cause: pause the campaign that caused complaints, remove invalid and unengaged addresses, close any open relay or compromised account, and confirm SPF, DKIM, and DMARC are passing. Requesting removal without fixing the cause usually leads to a relisting, and repeat listings take longer to clear.
If you send through a shared IP pool at an ESP, the provider handles delisting for the pool, but your sending behavior still affects everyone on it. Persistent problems usually end with the ESP moving or suspending the account.