Checking IP addresses using SpamCannibal

NO WARRANTY OR LIABILITY: BY USING THE DNSBL, IT'S DATA, OR ANY INFORMATION CONTAINED ON THE SPAMCANNIBAL WEBSITE, YOU ACKNOWLEDGE AND AGREE THAT THE DNSBL AND IT'S DATA ARE PROVIDED "AS IS", SPAMCANNIBAL DOES NOT GUARANTEE THE EFFECTIVENESS OR RESULTS OF THE DNSBL, IT'S DATA, OR ANY OTHER SERVICE OR PRODUCT PROVIDED BY SPAMCANNIBAL, AND ANY AND ALL WARRANTIES, IMPLIED OR OTHERWISE, ARE EXPRESSLY EXCLUDED. IN NO EVENT SHALL SPAMCANNIBAL, OR ITS OWNERS, OPERATORS, PARENT, SUBSIDIARIES OR LICENSORS, BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND ARISING OUT OF OR IN CONNECTION WITH YOUR USE OF THE DNSBL, IT'S DATA, OR THE SPAMCANNIBAL WEBSITE, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY.

You can send a DNS query to bl.spamcannibal.org to check if an address is in the SpamCannibal database. Addresses that are found in the database will return a DNS "A" response of 127.0.0.2. If the address is not found, the query will return a status of NXDOMAIN.

EXAMPLE: 127.0.0.2 is always in the SpamCannibal database

~# dig 2.0.0.127.bl.spamcannibal.org

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36623
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;2.0.0.127.bl.spamcannibal.org. IN      A

;; ANSWER SECTION:
2.0.0.127.bl.spamcannibal.org. 43013 IN A       127.0.0.2

;; AUTHORITY SECTION:
bl.spamcannibal.org.    43030   IN      NS      bl.spamcannibal.org.

EXAMPLE: 127.0.0.255 is not in the database.

~# dig 255.0.0.127.bl.spamcannibal.org

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26187
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;255.0.0.127.bl.spamcannibal.org. IN    A

;; AUTHORITY SECTION:
bl.spamcannibal.org.    0       IN      SOA     bl.spamcannibal.org.
sysadm.spamcannibal.org. 1154806689 43200 900 172800 43200

The DNBSBL's used by our mail system are listed HERE

We suggest that you use Net::DNSBL::MultiDaemon to optimize DNSBL lookup and reduce the load on the DNSBL providers you use.