.verisign: Difference between revisions
Created page with "{{TLD| |logo = |status = Proposed |country = |language = |translation = |manager = |registryprovider = |registrations = |date = |type = Brand TLD |categor..." |
Updated delegation details. |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = | |status = Delegated | ||
|country = | |country = | ||
|language = | |language = | ||
|translation = | |translation = | ||
|manager = | |manager = | ||
|registryprovider = | |registryprovider = [[Verisign]] | ||
|registrations = | |registrations = | ||
|date = | |date = | ||
| Line 12: | Line 12: | ||
|category = | |category = | ||
|community = | |community = | ||
|priority = 1551 - [[Verisign]] | |||
|keypeople = | |keypeople = | ||
}} | }} | ||
'''.verisign''' is a [[Brand TLD]] | '''.verisign''' is a [[Brand TLD]] delegated in [[ICANN]]'s [[New gTLD Program]]. [[Verisign]]'s application succeeded and the extension was delegated to the [[Root Zone]] 25 November 2015.<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref> <ref>[http://newgtlds.icann.org/en/program-status/delegated-strings .VERISIGN Delegation. Retrieved 30 Nov 2015.}</ref> | ||
==Application Details== | |||
The following is excerpted from the applicant's response to question #18: | |||
"The .verisign gTLD will leverage the same industry-leading Internet technologies that have | |||
made the TLDs we operate reliable, secure, and available for more than a decade. The gTLD | |||
will reinforce the reputation and trust of Verisign products and services such as Verisign DDoS | |||
Protection, Verisign Managed DNS, and Verisign iDefense Security Intelligence Services. | |||
The .verisign gTLD will allow us to better differentiate our unique products and services by | |||
identifying the landing pages of such products and services as authentically Verisign’s. This | |||
identification will allow customers to feel secure that the information they are receiving is coming | |||
from Verisign and its authorized affiliates and not a third party that may be spoofing the site or | |||
operating a phishing scam. The .verisign gTLD will also provide credibility that the inventions | |||
and data we share through this gTLD come directly from Verisign. | |||
The .verisign gTLD will assure visitors to our site that the information they are receiving is | |||
coming from Verisign and not an unauthorized third party. The gTLD will act as a visual indicator | |||
for the user and will help build the Verisign brand and association to our services in the market. | |||
As such, registrations of domain names for the .verisign gTLD may only be performed by an | |||
authorized registrant acting on behalf of VeriSign, Inc. All domain name registrations in the | |||
gTLD will be registered to and maintained by VeriSign, Inc. for our own exclusive use. VeriSign, | |||
Inc. does not currently plan to sell, distribute, or transfer control or use of any registrations in | |||
the gTLD to any third party that is not an affiliate. Verisign intends to implement registration | |||
policies that: (i) require Verisign to approve any and all registrations; (ii) require all registrations | |||
to be in the name of Verisign and⁄or our affiliates; and (iii) require that control of such | |||
registrations and their use remain with Verisign and ⁄or our affiliates and partners. | |||
As the sole registrant for the .verisign gTLD, we will publish all required registrant information in | |||
our Whois system, which will not contain private or confidential information. We will also publish | |||
Verisign contact and customer support contact information on our .verisign website. To the | |||
extent .verisign allows registrations by individuals, Verisign will protect such confidential | |||
information of such registrants in substantially the same manner as we protect the confidential | |||
information of registrants in .name"<ref>[https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1300 Application Download, gTLDresult.ICANN.org] Retrieved 2 Mar 2013</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[Category:TLD]] | [[Category:TLD]] | ||
Latest revision as of 23:26, 30 November 2015
| Status: | Delegated |
| Registry Provider: | Verisign |
| Type: | Brand TLD |
| Priority #: | 1551 - Verisign |
More information: 
| |
.verisign is a Brand TLD delegated in ICANN's New gTLD Program. Verisign's application succeeded and the extension was delegated to the Root Zone 25 November 2015.[1] [2]
Application Details
The following is excerpted from the applicant's response to question #18:
"The .verisign gTLD will leverage the same industry-leading Internet technologies that have made the TLDs we operate reliable, secure, and available for more than a decade. The gTLD will reinforce the reputation and trust of Verisign products and services such as Verisign DDoS Protection, Verisign Managed DNS, and Verisign iDefense Security Intelligence Services.
The .verisign gTLD will allow us to better differentiate our unique products and services by identifying the landing pages of such products and services as authentically Verisign’s. This identification will allow customers to feel secure that the information they are receiving is coming from Verisign and its authorized affiliates and not a third party that may be spoofing the site or operating a phishing scam. The .verisign gTLD will also provide credibility that the inventions and data we share through this gTLD come directly from Verisign.
The .verisign gTLD will assure visitors to our site that the information they are receiving is coming from Verisign and not an unauthorized third party. The gTLD will act as a visual indicator for the user and will help build the Verisign brand and association to our services in the market.
As such, registrations of domain names for the .verisign gTLD may only be performed by an authorized registrant acting on behalf of VeriSign, Inc. All domain name registrations in the gTLD will be registered to and maintained by VeriSign, Inc. for our own exclusive use. VeriSign, Inc. does not currently plan to sell, distribute, or transfer control or use of any registrations in the gTLD to any third party that is not an affiliate. Verisign intends to implement registration policies that: (i) require Verisign to approve any and all registrations; (ii) require all registrations to be in the name of Verisign and⁄or our affiliates; and (iii) require that control of such registrations and their use remain with Verisign and ⁄or our affiliates and partners.
As the sole registrant for the .verisign gTLD, we will publish all required registrant information in our Whois system, which will not contain private or confidential information. We will also publish Verisign contact and customer support contact information on our .verisign website. To the extent .verisign allows registrations by individuals, Verisign will protect such confidential information of such registrants in substantially the same manner as we protect the confidential information of registrants in .name"[3]
References
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ [http://newgtlds.icann.org/en/program-status/delegated-strings .VERISIGN Delegation. Retrieved 30 Nov 2015.}
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 2 Mar 2013