What started several upgrades to the contact Web Form were a few spam messages coming into the mail account that I have reserved for the site. These probable bots would start going on and on about driving traffic to my site, but wouldn't bother to leave any contact information. It was precisely that omission that suggested to me these messages were not being sent by people. It was after a few of these I started to look into CAPTCHA technology, and became enamored of one in particular: the Google reCAPTCHA actually uses texts from digitized books. Usually, the user is presented one word the system "knows" and one word the system does not. You type in the values that you see, and, for the word that is not known, your response is collected and compared with others; your percentage for getting the value correct is determined by the number of matching answers in the database. Getting both words right allows your operation to continue; missing one or both means taking a crack at a different pair. Ideally, the process basically affords Netizens the opportunity to correct scans of literary works, allowing them to be published digitally. Who wouldn't support that? Bots, meanwhile cannot interpret the text within a CAPTCHA; therefore, in my case, my spam traffic should drop significantly, if not completely. Google did a fairly good job at describing the mechanics of plugging the control into your .NET solution. At a high level, you start by registering your site with Google; you'll receive a private and public key pair, which you'll use when you wire up the control. Next, download the library and adding the component (a DLL) to your solution. This creates a /Bin (note the case) directory in your solution which contains Recaptcha.dll. (When you publish the site to your production server, you'll notice the dll is part of the standard /bin that contains your compiled code.) A tip to offer here: Don't download the library to someplace that's part of your development solution, like a /lib directory (just like I DID; I guess I've been working in Java too much lately). When you publish your site, that /lib directory will go up along with everything else, needlessly, unless you exclude it. Next, in your code forward, you register the control with the Web Form, and paste the code for the control inside your