How blocklists work

Most public blocklists are published through DNS, which is why they are often called DNSBLs. RFC 5782 describes the mechanism. To check whether the connecting IP 192.0.2.99 is listed on a zone such as zen.spamhaus.org, the receiving server reverses the octets and looks up 99.2.0.192.zen.spamhaus.org. If the name does not exist, the IP is not listed. If it returns an A record in the 127.0.0.x range, the IP is listed, and a TXT record usually explains why.

The return code tells the receiver which list matched. On Spamhaus zones, for example, 127.0.0.2 indicates the SBL (known spam sources), 127.0.0.4 the XBL (compromised or infected hosts), and 127.0.0.10 or 127.0.0.11 the PBL (IP ranges that should not send mail directly to the internet). Domain blocklists such as the Spamhaus DBL work the same way but check domain names found in the envelope, headers, and links in the message body.

When a receiving server rejects mail based on a listing, the sender sees an SMTP error during the conversation. The exact text varies by server, but it often looks like this:

554 5.7.1 Service unavailable; Client host [192.0.2.99] blocked using zen.spamhaus.org

One practical detail: Spamhaus does not answer free queries made through large public DNS resolvers, and returns the error code 127.255.255.254 instead. A self-check run through a public resolver can therefore give a misleading result. Use the operator’s own lookup page.

How something gets blocklisted

Common triggers include:

  • Spam trap hits, especially pristine traps and honeypots that show a list was purchased or scraped (see what is a spam trap).
  • Compromised infrastructure, such as a hacked mailbox, a vulnerable web form, or malware sending through your IP.
  • High complaint rates from recipients marking mail as spam.
  • Sudden volume spikes from an IP or domain with little sending history.
  • Policy listings, such as dynamic or residential IP space on the PBL, which signal that the IP should relay through a proper mail server rather than indicating abuse.

Blocklists aren’t one single list

There are many independent operators, each with its own criteria, data, and removal process. Spamhaus (SBL, XBL, PBL, and DBL, combined in the ZEN zone), Barracuda, and SpamCop are widely used. Mailbox providers such as Gmail and Microsoft also maintain internal filtering data that is not published. Lists also come and go: SORBS, once a common choice, shut down in 2024, so checks against it no longer mean anything. Because different receivers consult different lists, the same message can be rejected by one provider and delivered normally by another.

Why it matters

A listing on a widely used list can stop delivery to a large share of business and consumer mailboxes at once, and the effect is immediate. Blocked campaigns mean lost revenue, missed password resets, and unanswered sales outreach. A listing also signals deeper problems: a bad list source, a compromised account, or rising complaints that will keep damaging sender reputation after delisting if left unaddressed.

What to do if you are listed

  1. Identify exactly what is listed. Confirm whether it is your IP, your sending domain, or a domain in your links, and which zone matched.
  2. Read the listing reason on the operator’s lookup page.
  3. Fix the root cause. Secure compromised accounts, pause the list segment that hit traps, and remove addresses from suspect sources.
  4. Request removal through the operator’s own process, and only after the fix is in place. Repeat listings are typically harder to clear.
  5. Keep monitoring so a new listing is caught within hours rather than discovered through a drop in results weeks later.

Where RocketVerifier helps

Deliverability monitoring checks your sending domains and IPs against major blocklists and alerts you to new listings, alongside SPF, DKIM, and DMARC monitors. Bulk email verification removes invalid addresses and trap risks that often cause listings in the first place. When a receiving server rejects a verification check because of a policy or blocklist rule, RocketVerifier reports the result as unknown with a blocked sub_status rather than calling the address undeliverable, and unknown results are never charged.