Changes

{{CompanyInfo|

{{Actor

| logo            = verisignlogo.png

| platsponsor = ICANNWiki [[Sponsorship|Platinum Sponsor]]

|actor type=Root Server Operator, Domain Name Registry

| type            = Public

|country=USA

| industry        = Internet, Communications, Registry

|website=[https://www.verisign.com Verisign.com]

| founded         = 1995

|issue areas=DNS

| founders       = [[Jim Bidzos]]

|Logo=verisignlogo.png

|founded=1995

| headquarters   = 12061 Bluemont Way,<br/>Reston, VA 20190

|founders=[[Jim Bidzos]]

|headquarters=12061 Bluemont Way,<br/>Reston, VA 20190

|employees=1,009 worldwide<ref name="factsheet">[http://www.verisigninc.com/en_US/company-information/about-verisign/fact-sheet/index.xhtml Fact Sheet]. Verisign.</ref>

|revenue=$772 million (2011 Naming Services Revenue)<ref name="factsheet"></ref>

| employees       = 1,009 worldwide<ref name="factsheet">[http://www.verisigninc.com/en_US/company-information/about-verisign/fact-sheet/index.xhtml Fact Sheet]. Verisign.</ref>

|twitter=VERISIGN

| revenue         = $772 million (2011 Naming Services Revenue)<ref name="factsheet"></ref>

|keypeople=[[Jim Bidzos]], Founder, Chairman, CEO<br>

[[Pat Kane]], SVP, Naming and Directory Services<br>

| twitter         = VERISIGN

| keypeople       =  

[[Jim Bidzos]], Founder, Chairman, CEO<br>

[[Pat Kane]], SVP and GM of Naming Services<br>

[[Keith Drazek]], Director of Policy<br>

[[Keith Drazek]], Director of Policy<br>

[[Chuck Gomes]], VP of Policy and Compliance<br>

[[Chuck Gomes]], VP of Policy and Compliance<br>

[[Scott Schnell]], SVP of Marketing<br>

[[Scott Schnell]], SVP of Marketing<br>

[[George Kilguss III]] SVP and Chief Financial Officer.<br>

[[George Kilguss III]] SVP and Chief Financial Officer.<br>

[[Joe Waldron]], VP of Core Naming Services<br>

[[Joe Waldron]], VP of Core Naming Services<br>

}}

}}

'''Verisign''' is an Internet infrastructure service provider. It is based in Reston, VA and was founded in 1995. The company has offices around the world, in Virginia, California, Washington D.C., India, Brazil, China, Australia, Switzerland, and the UK.

'''Verisign''' is an Internet infrastructure service provider. It is based in Reston, VA and was founded in 1995. The company has offices around the world, in Virginia, California, Washington D.C., India, Brazil, China, Australia, Switzerland, and the UK.

Its registry services include operating the authoritative directory for the following [[TLD]]s:

Its registry services include operating the authoritative directory for the following [[TLD]]s:

 

* [[.com]]

* [[.com]]

* [[.net]]

* [[.net]]

* [[.edu]]

* [[.edu]]

* [[.gov]]

* [[.gov]]

 

Verisign runs two of the world's thirteen root servers: a.root-servers.net and j.root-servers.net, which are considered national IT assets by the U.S. Federal government.<ref name="factsheet"></ref> Verisign's average daily [[DNS|Domain Name System]] (DNS) query load for the first quarter of 2012 was 66 billion, with a peak of 74 billion; this represents a daily average increase of 4 percent over the previous quarter, while the peak decreased 37 percent.<ref>[http://www.marketwire.com/press-release/internet-grows-to-more-than-233-million-domain-names-in-the-first-quarter-of-2012-nasdaq-vrsn-1679901.htm Internet Grows to More than 233 million Domain names In The First Quarter]. Market Wire. Published 2012 July 13.</ref>

Verisign runs two of the world's thirteen root servers: a.root-servers.net and j.root-servers.net, which are considered national IT assets by the U.S. Federal government.<ref name="factsheet"></ref> During the fourth quarter of 2015, Verisign’s average daily Domain Name System (DNS) query load was approximately 123 billion queries per day across all TLDs operated by Verisign, with a peak of nearly 194 billion; this represents a daily average increase of 2.8 percent, while the peak decreased 67 percent.<ref>[http://www.businesswire.com/news/home/20160414006612/en/Internet-Grows-314-Million-Domain-Names-Fourth Business Wire: Internet Grows. Retrieved 17 Jun 2016.]</ref>

Verisign was also well-known for its authentication services, which included business authentication services such as implementing and operating secure networks, utilizing [[SSL]] protocol, encrypting transactions and communications, and user authentication services such as identity protection, fraud detection, and public key infrastructure.<ref>[http://finance.yahoo.com/q/pr?s=VRSN VRSN]. Yahoo! Finance.</ref> Those services were sold to [[Symantec]] in 2010.<ref name="reuters1">[http://www.reuters.com/article/2010/05/18/verisign-idUSN1816653320100518 UPDATE 2-Symantec close to buying VeriSign unit -- source]. Reuters. Published 2010 May 18.</ref> Prior to selling those services, Verisign had 3,000,000 certificates in operation, which made it the largest[[CA| Certificate Authority]] behind the encryption and authentication on the Internet.<ref>[http://en.wikipedia.org/wiki/Verisign Verisign, En.Wikipedia.org]</ref>

Verisign was also well-known for its authentication services, which included business authentication services such as implementing and operating secure networks, utilizing [[SSL]] protocol, encrypting transactions and communications, and user authentication services such as identity protection, fraud detection, and public key infrastructure.<ref>[http://finance.yahoo.com/q/pr?s=VRSN VRSN]. Yahoo! Finance.</ref> Those services were sold to [[Symantec]] in 2010.<ref name="reuters1">[http://www.reuters.com/article/2010/05/18/verisign-idUSN1816653320100518 UPDATE 2-Symantec close to buying VeriSign unit -- source]. Reuters. Published 2010 May 18.</ref> Prior to selling those services, Verisign had 3,000,000 certificates in operation, which made it the largest[[CA| Certificate Authority]] behind the encryption and authentication on the Internet.<ref>[http://en.wikipedia.org/wiki/Verisign Verisign, En.Wikipedia.org]</ref>

In October 2011, 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]</ref> In the first quarter of 2012, figures showed that it held more than 50% of registrations for all TLDs.<ref>[http://www.trefis.com/stock/vrsn/articles/108265/verisign-sits-pretty-at-39-registered-half-of-all-domain-names/2012-03-14 Verisign Sites Pretty at 39 Registered Half of All Domain Names, Trefis.com]</ref>  By the end of 2012's second quarter, Verisign had 240 million domain names across all of the TLDs it operates, with .com and .net holding 49% of the TLD market share, a drop of 2% from the first quarter.<ref>[http://www.trefis.com/stock/vrsn/articles/146666/verisigns-dropping-com-and-net-is-a-troubling-trend/2012-10-03 Verisign’s Dropping .com And .net Is A Troubling Trend, trefis.com]</ref>

In September 2015, Verisign's registry management for [[.com]] domains passed the 118 million mark.<ref>[https://www.verisign.com/en_US/internet-technology-news/verisign-press-releases/articles/index.xhtml?artLink=aHR0cDovL3ZlcmlzaWduLm13bmV3c3Jvb20uY29tL2FydGljbGUvcnNzP2lkPTE5ODUwMzk%3D Internet Grows. Retrieved 17 Jun 2016.]</ref> In the first quarter of 2012, figures showed that it held more than 50% of registrations for all TLDs.<ref>[http://www.trefis.com/stock/vrsn/articles/108265/verisign-sits-pretty-at-39-registered-half-of-all-domain-names/2012-03-14 Verisign Sites Pretty at 39 Registered Half of All Domain Names, Trefis.com]</ref>  By the end of 2012's second quarter, Verisign had 240 million domain names across all of the TLDs it operates, with .com and .net holding 49% of the TLD market share, a drop of 2% from the first quarter.<ref>[http://www.trefis.com/stock/vrsn/articles/146666/verisigns-dropping-com-and-net-is-a-troubling-trend/2012-10-03 Verisign’s Dropping .com And .net Is A Troubling Trend, trefis.com]</ref>

== Products and Services ==

== Products and Services ==

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

In March 2012, [[ICANN]] posted a proposal for Verisign's proposed renewal of the 2006 .com registry agreement between the two parties.<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,<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> potentially netting ICANN an additional $8 million in revenue annually.<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].

In August 2012, three of [[ICANN]]'s Constituencies ([[ALAC]], [[GNSO]] [[Business Constituency]], [[GNSO]] [[Intellectual Property Constituency]]) sent a letter to ICANN complaining that the organization held its renewal talks with Verisign behind closed doors and the result is that there are no [[Whois|Thick Whois]] requirements for the .com TLD.<ref>[http://domainnamewire.com/2012/08/21/constituencies-blast-icanns-closed-door-verisign-com-contract-renewal/ Constituencies Blast ICANNs Closed Door Verisign Com Contract Renewal, DomainNameWire.com]</ref> The decision could not move forward without approval from the [[DOC|Department of Commerce]],<ref name="verisign2"></ref> which Verisign received on November 29th, 2012.<ref name="verisign3">[https://investor.verisign.com/releaseDetail.cfm?ReleaseID=724216 Verisign Announces US Department of Commerce Approval of Newly Revised .com Registry Agreement], Verisign.com. Published 30 November 2012.</ref>

In August 2012, three of [[ICANN]]'s Constituencies ([[ALAC]], [[GNSO]] [[Business Constituency]], [[GNSO]] [[Intellectual Property Constituency]]) sent a letter to ICANN complaining that the organization held its renewal talks with Verisign behind closed doors and the result is that there are no [[Whois|Thick Whois]] requirements for the .com TLD.<ref>[http://domainnamewire.com/2012/08/21/constituencies-blast-icanns-closed-door-verisign-com-contract-renewal/ Constituencies Blast ICANNs Closed Door Verisign Com Contract Renewal, DomainNameWire.com]</ref> The decision could not move forward without approval from the [[DOC|Department of Commerce]], which Verisign received on November 29th, 2012.<ref name="verisign2"></ref><ref name="verisign3">[https://investor.verisign.com/releaseDetail.cfm?ReleaseID=724216 Verisign Announces US Department of Commerce Approval of Newly Revised .com Registry Agreement], Verisign.com. Published 30 November 2012.</ref>

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, as new price increases will be circumstancial and subject to Commerce Department approval.<ref name="verisign3"></ref>

* 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>

 

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

==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. They also announced that they had been contracted by 220 new gTLD applicants to provide technical backend services.<ref>[http://domainincite.com/breaking-verisign-has-220-new-gtld-clients/ Breaking: Verisign has 220 new gTLD clients], DomainIncite.com. Published 26 April 2012.</ref><ref>[http://domainnamewire.com/2012/04/26/verisign-is-backend-for-220-new-tld-applicants-and-applies-for-14-itself/ VeriSign is backend for 220 new TLD applicants and applies for 14 itself], DomainNameWire.com. Published 26 April 2012.</ref> They were the fourth most popular registry services provider, contracted by a total of 12% of applicants.<ref>[http://domainincite.com/9442-the-registry-back-end-market-numbers-are-in The Registry Back end Market Numbers are In], DomainIncite.com. Published 17 June 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.

In November 2012, the three entities most responsible for the Internet's [[Root Zone]], [[ICANN]], [[NTIA]], and Verisign, confirmed that they were prepared with enough resources to launch up to 100 new gTLDs per week.<ref>[http://domainincite.com/10961-icann-verisign-and-ntia-ready-for-100-new-gtlds-per-week ICANN Verisign and Ntia Ready for 100 New gTLDs per week], DomainIncite.com. Published 8 November 2012.</ref>

In November 2012, the three entities most responsible for the Internet's [[Root Zone]], [[ICANN]], [[NTIA]], and Verisign, confirmed that they were prepared with enough resources to launch up to 100 new gTLDs per week.<ref>[http://domainincite.com/10961-icann-verisign-and-ntia-ready-for-100-new-gtlds-per-week ICANN Verisign and Ntia Ready for 100 New gTLDs per week], DomainIncite.com. Published 8 November 2012.</ref>

This solution also works for those that are conducting 'first come – first served' style sunrise processes."<ref>[http://domainincite.com/10694-ip-interests-should-join-the-trademark-clearinghouse-meeting-on-tuesday IP interests Should Join The Trademark Clearinghouse Meeting], DomainIncite.com. Published 5 October 2012.</ref>

This solution also works for those that are conducting 'first come – first served' style sunrise processes."<ref>[http://domainincite.com/10694-ip-interests-should-join-the-trademark-clearinghouse-meeting-on-tuesday IP interests Should Join The Trademark Clearinghouse Meeting], DomainIncite.com. Published 5 October 2012.</ref>

== Security Breach==

== Security Breach==

* '''2012 June''' - ICANN renewed Verisign's contract to run the registry for the [[.com]] TLD.<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>

* '''2012 June''' - ICANN renewed Verisign's contract to run the registry for the [[.com]] TLD.<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>

==Acquisitions==

==Acquisitions==

==References==

==References==

{{reflist}}

{{reflist}}</div>

[[Category: Companies]]

[[Category: Companies]]

[[Category: Registries]]

[[Category: Registries]]

[[Category: Past Sponsor]]

[[Category: Past Supporters]]

[[Category: Sponsor]]