Jump to content

Verisign: Difference between revisions

From ICANNWiki
No edit summary
Line 24: Line 24:
[[Shane Tews]], Global Public Policy, Senior Washington Rep.<br>
[[Shane Tews]], Global Public Policy, Senior Washington Rep.<br>
[[Chuck Gomes]], VP of Policy and Compliance<br>
[[Chuck Gomes]], VP of Policy and Compliance<br>
[[Samantha Frida]], Senior Manager
}}
}}



Revision as of 16:53, 23 December 2011

Type: Public
Industry: Internet, Communications, Registry
Founded: USA (1995)
Founder(s): Jim Bidzos
Headquarters: 487 East Middlefield Road,
Mountain View, CA 94043
Country: USA
Employees: 2,225
Revenue: $1.5 billion USD (2007)
Website: Verisigninc.com
Twitter: @VERISIGN
Key People
Jim Bidzos, Founder, Chairman, CEO

Pat Kane, SVP and GM of Naming Services
Keith Drazek, Director of Policy
Shane Tews, Global Public Policy, Senior Washington Rep.
Chuck Gomes, VP of Policy and Compliance

Verisign is an Internet infrastructure service provider. It is s based in Mountain View, CA and was founded in 1995. Verisign has offices in California, Washington D.C., Indiana, as well as Japan, India, Brazil, China, Australia, Switzerland, and the UK.

Its registry services include the provision of authoritative directory of:

It previously was famous for its authentication services, which included business authentication services such as implementing and operating secure networks, utilizing SSL protocol, encrypting transactions and communications, and user authentication services such as, identity protection , fraud detection, and public key infrastructure.[1] Those services were sold to Symantec in 2010.[2]

History[edit | edit source]

  • 1995 RSA pioneered two-factor authentication and encryption and Verisign was founded as a 'spin-off' of the RSA security technology to act as a certificate authority.[3]
  • June, 1995 Verisign announced partnerships with Apple Computer Inc. and Netscape Communications Corp. to implement VeriSign's Digital IDs in their software products.[4]
  • January, 1996 Verisign introduced the first online digital certificate issue system at the RSA Data Security Conference in San Francisco.[6] Verisign also announced an agreement with Terisa Systems to develop a new and complete internet security solution.[7]
  • January, 1996 Secure Email was launched. Verisign lunched Code Signing with Microsoft in March 1996. In August, 1996, Microsoft and Verisign announced the availability of client authentication technology for Microsoft IE users by using Verisign Digital IDs. [8]
  • 1997, the First Internet Commerce Transactions Linking Europe, Asia, and the United States was conducted by Verifone and Verisign.[9] The United States Department of Commerce approved VeriSign's plans to issue new Verisign Global Server IDs in June 1997 allowing 128-bit encryption.[10]
  • 1997 VeriSign filed to raise $40 million for its public stock.[11] On January 10, 1998, VeriSign went public.[12]
  • July, 1997 Verisign is acquired by SecureIT, a network security service company.[13]
  • October, 1998 Verisign released a fully integrated PKI platform, OnSite 4.0.[14]
  • November, 1998 Verisign offered Y2k testing certs for free.
  • December, 1998, Verisign introduced digital certificate service for Wireless Application Protocol (WAP) servers and gateways.[15]
  • In March, 2000, Verisign acquired Network Solutions for $21 billion USD, which was the largest Internet purchase to date.[16][17]
  • May, 2005 Verisign introduced a new 2048 bit VeriSign Class 3 Secure Server CA which was used to sign Secure Site Certificates obtained from thier website for IIS web servers.[19]
  • November, 2005 Verisign's payment gateway business, Paypal, was sold to eBay for approximately $370 million.[20].
  • December, 2006 Verisign introduces Extended Validation SSL Certificates, standard practices for certificate validation and display approved by a group of leading SSL Certificate Authorities and browser vendors.[21]
  • November, 2007 Verisign announced plans to divest in its slower growing units and invest more in website naming and internet security services.[22] Report shown these steps had cuthalf of its employeers.
  • 2008 Verisign sold its global Digital Brand Management Services business for US$50 million to MelbourneIT.[25]
  • In May 2010, Verisign sold the entire Authentication Services division to Symantec for 1.28 million.[26] Because of this deal, Symantec now has the right to Verisign's old logo and the "Verisign Secured" tag for SSL certification.
  • In July, 2011, Mark McLaughlin resigned from his position as CEO. He worked with Verisign since 2000, and had been CEO since 2009. Following Mr. McLaughlin's departure, Founder, Chairman, and former CEO Jim Bidzos resumed his duties as CEO.[27] Another prominent executive, CFO Brian Robins, resigned in September, 2011. This happened as Verisign's stocks suffered and rumors of a buyout started circulating.[28]
  • In October, 2011, Verisign submitted its plan for a new Verisign Anti-Abuse Domain Use Policy for approval by ICANN. The policy would allow Verisign to scan domains in the .com, .net, and .name namespaces for malware, as well as to create a suspension system for sites knowingly hosting malware. These scans would be conducted quarterly, and a registrar would be able to opt out.[29] The policy would also allow Verisign to shut down websites at the request of law enforcement officials, and possibly for trademark interests.[30] The policy was deemed controversial, with concern about government involvement in the Internet, as well as concern from domain registrars regarding the blurring of lines between registries and registrars.[31] Two days after releasing the proposal, Verisign withdrew the request.[32]
  • It was announced after the 2011 ICANN Board's of approval of a new gTLD program that Verisign would pursue new IDN translations of it popular .com namespace.[33]

Acquisitions[edit | edit source]

  • January, 2005 - Verisign buys wireless photo messaging firm LightSurf for about $270 million.[35]
  • July, 2005 - Verisign aquires security intelligence specialist iDefense for $40 Million.[38].
  • March, 2006 - Verisign anounced acquisition of Kontiki for $62 million.[39]

Products and Services[edit | edit source]

Verisign provides its services through two divisions, its Internet Services division and the Security Service Division. The Internet Services division includes Naming & Directory Services such as domain name registration for .com and .net, and DNS-related and RFID services.

Verisign sold its Security Services to Symantec in May, 2010. Verisign's Security Services included managing services such firewalls, intrusion detection and prevention, vulnerability protection, etc. It also provided global security consulting, email security, authentication and digital certificate/SSL validation, and Extended Validation (High Assurance) SSL Certificates.

Selling Authentication Services Business to Symantec[edit | edit source]

Verisign's logo, a check mark and the tag "VeriSign Secured" is one of the most trusted trademark of secured website. Even though providing internet security was the primary objective of the company, over time Verisign shifted its priority to website management and domain registration business.

Verisign began by selling some of its services piecemeal. Finally, in May 2010, Verisign sold the entire division to Symantec for 1.28 million.[43] Because of this deal, Symantec now has the right to VeriSign's logo and the "VeriSign Secured" tag for SSL certification.

Domain Slamming[edit | edit source]

In May 2002, BulkRegister sued Verisign for domain slamming.[44] BulkRegister claimed Verisign "engaged in unfair practices" with a recent marketing campaign that attempted to get domain owners to use Verisign to renew their existing policy. In 2003, Verisign was found not to have broken the law and as a result did not need to pay any fine. However, Verisign was barred from suggesting domain renewal or expiration prospects.[45]

Site Finder Service and Issues with ICANN[edit | edit source]

Verisign launched Site Finder September, 2007, which caused a user to be redirected to its Site Finder search engine after the user attempted to access an unregistered address. ICANN published a report against this policy stating "Verisign violated architectural principles, codes of conduct and good practice." ICANN had declared Site Finder in violation of Verisign's contracts for running the master address lists for .com[46] Later, ICANN asked Verisign to suspend its Site Finder service.[47]

In October,a hearing took place place in Washington, D.C. to review technical issues with the U.S. Department of Commerce, which gives permission to Verisign to operate the DNS for .com and .net; VeriSign subsequently shut down the service.

Later, in February 2004, Verisign sued ICANN claiming it had unlawfully been prevented from adding new features to .com and .net.[48]. In August 2004, the claim was moved from federal to California state court. [49] Eventually, in late 2005, Verisign and ICANN announced a proposed settlement introducing terms for new registry services in the .com registry.

The documents of these agreements are publicly available at ICANN's official website and can be viewed here. It should be mentioned that the terms of these agreement were subject to public criticism.

Also, in other domain name negotiations with ICANN, Verisign traded the .org TLD in return for continued rights over .com. In mid 2005, when Verisign's contract for operation with .net expired, Verisign and 5 other companies bid for it. Verisign was supported by renowned IT companies like Microsoft, IBM, Sun Microsystems, and MCI. Finally, on June 8, 2005 ICANN announced that Verisign had been approved to operate .net until 2011.[50]

New gTLDs[edit | edit source]

In December, 2011, weeks before the opening of ICANN's new gTLD program, the Chinese national registry, CNNIC, announced that it was applying for the IDN equivalents of .company, and .network.[51] This move was seen as potentially problematic given Verisign's own plans to seek the IDN equivalents of their .com and .net TLDs; Verisign has perviously said that they will apply for all transliterated versions of .com and .net.[52]

References[edit | edit source]