VRSN » Topics » We rely on third parties who maintain and control root zone servers and route Internet communications.

This excerpt taken from the VRSN 10-Q filed May 8, 2009.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a non-regulated basis. Root zone servers are name servers that contain authoritative data for the very top of the DNS hierarchy. These servers have the software and data needed to locate name servers that contain authoritative data for the top-level domains. Because of the importance to the functioning of the Internet of these root zone servers, our Naming Services business could be harmed if these independent operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our Naming Services business could be harmed if any of these volunteer operators fails to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root zone server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

This excerpt taken from the VRSN 10-K filed Mar 3, 2009.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a non-regulated basis. Root zone servers are name servers that contain authoritative data for the very top of the DNS hierarchy. These servers have the software and data needed to locate name servers that contain authoritative data for the top-level domains. Because of the importance to the functioning of the Internet of these root zone servers, our Naming Services business could be harmed if these independent operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our Naming Services business could be harmed if any of these volunteer operators fails to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root zone server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

This excerpt taken from the VRSN 10-Q filed Nov 7, 2008.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a non-regulated basis. Root zone servers are name servers that contain authoritative data for the very top of the Domain Name System (“DNS”) hierarchy. These servers have the software and data needed to locate name servers that contain authoritative data for the top-level domains. Because of the importance to the functioning of the Internet of these root zone servers, our Naming Services business could be harmed if these independent operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our Naming Services business could be harmed if any of these volunteer operators fails to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root zone server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

60


Table of Contents
This excerpt taken from the VRSN 10-Q filed Aug 8, 2008.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a non-regulated basis. Root zone servers are name servers that contain authoritative data for the very top of the Domain Name System (“DNS”) hierarchy. These servers have the software and data needed to locate name servers that contain authoritative data for the top-level domains. Because of the importance to the functioning of the Internet of these root zone servers, our Naming Services business could be harmed if these independent operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our Naming Services business could be harmed if any of these volunteer operators fails to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root zone server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

53


Table of Contents

Services offered by our 3IS segment rely on the continued integrity of public key cryptography technology that may be compromised or proven obsolete over time.

Services offered by our 3IS segment depend on public key cryptography technology. With public key cryptography technology, a user is given a public key and a private key, both of which are required to perform encryption and decryption operations. The security afforded by this technology depends on the integrity of a user’s private key and that it is not lost, stolen or otherwise compromised. The integrity of private keys also depends in part on the application of specific mathematical principles known as “factoring.” This integrity is predicated on the assumption that the factoring of large numbers into their prime number components is difficult. Should an easy factoring method or other method be developed, the security of encryption products utilizing public key cryptography technology may require significant modifications or would be reduced or eliminated. Furthermore, any significant advance in techniques for attacking cryptographic systems could also render some or all of our existing PKI services obsolete or unmarketable. If improved techniques for attacking cryptographic systems were ever developed, we would likely have to reissue digital certificates to some or all of our customers, which could damage our reputation and brand or otherwise harm our business. In the past there have been public announcements of the successful attack upon cryptographic keys of certain kinds and lengths and of the potential misappropriation of private keys and other activation data. This type of publicity could also hurt the public perception as to the safety of the public key cryptography technology included in our digital certificates. This negative public perception could harm our business.

This excerpt taken from the VRSN 10-Q filed May 12, 2008.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a non-regulated basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these independent operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our registry services business could be harmed if any of these volunteer operators fails to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

This excerpt taken from the VRSN 10-K filed Feb 29, 2008.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a non-regulated basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these independent operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

This excerpt taken from the VRSN 10-Q filed Nov 5, 2007.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

59


Table of Contents
This excerpt taken from the VRSN 10-Q filed Aug 9, 2007.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

This excerpt taken from the VRSN 10-Q filed Jul 16, 2007.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

This excerpt taken from the VRSN 10-Q filed Jul 12, 2007.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

101


Table of Contents
This excerpt taken from the VRSN 10-Q filed Jul 12, 2007.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

This excerpt taken from the VRSN 10-K filed Jul 12, 2007.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the thirteen root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

38


Table of Contents

 

This excerpt taken from the VRSN 10-Q filed May 10, 2006.

We rely on third parties who maintain and control root zone servers and route Internet communications.

We currently administer and operate only two of the 13 root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

This excerpt taken from the VRSN 10-K filed Mar 13, 2006.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the 13 root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

This excerpt taken from the VRSN 10-Q filed Nov 9, 2005.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the 13 root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

This excerpt taken from the VRSN 10-Q filed Aug 9, 2005.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the 13 root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

This excerpt taken from the VRSN 10-Q filed May 10, 2005.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the 13 root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

53


Table of Contents
This excerpt taken from the VRSN 10-K filed Mar 16, 2005.

We rely on third parties who maintain and control root zone servers and route Internet communications.

 

We currently administer and operate only two of the 13 root zone servers. The others are administered and operated by independent operators on a volunteer basis. Because of the importance to the functioning of the Internet of these root zone servers, our registry services business could be harmed if these volunteer operators fail to maintain these servers properly or abandon these servers, which would place additional capacity demands on the two root zone servers we operate.

 

Further, our registry services business could be harmed if any of these volunteer operators fail to include or provide accessibility to the data that it maintains in the root zone servers that it controls. In the event and to the extent that ICANN is authorized to set policy with regard to an authoritative root server system, as provided in our registry agreement with ICANN, it is required to ensure that the authoritative root will point to the top-level domain zone servers designated by us. If ICANN does not do this, our business could be harmed.

 

Wikinvest © 2006, 2007, 2008, 2009, 2010, 2011, 2012. Use of this site is subject to express Terms of Service, Privacy Policy, and Disclaimer. By continuing past this page, you agree to abide by these terms. Any information provided by Wikinvest, including but not limited to company data, competitors, business analysis, market share, sales revenues and other operating metrics, earnings call analysis, conference call transcripts, industry information, or price targets should not be construed as research, trading tips or recommendations, or investment advice and is provided with no warrants as to its accuracy. Stock market data, including US and International equity symbols, stock quotes, share prices, earnings ratios, and other fundamental data is provided by data partners. Stock market quotes delayed at least 15 minutes for NASDAQ, 20 mins for NYSE and AMEX. Market data by Xignite. See data providers for more details. Company names, products, services and branding cited herein may be trademarks or registered trademarks of their respective owners. The use of trademarks or service marks of another is not a representation that the other is affiliated with, sponsors, is sponsored by, endorses, or is endorsed by Wikinvest.
Powered by MediaWiki