Latest Tweets7G Firewall (beta): perishablepress.com/7g-firewal…
Perishable Press

Protect Your Site with a Blackhole for Bad Bots

[ Black Hole (Vector) ] 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 honeypot 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.

Contents

Tip: For a shorter version of this tutorial, check out the Quick Start Guide »
WordPress user? Check out the free Blackhole plugin and Blackhole Pro »

Intro

[ Black Hole (Graphic) ] 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. So the percentage of false positives is extremely low to non-existent. It’s an ideal way to protect your site against bad bots silently, efficiently, and effectively.

With a few 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.

[ Blackhole for Bad Bots ] The Blackhole is built with PHP, and uses a bit of .htaccess to protect the blackhole directory. Refined over the years and completely revamped for this tutorial, the Blackhole consists of a plug-&-play /blackhole/ directory that contains the following three files:

  • .htaccess – protects the log file
  • blackhole.dat – log file
  • index.php – blackhole script

These three files work together to create the Blackhole for Bad Bots. If you are running WordPress, the Blackhole plugin is recommended instead of this standalone PHP version.

Note: By default, .htaccess files are hidden on Windows and OS X, so to view them you need to enable “Show hidden files” on your machine, or use any FTP or code-editing app that is capable of displaying them. It’s a common feature.

Overview

The Blackhole is developed to make implementation as easy as possible. Here is an overview of the steps:

  1. Upload the /blackhole/ directory to your site
  2. Edit the three variables in the “EDIT HERE” section in index.php.
  3. Ensure writable server permissions for the blackhole.dat file
  4. Add a single line to the top of your pages to include the index.php file
  5. Add a hidden link to the /blackhole/ directory in the footer
  6. Forbid crawling of /blackhole/ by adding a line to your robots.txt

So installation is straightforward, but there are many ways to customize functionality. For complete instructions, jump ahead to the installation steps. For now, I think a good way to understand how it works is to check out a demo..

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 set up as a sandbox, so when you trigger the trap, it blocks you only from the demo itself. Here’s how it works:

  1. First visit to the Blackhole demo loads the trap page, runs the whois lookup, and adds your IP address to the blacklist data file
  2. Once your IP is added to the blacklist, all future requests for the Blackhole demo will be denied access

So you get one chance (per IP address) to see how it works. Once you visit the demo, your IP address will be blocked from the demo only — you will still have full access to this tutorial (and everything else at Perishable Press). So with that in mind, here is the demo link (opens new tab):

Visit once to see the Blackhole trap, and then again to observe that you’ve been blocked. Again, even if you are blocked from the demo page, you will continue to have access to everything else here at Perishable Press.

Tip: You can visit the Blackhole Demo via any free proxy service if you want to try again and do another test.

How to Install

[ Black Hole (Physical) ] Here are complete instructions for implementing the PHP/standalone of Blackhole for Bad Bots. Note that these steps are written for Apache servers running PHP. The steps are the same for other PHP-enabled servers (e.g., Nginx, IIS), but you will need to replace the .htaccess file and rules with whatever works for particular server environment. Note: for a concise summary of these steps, check out this tutorial.

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 4.

Step 2: Edit the three variables in the “EDIT HERE” section in index.php.

Step 3: 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 4: Include the Blackhole script by adding the following line to the top of your pages (e.g., header.php):

<?php include(realpath(getenv('DOCUMENT_ROOT')) . '/blackhole/index.php'); ?>

The Blackhole script checks the bot’s IP address against the blacklist data file. If a match is found, the request is blocked with a customizable message. View the source code for more information.

Step 5: Add a hidden link to the /blackhole/ directory in the footer of your site’s web pages:

<a rel="nofollow" style="display:none;" href="https://example.com/blackhole/">Do NOT follow this link or you will be banned from the site!</a>

This is the hidden trigger link that bad bots will follow. It’s currently hidden with CSS, so 99.999% of visitors won’t ever see it. Alternately, to hide the link from users without relying on CSS, replace the anchor text with a transparent 1-pixel GIF image. For example:

<a rel="nofollow" style="display:none;" href="http://example.com/blackhole/" title="Do NOT follow this link or you will be banned from the site!"><img src="/images/1px.gif" alt="" /></a>

Remember to edit the link href value and the image src to match the correct locations on your server.

Step 6: 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.” So it is important to get your robots rules correct.

Step 7: Done! Remember to test thoroughly before going live. Also check out the section on customizing for more ideas.

Testing

[ Black Hole (Figurative) ] You can verify that the script is working by visiting the hidden trigger link (added in step 5). That should take you to the Blackhole warning page for your first visit, and then block you from further access on subsequent visits. To verify that you’ve been blocked entirely, try visiting any other page on your site. To restore site access at any time, you can clear the contents of the blackhole.dat log file.

Important: Make sure that all of the rules in your robots.txt file are correct and have proper syntax. For example, you can use the free robots.txt validator in Google Webmaster Tools (requires Google account).

Tip: To reset the list of blocked bots at any time, simply clear the contents of the blackhole.dat file.

Customize

The previous steps will get the Blackhole set up with default configuration, but there are some details that you may want to customize:

  • index.php (lines 25–27): Edit the three email variables
  • index.php (line 107): Check/replace path to your contact form
  • index.php (lines 130–152): Customize markup of the warning page
  • index.php (line 167): Customize the list of whitelisted bots

These are the recommended changes, but the PHP is clean and generates valid HTML, so feel free to modify the markup or anything else as needed.

Troubleshoot

If you get an error letting you know that a file cannot be found, it could be an issue with how the script specifies the absolute path, using getenv('DOCUMENT_ROOT'). That function works on a majority of servers, but if it fails on your server for whatever reason, you can simply replace it with the actual path. From Step 4, the include script looks like this:

<?php include(realpath(getenv('DOCUMENT_ROOT')) . '/blackhole/index.php'); ?>

So if you are getting not-found or similar errors, try this instead:

/var/www/httpdocs/blackhole/index.php

So that would be the actual absolute path to the blackhole index.php file on your server. As long as you get the path correct, it’s gonna fix any “file can’t be found” type errors you may be experiencing.

If in doubt about the actual full absolute path, consult your web host or use a PHP function or constant such as __DIR__ to obtain the correct infos. And check out my tutorial over at WP-Mix for more information about including files with PHP and WordPress.

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.

By default, the Blackhole DOES NOT BLOCK any of the big search engines. So Google, Bing, and company always will be allowed access to your site, even if they disobey your robots.txt rules. See the next section for more details.

Whitelist Good Bots

In order to ensure that all of the major search engines always have access to your site, Blackhole whitelists the following bots:

  • AOL.com
  • Baidu
  • Bing/MSN
  • DuckDuckGo
  • Google
  • Teoma
  • Yahoo!
  • Yandex

Additionally, popular social media services are whitelisted, as well as some other known “good” bots. To whitelist these bots, the Blackhole script uses regular expressions to ensure that all possible name variations are allowed access. For each request made to your site, Blackhole checks the User Agent and always allows anything that contains any of the following strings:

a6-indexer, adsbot-google, ahrefsbot, aolbuild, apis-google, baidu, bingbot, bingpreview, butterfly, cloudflare, duckduckgo, embedly, facebookexternalhit, facebot, googlebot, ia_archiver, linkedinbot, mediapartners-google, msnbot, netcraftsurvey, outbrain, pinterest, quora, rogerbot, showyoubot, slackbot, slurp, sogou, teoma, tweetmemebot, twitterbot, urlresolver, vkshare, w3c_validator, wordpress, wprocketbot, yandex

So any bot that reports a user agent that contains any of these strings will NOT be blocked and always will have full access to your site. To customize the list of whitelisted bots, open index.php and locate the function blackhole_whitelist(), where you will find the list of allowed bots.

The upside of 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 your decision where to draw the line.

With PHP, it is possible to verify the true identity of each bot, but 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 and other major web services.

Tip: Check out CLI Forward-Reverse Lookup for how to verify bot identity.

License & Disclaimer

Terms of Use: Blackhole for Bad Bots is released under GNU General Public License. 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.

Questions & Feedback

Questions? Comments? Send ’em via my contact form. Thanks!

Download

Here you can download the latest version of Blackhole for Bad Bots. By downloading, you agree to the terms.

Standalone PHP version, last updated: 2019/03/26
Blackhole for Bad Bots – Version 4.2 (4KB zip)
Note: if you have trouble “unzipping” the file, try downloading the file again using the Iridium browser.

Jeff Starr
About the Author Jeff Starr = Designer. Developer. Producer. Writer. Editor. Etc.
Archives
184 responses
  1. Mark, in his info he says you will only be banned from the blackhole demo page on this site. After you visit that page twice, it should show you as banned from there, but you can still visit this page – otherwise you wouldn’t be able to get any further help here.

    What type of site are you putting it on? Did you add the call for blackhole.php to your pages? If you’re using a script that uses a template, you may need to add it to the template. That’s what I had to do.

  2. Kate, the demo you are talking about is the Blackhole Demo, not the /blackhole/.

    yes I added the call on the pages. I tried it on two different hostings and on static html on WP and articlems sites.

    On the WP site in the end I even parroted this very one, that’s how I got to test THIS blackhole that doesn’t seem to ban me. Not sure what I am doing, lol. anyway it doesn’t matter… I have a system nowadays that doesn’t even require my own hosting to make a few pennies so I don’t care about anything.

  3. Btw about the suspension of this account, they will suspend all sites because they just don’t care about you, I have had that happen on all sorts of hosting packages over the years, what you want to do is develop a way to use FREE hostings like blogspot, wordpress etc etc using ONLY your domain and nothing else (hint hint)

  4. Somebody put my site on a “hack this site” forum. For months I have been inundated with bots attacking my guestbook all day every day – I mean like every minute of the day. I am using the Lazarus Guestbook where “spamming is futile”. I also have a security program that prevents spamming in other areas of the site. They have never been able to hack the site or get any spam through, but I still find it stressing just reviewing my logs and looking at all their failed attempts. Also, they are using up my bandwidth.

    Last night I installed the blackhole trap in two places on my site. The first one I put in the blackhole folder.

    Next, I renamed my Guestbook directory to something else and added it to the robots exclusion. Then I created a new folder with the old Guestbook directory name and put the blackhole script in it.

    The spamers visiting the old guestbook folder are being trapped and blocked. Today is the first day in a long time where there are zero log entries for spamming the guestbook.

    Thanks! I only wish I had found it sooner.

  5. I took a look at the PHP files. In the blackhole.php, unless I am missing something, wouldn’t it make more sense to check the whitelisted user agents against the current $_SERVER[‘HTTP_USER_AGENT’] rather than opening and scanning the .dat file?

    Also, I would suggest breaking out of the while loop as soon as a match is found. No sense in reading the rest of the file.

    Any recommendations on applying this solution to a static site? I maintain a 500 page static site. I really don’t want to change them all to php and adding a directive to the .htaccess file to process all html files as php does not work with this host.

    The only way I can see is to add the IP addresses directly to the .htaccess file. But it’s a little scary to have a script editing .htacess on the fly.

  6. @ Jennifer. User agents can be spoofed very easily which is why we’re banning based on the bots behaviour.

    Not sure what to do for your static site. I wouldn’t have a script editing the htaccess file. You could maybe cron it to only update htaccess once a day/week.

  7. The script adds the IP address to the ban list based on them visiting the forbidden page. But then when checking the ban list, the script ignores any entry that matches a whitelisted user agent. There is no additional checking that I can see. So why bother checking the ban list at all for those with a whitelisted user agent?

    The only benefit this could possibly have (vs checking the user agent directly) is if this time the bot is using a whitelisted user agent, but last time it didn’t. That seems unlikely.

    I know it would be resource heavy to do reverse lookup as part of blackhole.php. But what about doing a reverse lookup as part of index.php? If the user agent is a whitelisted one, then do a reverse lookup. If the reverse lookup confirms the user agent, then don’t add it to the ban list. You could still send the email out for information.

    Then blackhole.php wouldn’t look at the user agent at all. If it’s on the ban list, block it.

  8. Jeff thx for the amazing tool.

    Can we allow a bot which has previously been blocked. I looking at this from a testing perspective to test from my computer and once I am blocked, I simply remove the block to let me through.

    Regards,
    Vinny

  9. I don’t know why, but sometimes I get an email telling I’ve been banned from my own site. I need to edit the .dat file then. Maybe it’s related to some kind of prefetching, so I suddendly removed any mention to the blackhole from my browsing history. I hope this will stop to do nasty things. :)

  10. screenmates January 9, 2011 @ 7:02 pm

    How about storing the previous value in session:

    if (isset($_SESSION[‘bh’]) && $_SESSION[‘bh’])
    $badbot = 1;
    else
    {
    $badbot = 0;



    }

    HTML goes here…

  11. screenmates January 9, 2011 @ 8:39 pm

    John S. Britsios: You suggested that placing a robots meta tag nofollow,noindex,noarchive in the index.php. But if the bot already made it to the index.php to read the meta tag directive, the bot is already in the blackhole folder and hence banned by then?

  12. I think he suggested to use an auxiliary page to check against instead of the index.php. :)
    BTW LOL my blackhole keeps blocking the BingBot. :D

[ Comments are closed for this post ]