Block anonymizer traffic to website completely?

If you running under Apache and can edit your .htaccess file you can add:

Order Allow,Deny
deny from 192.238.24.0/21
deny from 216.41.140.0/23
deny from 209.116.0.0/14
Allow from all

If you already have a section with the order statement just add the deny statements after other denies.

This should work for IPV4 numbers that they use. I don’t know if they use any other ranges.

I am working on version 6.00 of this plugin and the last range is blocked by the plugin, but I have not seen any spam from the first two CIDRS so they may just be corporate numbers. The last CIDR is a larger network called XO which is a known spam source.

Keith

Thanks so much for your quick reply, Keith! I’ll add the deny IP statements to my .htaccess file. Any idea when your 6.0 version will be available? I may just try to find out what XO ips are. Hope this will keep out anyone trying to browse anonymously!

6.0 is a huge rewrite. There are nearly 200 files and 1.3 megs of PHP code. (I use lazy class loading so it uses less memory than version 5, which used less memory than version 4.) I was preparing to make it a pay plugin and I have doubled the number of features. I am going to release it for beta when I get a stable version and then I’ll make a decision about releasing it on the WordPress repository. I would still like to keep it free, but I would not have time to support it fully – it is a problem.

I have been writing the plugin option pages – so far there are 11 pages of options. I have been working an hour or so a day for three weeks and I am not near the end.

I took out Red herring forms and honeypots to trap spammers because it conflicts with so many themes. I added tests for common exploits and cross browser scripts. I added a scan to the database looking for threats.

I added a block by country option with over a hundred countries. I added the ability to block some robots from the entire site, not just the comments and login. This blocks scrapers like WGET and badly behaved robots.

I added support for Google reCaptcha, OpenCaptcha and SolveMedia captcha on the second chance screen, and yanked my custom captcha.

Needless to say it is a mess. I have not tested enough of it and I will have to put it on a website for a week or so to see if it crashes. I no longer have a Networked Blog install so I’ll have to make one and see if I can attract spammers in order to test the network functions.

Keith