Changes

Jump to navigation Jump to search
no edit summary
Line 83: Line 83:  
* In July, 2011, [[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 WHIR]</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, DomainIncite.com]</ref>
 
* In July, 2011, [[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 WHIR]</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, DomainIncite.com]</ref>
   −
* In October, 2011, 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/ Domain Name Wire: VeriSign Proposes Takedown Procedures and Malware Scanning for .Com]</ref> The policy was deemed controversial, with concern about government involvement in the Internet, as well as concern from domain registrars. Two days after releasing the proposal, Verisign withdrew the request.<ref>[http://domainnamewire.com/2011/10/13/breaking-verisign-withdraws-request-for-domain-takedown/ Domain Name Wire: VeriSign Withdraws Request for Domain Takedown]</ref>
+
* In October, 2011, 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/ Domain Name Wire: VeriSign Proposes Takedown Procedures and Malware Scanning for .Com]</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/ Domain Incite: Registrars not happy with VeriSign abuse plans]</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/ Domain Name Wire: VeriSign Withdraws Request for Domain Takedown]</ref>
    
==Acquisitions==
 
==Acquisitions==
14,326

edits

Navigation menu