Changes

{{Actor

{{Actor

|stakeholder group=Business

|stakeholder group=Business

|actor type=Root Server Operator, Registries

|actor type=

|country=USA

|country=USA

|website= https://www.verisign.com

|website= https://www.verisign.com

In February 2010, Agiliance Inc., a leading independent provider of Integrated Governance, Risk and Compliance (GRC) solutions, announced that its threat and vulnerability automation solution would be integrated with iDefense Security Intelligence Services.<ref>[http://www.agiliance.com/news/pr_20100223_VeriSign_iDefense.html Verisign iDefense], Agiliance.com. Published 23 February 2010.</ref>

In February 2010, Agiliance Inc., a leading independent provider of Integrated Governance, Risk and Compliance (GRC) solutions, announced that its threat and vulnerability automation solution would be integrated with iDefense Security Intelligence Services.<ref>[http://www.agiliance.com/news/pr_20100223_VeriSign_iDefense.html Verisign iDefense], Agiliance.com. Published 23 February 2010.</ref>

In 2012, Frost and Sullivan recognized Verisign's iDefense with the 2012 North American Frost & Sullivan Award for Product Differentiation; the decision was made based off its analysis of the vulnerability research market. Frost & Sullivan Research Analyst, Richard Martinez, noted that, "Verisign iDefense Security Intelligence Services provide around-the-clock access to relevant and actionable cyber intelligence, supporting decision-makers with threat awareness, vulnerability management and incident management resources." It was also noted that Verisign created the iDefense Vulnerability Contributor Program with hundreds of expert vulnerability researchers from around the globe, to provide insight into the cyber underground, undiscovered vulnerabilities and global threats in more than 20 languages.<ref>[http://www.circleid.com/posts/20120730_frost_sullivan_recognizes_verisign_idefense_for_security_services/ Frost Sullivan Recognizes Verisign for Security Services], CircleID.com. Retrieved 16 November 2012.</ref>

In 2012, Frost and Sullivan recognized Verisign's iDefense with the 2012 North American Frost & Sullivan Award for Product Differentiation; the decision was made based on its analysis of the vulnerability research market. Frost & Sullivan Research Analyst, Richard Martinez, noted that "Verisign iDefense Security Intelligence Services provide around-the-clock access to relevant and actionable cyber intelligence, supporting decision-makers with threat awareness, vulnerability management and incident management resources." It was also noted that Verisign created the iDefense Vulnerability Contributor Program with hundreds of expert vulnerability researchers from around the globe, to provide insight into the cyber underground, undiscovered vulnerabilities and global threats in more than 20 languages.<ref>[http://www.circleid.com/posts/20120730_frost_sullivan_recognizes_verisign_idefense_for_security_services/ Frost Sullivan Recognizes Verisign for Security Services], CircleID.com. Retrieved 16 November 2012.</ref>

== Relationship with ICANN ==

== Relationship with ICANN ==

===Site Finder Service===

===Site Finder Service===

Verisign launched its Site Finder service in September 2003, which redirected end-users to its Site Finder search engine if they attempted to access unregistered web addresses. [[ICANN]] published a report against this policy stating, "Verisign violated architectural principles, codes of conduct and good practice," and ICANN declared Site Finder in violation of Verisign's contracts for running the master address lists for [[.com]]<ref>"[http://www.out-law.com/page-4716 ICANN report attacks VeriSign Site Finder service], Out-Law.com.</ref> [[ICANN]] then asked Verisign to suspend its Site Finder service.<ref>[http://www.out-law.com/page-3921 ICANN asks VeriSign to suspend Site Finder service], Out-Law.com.</ref> In October, a hearing took place place in Washington, D.C. to review technical issues with the [[DOC|U.S. Department of Commerce]], which authorizes Verisign to operate the [[DNS]] for [[.com]] and [[.net]]. VeriSign subsequently shut down the service.

Verisign launched its Site Finder service in September 2003, which redirected end-users to its Site Finder search engine if they attempted to access unregistered web addresses. [[ICANN]] published a report against this policy stating, "Verisign violated architectural principles, codes of conduct and good practice," and ICANN declared Site Finder in violation of Verisign's contracts for running the master address lists for [[.com]]<ref>"[http://www.out-law.com/page-4716 ICANN report attacks VeriSign Site Finder service], Out-Law.com.</ref> [[ICANN]] then asked Verisign to suspend its Site Finder service.<ref>[http://www.out-law.com/page-3921 ICANN asks VeriSign to suspend Site Finder service], Out-Law.com.</ref> In October, a hearing took place in Washington, D.C. to review technical issues with the [[DOC|U.S. Department of Commerce]], which authorizes Verisign to operate the [[DNS]] for [[.com]] and [[.net]]. VeriSign subsequently shut down the service.

In February 2004, Verisign sued [[ICANN]] claiming Verisign had unlawfully been prevented from adding new features to [[.com]] and [[.net]].<ref>[http://news.cnet.com/2100-1038-5165982.html VeriSign sues ICANN to restore Site Finder], CNet.com. Published 26 February 2004.</ref>. In August 2004, the claim was moved from federal to California state court.<ref>[http://www.icann.org/en/general/litigation-verisign.htm Verisign, Inc. v. ICANN], ICANN.org.</ref> More than a year later, in late 2005, Verisign and ICANN announced a proposed settlement that introduced new terms for registry services in the [[.com]] registry. The documents of these agreements are publicly available at ICANN's official website and can be viewed [http://www.icann.org/tlds/agreements/verisign/settlement-agreements.htm here].

In February 2004, Verisign sued [[ICANN]] claiming Verisign had unlawfully been prevented from adding new features to [[.com]] and [[.net]].<ref>[http://news.cnet.com/2100-1038-5165982.html VeriSign sues ICANN to restore Site Finder], CNet.com. Published 26 February 2004.</ref>. In August 2004, the claim was moved from federal to California state court.<ref>[http://www.icann.org/en/general/litigation-verisign.htm Verisign, Inc. v. ICANN], ICANN.org.</ref> More than a year later, in late 2005, Verisign and ICANN announced a proposed settlement that introduced new terms for registry services in the [[.com]] registry. The documents of these agreements are publicly available at ICANN's official website and can be viewed [http://www.icann.org/tlds/agreements/verisign/settlement-agreements.htm here].

===.com Renewals===

===.com Renewals===

The dropping of the aforementioned litigation between Verisign and ICANN cleared the way for the renewal of the [[.com]] registry agreement from 2005 through 2012.<ref>[http://www.theregister.co.uk/2005/10/25/verisign_icann_deal/ Verisign ICANN deal], TheRegister.co.uk. Puhed 25 October 2005.</ref> The agreement and its appendices can be viewed via the ICANN site [http://www.icann.org/en/about/agreements/registries/com here].

The dropping of the aforementioned litigation between Verisign and ICANN cleared the way for the renewal of the [[.com]] registry agreement from 2005 through 2012.<ref>[http://www.theregister.co.uk/2005/10/25/verisign_icann_deal/ Verisign ICANN deal], TheRegister.co.uk. Published 25 October 2005.</ref> The agreement and its appendices can be viewed via the ICANN site [http://www.icann.org/en/about/agreements/registries/com here].

In March 2012, [[ICANN]] posted a proposal for Verisign's potential renewal of the 2006 .com registry agreement.<ref>[http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm .com Registry Agreement Renewal], ICANN.org.</ref> Three months later, in June 2012, the [[ICANN Board]] went against community suggestions to approve Verisign's .com registry agreement for an additional seven years after its expiration on November 30th, 2012. According to the ICANN decision, Verisign would've also been allowed to increase its registry fee by 7% in four out of the next seven years,<ref>[http://domainincite.com/9610-icann-gives-verisigns-com-contract-the-nod ICANN gives Verisign’s .com contract the nod], DomainIncite.com. Published 25 June 2012. Retrieved 28 November 2012.</ref> but this decision was changed by the [[DOC|Department of Commerce]]. Nonetheless, the new policy will result in Verisign paying ICANN a $0.25 fee for every .com registration, renewal, or transfer, instead of the lump sums it paid previously, potentially netting ICANN an additional $8 million in revenue annually.<ref>[http://domainincite.com/9845-icann-to-get-8-million-more-from-new-com-deal ICANN to get $8 million more from new .com deal], DomainIncite.com. Published 27 July 2012. Retrieved 28 November 2012.</ref><ref name="verisign2">[http://domainincite.com/10865-breaking-us-probing-verisign-price-hikes-com-contract-extended US probing Verisign price hikes, .com contract may be extended], DomainIncite.com. Published 25 October 2012. Retrieved 28 November 2012.</ref> The original board resolutions can be viewed [http://www.icann.org/en/groups/board/documents/resolutions-23jun12-en.htm#2 here].

In March 2012, [[ICANN]] posted a proposal for Verisign's potential renewal of the 2006 .com registry agreement.<ref>[http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm .com Registry Agreement Renewal], ICANN.org.</ref> Three months later, in June 2012, the [[ICANN Board]] went against community suggestions to approve Verisign's .com registry agreement for an additional seven years after its expiration on November 30th, 2012. According to the ICANN decision, Verisign would've also been allowed to increase its registry fee by 7% in four out of the next seven years,<ref>[http://domainincite.com/9610-icann-gives-verisigns-com-contract-the-nod ICANN gives Verisign’s .com contract the nod], DomainIncite.com. Published 25 June 2012. Retrieved 28 November 2012.</ref> but this decision was changed by the [[DOC|Department of Commerce]]. Nonetheless, the new policy will result in Verisign paying ICANN a $0.25 fee for every .com registration, renewal, or transfer, instead of the lump sums it paid previously, potentially netting ICANN an additional $8 million in revenue annually.<ref>[http://domainincite.com/9845-icann-to-get-8-million-more-from-new-com-deal ICANN to get $8 million more from new .com deal], DomainIncite.com. Published 27 July 2012. Retrieved 28 November 2012.</ref><ref name="verisign2">[http://domainincite.com/10865-breaking-us-probing-verisign-price-hikes-com-contract-extended US probing Verisign price hikes, .com contract may be extended], DomainIncite.com. Published 25 October 2012. Retrieved 28 November 2012.</ref> The original board resolutions can be viewed [http://www.icann.org/en/groups/board/documents/resolutions-23jun12-en.htm#2 here].

Verisign is to serve as the registry operator for .com from December 2012 through November 2018, with new terms and conditions, including:

Verisign is to serve as the registry operator for .com from December 2012 through November 2018, with new terms and conditions, including:

* Verisign's current pricing of $7.85 per domain name registration will remain unchanged for the next six years;

* Verisign's current pricing of $7.85 per domain name registration will remain unchanged for the next six years;

* Verisign no longer holds the right to increasing prices up to seven percent over the six-year term, and all new price increases will be circumstantial and subject to Commerce Department approval.<ref name="verisign3"></ref>

* Verisign no longer holds the right to increase prices up to seven percent over the six-year term, and all-new price increases will be circumstantial and subject to Commerce Department approval.<ref name="verisign3"></ref>

Those who benefit most from the prize freeze include consumers, those who purchase .com domain names in bulk, brand owners who maintain expensive defensive registrations, and registrars who no longer need to pass on cost increases to their consumers.<ref>[http://domainincite.com/11176-winners-and-losers-in-the-new-com-pricing-regime Winners and losers in the new .com pricing regime], DomainIncite.com. Published 30 November 2012.</ref>

Those who benefit most from the prize freeze include consumers, those who purchase .com domain names in bulk, brand owners who maintain expensive defensive registrations, and registrars who no longer need to pass on cost increases to their consumers.<ref>[http://domainincite.com/11176-winners-and-losers-in-the-new-com-pricing-regime Winners and losers in the new .com pricing regime], DomainIncite.com. Published 30 November 2012.</ref>

"Consumers will benefit from  Verisign's removal of the automatic price increases," said [[Larry Strickling]] of [[NTIA]]. "At the same time, the agreement protects the security and stability of the Internet by allowing Verisign to take cost-based price increases where justified."<ref>[http://www.ntia.doc.gov/press-release/2012/department-commerce-approves-verisign-icann-com-registry-renewal-agreement Department of Commerce Approves Verisign-ICANN .com Registry Renewal Agreement], NTIA.doc.gov. Published 30 November 2012.</ref>

"Consumers will benefit from  Verisign's removal of the automatic price increases," said [[Larry Strickling]] of [[NTIA]]. "At the same time, the agreement protects the security and stability of the Internet by allowing Verisign to take cost-based price increases where justified."<ref>[http://www.ntia.doc.gov/press-release/2012/department-commerce-approves-verisign-icann-com-registry-renewal-agreement Department of Commerce Approves Verisign-ICANN .com Registry Renewal Agreement], NTIA.doc.gov. Published 30 November 2012.</ref>

If [[ICANN]]'s [[new gTLD]] program becomes successful and "market power" is removed from .com's, Verisign believes that all price caps on .com's could be lifted as early as 2014.<ref>[http://www.thedomains.com/2012/11/30/verisign-if-new-gtlds-are-successful-we-might-be-able-to-lift-all-price-caps-on-coms/ Verisign: If New gTLD’s Are Successful We Might Be Able To Lift All Price Caps On .Com’s], TheDomains.com. Published 30 November 2012.</ref>

If [[ICANN]]'s [[New gTLD Program]] becomes successful and "market power" is removed from .com's, Verisign believes that all price caps on .com's could be lifted as early as 2014.<ref>[http://www.thedomains.com/2012/11/30/verisign-if-new-gtlds-are-successful-we-might-be-able-to-lift-all-price-caps-on-coms/ Verisign: If New gTLD’s Are Successful We Might Be Able To Lift All Price Caps On .Com’s], TheDomains.com. Published 30 November 2012.</ref>

===.net Renewals===

===.net Renewals===

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 of the [[.net]] TLD expired, Verisign and five other companies bid for it. Verisign was supported by renowned IT companies like Microsoft, [[IBM]], [[Sun Microsystems]], and [[MCI]]. On June 8, 2005, ICANN announced that Verisign had been approved to operate [[.net]] until 2011.<ref>[http://www.icann.org/en/tlds/dotnet-reassignment/dotnet-general.htm General Information Regarding Designation of the Subsequent .net registry Operator], ICANN.org.</ref> These agreements have presumptive right of renewal clauses that encourage the registry operators to invest in critical Internet infrastructure. Verisign was subsequently approved to operate the .net registry through 2017.<ref>[http://www.internetnews.com/infra/icann-renews-verisigns-.net-contract.html ICANN Renews Verisign .net Contract], InternetNews.com. Published 5 July 2011.</ref>

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 the operation of the [[.net]] TLD expired, Verisign and five other companies bid for it. Verisign was supported by renowned IT companies like Microsoft, [[IBM]], [[Sun Microsystems]], and [[MCI]]. On June 8, 2005, ICANN announced that Verisign had been approved to operate [[.net]] until 2011.<ref>[http://www.icann.org/en/tlds/dotnet-reassignment/dotnet-general.htm General Information Regarding Designation of the Subsequent .net registry Operator], ICANN.org.</ref> These agreements have the presumptive right of renewal clauses that encourage the registry operators to invest in critical Internet infrastructure. Verisign was subsequently approved to operate the .net registry through 2017.<ref>[http://www.internetnews.com/infra/icann-renews-verisigns-.net-contract.html ICANN Renews Verisign .net Contract], InternetNews.com. Published 5 July 2011.</ref>

===.net Audit===

===.net Audit===

In January, 2013, Senior Vice President [[Pat Kane]] sent [[ICANN]] a letter stating that it had no intentions submitting to an ICANN audit of its [[.net]] registry. Kane wrote, "Verisign has no contractual obligations under its .net Registry Agreement with ICANN to comply with the proposed audit. Absent such express contractual obligations, Verisign will not submit itself to an audit by or at the direction of ICANN of its books and records." This comes directly after implementing a new "Contractual Compliance Audit Program", introduced under new CEO [[Fadi Chehadé]] in mid-late 2012 as a 3 year plan to ensure all registries and registrars are following their contracts. A registry audit would entail a review of compliance with [[Whois]], zone file access, data escrow, monthly reporting, and other policies outlined in the registry agreements. Mr. Chehadé had made a big focus of Contract Compliance and had promoted the head of Compliance, [[Maguy Serad]], to report directly to him.<ref>[http://domainincite.com/11560-in-major-snub-verisign-refuses-to-let-icann-audit-net In Major Sub Verisign Refuses to Let ICANN Audit Net, DomainIncite.com]Published & retrieved 11 Jan 2012</ref>

In January 2013, Senior Vice President [[Pat Kane]] sent [[ICANN]] a letter stating that it had no intentions of submitting to an ICANN audit of its [[.net]] registry. Kane wrote, "Verisign has no contractual obligations under its .net Registry Agreement with ICANN to comply with the proposed audit. Absent such express contractual obligations, Verisign will not submit itself to an audit by or at the direction of ICANN of its books and records." This comes directly after implementing a new "Contractual Compliance Audit Program", introduced under new CEO [[Fadi Chehadé]] in mid-late 2012 as a 3-year plan to ensure all registries and registrars are following their contracts. A registry audit would entail a review of compliance with [[Whois]], zone file access, data escrow, monthly reporting, and other policies outlined in the registry agreements. Mr. Chehadé had made a big focus of Contract Compliance and had promoted the head of Compliance, [[Maguy Serad]], to report directly to him.<ref>[http://domainincite.com/11560-in-major-snub-verisign-refuses-to-let-icann-audit-net In Major Sub Verisign Refuses to Let ICANN Audit Net, DomainIncite.com]Published & retrieved 11 Jan 2012</ref>

==New gTLDs==

==New gTLDs==

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.<ref>[http://tech.sina.com.cn/i/2011-12-20/10326538420.shtml .company .network Domain Names], Sina.com. Published 20 December 2011.</ref> This move was seen as potentially problematic given Verisign's own plans to seek the IDN equivalents of their [[.com]] and [[.net]] TLDs, such as their intention to apply for multiple transliterated versions of .com and .net.<ref>[http://www.managingip.com/Article/2761204/VeriSign-wants-com-and-net-IDNs.html Verisign Wants Com and Net], ManagingIP.com.  Published 3 February 2011.</ref> Verisign's [[Pat Kane]] later added in January 2012 that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be foreign language transliterations of [[.com]].<ref>[http://seekingalpha.com/article/322517-verisign-management-discusses-q4-2011-results-earnings-call-transcript?part=qanda 2011 Results Earnings Call Transcript], SeekingAlpha.com. Published 26 January 2012.</ref> Expected languages included Japanese, Korean, Chinese, Cyrillic, Arabic, and Hebrew.<ref>[http://domainnamewire.com/2012/01/26/verisign-plans-to-apply-for-about-12-new-top-level-domain-names/ Verisign Plans to Apply for About 12 New Top Level Domain Names], DomainNameWire.com. Published 26 January 2012.</ref> It was also noted then that Verisign had already been chosen to provide [[registry]] services for several [[Brand gTLD|.brand]] initiatives.<ref>[http://domainincite.com/verisign-to-apply-for-a-dozen-new-gtlds/ Verisign to Apply for a Dozen New gTLDs], DomainIncite.com. Published 27 January 2012.</ref>

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.<ref>[http://tech.sina.com.cn/i/2011-12-20/10326538420.shtml .company .network Domain Names], Sina.com. Published 20 December 2011.</ref> This move was seen as potentially problematic given Verisign's own plans to seek the IDN equivalents of their [[.com]] and [[.net]] TLDs, such as their intention to apply for multiple transliterated versions of .com and .net.<ref>[http://www.managingip.com/Article/2761204/VeriSign-wants-com-and-net-IDNs.html Verisign Wants Com and Net], ManagingIP.com.  Published 3 February 2011.</ref> Verisign's [[Pat Kane]] later added in January 2012 that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be foreign language transliterations of [[.com]].<ref>[http://seekingalpha.com/article/322517-verisign-management-discusses-q4-2011-results-earnings-call-transcript?part=qanda 2011 Results Earnings Call Transcript], SeekingAlpha.com. Published 26 January 2012.</ref> Expected languages included Japanese, Korean, Chinese, Cyrillic, Arabic, and Hebrew.<ref>[http://domainnamewire.com/2012/01/26/verisign-plans-to-apply-for-about-12-new-top-level-domain-names/ Verisign Plans to Apply for About 12 New Top Level Domain Names], DomainNameWire.com. Published 26 January 2012.</ref> It was also noted then that Verisign had already been chosen to provide [[registry]] services for several [[Brand gTLD|.brand]] initiatives.<ref>[http://domainincite.com/verisign-to-apply-for-a-dozen-new-gtlds/ Verisign to Apply for a Dozen New gTLDs], DomainIncite.com. Published 27 January 2012.</ref>

During its first quarter earnings report, on April 26, 2012, it was confirmed that Verisign would be applying for 14 new gTLDs, 12 of which are foreign language transliterations of .com and .net.

During its first-quarter earnings report, on April 26, 2012, it was confirmed that Verisign would be applying for 14 new gTLDs, 12 of which are foreign language transliterations of .com and .net.

The languages chosen for transliterations include: Thai, Deva, Korean (Hang), Chinese (Hant/Traditional & Hans/Simplified), Hebrew, Russian, Arabic, Japanese. The two non-IDN applications by the company are for [[.comsec]] and [[.verisign]].

The languages chosen for transliterations include: Thai, Deva, Korean (Hang), Chinese (Hant/Traditional & Hans/Simplified), Hebrew, Russian, Arabic, Japanese. The two non-IDN applications by the company are for [[.comsec]] and [[.verisign]].

In July 2013, Verisign's [[Pat Kane]] outlined in an article<ref>[http://blogs.verisigninc.com/blog/entry/update_on_verisign_s_idn Update on Versigns IDNs Versigininc.com] Retrieved 4 Oct 2013</ref> the company's plans for allowing existing registrants of second-level [[IDN]] domain names to secure the matching domain under Verisign's new [[IDN]] gTLDs. For example, if you're the registrant of the Hebrew word for "website" that is registered as a second-level domain under [[.com]], you will have the rights to that second-level name under the gTLD "[[.קוֹם|קוֹם.]]" but you will not have the rights under the Hebrew transliteration of ".net" if it existed.<ref>[http://domainincite.com/13702-verisign-lays-out-buy-once-idn-gtld-plans Verisign lays out buy once IDN gTLD plans, Domain Incite] Retrieved 4 Oct 2013</ref>

In July 2013, Verisign's [[Pat Kane]] outlined in an article<ref>[http://blogs.verisigninc.com/blog/entry/update_on_verisign_s_idn Update on Versign's IDNs Versigininc.com] Retrieved 4 Oct 2013</ref> the company's plans for allowing existing registrants of second-level [[IDN]] domain names to secure the matching domain under Verisign's new [[IDN]] gTLDs. For example, if you're the registrant of the Hebrew word for "website" that is registered as a second-level domain under [[.com]], you will have the rights to that second-level name under the gTLD "[[.קוֹם|קוֹם.]]" but you will not have the rights under the Hebrew transliteration of ".net" if it existed.<ref>[http://domainincite.com/13702-verisign-lays-out-buy-once-idn-gtld-plans Verisign lays out to buy once IDN gTLD plans, Domain Incite] Retrieved 4 Oct 2013</ref>

===Clients===

===Clients===

"This proposed model simplifies the ICANN model by decreasing the coupling between the Trademark Clearinghouse (TMCH) and registries. The model is as follows:

"This proposed model simplifies the ICANN model by decreasing the coupling between the Trademark Clearinghouse (TMCH) and registries. The model is as follows:

# The TMCH generates and maintains a global public-private key pair and provides the public key to the registrars and registries. This can be done simply by publishing the public key on the TMCH website. This website should be provided over HTTPs using a digital certificate from a reputable certificate authority. The DNS records associated with this website should be protected using DNSSEC. We believe that there are no issues with security of the public key and anyone in the world can have access to it.

# The TMCH generates and maintains a global public-private key pair and provides the public key to the registrars and registries. This can be done simply by publishing the public key on the TMCH website. This website should be provided over HTTPs using a digital certificate from a reputable certificate authority. The DNS records associated with this website should be protected using DNSSEC. We believe that there are no issues with the security of the public key and anyone in the world can have access to it.

# Once the TMCH has authenticated the trademark information provided by the trademark holder, and validated the use requirements for eligibility to participate in sunrise, the TMCH signs the sunrise (trademark) data with its private key. The digitally signed information is referred to as the ‘Signed Mark Data’ (SMD) and is provided to the mark holder. Typically, this would be in the form of a file download from the TMCH website. The SMD includes all of the domain labels (domain names) possible to be used in registrations for the validated trademark (IDN variants excluded).

# Once the TMCH has authenticated the trademark information provided by the trademark holder and validated the use requirements for eligibility to participate in sunrise, the TMCH signs the sunrise (trademark) data with its private key. The digitally signed information is referred to as the ‘Signed Mark Data’ (SMD) and is provided to the mark holder. Typically, this would be in the form of a file download from the TMCH website. The SMD includes all of the domain labels (domain names) possible to be used in registrations for the validated trademark (IDN variants excluded).

# As each TLD begins its sunrise phase, the mark holder selects a registrar and provides the registrar with the SMD as part of an application for a name within the applicable sunrise period. The registrar (or its reseller) has the ability, if it chooses to, to validate the information using the TMCH public key and then forward the information to the registry to create the application.

# As each TLD begins its sunrise phase, the mark holder selects a registrar and provides the registrar with the SMD as part of an application for a name within the applicable sunrise period. The registrar (or its reseller) has the ability, if it chooses to, to validate the information using the TMCH public key and then forward the information to the registry to create the application.

# The registry verifies the signature of the SMD with the public key and verifies that one of the labels within the SMD matches the domain label being registered. The registry may also then verify any other information in the SMD to ensure it is consistent with the registry’s sunrise eligibility policies. The application, or domain name, is then created.

# The registry verifies the signature of the SMD with the public key and verifies that one of the labels within the SMD matches the domain label being registered. The registry may also then verify any other information in the SMD to ensure it is consistent with the registry’s sunrise eligibility policies. The application, or domain name, is then created.

===Raises Questions on Security & Readiness===

===Raises Questions on Security & Readiness===

In late March 2013, Verisign sent [[ICANN]] and the [[DOC|U.S. Dept. of Commerce]] a report analyzing the readiness of [[ICANN]] to safely implement its [[New gTLD Program]]. The 21 page document covered a large variety of issues but focused on readiness and potential weak points in the program and the implementation of New gTLDs. Many speculated at reasons beyond public welfare for the report being issued, such as an interest in delaying the program due to its vested interest in the .com market dominance. Still, Verisign has over 200 new gTLD clients that are looking towards implementation in order to start profiting from or otherwise utilizing their applied-for extensions. ICANN's CEO, Mr. [[Fadi Chehadé]], defended the organization's readiness and noted that the report contained no new information or areas that have not been addressed, stressing that the program was continuing on schedule with an acute attention to all matters of security.<ref>[http://domainincite.com/12465-chehade-says-no-delay-as-verisign-drops-a-security-bomb-on-icann Chehade Says No Delay as Verisign Drops a Security Bomb, DomainIncite.com] Published& Retrieved March 29 2013</ref>

In late March 2013, Verisign sent [[ICANN]] and the [[DOC|U.S. Dept. of Commerce]] a report analyzing the readiness of [[ICANN]] to safely implement its [[New gTLD Program]]. The 21-page document covered a large variety of issues but focused on readiness and potential weak points in the program and the implementation of New gTLDs. Many speculated at reasons beyond public welfare for the report being issued, such as an interest in delaying the program due to its vested interest in the .com market dominance. Still, Verisign has over 200 new gTLD clients that are looking towards implementation in order to start profiting from or otherwise utilizing their applied-for extensions. ICANN's CEO, Mr. [[Fadi Chehadé]], defended the organization's readiness and noted that the report contained no new information or areas that have not been addressed, stressing that the program was continuing on schedule with acute attention to all matters of security.<ref>[http://domainincite.com/12465-chehade-says-no-delay-as-verisign-drops-a-security-bomb-on-icann Chehade Says No Delay as Verisign Drops a Security Bomb, DomainIncite.com] Published& Retrieved March 29 2013</ref>

== Security Breach==

== Security Breach==

== Selling Authentication Services Business to Symantec ==

== Selling Authentication Services Business to Symantec ==

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

Verisign's previous logo, a checkmark and the tag "VeriSign Secured", is one of the most trusted marks of secured websites. Even though providing Internet security was an initial objective of the company, Verisign shifted its priority over time to website management and its 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.<ref name="reuters1"></ref>  Because of this deal, Symantec now has the right to VeriSign's authentication logo and the "VeriSign Secured" tag for [[SSL]] certification. Verisign's Security Services included managing services such as 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.

Verisign began by selling some of its services piecemeal. Finally, in May 2010, Verisign sold the entire division to Symantec for 1.28 million.<ref name="reuters1"></ref>  Because of this deal, Symantec now has the right to VeriSign's authentication logo and the "VeriSign Secured" tag for [[SSL]] certification. Verisign's Security Services included managing services such as 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.

== BulkRegister Accusations ==

== BulkRegister Accusations ==

In May 2002, [[BulkRegister]] sued Verisign for [[domain slamming]].<ref>[http://www.internetnews.com/xSP/article.php/1121321/BulkRegister-Sues-VeriSign-for-Slamming.htm BulkRegister Sues VeriSign for Slamming]. Internet News. Published 2002 May 13.</ref> 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 fines. However, Verisign was barred from suggesting domain renewal or expiration prospects.<ref>[http://www.theregister.co.uk/2003/09/25/verisign_slammed_for_domain_renewal/ VeriSign slammed for domain renewal scam]. The Register. Published 2003 September 25.</ref>

In May 2002, [[BulkRegister]] sued Verisign for [[domain slamming]].<ref>[http://www.internetnews.com/xSP/article.php/1121321/BulkRegister-Sues-VeriSign-for-Slamming.htm BulkRegister Sues VeriSign for Slamming]. Internet News. Published 2002 May 13.</ref> 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 fines. However, Verisign was barred from suggesting domain renewal or expiration prospects.<ref>[http://www.theregister.co.uk/2003/09/25/verisign_slammed_for_domain_renewal/ VeriSign slammed for domain renewal scam]. The Register. Published 2003 September 25.</ref>

==Waiting List Service (WLS)==

==Waiting List Service (WLS)==

On January 26, 2004, ICANN General Counsel and Secretary [[John Jeffrey]] sent Verisign the Conclusion of the Negotiation regarding ICANN's conditions prior to the implementation of the WLS wherein a special provision stated that the amendments made to the [[.com]] and [[.net]] registry needed approval from [[DOC|U.S. Department of Commerce]] (DOC).<ref>[http://www.icann.org/en/correspondence/jeffrey-to-lewis-26jan04.pdf Conclusion of WLS Negotiations]. ICANN. Retrieved 2004 January 26.</ref> The implementation of the WLS was delayed due to Verisign's failure to seek approval from the DOC and to make necessary changes to its .net registry agreement.<ref>[http://www.icann.org/en/legal/verisign-v-icann/icann-net-arbitration-request-12nov04.pdf International Chamber of Commerce International Court of Arbitration ICANN vs. Verisign]. ICANN. Published 2004 November 12.</ref>

On January 26, 2004, ICANN General Counsel and Secretary [[John Jeffrey]] sent Verisign the Conclusion of the Negotiation regarding ICANN's conditions prior to the implementation of the WLS wherein a special provision stated that the amendments made to the [[.com]] and [[.net]] registry needed approval from [[DOC|U.S. Department of Commerce]] (DOC).<ref>[http://www.icann.org/en/correspondence/jeffrey-to-lewis-26jan04.pdf Conclusion of WLS Negotiations]. ICANN. Retrieved 2004 January 26.</ref> The implementation of the WLS was delayed due to Verisign's failure to seek approval from the DOC and to make necessary changes to its .net registry agreement.<ref>[http://www.icann.org/en/legal/verisign-v-icann/icann-net-arbitration-request-12nov04.pdf International Chamber of Commerce International Court of Arbitration ICANN vs. Verisign]. ICANN. Published 2004 November 12.</ref>

Verisign filed a legal case against ICANN on February 26, 2004. The company accused ICANN of seriously abusing its technical coordination function by requiring Verisign to stop its Site Finder Service to the .com and .net domain name space. The company also noted the delay of the implementation of the WLS and the inclusion of new procedures not required by the 2001 .com and .net registry agreements, such as the price reduction for the WLS service. According to Verisign, the conditions benefited the different ICANN constituencies but were unfavorable to the company. Furthermore, Verisign pointed out that ICANN denied the company the ability to profit by delaying the WLS while other companies were able to offer similar services to Internet users.<ref>[http://www.icann.org/en/legal/verisign-v-icann/verisign-v-icann-complaint-26feb04.pdf Verisign Vs. ICANN]. ICANN. Published 2004 February 26.</ref>

Verisign filed a legal case against ICANN on February 26, 2004. The company accused ICANN of seriously abusing its technical coordination function by requiring Verisign to stop its Site Finder Service to the .com and .net domain namespace. The company also noted the delay of the implementation of the WLS and the inclusion of new procedures not required by the 2001 .com and .net registry agreements, such as the price reduction for the WLS service. According to Verisign, the conditions benefited the different ICANN constituencies but were unfavorable to the company. Furthermore, Verisign pointed out that ICANN denied the company the ability to profit by delaying the WLS while other companies were able to offer similar services to Internet users.<ref>[http://www.icann.org/en/legal/verisign-v-icann/verisign-v-icann-complaint-26feb04.pdf Verisign Vs. ICANN]. ICANN. Published 2004 February 26.</ref>

United States District Court Judge Howard Matz dismissed the lawsuit on August 26, 2004. According to the judge, Verisign failed to provide sufficient evidence to prove its anti-trust complaint against ICANN.<ref>[http://www.prnewswire.com/news-releases/us-federal-district-court-dismisses-verisigns-anti-trust-claim-against-icann-with-prejudice-71761617.html U.S. Federal District Court Dismisses VeriSign's Anti-Trust Claim Against ICANN with Prejudice]. PR News Wire.</ref> Verisign elevated the case to the Superior Court of California in Los Angeles,<ref>[http://www.fateback.com/news/domain_names/data/VeriSign_refiles_lawsuit_against_ICANN.html Verisign Re-files lawsuit against ICANN]. Face Back. Published 2004 September 1.</ref> and the two parties settled the lawsuit on February 28, 2006. The settlement permanently killed the WLS.<ref>[http://www.icann.org/en/announcements/announcement-28feb06.htm Settlement Agreement]. ICANN. Published 2006 February 28.</ref>

United States District Court Judge Howard Matz dismissed the lawsuit on August 26, 2004. According to the judge, Verisign failed to provide sufficient evidence to prove its antitrust complaint against ICANN.<ref>[http://www.prnewswire.com/news-releases/us-federal-district-court-dismisses-verisigns-anti-trust-claim-against-icann-with-prejudice-71761617.html U.S. Federal District Court Dismisses VeriSign's Anti-Trust Claim Against ICANN with Prejudice]. PR News Wire.</ref> Verisign elevated the case to the Superior Court of California in Los Angeles,<ref>[http://www.fateback.com/news/domain_names/data/VeriSign_refiles_lawsuit_against_ICANN.html Verisign Re-files lawsuit against ICANN]. Face Back. Published 2004 September 1.</ref> and the two parties settled the lawsuit on February 28, 2006. The settlement permanently killed the WLS.<ref>[http://www.icann.org/en/announcements/announcement-28feb06.htm Settlement Agreement]. ICANN. Published 2006 February 28.</ref>

==Infrastructure Research Grant Program==

==Infrastructure Research Grant Program==

The Infrastructure Research Program was launched by Verisign in 2010 as part of the 25th anniversary celebration of the [[.com]] TLD. The company awarded a total of $300,000 to four compelling infrastructure research projects. Each project was given $75,000 and the program concluded in October 2011. In January 2012, the company announced that it will award two new $200,000 infrastructure research grants to compelling projects concentrating on topics of internet access and global infrastructural challenges, particularly those in developing countries. Experts in technology and policy development who have made significant contributions in the growth of the internet industry will judge the research project proposals.<ref>[http://www.circleid.com/posts/20120117_verisign_to_award_new_infrastructure_research_grants/ Verisign to Award New Infrastructure Research Grants]. Circle ID. Published 2012 January 17.</ref>

The Infrastructure Research Program was launched by Verisign in 2010 as part of the 25th-anniversary celebration of the [[.com]] TLD. The company awarded a total of $300,000 to four compelling infrastructure research projects. Each project was given $75,000 and the program concluded in October 2011. In January 2012, the company announced that it will award two new $200,000 infrastructure research grants to compelling projects concentrating on topics of internet access and global infrastructural challenges, particularly those in developing countries. Experts in technology and policy development who have made significant contributions to the growth of the internet industry will judge the research project proposals.<ref>[http://www.circleid.com/posts/20120117_verisign_to_award_new_infrastructure_research_grants/ Verisign to Award New Infrastructure Research Grants]. Circle ID. Published 2012 January 17.</ref>

==History==

==History==

* '''1995 August''' - Verisign appointed [[Stratton Sclavos]] President and CEO.<ref>[http://www.thefreelibrary.com/VeriSign+appoints+Stratton+D.+Sclavos+president+and+CEO%3B+Industry...-a017194995 VeriSign appoints Stratton D. Sclavos president and CEO]. The Free Library. Published 1995 August 17.</ref>

* '''1995 August''' - Verisign appointed [[Stratton Sclavos]] President and CEO.<ref>[http://www.thefreelibrary.com/VeriSign+appoints+Stratton+D.+Sclavos+president+and+CEO%3B+Industry...-a017194995 VeriSign appoints Stratton D. Sclavos president and CEO]. The Free Library. Published 1995 August 17.</ref>

* '''1996 January''' - Verisign introduced the first online digital certificate issue system at the [[RSA]] Data Security Conference in San Francisco.<ref>[http://www.referenceforbusiness.com/history2/29/VeriSign-Inc.html VeriSign, Inc. - Company Profile]. Reference for Business.</ref> Verisign also announced an agreement with [[Terisa Systems]] to develop a new and complete Internet security solutions.<ref> [http://www.thefreelibrary.com/VERISIGN+AND+TERISA+SYSTEMS+PARTNER+TO+DELIVER+INTERNET+COMMERCE...-a017778731 Verisign and Turisa Systems to Partner]. The Free Library. Published 1996 January 16.</ref>

* '''1996 January''' - Verisign introduced the first online digital certificate issue system at the [[RSA]] Data Security Conference in San Francisco.<ref>[http://www.referenceforbusiness.com/history2/29/VeriSign-Inc.html VeriSign, Inc. - Company Profile]. Reference for Business.</ref> Verisign also announced an agreement with [[Terisa Systems]] to develop new and complete Internet security solutions.<ref> [http://www.thefreelibrary.com/VERISIGN+AND+TERISA+SYSTEMS+PARTNER+TO+DELIVER+INTERNET+COMMERCE...-a017778731 Verisign and Turisa Systems to Partner]. The Free Library. Published 1996 January 16.</ref>

* '''1996 January''' - 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. <ref> [http://www.microsoft.com/presspass/press/1996/aug96/clientpr.mspx Microsoft and VeriSign Announce Availability of Digital IDs For Microsoft Internet Explorer 3.0 User]. Microsoft. Published 1996 August 13.</ref>  

* '''1996 January''' - Secure Email was launched. Verisign launched 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. <ref> [http://www.microsoft.com/presspass/press/1996/aug96/clientpr.mspx Microsoft and VeriSign Announce Availability of Digital IDs For Microsoft Internet Explorer 3.0 User]. Microsoft. Published 1996 August 13.</ref>  

* '''1997''' - the First Internet Commerce Transactions Linking Europe, Asia, and the United States was conducted by [[Verifone]] and Verisign.<ref> [http://www.thefreelibrary.com/VeriFone+and+VeriSign+Conduct+First+Internet+Commerce+Transactions...-a019591264 VeriFone and VeriSign Conduct First Internet Commerce Transactions Linking Europe, Asia and the United States Through Global Security Standard]. The Free Library. Published 1997 July 18</ref> The United States [[DOC|Department of Commerce]] approved VeriSign's plans to issue new Verisign Global Server IDs in June 1997, which allowed 128-bit encryption.

* '''1997''' - the First Internet Commerce Transactions Linking Europe, Asia, and the United States was conducted by [[Verifone]] and Verisign.<ref> [http://www.thefreelibrary.com/VeriFone+and+VeriSign+Conduct+First+Internet+Commerce+Transactions...-a019591264 VeriFone and VeriSign Conduct First Internet Commerce Transactions Linking Europe, Asia and the United States Through Global Security Standard]. The Free Library. Published 1997 July 18</ref> The United States [[DOC|Department of Commerce]] approved VeriSign's plans to issue new Verisign Global Server IDs in June 1997, which allowed 128-bit encryption.

* '''1998 November''' - Verisign offered Y2K testing certs for free.

* '''1998 November''' - Verisign offered Y2K testing certs for free.

* '''1998 December''' - Verisign introduced digital certificate service for Wireless Application Protocol (WAP) servers and gateways.<ref>[http://www.wapforum.org/new/122199_verisign.htm Verisign Launches World's Most Comprehensive Digital Certificate Service for Wireless Web Servers]. WAP Forum. Published 1999 December 21.</ref>  

* '''1998 December''' - Verisign introduced a digital certificate service for Wireless Application Protocol (WAP) servers and gateways.<ref>[http://www.wapforum.org/new/122199_verisign.htm Verisign Launches World's Most Comprehensive Digital Certificate Service for Wireless Web Servers]. WAP Forum. Published 1999 December 21.</ref>  

* '''2000 March''' - Verisign acquired [[Network Solutions]] for $21 billion USD, which was the largest Internet purchase to date.<ref>[http://about-networksolutions.com/corporate-history.php Corporate History]. Network Solutions.</ref><ref name="networksolutions">[http://money.cnn.com/2000/03/07/deals/verisign/ VeriSign buys domain firm]. CNN Money. Published 2000 March 7.</ref>

* '''2000 March''' - Verisign acquired [[Network Solutions]] for $21 billion USD, which was the largest Internet purchase to date.<ref>[http://about-networksolutions.com/corporate-history.php Corporate History]. Network Solutions.</ref><ref name="networksolutions">[http://money.cnn.com/2000/03/07/deals/verisign/ VeriSign buys domain firm]. CNN Money. Published 2000 March 7.</ref>

* '''2006 December''' - Verisign introduced Extended Validation [[SSL]] Certificates, standard practices for certificate validation and display approved by a group of leading [[SSL Certificate Authorities]] and browser vendors.<ref>[https://www.symantec.com/page.jsp?id=how-ssl-works How SSL Works]. Verisign.</ref>

* '''2006 December''' - Verisign introduced Extended Validation [[SSL]] Certificates, standard practices for certificate validation and display approved by a group of leading [[SSL Certificate Authorities]] and browser vendors.<ref>[https://www.symantec.com/page.jsp?id=how-ssl-works How SSL Works]. Verisign.</ref>

* '''2007 November''' - Verisign announced plans to divest in its slower growing units and invest more in website naming and Internet security services. Projections suggested that these steps would cut Verisign's workforce in half.<ref>[http://www.reuters.com/article/idUSN1416428420071114 VeriSign to divest slower units, sees staff halved]. Reuters. Published 2007 November 14.</ref>  

* '''2007 November''' - Verisign announced plans to divest in its slower-growing units and invest more in website naming and Internet security services. Projections suggested that these steps would cut Verisign's workforce in half.<ref>[http://www.reuters.com/article/idUSN1416428420071114 VeriSign to divest slower units, sees staff halved]. Reuters. Published 2007 November 14.</ref>  

* '''2008''' - Verisign sold its global Digital Brand Management Services business for US$50 million to [[MelbourneIT]].<ref>[http://www.thewhir.com/web-hosting-news/050108_Melbourne_IT_Buys_VeriSign_Assets Melbourne IT Buys VeriSign Assets]. The Whir. Published 2008 May 1.</ref>

* '''2008''' - Verisign sold its global Digital Brand Management Services business for US$50 million to [[MelbourneIT]].<ref>[http://www.thewhir.com/web-hosting-news/050108_Melbourne_IT_Buys_VeriSign_Assets Melbourne IT Buys VeriSign Assets]. The Whir. Published 2008 May 1.</ref>

* '''2010 August''' - Verisign announced that it would move its headquarters from Mountain View, California to Reston, Virginia within the coming year. The move was explained given that 95% of the company's business is based on the East coast.<ref>[http://www.bizjournals.com/washington/blog/2010/08/verisign_shifts_headquarters_to_virginia.html Verisign Shifts Headquarters to Virginia]. Biz Journals. Published 2010 August 27.</ref>

* '''2010 August''' - Verisign announced that it would move its headquarters from Mountain View, California to Reston, Virginia within the coming year. The move was explained given that 95% of the company's business is based on the East coast.<ref>[http://www.bizjournals.com/washington/blog/2010/08/verisign_shifts_headquarters_to_virginia.html Verisign Shifts Headquarters to Virginia]. Biz Journals. Published 2010 August 27.</ref>

* '''2011 July''' - [[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.<ref>[http://www.thewhir.com/web-hosting-news/072911_VeriSign_CEO_Resigns_Founder_and_Chairman_Resumes_CEO_Duties Verisign CEO resigns.] The Wir. </ref> Another prominent executive, CFO Brian Robins, resigned in September, 2011. This happened as Verisign's stocks suffered and rumors of a buyout started circulating.<ref>[http://domainincite.com/verisign-cfo-quits-after-buyout-rumors/ VeriSign CFO quits]. Domain Incite. Published 2011 September 8.</ref>

* '''2011 July''' - [[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.<ref>[http://www.thewhir.com/web-hosting-news/072911_VeriSign_CEO_Resigns_Founder_and_Chairman_Resumes_CEO_Duties Verisign CEO resigns.] The Wir. </ref> Another prominent executive, CFO Brian Robins, resigned in September 2011. This happened as Verisign's stocks suffered and rumors of a buyout started circulating.<ref>[http://domainincite.com/verisign-cfo-quits-after-buyout-rumors/ VeriSign CFO quits]. Domain Incite. Published 2011 September 8.</ref>

* '''2011 October''' - 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.<ref>[http://domainnamewire.com/2011/10/11/verisign-proposes-takedown-procedures-and-malware-scanning-for-com/ VeriSign Proposes Takedown Procedures and Malware Scanning for .Com]. Domain Name Wire. Published 2011 October 11.</ref> The policy would also allow Verisign to shut down websites at the request of law enforcement officials, and possibly for trademark interests.<ref>[http://www.circleid.com/posts/20111014_verisign_proposal_sudden_withdrawal_of_domain_anti_abuse_policy/ Of Canaries and Coal Mines: Verisign's Proposal and Sudden Withdrawal of Domain Anti-Abuse Policy]. CircleID. Published 2011 October 14.</ref> 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.<ref>[http://domainincite.com/registrars-not-happy-with-verisign-abuse-plans/ Registrars not happy with VeriSign abuse plans]. Domain Incite. Published 2011 October 12.</ref> Two days after releasing the proposal, Verisign withdrew the request.<ref>[http://domainnamewire.com/2011/10/13/breaking-verisign-withdraws-request-for-domain-takedown/ VeriSign Withdraws Request for Domain Takedown]. Domain Name Wire. Published 2011 October 13.</ref>

* '''2011 October''' - 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.<ref>[http://domainnamewire.com/2011/10/11/verisign-proposes-takedown-procedures-and-malware-scanning-for-com/ VeriSign Proposes Takedown Procedures and Malware Scanning for .Com]. Domain Name Wire. Published 2011 October 11.</ref> The policy would also allow Verisign to shut down websites at the request of law enforcement officials, and possibly for trademark interests.<ref>[http://www.circleid.com/posts/20111014_verisign_proposal_sudden_withdrawal_of_domain_anti_abuse_policy/ Of Canaries and Coal Mines: Verisign's Proposal and Sudden Withdrawal of Domain Anti-Abuse Policy]. CircleID. Published 2011 October 14.</ref> 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.<ref>[http://domainincite.com/registrars-not-happy-with-verisign-abuse-plans/ Registrars not happy with VeriSign abuse plans]. Domain Incite. Published 2011 October 12.</ref> Two days after releasing the proposal, Verisign withdrew the request.<ref>[http://domainnamewire.com/2011/10/13/breaking-verisign-withdraws-request-for-domain-takedown/ VeriSign Withdraws Request for Domain Takedown]. Domain Name Wire. Published 2011 October 13.</ref>

* '''2011 October''' - Verisign's registry management for [[.com]] domains passed the 100 million mark.<ref>[http://domainincite.com/com-passed-100-million-mark-in-october/ Com Passed 100 million mark in October]. Domain Incite. Published 2012 February 2.</ref>

* '''2011 October''' - Verisign's registry management for [[.com]] domains passed the 100 million mark.<ref>[http://domainincite.com/com-passed-100-million-mark-in-october/ Com Passed 100 million mark in October]. Domain Incite. Published 2012 February 2.</ref>

* July 2005 - Verisign aquires security intelligence specialist '''iDefense''' for $40 Million.

* July 2005 - Verisign aquires security intelligence specialist '''iDefense''' for $40 Million.

* March 2006 - Verisign anounced acquisition of '''Kontiki''' for $62 million.<ref>[http://www.zdnet.com/news/verisign-to-acquire-kontiki/147195 VeriSign to acquire Kontiki]. ZDNet. Published 2006 March 13.</ref>

* March 2006 - Verisign announced the acquisition of '''Kontiki''' for $62 million.<ref>[http://www.zdnet.com/news/verisign-to-acquire-kontiki/147195 VeriSign to acquire Kontiki]. ZDNet. Published 2006 March 13.</ref>

* May 2006 - Acquisition of '''GeoTrust Inc.''', for $125 million.<ref>[http://news.netcraft.com/archives/2006/05/17/verisign_to_buy_geotrust_combining_top_ssl_providers.html Compliance and Privacy]. Net Craft. Published 2006 May 17.</ref>

* May 2006 - Acquisition of '''GeoTrust Inc.''', for $125 million.<ref>[http://news.netcraft.com/archives/2006/05/17/verisign_to_buy_geotrust_combining_top_ssl_providers.html Compliance and Privacy]. Net Craft. Published 2006 May 17.</ref>