Verisign

Verisign Inc. is an American company based in Reston, Virginia, United States that operates a diverse array of network infrastructure, including two of the Internet's thirteen root nameservers, the authoritative registry for the .com, .net, and .name generic top-level domains and the .cc and .tv country-code top-level domains, and the back-end systems for the .jobs, .gov, and .edu top-level domains. Verisign also offers a range of security services, including managed DNS, distributed denial-of-service (DDoS) attack mitigation[7] and cyber-threat reporting.

Verisign, Inc.
Type of site
Public
Traded as
FoundedApril 12, 1995 (1995-04-12)[1]
Headquarters
Reston, Virginia
,
U.S.
Founder(s)James Bidzos
Key peopleJames Bidzos
(Chairman, President & CEO)
IndustryInternet, Communications
Revenue US$1.17 billion (2017)[2]
Operating income US$686.6 million (2016)[3]
Net income US$492 million (2017)[2]
Total assets US$2.941 billion (2017)[4]
Total equity −US$1.201 billion (2016)[2]
Employees1,019[5]
URLwww.verisign.com
Alexa rank 20,539 (November 2015)[6]

In 2010, Verisign sold its authentication business unit – which included Secure Sockets Layer (SSL) certificate, public key infrastructure (PKI), Verisign Trust Seal, Verisign Trust Seal, and Verisign Identity Protection (VIP) services – to Symantec for $1.28 billion.[8] The deal capped a multi-year effort by Verisign to narrow its focus to its core infrastructure and security business units. Symantec later sold this unit to DigiCert in 2017.[9] On October 25, 2018, NeuStar, Inc. acquired VeriSign’s Security Service Customer Contracts. [10] The acquisition effectively transferred Verisign Inc.’s Distributed Denial of Service (DDoS) protection, Managed DNS, DNS Firewall and fee-based Recursive DNS services customer contracts.[11]

Verisign's former chief financial officer (CFO) Brian Robins announced in August 2010 that the company would move from its original location of Mountain View, California, to Dulles in Northern Virginia by 2011 due to 95% of the company's business being on the East Coast.[12] The company is incorporated in Delaware.[13]

History

Verisign was founded in 1995 as a spin-off of the RSA Security certification services business. The new company received licenses to key cryptographic patents held by RSA (set to expire in 2000) and a time-limited non-compete agreement. The new company served as a certificate authority (CA) and its initial mission was "providing trust for the Internet and Electronic Commerce through our Digital Authentication services and products". Prior to selling its certificate business to Symantec in 2010, Verisign had more than 3 million certificates in operation for everything from military to financial services and retail applications, making it the largest CA in the world.

In 2000, Verisign acquired Network Solutions,[14] which operated the .com, .net and .org TLDs under agreements with the Internet Corporation for Assigned Names and Numbers (ICANN) and the United States Department of Commerce. Those core registry functions formed the basis for Verisign's naming division, which is now the company's largest and most significant business unit.[15] In 2002, Verisign was charged with violation of the Securities Exchange Act.[16] Verisign divested the Network Solutions retail (domain name registrar) business in 2003, retaining the domain name registry (wholesale) function as its core Internet addressing business.[17]

For the year ended December 31, 2010, Verisign reported revenue of $681 million, up 10% from $616 million in 2009.[18] Verisign operates two businesses, Naming Services, which encompasses the operation of top-level domains and critical Internet infrastructure, and Network Intelligence and Availability (NIA) Services, which encompasses DDoS mitigation, managed DNS and threat intelligence.

On August 9, 2010, Symantec completed its approximately $1.28 billion acquisition of Verisign's authentication business, including the Secure Sockets Layer (SSL) Certificate Services, the Public Key Infrastructure (PKI) Services, the Verisign Trust Services, the Verisign Identity Protection (VIP) Authentication Service, and the majority stake in Verisign Japan. The deal capped a multi-year effort by Verisign to narrow its focus to its core infrastructure and security business units.[19] Following ongoing controversies regarding Symantec's handling of certificate validation, which culminated in Google untrusting Symantec-issued certificates in its Chrome web browser, Symantec sold this unit to DigiCert in 2017.[9]

Verisign's share price tumbled in early 2014, hastened by the U.S. government's announcement that it would "relinquish oversight of the Internet's domain-naming system to a non-government entity".[20] Ultimately the Internet Corporation for Assigned Names and Numbers chose to continue VeriSign's role as the root zone maintainer and the two entered into a new contract in 2016.

Naming services
Security token produced by Verisign

Verisign's core business is its naming services division. The division operates the authoritative domain name registries for two of the Internet's most important top-level domains, .com and .net. It is also the contracted registry operator for the .name and .gov top-level domains as well as the country code top-level domains .cc (Cocos Islands) and .tv (Tuvalu). In addition, Verisign is the primary technical subcontractor for the .edu, and .jobs top-level domains for their respective registry operators, which are non-profit organizations; in this role Verisign maintains the zone files for these particular domains and hosts the domains from their domain servers.[21] Registry operators are the "wholesalers" of Internet domain names, while domain name registrars act as the “retailers”, working directly with consumers to register a domain name address.

Verisign also operates two of the Internet's thirteen "root servers" which are identified by the letters A-M (Verisign operates the “A” and “J” root servers). The root servers form the top of the hierarchical Domain Name System that supports most modern Internet communication. Verisign also generates the globally recognized root zone file and is also responsible for processing changes to that file once they are ordered by ICANN via IANA and approved by the U.S. Department of Commerce. Changes to the root zone were originally distributed via the A root server, but now they are distributed to all thirteen servers via a separate distribution system which Verisign maintains. Verisign is the only one of the 12 root server operators to operate more than one of the thirteen root nameservers. The A and J root servers are "anycasted” and are no longer operated from any of the company's own datacenters as a means to increase redundancy and availability and mitigate the threat of a single point of failure. In 2016 the Department of Commerce ended its role in managing the Internet's DNS and transferred full control to ICANN. While this initially negatively impacted VeriSign's stock, ICANN eventually chose to contract with Verisign to continue its role as the root zone maintainer.

VeriSign's naming services division dates back to 1993 when Network Solutions was awarded a contract by the National Science Foundation to manage and operate the civilian side of the Internet's domain name registrations.[22] Network Solutions was the sole registrar for all of the Internet's non governmental generic top-level domains until 1998 when ICANN was established and the new system of competitive registrars was implemented. As a result of these new policies, Network Solutions divided itself into two divisions. The NSI Registry division was established to manage the authoritative registries that the company would still operate and was separated from the customer-facing registrar business that would have to compete with other registrars. The divisions were even geographically split with the NSI Registry moving from the corporate headquarters in Herndon, Virginia, to nearby Dulles, Virginia. In 2000, VeriSign purchased Network Solutions taking over its role in the Internet DNS. The NSI Registry division eventually became VeriSign's naming services division while the remainder of Network Solutions was later sold by Verisign in 2003 to Pivotal Equity Group.

Company properties

Following the sale of its authentication services division in 2010, Verisign relocated from its former headquarters in Mountain View, California, to the headquarters of the naming division in Sterling, Virginia (originally NSI Registry's headquarters). Verisign began shopping that year for a new permanent home shortly after moving. They signed a lease for 12061 Bluemont Way in Reston, the former Sallie Mae headquarters, in 2010 and decided to purchase the building in September 2011. They have since terminated their lease of their current space in two buildings at Lakeside@Loudoun Technology Center. The company completed its move at the end of November 2011. The new headquarters is located in the Reston Town Center development which has become a major commercial and business hub for the region. In addition to its Reston headquarters, Verisign owns three data center properties. One at 22340 Dresden Street in Dulles, Virginia not far from its corporate headquarters (within the large Broad Run Technology Park), one at 21 Boulden Circle in New Castle, Delaware, and a third in Fribourg, Switzerland. Their three data centers are mirrored so that a disaster at one data center has a minimal impact on operations. Verisign also leases an office suite in downtown Washington, D.C., on K street where its government relations office is located. It also has leased server space in numerous internet data centers around the world where the DNS constellation resolution sites are located, mostly at major internet peering facilities. One such facility is at the Equinix Ashburn Datacenter in Ashburn, Virginia, one of the world's largest datacenters and internet transit hubs.

Controversies

2001: Code signing certificate mistake

In January 2001, Verisign mistakenly issued two Class 3 code signing certificates to an individual claiming to be an employee of Microsoft.[23] The mistake was not discovered and the certificates were not revoked until two weeks later during a routine audit. Because Verisign code-signing certificates do not specify a Certificate Revocation List Distribution Point, there was no way for them to be automatically detected as having been revoked, placing Microsoft's customers at risk. Microsoft had to later release a special security patch in order to revoke the certificates and mark them as being fraudulent.[24]

2002: Domain transfer law suit

In 2002, Verisign was sued for domain slamming – transferring domains from other registrars to themselves by making the registrants believe they were merely renewing their domain name. Although they were found not to have broken the law, they were barred from suggesting that a domain was about to expire or claim that a transfer was actually a renewal.[25]

In September 2003, Verisign introduced a service called Site Finder, which redirected Web browsers to a search service when users attempted to go to non-existent .com or .net domain names. ICANN asserted that Verisign had overstepped the terms of its contract with the U.S. Department of Commerce, which in essence grants Verisign the right to operate the DNS for .com and .net, and Verisign shut down the service. Subsequently, Verisign filed a lawsuit against ICANN in February 2004, seeking to gain clarity over what services it could offer in the context of its contract with ICANN. The claim was moved from federal to California state court in August 2004.[26] In late 2005 Verisign and ICANN announced a proposed settlement which defined a process for the introduction of new registry services in the .com registry. The documents concerning these settlements are available at ICANN.org.[27] The ICANN comments mailing list archive[28] documents some of the criticisms that have been raised regarding the settlement. Additionally Verisign was involved in the sex.com matter decided by the Ninth circuit.[29]

2003: Gives up .org domain

In keeping with ICANN's charter to introduce competition to the domain name marketplace, Verisign agreed to give up its operation of .org top-level domain in 2003 in exchange for a continuation of its contract to operate .com, which, at the time had more than 34 million registered addresses.

2005: Retains .net domain

In mid-2005, the existing contract for the operation of .net expired and five companies, including Verisign, bid for management of it. Verisign enlisted numerous IT and telecom heavyweights including Microsoft, IBM, Sun Microsystems, MCI, and others, to assert that Verisign had a perfect record operating .net. They proposed Verisign continue to manage the .net DNS due to its critical importance as the domain underlying numerous "backbone" network services. Verisign was also aided by the fact that several of the other bidders were foreign-based, which raised concerns in national security circles. On June 8, 2005, ICANN announced that Verisign had been approved to operate .net until 2011. More information on the .net bidding process is available at ICANN.[30] On July 1, 2011, ICANN announced that VeriSign's approval to operate .net was extended another six years, until 2017.[31]

2010: Data breach and disclosure controversy

In February 2012 Verisign revealed that their network security had been repeatedly breached in 2010. Verisign stated that the breach did not impact the Domain Name System (DNS) that they maintain, but would not provide details about the loss of data. Verisign was widely criticized for not disclosing the breach earlier and apparently attempting to hide the news in an October 2011 SEC filing.[32][33]

Because of the lack of details provided by Verisign, it was not clear whether the breach impacted the Certificate Signing business, acquired by Symantec in late 2010. According to Oliver Lavery, the Director of Security and Research for nCircle "Can we trust any site using Verisign SSL certificates? Without more clarity, the logical answer is no”.[32]

2010: Web site domain seizures

On November 29, 2010, the U.S. Immigration and Customs Enforcement (U.S. ICE) issued seizure orders against 82 web sites with .com Internet addresses that were reported to be involved in the illegal sale and distribution of counterfeit goods.[34] As registry operator for .com, Verisign performed the required takedowns of the 82 sites under order from law enforcement.[35] InformationWeek reported that "Verisign will say only that it received sealed court orders directing certain actions to be taken with respect to specific domain names".[36] The removal of the 82 websites was cited as an impetus for the launch of "the Dot-P2P Project"[37] in order to create a decentralized DNS service without centralized registry operators. Following the disappearance of WikiLeaks[38] during the following week[39] and its forced move to wikileaks.ch, a Swiss domain, the Electronic Frontier Foundation warned of the dangers of having key pieces of Internet infrastructure such as DNS name translation under corporate control.[40]

gollark: I didn't say that that produces *good* outcomes for people involved.
gollark: Apparently the (or at least a) reason for this problem is that a degree works as a proxy for some minimum standard at stuff like being able to consistently do sometimes-boring things for 4 years, remember information and do things with it, and manage to go to class on time. So it's useful information regardless of whether the employer actually needs your specialized knowledge at all (in many cases, they apparently do not). And they're increasingly common, so *not* having one is an increasing red flag - you may have some sort of objection to the requirement for them, but that can't be distinguished from you just not being able to get one.
gollark: The solution, clearly, is to ban asking people if they have degrees when hiring, and force them to be tested on other things instead.
gollark: That wouldn't destroy it.
gollark: The most feasible way would probably be to deorbit the earth with MANY mass drivers.

References
  1. "Verisign Company Profile - CNNMoney.com". CNN Money. Archived from the original on October 10, 2017. Retrieved September 1, 2016.
  2. "Verisign Reports Fourth Quarter and Full Year 2017 Results". Archived from the original on April 4, 2018. Retrieved April 3, 2018.
  3. "VRSN Company Financials". NASDAQ. Archived from the original on December 6, 2017. Retrieved December 5, 2017.
  4. "VERISIGN INC 2016". NASDAQ. Archived from the original on October 18, 2018. Retrieved December 5, 2017.
  5. "VeriSign, Inc. – 2015 10-K". Verisign. Archived from the original on June 6, 2017. Retrieved March 1, 2016.
  6. "verisign.com Site Overview". Alexa Internet. Archived from the original on October 18, 2015. Retrieved November 10, 2015.
  7. Lombard, Lisa (May 2013). "DDoS and other Malicious Attacks take advantage of Vulnerable Printers" (PDF). Teletimes. p. 26. Archived from the original (PDF) on December 3, 2013. Retrieved August 24, 2013.
  8. Antone Gonsalves (May 20, 2010). "Symantec To Buy VeriSign Unit For $1.28 Billion – Storage – Disaster". Informationweek.com. Archived from the original on May 22, 2010. Retrieved July 13, 2013.
  9. "Symantec Plans to Sell This Business for Nearly $1 Billion". Fortune. August 2, 2017. Archived from the original on January 4, 2018. Retrieved March 1, 2018.
  10. "NeuStar Acquires VeriSign - Security Services Customer Contracts | Mergr". mergr.com. Archived from the original on February 29, 2020. Retrieved February 29, 2020.
  11. "Neustar Acquires Verisign's Security Services Customer Contracts". home.neustar. Archived from the original on April 19, 2019. Retrieved February 29, 2020.
  12. Krouse, Sarah (August 27, 2010). "VeriSign shifts headquarters to Virginia". Washington Business Journal. Archived from the original on August 30, 2010. Retrieved March 1, 2018.
  13. "EDGAR Search Results". www.sec.gov. Archived from the original on October 16, 2018. Retrieved October 16, 2018.
  14. "Verisign acquires Network Solutions for $21B - Mar. 7, 2000". money.cnn.com. Archived from the original on April 12, 2011. Retrieved April 12, 2011.
  15. Kell, John (July 25, 2013). "VeriSign boosts profit 23% on revenue, margins". The Wall Street Journal. Archived from the original on August 1, 2013. Retrieved August 24, 2013.
  16. "The Emerson Firm Announces Class Action Lawsuit Against VeriSign Inc. on Behalf of Investors — VRSN". May 16, 2002. Archived from the original on August 7, 2014. Retrieved July 19, 2013.
  17. "VeriSign To Sell Network Solutions, Exit Registrar Business - News - TechNewsWorld". www.technewsworld.com. Archived from the original on March 18, 2012. Retrieved April 12, 2011.
  18. "VERISIGN REPORTS 10% YEAR-OVER-YEAR REVENUE GROWTH IN 2010". Archived from the original on November 2, 2011. Retrieved April 12, 2011.
  19. Dealbook. "Symantec Acquires VeriSign for $1.28 Billion". Archived from the original on March 2, 2018. Retrieved March 5, 2017.
  20. "VeriSign Inc. (VRSN) Pulled Back After Government Transition". March 18, 2014. Archived from the original on April 13, 2014. Retrieved April 12, 2014.
  21. "Registry Agreements". ICANN. Archived from the original on November 6, 2015. Retrieved November 30, 2015.
  22. National Science Foundation "A Brief History of NSF and the Internet". nsf.gov. Archived from the original on November 27, 2015. Retrieved November 30, 2015.
  23. "Microsoft Security Bulletin MS01-017: Erroneous VeriSign-Issued Digital Certificates Pose Spoofing Hazard". Microsoft. March 22, 2001. Archived from the original on June 24, 2012. Retrieved June 30, 2012.
  24. "Windows Security Update: Verisign Digital Certificates Spoofing Hazard". Microsoft. March 28, 2001. Retrieved June 30, 2012.
  25. TheRegister.co.uk Archived August 10, 2017, at the Wayback Machine: VeriSign slammed for domain renewal scam
  26. "Litigation Documents". ICANN.org. March 26, 2007. Archived from the original on July 12, 2007. Retrieved August 21, 2007.
  27. "ICANN". www.icann.org. Archived from the original on February 7, 2006. Retrieved February 3, 2006.
  28. "ICANN Email Archives: [settlement-comments]". forum.icann.org. Archived from the original on February 18, 2006. Retrieved February 3, 2006.
  29. "Kremen v. Network Solutions, Inc" (PDF). July 25, 2003. Archived from the original (PDF) on February 3, 2007. Retrieved August 21, 2007.
  30. "ICANN - Archives - General Information Regarding Designation of the Subsequent .net registry Operator". icann.org. Archived from the original on December 4, 2004. Retrieved December 4, 2004.
  31. "ICANN". www.icann.org. Archived from the original on October 3, 2015. Retrieved October 1, 2015.
  32. Bradley, Tony (February 2, 2012). "VeriSign Hacked: What We Don't Know Might Hurt Us". PCWorld. Archived from the original on June 11, 2013. Retrieved July 13, 2013.
  33. Albanesius, Chloe (February 2, 2012). "VeriSign Hacked Multiple Times in 2010 | News & Opinion". PCMag.com. Archived from the original on January 16, 2013. Retrieved July 13, 2013.
  34. "82 Websites removed by DNS removal". Archived from the original on December 2, 2010. Retrieved November 12, 2010.
  35. "Verisign implicated in DNS annulment". Archived from the original on December 1, 2010. Retrieved November 12, 2010.
  36. "Verisign acknowledges DNS removals". Archived from the original on December 6, 2010. Retrieved November 12, 2010.
  37. "Peer-to-peer response to Verisign's DNS removals". Archived from the original on March 28, 2018. Retrieved November 12, 2010.
  38. 213.251.145.96 Archived December 10, 2010, at the Wayback Machine
  39. Arthur, Charles (January 8, 2010). "WikiLeaks under attack: the definitive timeline". the Guardian. Archived from the original on January 17, 2017. Retrieved December 18, 2016.
  40. "EFF warns of Internet chokepoints". Archived from the original on December 5, 2010. Retrieved November 12, 2010.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.