One of my favorite security measures here at Perishable Press is the site’s virtual Blackhole trap for bad bots. The concept is simple: include a hidden link to a robots.txt-forbidden directory somewhere on your pages. Bots that ignore or disobey your robots rules will crawl the link and fall into the trap, which then performs a WHOIS Lookup and records the event in the blackhole data file. Once added to the blacklist data file, bad bots immediately are denied access to your site. I call it the “one-strike” rule: bots have one chance to follow the robots.txt protocol, check the site’s robots.txt file, and obey its directives. Failure to comply results in immediate banishment. The best part is that the Blackhole only affects bad bots: normal users never see the hidden link, and good bots obey the robots rules in the first place.
In five easy steps, you can set up your own Blackhole to trap bad bots and protect your site from evil scripts, bandwidth thieves, content scrapers, spammers, and other malicious behavior.
The Blackhole is built with PHP, and uses a bit of .htaccess to protect the blackhole directory. The blackhole script combines heavily modified versions of the Kloth.net script (for the bot trap) and the Network Query Tool (for the whois lookups) (404 link removed 2012/07/08). Refined over the years and completely revamped for this tutorial, the Blackhole consists of a single plug-&-play directory that contains the following four files:
.htaccess– basic directory protectionblackhole.dat– server-writable log file (serves as the blacklist)blackhole.php– checks requests against blacklist and blocks bad botsindex.php– generates blackhole page, performs whois lookup, sends email, and logs data
These four files are all contained in a single directory named “blackhole”.
Installation Overview
I set things up to make implementation as easy as possible. Here are the five basic steps:
- Upload the
/blackhole/directory to your site - Ensure writable server permissions for the
blackhole.datfile - Add a single line to the top of your pages to include the
blackhole.phpfile - Add a hidden link to the
/blackhole/directory in the footer of your pages - Prohibit crawling of the
/blackhole/by adding a line to yourrobots.txtfile
It’s that easy to install on your own site, but there are many ways to customize functionality. For complete instructions, jump ahead to Implementation and Configuration. For now, I think a good way to understand how it works is to check out a demo..
One-time Live Demo
I have set up a working demo of the Blackhole for this tutorial. It works exactly like the download version, but it’s configured to block you only from the demo, not from the entire site. Here’s how it works:
- First visit to the Blackhole demo loads the trap page, runs the whois lookup, and adds your IP address to the blacklist data file
- Once you’re added to the blacklist, all subsequent requests for the Blackhole demo will be denied access
So you get one chance to see how it works. Once you visit, your IP will be blocked from the demo only – you will still have full access to this tutorial (and everything else). That said, here is the demo link: Blackhole Demo. Visit once to see the Blackhole trap, and then again to observe that you’ve been blocked. If I were to include the blackhole.php in the header of my theme files, you would be banned from pretty much the entire site.
Implementation and Configuration
Here are complete instructions for implementing and configuring the Perishable Press Blackhole:
Step 1: Download the Blackhole zip file, unzip and upload to your site’s root directory. This location is not required, but it enables everything to work out of the box. To use a different location, edit the include path in Step 3.
Step 2: Change file permissions for blackhole.dat to make it writable by the server. The permission settings may vary depending on server configuration. If you are unsure about this, ask your host. Note that the blackhole script needs to be able to read, write, and execute the blackhole.dat file.
Step 3: Include the bot-check script by adding the following line to the top of your pages:
<?php include($_SERVER['DOCUMENT_ROOT'] . "/blackhole/blackhole.php"); ?>
The blackhole.php script checks the request IP against the blacklist data file. If a match is found, the request is blocked with a customizable message. See the source code for more information.
Step 4: Include a hidden link to the /blackhole/ directory in the footer of your pages:
<a style="display:none;" href="http://example.com/blackhole/" rel="nofollow">Do NOT follow this link or you will be banned from the site!</a>
This is the hidden link that bad bots will follow. It’s currently hidden with CSS, so 99% of visitors won’t ever see it. To hide the link from users without CSS, replace the anchor text with a transparent 1-pixel GIF image.
Step 5: Finally, add a Disallow directive to your site’s robots.txt file:
User-agent: *
Disallow: /*/blackhole/*
This step is pretty important. Without the proper robots directives, all bots would fall into the Blackhole because they wouldn’t know any better. If a bot wants to crawl your site, it must obey the rules! The robots rule that we are using basically says, “All bots DO NOT visit the /blackhole/ directory or anything inside of it.” More on this in the next section..
Further customization: The previous five steps will get the Blackhole working, but the index.php requires a few modifications. Open the index.php file and make the following changes:
- Line #54: Edit the path to your site’s
robots.txtfile - Line #56: Edit the path to your contact page (or email address)
- Lines #140/141: Edit email address with your own
- And in
blackhole.php, edit line #53 with your contact info
These are the recommended changes, but the PHP is clean and generates valid HTML5, so feel free to modify the source code as needed. Note that beyond these three items, no other edits need made.
Caveat Emptor
Blocking bots is serious business. Good bots obey robots.txt rules, but there may be potentially useful bots that do not. Yahoo is the perfect example: it’s a valid search engine that sends some traffic, but sadly the Yahoo Slurp bot is too stupid to follow the rules. Since setting up the Blackhole several years ago, I’ve seen Slurp disobey robots rules hundreds of times. Bottom line: the Blackhole will block any bot that disobeys the Update: By default, the Blackhole no longer blocks any of the popular search engines. See the next section for more information.robots.txt directives. Proceed accordingly.
Whitelisting Search Bots
Initially, the Blackhole blocked any bot that disobeyed the robots.txt directives. Unfortunately, as discussed in the comments, Googlebot, Yahoo, and other major search bots do not always obey robots rules. And while blocking Yahoo! Slurp is debatable, blocking Google, MSN/Bing, et al would just be dumb. Thus, the Blackhole now “whitelists” any user agent identifying as any of the following:
- googlebot (Google)
- msnbot (MSN/Bing)
- yandex (Yandex)
- teoma (Ask)
- slurp (Yahoo)
Whitelisting these user agents ensures that anything claiming to be a major search engine is allowed open access. The downside is that user-agent strings are easily spoofed, so a bad bot could crawl along and say, “hey look, I’m teh Googlebot!” and the whitelist would grant access. It is possible to verify the true identity of each bot, but as X3M explains in the comments, doing so consumes significant resources and could overload the server. Avoiding that scenario, the Blackhole errs on the side of caution: it’s better to allow a few spoofs than to block any of the major search engines.
License and Disclaimer
The Perishable Press Blackhole is released under GNU General Public License. Check the Creative Commons for a summary and/or see the Blackhole source code for additional information. Also note that by downloading the Blackhole, you agree to accept full responsibility for its use. In no way shall the author be held accountable for anything that happens after the file has been downloaded.
Blackhole Download
Here you can download the current version of the Blackhole:
Blackhole - version 1.2 - 8KB ZIP
178 Responses
Alex Chudnovsky – January 13, 2011
Hi,
We run Majestic-12 Distributed Search engine project and our attention was brought to our alleged bot’s bad behavior – we were directed to this tool.
Our quick investigation has shown that the root of the problem is non-standard robots.txt that is recommended on this page, please read quote from the standard:
“Note the ‘*’ is a special token, meaning “any other User-agent”; you cannot use wildcard patterns or regular expressions in either User-agent or Disallow lines. Two common errors: Wildcards are _not_ supported: instead of ‘Disallow: /tmp/*’ just say ‘Disallow: /tmp/’.”
Source: http://www.robotstxt.org/faq/robotstxt.html
This is the error that will wrongly catch our bot and others who perfectly well comply with standard robots.txt.
Please change robots.txt to be:
Disallow: /blackholeThere is NO need to add * or / at the end of URL as prefix matching is used – this is a simple change that will give fair chance to bot and you won’t be banning Yahoo for no reason – white list is not a solution, support standards is.
I am aware that Google and some other bots support non-standard extensions, however if you just plan to allow white listed bots then there is no need to create this trap that any standard complaint bot will fall into.
Best regards,
Alex Chudnovsky
Managing Director
Email :
alexc@majestic12.co.ukWeb :
http://www.majestic12.co.ukMajestic-12 Ltd
Faraday Wharf, Holt Street
Aston Science Park, Birmingham
B7 4BB
Barbara – January 16, 2011
I have followed all the steps above, and I get the trap page, the Whois works, and it logs to the .dat file. I have the include in the header of my site – but I am not getting banned from the site.
Any idea where I need to look to try and make this work?
Barbara – January 16, 2011
Nevermind, I found it. I also had to use the filename path the way Lazza suggested in #105 to get it to ban me. Thanks for that!
Lazza – January 16, 2011
I’m glad you solved it. :)
@ Jeff, will you consider updating the path thing and the robots.txt one? IMHO those two fixes will lead to less hassle for simple users. ;)
Jenny – January 18, 2011
@Jeff, thanks for the great tool !
I arrived the final step- Which index.php to edit?
I have a nearly empty index.php in root, another empty index.php in wp-content/ , the next is the index.php in my theme’s directory. Which one?
Thanks!
Jenny – January 18, 2011
Nevermind, I sorted it out, it’s blackhole/index.php
Jenny – January 18, 2011
@Jeff,
I got it set up and running. However, the .dat file wasn’t writable till I changed it to 777. So, now, the whole world can edit it?
Another question- From reading above comments, it seems Whois-look-up is resource comsuming. So, why not just ban them without the whois process?
Kate – January 18, 2011
Jenny, maybe it’s the type of server you are on. Setting permissions at 666 works fine for me.
Lazza – January 19, 2011
@ Jenny, you can disable it by deleting the piece of code in the script. By the way since my hosting has troubles with whois but supports remote file opening, I edited the script to “rip” the whois data from an external website (you know those free dns/whois services online). :P
Isiah – February 12, 2011
For some reason I can’t seem to ban myself!!
I’m getting a 500 internal server error each time I type http://my domain]/blackhole/index.php into the addresss bar of a browser to test it all out.
Matt – February 18, 2011
Question – when you have caching enabled (WP Super Cache for me), it can cache the rejected page. How would you avoid that happening?
Ken – February 21, 2011
Problem with phpBB2
I’m trying to use blackhole with Extreme-Styles Mod which allows includes to be used inside TPL templates.
In
overall_header.tplI can include a
/blackhole/test.txtfile.I can not include
/blackhole/blackhole.phpAny thoughts greatly appreciated.
PS
I have blackhole installed on 90 dynamic storefronts with no issues.
Thanks for a great script!