Email blocklists explained: what a listing means and what to do next

What an email blacklist actually is

“Blacklist” and “blocklist” mean the same thing here; most operators now say blocklist. Technically, most are DNS-based lists, or DNSBLs: a DNS zone that answers when an IP address or domain is listed. RFC 5782 documents the convention. To check IPv4 address 192.0.2.99, a mail server reverses the octets, appends the list’s zone, and looks the name up. An A record answer—typically 127.0.0.2—means the address is listed, and a TXT record can carry the reason. [1]

Receivers query lists at different points. Spamhaus, for example, positions its IP lists for the initial connection and its Domain Blocklist for SMTP identities and message content. A listing therefore does not mean “blocked everywhere.” It means receivers that use that list, at that stage, may reject, defer, or score your mail. [2][3]

IP lists and domain lists answer different questions

Each operator publishes its own lists with its own criteria and removal rules, so read the specific list’s policy rather than assuming one behaves like another. RFC 5782 notes that domain-based lists exist alongside IP lists, although they are far less common. Spamhaus’s main lists illustrate the range. [1]

Sources [2][4][5][3]

How to check a sending IP or domain

If you query DNSBLs directly from your own systems, read the usage terms first. Spamhaus limits free use to non-commercial use by small and medium organizations at volumes consistent with that use. The network sending the query must be identifiable—your own resolver, or a public resolver that passes client-subnet information—and queries from large shared hosting are not accepted. Commercial users need a paid data service. A monitoring check whose queries are being refused is not a clean result. [6]

• Check every IP that actually hands your mail to receivers, plus the visible From domain, the return-path domain, and any domain that appears in links.
• Use the list operator’s own lookup first. Spamhaus’s IP and Domain Reputation Checker accepts IP addresses, domains, and email addresses and shows each listing with removal information.
• Treat multi-list lookup sites as a starting point, and confirm anything important with the operator that publishes the list.
• Keep dated results. A listing that appeared the day after a new segment launched tells you something a single snapshot cannot.

Sources [7]

What a listing does and does not tell you

A listing is evidence, not a verdict on your whole program. Spamhaus’s categories show the range: an XBL entry points to a compromised or misbehaving machine, a PBL entry reflects network policy, and an SBL or DBL entry points to spam or abuse associated with the IP or domain. The first two can affect a careful sender on shared or misconfigured infrastructure; the last two usually mean the operator has seen mail it considers spam. [5][2][4][3]

It also does not mean all mail stops. Receivers choose which lists to use and how much weight to give them. Do not read partial delivery as permission to continue, though: the behavior that produced a listing usually shows up in bounces, deferrals, and complaints as well.

For cold outreach, check the causes inside your control first: unverified or guessed addresses, volume that outran reputation, weak audience relevance, and messages recipients mark as spam.

Fix the cause, then use the operator’s removal process

Spamhaus says there is never a fee to remove any of its listings and that any offer to remove one for a fee is a scam. It also says deliverability consultants have no special privilege to influence or expedite SBL listings. Be skeptical of anyone selling guaranteed delisting. [8]

Where Spamhaus cannot process a removal immediately, its checker raises a ticket with the delisting team. Asking before the cause is fixed only wastes that step. [7]

• Pause the affected stream while you investigate.
• Read the listing reason and evidence from the operator, not from a third-party summary.
• Find the cause: a compromised host or credential, a misconfigured server, a bad list segment, excessive volume, or content and links that attract complaints.
• Fix it and document what changed—segments removed, credentials rotated, hosts cleaned, volume reduced.
• Request removal through the operator’s own process. For the Spamhaus SBL, the network provider responsible for the IP asks once the abuse has stopped; XBL and CSS removals go through the reputation checker.
• Resume slowly and watch bounces, deferrals, and complaints before returning to normal volume.

Sources [4][7]

Why rotating IPs or domains is the wrong fix

When a listing hits, the tempting move is to shift volume to a fresh IP or a newly registered look-alike domain. That keeps the audience, copy, and volume that caused the problem while hiding the sender from the signal. List operators watch for the pattern: Spamhaus names snowshoe configurations with poor or frequently changing identification among its SBL criteria, and rapid identity changes while delivering mail among the behaviors behind XBL listings. [4][5]

It can also break rules you agreed to. Actually Agentic’s terms, for example, prohibit using the service to evade blocks; check your own provider’s acceptable-use policy for the equivalent clause. A program that needs a new identity every few weeks has a targeting or consent problem, not an infrastructure problem. [9]

Separate sending domains are still reasonable for isolating message streams in advance. The difference is intent and transparency: separation limits blast radius before anything goes wrong, while rotation after a listing is an attempt to keep sending the same mail under a different name.

How Actually Agentic responds to a listing

Before launch, Actually Agentic checks sending IPs against its configured DNSBL zones. A listed IP puts the campaign on hold, opens a critical abuse case, and alerts an operator. Remediation is manual: the system does not attempt automatic delisting and does not route around a blocklist failure by switching to another IP or domain. [9]

Actually Agentic is prelaunch. Because commercial monitoring falls outside Spamhaus’s free-use terms, production monitoring needs a commercial DNSBL license rather than free queries. None of these gates guarantee inbox placement; they make it harder to keep sending into a known problem. [6]