November 27, 2014
There has been a continuous DDOS attack against the CBL for the past
few days attempting to game the removal system.
As a consequence, we have had to implement a CAPTCHA system on CBL lookups.
We deeply regret having to do this after 11 years of not needing CAPTCHA,
but the spambot operators make it necessary.
This also prevents the lookup page from working UNLESS you use it manually.
If you have any sort of automated, scripted, or plug-in'd CBL queries, turn it
off NOW. This has always been prohibited, we will be more aggressive in stomping
June 14, 2014
Online Gameover Zeus Detector
June 2, 2014
SpamHaus/the CBL is assisting the US Department of Justice (DOJ),
Federal Bureau of Investigation (FBI),
numerous other international law enforcement agencies and many private security
organizations around the world in an operation to disrupt and mitigate
the Gameover Zeus (GOZ) and Cryptolocker botnets.
This is not expected, by itself, to destroy these botnets. But it
will disrupt it, and give more chance to eradicate individual
infections during the time they've been rendered relatively harmless.
This is the
US Department of Justice Announcement and
FBI Press Release.
A similar alert has been published by the
UK National Crime Agency (NCA).
The most important/up-to-date mitigation information is published
I'm listed, what do I do?
The CBL has easy self-removal. See:
CBL Lookup AND Removal
It will provide you with information on why the IP was listed, how
to correct the problem that caused the listing, and
a link to do self-removal.
The rest of these web pages are intended to help you understand
what could cause a listing, and how to diagnose/remediate the problem.
The CBL expects you to resolve the problem, preferably before you
do a delisting.
If you simply delist without resolving the problem, it will almost
certainly list again.
Of late a lot of people are emailing us and asking us to delist
an IP address.
We can't do it more quickly than you can.
It's a LOT faster if you do it yourself.
What is the CBL?
The CBL takes its source data from very large mail
server (SMTP) installations.
Some of these are pure spamtrap servers, and some are not.
The CBL only lists IPs exhibiting characteristics which
are specific to open proxies of various sorts (HTTP, socks, AnalogX,
wingate, Bagle call-back proxies etc) and dedicated Spam BOTs
(such as Cutwail, Rustock, Lethic etc) which
have been abused to send spam, worms/viruses that do their own direct
mail transmission, or some types of trojan-horse or "stealth"
spamware, dictionary mail harvesters etc.
The CBL does not list based upon the volume
of email from a given IP address.
The CBL also lists certain portions of botnet infrastructure, such
as Spam BOT/virus infector download web sites, botnet infected machines,
machines participating in DDOS, and other web sites or name servers
primarily dedicated to the use of botnets.
Considerable care is taken to avoid listing IP addresses that are shared
or are likely to be shared with legitimate use, except in the
case of infector download websites, phish emission or DDOS.
Our botnet detections may not necessarily directly involve the
observation of spam emission, but most botnets are at least occasionally
involved in email spam, in addition to infostealing, DDOS attacks etc.
In other words, the CBL only lists IPs that have attempted email
connections to one of our servers in such a way as to indicate that
the sending IP is infected with a spam-sending virus or worm, acting
as a open proxy for the sending of spam, OR, IPs primarily used in
the operation of botnets
The CBL does NO probes. In other words, the CBL
NEVER makes connections to other machines to "test" anything.
The CBL does NOT test for nor list open SMTP relays.
The CBL only lists individual IPs, it NEVER lists ranges.
The CBL does NOT care whether an IP is dynamic or not,
if connections the IP makes indicate that it's infected, it is
The CBL does NOT attempt to associate IP addresses to
persons or organizations, and furthermore, a CBL listing
should NOT be construed as accusing anyone of spamming -
virtually all listees are the victims of a virus or other compromise, not
The CBL does NOT accept external submissions for listing.
Hence it is not possible for the CBL to be used as an instrument of
revenge (eg: "disgruntled ex-employee" or "competitor").
The CBL operates in an entirely automated way designed to avoid
listings due to bounces of forged spam, virus
bounces, and "real" mail servers emitting the occasional spam.
However, in some circumstances severe mail server misconfiguration
can make it look as if a mail server is infected.
It does not attempt to list every possible spam source.
This list is based on information believed to be reliable. No
warranty is made that it is accurate or complete.... Use entirely at
your own risk.
There is no supporting data or "evidence" file available for any given
listing, and no mechanism to ask why any given listing took place. To
counteract this, there is an automated no-questions-asked removals
procedure allowing any affected party to delist a specific IP address
rapidly. However, delisted IPs are relisted if new evidence of spam
activity is subsequently detected.
Entries automatically expire after a period of time. The approximate
detection time of a specific entry can be obtained from the web
What to do if you're listed/How do I get delisted?
Use the lookup tool it will
often give you further detail.
It gives the link to the delisting tool.
See the FAQ for more information on
how to identify and resolve a CBL listing.
How to use the CBL
Before using the CBL, you should read our
terms and conditions.
The CBL can be queried in the usual way for DNS-based blocking lists,
under the name cbl.abuseat.org.
Entries in the CBL are returned with an IP address (always 127.0.0.2) and
a TXT record containing a link to the lookup/removal pages.
If you wish to run a local server using the CBL data you can download
the CBL zone. Please see our FAQ under the
subject "How do I download the CBL as a list of IPs?"
We're getting a lot of reports of spurious blocking caused by sites using
the CBL to block authenticated access to smarthosts / outgoing mail servers.
THE CBL is only designed to be used on INCOMING mail, i.e. on the
hosts that your MX records point to.
If you use the same hosts for incoming mail and smarthosting, then you
should always ensure that you exempt authenticated clients from CBL checks,
just as you would for dynamic/dialup blocklists.
Another way of putting this is: "Do not use the CBL to block your
The CBL and http://cbl.abuseat.org web pages are copyright ©
2003-2013, all unauthorized copying is prohibited