I have discovered that VeriSign's SiteFinder service breaks Microsoft's Outlook and Microsoft's Outlook Express email readers as well as many of the standard Windows Networking Utilities by providing misleading error messages, temporary lockups, and incorrect status information.
Want a sense of just how much traffic VeriSign is receiving from its SiteFinder service? Alexa, with its Alexa Toolbar and associated traffic tracking services, makes it easy to find out...Over the past three months, taken as a whole, VeriSign had traffic rank 1,559. But today its traffic rank is 19, meaning...
The Internet Corporation for Assigned Names and Numbers (ICANN) has released an "Advisory" concerning VeriSign's deployment of DNS wildcard (Site Finder) service: "Since the deployment, ICANN has been monitoring community reaction, including analysis of the technical effects of the wildcard, and is carefully reviewing the terms of the .com and .net Registry Agreements. In response to widespread expressions of concern from the Internet community about the effects of the introduction of the wildcard..."
Popular Enterprises LLC, the parent company of Netster.com, has filed a $100 million dollar lawsuit against VeriSign, Inc. The Complaint alleges antitrust violations, unfair competition and violations of the Deceptive and Unfair Trade Practices Act based upon VeriSign's release of the Site Finder product. The suit requests injunctive relief to prevent VeriSign from operating Sitefinder, and to otherwise cease what Popular Enterprises believes to be its monopolistic practices.
It is openly admitted , in the same Implementation PDF file, that all accesses to the Site Finder service are monitored and archived. A further worry for users is the privacy policy and terms of service posted on the Site Finder service. Not only does the simple act of mistyping a URL implicitly cause you, the end user, to accept VeriSign's Terms of Service and Privacy Policy without the chance to review and accept or decline either, but critical information as described above is not disclosed in either policy (as of this writing). The Privacy Policy clearly states...
The Internet Corporation for Assigned Names and Numbers (ICANN) and the United States Department of Commerce (DoC) today announced that they agreed to extend their joint Memorandum of Understanding (MoU) for three additional years until September 30, 2006.
The ICANN At-Large Advisory Committee would like to bring to ICANN's attention concerns about VeriSign's surprising roll-out of the "SiteFinder" service for .com and .net. This practice raises grave technical concerns, as it de facto removes error diagnostics from the DNS protocol, and replaces them by an error handling method that is tailored for HTTP, which is just one of the many Internet protocols that make use of the DNS.
Here's another interesting angle on the Verisign Site Finder Web site. VeriSign has hired a company called Omniture to snoop on people who make domain name typos. I found this Omniture Web bug on a VeriSign Site Finder Web page...
As a domain holder myself (of vix.com), I would not have chosen ".com" for my parent domain name back in 1988 had there been a wildcard domain name [that activates Site Finder service] under ".com". The risk of someone attempting to reach me but ending up talking to someone else instead would have been seen as "too great". I am now searching for a new parent domain whose publisher will guarantee me, in perpetuity, that there will be no wildcard name as there now is in "com".
We Internet users, who either own domain names or have an interest in the domain name system, wish to object to the VeriSign's Site Finder system. We believe that the system: 1) Breaks technical standards, by rewriting the expected error codes to instead point to VeriSign's pay-per-click web directory, and threatens the security and stability of the Internet; 2) Breaks technical standards affecting email services, and other Internet systems...