Verisign

From Wikipedia, the free encyclopedia
(Redirected from VeriSign)

Template:Short description Template:DMCA Template:DMCA

Page Module:Infobox/styles.css has no content.Page Template:Infobox company/styles.css has no content.

Verisign, Inc.
Company type
Public
Page Template:Plainlist/styles.css has no content.
ISINScript error: No such module "WikidataIB".
IndustryScript error: No such module "WikidataIB".
PredecessorScript error: No such module "WikidataIB".
IncorporatedScript error: No such module "WikidataIB".
FoundedScript error: No such module "WikidataIB".
FounderScript error: No such module "WikidataIB".
DefunctScript error: No such module "WikidataIB".
SuccessorScript error: No such module "WikidataIB".
HeadquartersReston, Virginia,
U.S.
Key people
Page Template:Plainlist/styles.css has no content.
RevenueScript error: No such module "WikidataIB".
Script error: No such module "WikidataIB".
Script error: No such module "WikidataIB".
Total assetsScript error: No such module "WikidataIB".
Total equityDecrease US$−2.2 billion (2025)
Number of employees
Script error: No such module "WikidataIB".
ParentScript error: No such module "WikidataIB".
Page Module:Infobox/styles.css has no content.
ASNsPage Template:Plainlist/styles.css has no content.
  • Lua error in Module:WikidataCheck at line 29: attempt to index field 'wikibase' (a nil value).Template:Autnum (primary)
  • Lua error in Module:WikidataCheck at line 29: attempt to index field 'wikibase' (a nil value).Template:Autnum (J-root)
Websiteverisign.com
Footnotes / references
[1]

Script error: No such module "Check for conflicting parameters".Script error: No such module "Check for deprecated parameters".

Verisign, Inc. is an American company based in Reston, Virginia, that operates a diverse array of network infrastructure, including two of the Internet's thirteen root nameservers, the authoritative registry for the Page Template:Mono/styles.css has no content..com, Page Template:Mono/styles.css has no content..net, and Page Template:Mono/styles.css has no content..name generic top-level domains and the Page Template:Mono/styles.css has no content..cc country-code top-level domains, and the back-end systems for the Page Template:Mono/styles.css has no content..jobs and Page Template:Mono/styles.css has no content..edu sponsored top-level domains.[3]

In 2010, Verisign sold its authentication business unit – which included Secure Sockets Layer (SSL) certificate, public key infrastructure (PKI), Verisign Trust Seal, and Verisign Identity Protection (VIP) services – to Symantec for $1.28 billion.[4] 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.[5] On October 25, 2018, NeuStar, Inc. acquired VeriSign's Security Service Customer Contracts.[6] 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.[7]

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.[8] The company is incorporated in Delaware.[9]

History

Historical logo

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 for $21billion,[10] which operated the Page Template:Mono/styles.css has no content..com, Page Template:Mono/styles.css has no content..net and Page Template:Mono/styles.css has no content..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 by then had become the company's largest and most significant business unit.[11] In 2002, Verisign was charged with violation of the Securities Exchange Act.[12] Verisign divested the Network Solutions retail (domain name registrar) business in 2003 for $100million, retaining the domain name registry (wholesale) function as its core Internet addressing business.[13]

For the year ended December 31, 2010, Verisign reported revenue of $681 million, up 10% from $616 million in 2009.[14] 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.[15] 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 for $950 Million.[16]

On 14 December 2021, the Ministry of Justice, Communication and Foreign Affairs of the Tuvalu Government announced on Facebook that they have selected GoDaddy Registry as the new registry service provider for the domain after Verisign did not participate in the renewal process.[17]

In 2011, Verisign was selected by the General Services Administration (GSA) to operate the registry services for the Page Template:Mono/styles.css has no content..gov top-level domain.[18] They continued to operate Page Template:Mono/styles.css has no content..gov service until 2023, when Cybersecurity and Infrastructure Security Agency (CISA) chose Cloudflare to replace Verisign as the .gov operator.[19]

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 ICANN 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, Page Template:Mono/styles.css has no content..com and Page Template:Mono/styles.css has no content..net, and .name. It is the primary technical subcontractor for the Page Template:Mono/styles.css has no content..edu and Page Template:Mono/styles.css has no content..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. In addition, Verisign is also the contracted registry operator for the country code top-level domain Page Template:Mono/styles.css has no content..cc (Cocos Islands).[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. It formerly was the contracted registry for .gov top-level domains as well as for the country code top-level domain .tv (Tuvalu).

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's 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

Page Module:Message box/ambox.css has no content.

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.[23] 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.[24] 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.[25] 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.[citation needed] Microsoft had to later release a special security patch in order to revoke the certificates and mark them as being fraudulent.[26]

2002: Domain transfer lawsuit

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.[27]

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 Page Template:Mono/styles.css has no content..com or Page Template:Mono/styles.css has no content..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 Page Template:Mono/styles.css has no content..com and Page Template:Mono/styles.css has no content..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.[28] In late 2005, Verisign and ICANN announced a proposed settlement which defined a process for the introduction of new registry services in the Page Template:Mono/styles.css has no content..com registry. The documents concerning these settlements are available at ICANN.org.[29] The ICANN comments mailing list archive[30] documents some of the criticisms that have been raised regarding the settlement.

2003: Gives up Page Template:Mono/styles.css has no content..org domain

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

2005: Retains Page Template:Mono/styles.css has no content..net domain

In mid-2005, the existing contract for the operation of Page Template:Mono/styles.css has no content..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 Page Template:Mono/styles.css has no content..net. They proposed Verisign continue to manage the Page Template:Mono/styles.css has no content..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 based outside the United States, which raised concerns in national security circles. On June 8, 2005, ICANN announced that Verisign had been approved to operate Page Template:Mono/styles.css has no content..net until 2011. More information on the Page Template:Mono/styles.css has no content..net bidding process is available at ICANN.[31] On July 1, 2011, ICANN announced that VeriSign's approval to operate .net was extended another six years, until 2017.[32]

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.[33][34]

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. Some, such as Oliver Lavery, the Director of Security and Research for nCircle, doubted whether sites using Verisign SSL certificates could be trusted.[33]

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 Page Template:Mono/styles.css has no content..com Internet addresses that were reported to be involved in the illegal sale and distribution of counterfeit goods.[35] As registry operator for Page Template:Mono/styles.css has no content..com, Verisign performed the required takedowns of the 82 sites under order from law enforcement.[36] 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".[37] The removal of the 82 websites was cited as an impetus for the launch of "the Dot-P2P Project"[38] in order to create a decentralized DNS service without centralized registry operators. Following the disappearance of WikiLeaks 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]

2012: Web site domain seizure

In March 2012, the U.S. government declared that it has the right to seize domains ending in Page Template:Mono/styles.css has no content..com, Page Template:Mono/styles.css has no content..net, Page Template:Mono/styles.css has no content..cc, Page Template:Mono/styles.css has no content..tv, Page Template:Mono/styles.css has no content..name, and Page Template:Mono/styles.css has no content..org if the companies administering the domains are based in the U.S. The U.S. government can seize the domains ending in Page Template:Mono/styles.css has no content..com, Page Template:Mono/styles.css has no content..net, Page Template:Mono/styles.css has no content..cc, Page Template:Mono/styles.css has no content..tv, and Page Template:Mono/styles.css has no content..name by serving a court-order on Verisign, which manages those domains. The Page Template:Mono/styles.css has no content..org domain is managed by the Virginia-based non-profit Public Interest Registry. In March 2012, Verisign shut down the sports-betting site Bodog.com after receiving a court order, even though the domain name was registered to a Canadian company.[41]

References

Page Template:Reflist/styles.css has no content.

  1. ^ Page Module:Citation/CS1/styles.css has no content."Verisign 2025 Annual Report 10-K". U.S. Securities and Exchange Commission. February 5, 2026.
  2. ^ Page Module:Citation/CS1/styles.css has no content."Verisign Company Profile - CNNMoney.com". CNN Money. Archived from the original on October 10, 2017. Retrieved September 1, 2016.
  3. ^ Page Module:Citation/CS1/styles.css has no content."A global provider of domain name registry services and internet infrastructure | Verisign". www.verisign.com. Retrieved December 7, 2025.
  4. ^ Page Module:Citation/CS1/styles.css has no content.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.
  5. ^ Page Module:Citation/CS1/styles.css has no content."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.
  6. ^ Page Module:Citation/CS1/styles.css has no content."NeuStar Acquires VeriSign - Security Services Customer Contracts | Mergr". mergr.com. Archived from the original on February 29, 2020. Retrieved February 29, 2020.
  7. ^ Page Module:Citation/CS1/styles.css has no content."Neustar Acquires Verisign's Security Services Customer Contracts". home.neustar. Archived from the original on April 19, 2019. Retrieved February 29, 2020.
  8. ^ Page Module:Citation/CS1/styles.css has no content.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.
  9. ^ Page Module:Citation/CS1/styles.css has no content."EDGAR Search Results". www.sec.gov. Archived from the original on October 16, 2018. Retrieved October 16, 2018.
  10. ^ Page Module:Citation/CS1/styles.css has no content."Verisign acquires Network Solutions for $21B - Mar. 7, 2000". money.cnn.com. Archived from the original on April 12, 2011. Retrieved April 12, 2011.
  11. ^ Page Module:Citation/CS1/styles.css has no content.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.
  12. ^ Page Module:Citation/CS1/styles.css has no content."The Emerson Firm Announces Class Action Lawsuit Against VeriSign Inc. on Behalf of Investors — VRSN" (Press release). May 16, 2002. Archived from the original on August 7, 2014. Retrieved July 19, 2013.
  13. ^ Page Module:Citation/CS1/styles.css has no content."VeriSign To Sell Network Solutions, Exit Registrar Business - News - TechNewsWorld". www.technewsworld.com. October 17, 2003. Archived from the original on March 18, 2012. Retrieved April 12, 2011.
  14. ^ Page Module:Citation/CS1/styles.css has no content."VERISIGN REPORTS 10% YEAR-OVER-YEAR REVENUE GROWTH IN 2010". Archived from the original on November 2, 2011. Retrieved April 12, 2011.
  15. ^ Page Module:Citation/CS1/styles.css has no content.Dealbook (August 10, 2010). "Symantec Acquires VeriSign for $1.28 Billion". Archived from the original on March 2, 2018. Retrieved March 5, 2017.
  16. ^ Page Module:Citation/CS1/styles.css has no content.Raymond, Art (August 3, 2017). "Lehi's DigiCert swallows web security competitor in $1 billion deal". Deseret News. Archived from the original on August 4, 2017. Retrieved May 21, 2020.
  17. ^ Page Module:Citation/CS1/styles.css has no content.Allemann, Andrew (December 14, 2021). "GoDaddy wins contract to run .TV, Verisign didn't bid for renewal". Domain Name Wire | Domain Name News. Retrieved September 24, 2023.
  18. ^ Page Module:Citation/CS1/styles.css has no content.Lipowicz, Alice (February 3, 2011). "GSA selects VeriSign to manage .gov domain name registry". GCN. Archived from the original on March 6, 2025. Retrieved January 16, 2023.
  19. ^ Page Module:Citation/CS1/styles.css has no content.Murphy, Kevin (January 16, 2023). "Verisign loses prestige .gov contract to Cloudflare". DomainIncite. Retrieved January 16, 2023.
  20. ^ Page Module:Citation/CS1/styles.css has no content."VeriSign Inc. (VRSN) Pulled Back After Government Transition". March 18, 2014. Archived from the original on April 13, 2014. Retrieved April 12, 2014.
  21. ^ Page Module:Citation/CS1/styles.css has no content."Registry Agreements". ICANN. Archived from the original on November 6, 2015. Retrieved November 30, 2015.
  22. ^ National Science Foundation Page Module:Citation/CS1/styles.css has no content."A Brief History of NSF and the Internet". nsf.gov. Archived from the original on November 27, 2015. Retrieved November 30, 2015.
  23. ^ Page Module:Citation/CS1/styles.css has no content."VeriSign Inc. terminates Loudoun lease for Reston move". Washington Business Journal. September 20, 2010. Retrieved November 6, 2024.
  24. ^ Page Module:Citation/CS1/styles.css has no content."VeriSign Acquires Reston Office for $118M". benefitspro.com. Retrieved November 6, 2024.
  25. ^ Page Module:Citation/CS1/styles.css has no content."Microsoft Security Bulletin MS01-017 - Critical: Erroneous VeriSign-Issued Digital Certificates Pose Spoofing Hazard". Microsoft. March 22, 2001. Retrieved April 29, 2021.
  26. ^ Page Module:Citation/CS1/styles.css has no content."Windows Security Update: Verisign Digital Certificates Spoofing Hazard". Microsoft. March 28, 2001. Retrieved June 30, 2012.
  27. ^ TheRegister.co.uk Script error: No such module "webarchive".: VeriSign slammed for domain renewal scam
  28. ^ Page Module:Citation/CS1/styles.css has no content."Litigation Documents". ICANN.org. March 26, 2007. Archived from the original on July 12, 2007. Retrieved August 21, 2007.
  29. ^ Page Module:Citation/CS1/styles.css has no content."ICANN". www.icann.org. Archived from the original on February 7, 2006. Retrieved February 3, 2006.
  30. ^ Page Module:Citation/CS1/styles.css has no content."ICANN Email Archives: [settlement-comments]". forum.icann.org. Archived from the original on February 18, 2006. Retrieved February 3, 2006.
  31. ^ Page Module:Citation/CS1/styles.css has no content."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.
  32. ^ Page Module:Citation/CS1/styles.css has no content."ICANN". www.icann.org. Archived from the original on October 3, 2015. Retrieved October 1, 2015.
  33. ^ a b Page Module:Citation/CS1/styles.css has no content.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.
  34. ^ Page Module:Citation/CS1/styles.css has no content.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.
  35. ^ Page Module:Citation/CS1/styles.css has no content."82 Websites removed by DNS removal". Archived from the original on December 2, 2010. Retrieved November 12, 2010.
  36. ^ Page Module:Citation/CS1/styles.css has no content."Verisign implicated in DNS annulment". Archived from the original on December 1, 2010. Retrieved November 12, 2010.
  37. ^ Page Module:Citation/CS1/styles.css has no content."Verisign acknowledges DNS removals". Archived from the original on December 6, 2010. Retrieved November 12, 2010.
  38. ^ Page Module:Citation/CS1/styles.css has no content."Peer-to-peer response to Verisign's DNS removals". Archived from the original on March 28, 2018. Retrieved November 12, 2010.
  39. ^ Page Module:Citation/CS1/styles.css has no content.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. ^ Page Module:Citation/CS1/styles.css has no content."EFF warns of Internet chokepoints". Archived from the original on December 5, 2010. Retrieved November 12, 2010.
  41. ^ Page Module:Citation/CS1/styles.css has no content.Kravets, David (March 6, 2012). "Uncle Sam: If It Ends in .Com, It's .Seizable". Wired. Retrieved June 24, 2021.

Page Module:Side box/styles.css has no content.Page Template:Sister project/styles.css has no content.

Page Template:Plainlist/styles.css has no content.
Script error: No such module "Sister project logo".
Wikimedia Commons has media related to [[commons:Template:If then show|Template:If then show]].

Lua error in mw.title.lua at line 404: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').

Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found. Template:S&P 500 companies Lua error in package.lua at line 80: module 'Module:Authority control/config' not found.

Retrieved from "http://cosmopedia.co/index.php?title=Verisign&oldid=205125"