|May the source be with you, but remember the KISS principle ;-)|
|Contents||Bulletin||Scripting in shell and Perl||Network troubleshooting||History||Humor|
|News||Perl HTTP Logs Processing Scripts||.htaccess file||AWStats||Apache Webserver||HTTP Return Codes||mod rewrite|
|Requests for non-existing web pages||Referrer Spam||PHP probes||Requests for crossdomain.xml and other XML files||Mystery GET requests with URI scheme encoded PNG image in them||Lower case requests||Trailing junk in requests|
|Bangers||Bots that cause consistent 500 errors||Broken or undebugged robots||Requests for crossdomain.xml and other XML files||Frivolous POSTs||Non-PHP Web probes|
|Probes from bc.googleusercontent.com||Fighting rogue robots||Bots that couse consistent 500 errors||Large Sample of "Composition URL" fake hits|
|HTTP Protocol||Apache authentication and authorization using LDAP||Cheap Web hosting with SSH access||Web site monitoring||Sysadmin Horror Stories||Web Humor||Etc|
The number of bots accessing popular websites exceed the number of real users by wide margin. For example in one week Softpanorama site was accessed from 14735 unique addresses. Less then 5K of them can be classified as "real users" ( users that actually read at least one page on the site). That means that bots represent 66% of all IP addresses that accessed the site.
Only around 200 of those bots read robots.txt file. So all other robots can be viewed as rogue. In other words rogue robots dominate the Web. IP the fires GET request non-stop (50 more more request per minute) and does not read robots.txt should be classified as rogue robot too.
Most robots "uncritically" use URLs from the pages they scan and it looks like a lot of their source URLs are "poisoned". That include Google and Microsoft robots. What is worse is that some crazy URL that robot gets is used again and again -- looks like they have no mechanism to decrease validity of pages that contain many broken URLs. So much about Google intelligence and quality of Google programmers. Judging form actual behaviour they just don't care.
But truth be told behavior of all robots has elements of suspicious behavior.
One important method of distinguishing whether the robot is "crazy"/undebugged or outright evil is to check whether it obeys robots.txt file. You can include a couple of "test" directory for particular robot and observe results. Also you can (and should) include all old (now non-existent) directories and see which robots still attempt to access files in them.
The robots.txt patterns are matched by simple substring comparisons, so care should be taken to make sure that patterns matching directories have the final '/' character appended, otherwise all files with names starting with that substring will match, rather than just those in the directory intended.For example:
User-agent: * Disallow: /cgi-bin/ Disallow: /images/ Disallow: /tmp/ Disallow: /private/
The Robot Exclusion Standard does not mention anything about the "*" character in the
Disallow: statement. Some crawlers like Googlebot and Slurp recognize strings containing
"*", while MSNbot and Teoma interpret it in different way.
If robot does not obey robots.txt or is producing way too many 404 using non-existent URLs it should be hunted and killed ;-).
For example here is definitely evil robot :-)
184.108.40.206 - - [24/Aug/2012:03:51:00 -0700] "GET /Net/telnet.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 220.127.116.11 - - [24/Aug/2012:03:52:15 -0700] "GET /Algorithms/index.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 18.104.22.168 - - [24/Aug/2012:03:54:14 -0700] "GET /Bulletin/archive.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 22.214.171.124 - - [24/Aug/2012:03:54:14 -0700] "GET /Scripting/perl.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 126.96.36.199 - - [24/Aug/2012:03:54:21 -0700] "GET /Freenix/linux.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 188.8.131.52 - - [24/Aug/2012:03:55:22 -0700] "GET /Solaris/Whitepaper/index.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 184.108.40.206 - - [24/Aug/2012:04:01:39 -0700] "GET /Antivirus/Spyware/index.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 220.127.116.11 - - [24/Aug/2012:04:21:30 -0700] "GET /Skeptics/cs_skeptic.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 18.104.22.168 - - [24/Aug/2012:04:23:16 -0700] "GET /WWW/index.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 22.214.171.124 - - [24/Aug/2012:04:24:17 -0700] "GET /Bookshelf/xml.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 126.96.36.199 - - [24/Aug/2012:04:25:00 -0700] "GET /Social/overload.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)" 188.8.131.52 - - [24/Aug/2012:04:25:24 -0700] "GET /Admin/index.shtml%0D HTTP/1.0" 404 12973 "-" "Wget/1.12 (linux-gnu)"Very similar to "crazy robots" are "obnoxious copiers" who overload the site by trying to mirror all the content. Sometimes several times a day. For example:
Bug#699133 wget When issuing the following exact command wget -m http--www.softpanorama.org- I get wget malloc() smallb
Technical measures to stop bots
The administrator of a website can use various measures to stop or slow a bot. Some techniques include:
- Blocking an IP address. This will also block all browsing from that address.
- Disabling any web service API that the website's system might expose.
- Bots sometimes declare who they are (using user agent strings) and can be blocked on that basis (using robots.txt); 'googlebot' is an example. Some bots make no distinction between themselves and a human browser.
- Bots can be blocked by excess traffic monitoring.
- Bots can sometimes be blocked with tools to verify that it is a real person accessing the site, like a CAPTCHA. Bots are sometimes coded to explicitly break specific Captcha patterns.
- Commercial anti-bot services: Companies offer anti-bot and anti-scraping services for websites. A few web application firewalls have limited bot detection capabilities as well.
- Locating bots with a honeypot or other method to identify the IP addresses of automated crawlers.
- Using CSS sprites to display such data as phone numbers or email addresses, at the cost of accessibility to screen reader users.
Other report findings include:
- Bot traffic varies by website size: Small sites (1,000 visits/day) see 80.5 percent bots, medium sites (10,000 visits/day) 63.2 percent, large sites (100,000 visits/day) 56.2 percent, and very large sites (1M+ visits/day) 52.3 percent.
- Comparing the period covered by this report with the previous period, among malicious bots, impersonators have increased by 10 percent, while hacking tools are down to 3.5 percent, and scraping bots are up 3 percent. Spam bots held steady at 0.5 percent.
- Good bot traffic is down by 4 percent, likely due to the broad decrease in RSS bot activity.
"We have been conducting this study since 2012, and one constant in our findings is that malicious bots are becoming increasingly sophisticated and harder to distinguish from humans. These bots pose a huge threat to websites and are capable of large-scale hack attacks, DDoS floods, spam schemes and click fraud campaigns," said Marc Gaffan, CEO of Incapsula. "With the vulnerabilities exposed in the past year, notably Shellshock, it is more important than ever that companies operating websites are diligent in securing their sites from malicious traffic."
Softpanorama hot topic of the month
Robots exclusion standard - Wikipedia, the free encyclopedia
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes. If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner.
ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: September, 12, 2017