Wiki / Reputation
Risk: IP address blocklist check
The IP address of your website or mail server is on at least one of the four Spamhaus lists that ZEN combines, so mail servers using ZEN can reject mail sent from it. The code decides the urgency: 127.0.0.10 or .11 (PBL) on an address that sends no mail changes nothing, the others need work today.
What it does not mean. The entry is about the IP address, not your domain: on shared hosting many customers share it. PBL is not a sign of infection or spam: Spamhaus writes that a PBL listing is not the result of anything the end user did, and that PBL should not be used to block access to web servers.
- In our report
- Risk (red). The website IP line weighs 2.0 of 2.0, the mail server IP line 0.8
- Time to fix
- An approved removal applies at once, in some systems within 24 hours. CSS expires 3 days after the last detection
- Can it break things
- Removal requested before the fix: the address is listed again
How to fix it
Read the code first: each means a different list and a different fix. Removal is free; Spamhaus calls any offer of paid removal a scam.
Which list (tested with dig 9.10.6)
dig +short 10.2.0.192.zen.spamhaus.org
dig +short TXT 10.2.0.192.zen.spamhaus.orgThe address is written backwards: 192.0.2.10 becomes 10.2.0.192. The first command returns the code, the second names the list and the page of the entry.
CSS, code 127.0.0.3: server name and reverse DNS
dig +short -x 8.8.8.8
dig +short dns.googleOn Google's address: the reverse record returns a name, the name returns the same address. Your mail server needs the same pair and must introduce itself (HELO) by that name: postconf myhostname (Postfix, tested on 3.2.2) or exim -bP primary_hostname (Exim, 4.97). Spamhaus also names hacked mailboxes and a CMS sending mail. In the cases we handled, the cause was a mailbox forwarding everything, spam included, to Gmail: turn that off.
XBL, code 127.0.0.4: hacked site or infected device
exim -bpcThe number of messages waiting in the Exim queue (tested on 4.97): thousands where there are normally a few means the server is sending mail that is not yours. Spamhaus singles out outdated WordPress, Joomla, Drupal and plugins. Clean up first: otherwise the address is listed again the next time it connects to Spamhaus systems.
Removal request
https://check.spamhaus.orgThe only place where CSS, XBL and PBL entries are removed. SBL removal can be requested only by the provider in charge of the address: write to them. PBL: for your own mail server on a static address with matching A and reverse records, ask for an exclusion (valid for one year); otherwise send through your provider's mail server, signing in on port 587 or 465.
How to check
The first query tests your resolver; in the second, replace 1.0.0.127 with your address written backwards.
dig +short 2.0.0.127.zen.spamhaus.org; dig +short 1.0.0.127.zen.spamhaus.orgExpected
127.0.0.2
127.0.0.10
127.0.0.4The three codes belong to the official test address 127.0.0.2; nothing should follow for your address. If the test address returns nothing either, you are asking through a public resolver: use check.spamhaus.org. We queried a Spamhaus name server directly (@a.gns.spamhaus.org).

What can break
- Removal without a fix: CSS lists the address again immediately while the problem is detected, XBL as soon as the address connects again. Self-removals are limited.
- A check through a public resolver misleads. On 18 November 2026 the test address
127.0.0.2returned127.255.255.254through 1.1.1.1 and “not listed” (NXDOMAIN) through 8.8.8.8. Spamhaus blocks open public resolvers and recommends your own DNS server.
Possible values
From the Spamhaus documentation (checked on 18 November 2026). One address can return several codes.
| Code | List | What it means |
|---|---|---|
127.0.0.2 | SBL | A source of spam or malicious content |
127.0.0.3 | CSS | An automatically detected sender of low-reputation mail |
127.0.0.4 | XBL | An address showing signs of compromise |
127.0.0.9 | SBL (DROP) | Returned in addition to 127.0.0.2 since 1 June 2016 |
127.0.0.10 | PBL | Address not meant to send mail directly; range entered by the provider |
127.0.0.11 | PBL | The same; range entered by Spamhaus |
127.255.255.252 | Error | Typing error in the list name. Not a listing |
127.255.255.254 | Error | Query came through a public resolver. Not a listing |
127.255.255.255 | Error | Excessive number of queries. Not a listing |
Sources
- Spamhaus: DNSBL usage FAQ (return codes, error codes, public resolvers)
- Spamhaus: ZEN blocklist
- Spamhaus: PBL FAQ
- Spamhaus: CSS blocklist
- Spamhaus: XBL FAQ
- Spamhaus: SBL blocklist
- RFC 5782: DNS blocklists (how the address is written, test entries)
Changes
- Page published; code table checked against the Spamhaus documentation, dig queries run the same day.
