Changes

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

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

Its registry services include the provision of authoritative directory of:

Its registry services include the provision of authoritative directory of the following [[TLD]]s:

* [[.com]]

* [[.com]]

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

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

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

Verisign sold its Security Services to [[Symantec]] in May, 2010.  

In January, 2012, Verisign raised the wholesale prices of [[.com]] and [[.net]] registration by 7%, increasing the price from $7.34 to $7.85. [[Registrar]]s generally passed the price increase on to customers, and some used it as an excuse to raise their own prices beyond the 7% increase, with some increasing prices by 10 and 12 percent.<ref>[http://www.elliotsblog.com/registrars-increasing-prices-more-than-the-verisign-price-increase-7188 REgistrars Increasing Prices more than the Verisign Price Increase, ElliotsBlog.com]</ref>

In January, 2012, Verisign raised the wholesale prices of [[.com]] and [[.net]] registration by 7%, increasing the price from $7.34 to $7.85. [[Registrar]]s generally passed the price increase on to customers, and some used it as an excuse to raise their own prices beyond the 7% increase, with some increasing prices by 10 and 12 percent.<ref>[http://www.elliotsblog.com/registrars-increasing-prices-more-than-the-verisign-price-increase-7188 REgistrars Increasing Prices more than the Verisign Price Increase, ElliotsBlog.com]</ref>

== Selling Authentication Services Business to Symantec ==

== Selling Authentication Services Business to Symantec ==

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

Verisign's logo, a check mark and the tag "VeriSign Secured" is one of the most trusted trademark of secured website. Even though providing internet security was an initial objective of the company, over time Verisign shifted its priority 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>[http://www.reuters.com/article/idUSN1816653320100518 Reuters]</ref>  Because of this deal, Symantec now has the right to VeriSign's logo and the "VeriSign Secured" tag for SSL certification.

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>[http://www.reuters.com/article/idUSN1816653320100518 Reuters]</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.

== Domain Slamming ==

== Domain Slamming ==

== Security Breach==

== Security Breach==

As per routine for public companies, Verisign filed a quarterly 10-Q with the SEC in October 2011. The form includes a section asking about any security issues that could compromise the company, and in this instance Verisign disclosed a 2010 hack into limited parts of their computers and servers. While the disclosure suddenly got a lot of attention months later, one commentator notes that it is not a big deal at all and seemed to be a "minor network breach".<ref>[http://www.circleid.com/posts/20120202_world_notices_verisign_said_3_months_ago_they_had_security_breach/ World notices Verisign Said 3 months ago They Had Security Breach, CircleID.com]</ref> Verisign has since reaffirmed that its [[DNS]] was not compromised.<ref>[http://verisigninc.com/en_US/news-events/press-room/articles/index.xhtml?artLink=aHR0cHM6Ly9wcmVzcy52ZXJpc2lnbi5jb20vZWFzeWlyL2N1c3RvbXJlbC5kbz9lYXN5aXJpZD1BRkMwRkYwREI1QzU2MEQzJnZlcnNpb249bGl2ZSZwcmlkPTg0Nzg2OSZyZWxlYXNlanNwPWN1c3RvbV85Nw%3D%3D&CMP=TW Press Release, VerisignINC.com]</ref>

As per routine for public companies, Verisign filed a quarterly 10-Q with the SEC in October, 2011. The form includes a section asking about any security issues that could compromise the company, and in this instance Verisign disclosed a 2010 hack into limited parts of their computers and servers. While the disclosure suddenly got a lot of attention months later, one commentator notes that it was not a big deal at all and seemed to be a "minor network breach".<ref>[http://www.circleid.com/posts/20120202_world_notices_verisign_said_3_months_ago_they_had_security_breach/ World notices Verisign Said 3 months ago They Had Security Breach, CircleID.com]</ref> Verisign has since reaffirmed that its [[DNS]] was not compromised.<ref>[http://verisigninc.com/en_US/news-events/press-room/articles/index.xhtml?artLink=aHR0cHM6Ly9wcmVzcy52ZXJpc2lnbi5jb20vZWFzeWlyL2N1c3RvbXJlbC5kbz9lYXN5aXJpZD1BRkMwRkYwREI1QzU2MEQzJnZlcnNpb249bGl2ZSZwcmlkPTg0Nzg2OSZyZWxlYXNlanNwPWN1c3RvbV85Nw%3D%3D&CMP=TW Press Release, VerisignINC.com]</ref>

== Site Finder Service and Issues with ICANN ==

Verisign launched Site Finder September, 2007, which caused a user to be redirected to its Site Finder search engine after the user attempted to access an unregistered address. [[ICANN]] published a report against this policy stating "Verisign violated architectural principles, codes of conduct and good practice." [[ICANN]] had declared Site Finder in violation of Verisign's contracts for running the master address lists for [[.com]]<ref>"[http://www.out-law.com/page-4716 Out-law.com]</ref>

===Site Finder Service===

Later, [[ICANN]] asked Verisign to suspend its Site Finder service.<ref>[http://www.out-law.com/page-3921 Out-law.com]</ref>

Verisign launched Site Finder September, 2003, which caused a user to be redirected to its Site Finder search engine after the user attempted to access an unregistered address. [[ICANN]] published a report against this policy stating "Verisign violated architectural principles, codes of conduct and good practice," 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 Out-law.com]</ref> [[ICANN]] then asked Verisign to suspend its Site Finder service.<ref>[http://www.out-law.com/page-3921 Out-law.com]</ref> In October, a hearing took place place in Washington, D.C. to review technical issues with the U.S. Department of Commerce, which gives permission to Verisign to operate the [[DNS]] for [[.com]] and [[.net]]; VeriSign  subsequently shut down the service.

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

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

 

===.net Renewals===

Later, in February 2004, Verisign sued [[ICANN]] claiming it had unlawfully been prevented from adding new features to [[.com]] and [[.net]].<ref>[http://news.cnet.com/2100-1038-5165982.html CNet News]</ref>. In August 2004, the claim was moved from federal to California state court. <ref>[http://www.icann.org/en/general/litigation-verisign.htm ICANN.org]</ref> Eventually, in late 2005, Verisign and [[ICANN]] announced a proposed settlement introducing terms for new registry services in the [[.com]] registry.  

Also, in other domain name negotiations with [[ICANN]], Verisign traded the [[.org]] [[TLD]] in return for continued rights over [[.com]]. In mid 2005, when Verisign's contract for operation with [[.net]] expired, Verisign and 5 other companies bid for it. Verisign was supported by renowned IT companies like Microsoft, [[IBM]], [[Sun Microsystems]], and [[MCI]]. 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]</ref> These agreements have presumptive right of renewal clauses that encourage the registry operators to invest in critical Internet infrastructure. They were 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]</ref>

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]. It should be mentioned that the terms of these agreement were subject to public criticism.  

 

Also, in other domain name negotiations with [[ICANN]], Verisign traded the [[.org]] [[TLD]] in return for continued rights over [[.com]]. In mid 2005, when Verisign's contract for operation with [[.net]] expired, Verisign and 5 other companies bid for it. Verisign was supported by renowned IT companies like Microsoft, [[IBM]], [[Sun Microsystems]], and [[MCI]]. Finally, on June 8, 2005 [[ICANN]] announced that Verisign had been approved to operate [[.net]] until 2011.<ref>[http://www.icann.org/en/tlds/dotnet-reassignment/dotnet-general.htm]</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 Tech.Sina.com]</ref> This move was seen as potentially problematic given Verisign's own plans to seek the IDN equivalents of their [[.com]] and [[.net]] TLDs; Verisign has perviously said that they will apply for all transliterated versions of .com and .net.<ref>[http://www.managingip.com/Article/2761204/VeriSign-wants-com-and-net-IDNs.html Verisign Wants Com and Net, ManagingIP.com]</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 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]</ref> Confirmed languages that will be applied for include Japanese, Hangul, 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]</ref> At that time it was also noted 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]</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 Tech.Sina.com]</ref> This move was seen as potentially problematic given Verisign's own plans to seek the IDN equivalents of their [[.com]] and [[.net]] TLDs; Verisign has perviously said that they will apply for all transliterated versions of .com and .net.<ref>[http://www.managingip.com/Article/2761204/VeriSign-wants-com-and-net-IDNs.html Verisign Wants Com and Net, ManagingIP.com]</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 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]</ref> Confirmed languages that will be applied for include Japanese, Hangul, 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]</ref> At that time it was also noted 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]</ref>