The security company's domain-name division, which is responsible for managing all domain names ending in .com and .net, has been fighting criticism from much of the Internet's technical old guard since introducing its new "SiteFinder" service three weeks ago. SiteFinder redirected all mistyped and unregistered domain names to a VeriSign search page, an action that some said interfered with spam filters and other Internet applications.
After legal threats from the Internet Corporation for Assigned Names and Numbers (Icann), VeriSign pulled the service offline last week, reinstating the old system of error messages. But in a press conference on Monday, VeriSign executives said Icann did not have authority over the new service and that the company would fight back against the "prejudice and bias of a few folks who have a set way of doing things."
"The Internet got started by being very open and encouraging people to introduce new things," said Rusty Lewis, VeriSign's executive vice president, who oversees the domain names division. "In critical infrastructure, that hasn't been the case, and that's what we're fighting for here."
The ongoing dispute is one of the clearest illustrations in recent years of the potential value of the domain-name system and of the deeply conflicting philosophies about how it and other basic Net infrastructures should be controlled and regulated.
VeriSign has chafed over the past years over what it says are bureaucratic and pointless delays to domain-name system enhancements, such as allowing people to use non-English characters in .com domains. The SiteFinder service, which takes people who mistype an address to a search page with suggestions on what they might have meant, is just this kind of consumer-friendly enhancement, the company argued.
But critics, including Icann, the Internet Architecture Board, the Internet Society, and a chorus of longtime Net programmers, said the redirect service is an abuse of the company's control over .com and other domains.
"Icann's preliminary conclusion is that the changes to .com and .net... have had a substantial adverse effect on the core operation of the (domain name system), on the stability of the Internet and the .com and .net top-level domains, and may have additional adverse effects in the future," the regulatory group wrote in a letter on Friday. "Further, VeriSign's actions are not consistent with its contractual obligations under the .com and .net registry agreements."
At the press conference on Monday, VeriSign said it is convening a panel of Internet experts to evaluate the technical fallout from its change. Real technical problems have been far less widespread than reported, the company executives said, and they predict their data will show that the real impact was minimal.
Lewis said the company needs to make money from new services such as SiteFinder, or it will not be able to protect the Net's critical infrastructure. He cited a hacker's attack on the domain name system last year, in which VeriSign servers remained relatively unscathed -- largely because of the "substantial amount of capital we've had to invest," he said.
Without SiteFinder, "there will be a limited amount of opportunity to create investment dollars to invest back in infrastructure," Lewis said, warning that permanently eliminating the service could have negative effects on VeriSign's health and, by extension, the broader Internet. "If we don't (innovate), the infrastructure will not improve, and the Internet will be weaker."
The redirect service was "not a registry service that would be appropriately reviewed by Icann," Lewis added.
Several private lawsuits also have been filed against VeriSign over the issue, including a proposed class-action suit on behalf of a company that offered similar domain-name redirection services as a Web browser add-on.






Talkback
Depending on where / how you wind up getting to sitefinder you get treated to:
Sex video
Free porn
Anal sex
Porn video
adult toys
Lesbian
XXX videos
Viagra
Really helpful and innovative.. will never buy certificates or domains from them again.
SiteFinder broke our business model. We sign up new domain names for clients every day and we expect that as soon as our DNS is set up (within minutes), our clients can navigate to their new site. And it worked great... any browser trying to go to that domain would find no entry in the routers (a new domain, of course), so it would work backward to the DNS of the registrars and quickly find where the new domain DNS is hosted (on our DNS server), and then follow that to the new IP address for the domain. But SiteFinder hijacked that route, and our new domains became unusable until the next update of the master name servers. Our service no longer had the advantage of speed that we promised our customers, and instead offered confusion (domain unavailability) that lasted until the new name propagated fully throughout the net.