In fighting spam and other forms of Internet and e-mail abuse, many defenders of the \u2018Net have noticed that the worst offenders often include obviously false information in their WHOIS database entries. The WHOIS database records the contact information for each registered domain in the DNS.In my attacks on originators of spam, I\u2019ve often seen the phone number (nnn) 555-1212 (where nnn is an area code) supplied as the contact point; addresses such as \u201c12345 Street Road\u201d with bogus ZIP codes; real-looking phone numbers that turn out to be nonexistent or disconnected; and countless e-mail addresses that bounce like the walls in a squash court.The Internet Corporation for Assigned Names and Numbers (ICANN) regulates the administrative infrastructure of the Internet. In March, the board of directors voted to accept four important recommendations from the Generic Names Supporting Organization Council to maintain the integrity of information in the WHOIS database.Here are the recommendations:\u201c1. Accuracy of WHOIS Data.\u201cA. At least annually, a registrar must present to the Registrant the current WHOIS information, and remind the registrant that provision of false WHOIS information can be grounds for cancellation of their domain name registration. Registrants must review their WHOIS data, and make any corrections.\u201cB. When registrations are deleted on the basis of submission of false contact data or non-response to registrar inquiries, the redemption grace period - once implemented - should be applied. However, the redeemed domain name should be placed in registrar hold status until the registrant has provided updated WHOIS information to the registrar-of-record.\u201c2. Bulk Access to WHOIS Data.\u201cA. Use of bulk access WHOIS data for marketing should not be permitted. The Task Force therefore recommends that the obligations contained in the relevant provisions of the RAA be modified to eliminate the use of bulk access WHOIS data for marketing purposes\u2026\u201cB. Section 184.108.40.206 of the Registrar Accreditation Agreement currently describes an optional clause of registrars' bulk access agreements, which disallows further resale or redistribution of bulk WHOIS data by data users. The use of this clause shall be made mandatory.\u201dIn addition, the recommendations strongly support development of \u201ca reliable contact point to receive and act upon reports of false WHOIS data.\u201d The recommendation continued, \u201cICANN should encourage registrars to (i) provide training for these contact points in the handling of such reports, and (ii) require re-sellers of registration services to identify and train similar contacts.\u201dThese measures will help to fight the scourge of spam by shutting down entire domains run by dishonest people. They will also inadvertently shut down perfectly legitimate domains whose owners are too disorganized to keep their information up to date. If you run a business that depends on the existence of your own domain (e.g., for your own Web site or to send and receive important e-mail), you had better put proper measures into place to ensure that a named individual (and a backup person) are explicitly responsible for keeping the WHOIS database correctly updated (and your DNS registration fees paid on time) or you might suffer a self-imposed denial of service.Lastly, as you consider how to comply with these regulations and update your own registration information, keep one other factor in mind: no one has asked you to provide information that would permit easy social engineering. For example, you don\u2019t have to provide the exact name of the person(s) who will be the administrative contact and the technical contact; instead, you can give a title (e.g., Hostmaster) and an accurate and working, but generic e-mail address such as firstname.lastname@example.org. The additional benefit of such a system is that you control where e-mail directed to this address ends up; this flexibility means you don\u2019t have to update the WHOIS database every time you reassign responsibility for the domain to another employee. For the same reasons, the phone number can be the switchboard rather than a specific extension, thus allowing you to direct calls to the right person without giving away valuable internal information that might support a criminal hacker\u2019s attempts to spoof someone\u2019s identity.