Jump to content

.fairwinds: Difference between revisions

From ICANNWiki
No edit summary
Updated delegation details.
 
Line 1: Line 1:
{{TLD|
{{TLD|
|logo  =  
|logo  =  
|status = Proposed
|status = Delegated
|country  =  
|country  =  
|language =  
|language =  
Line 16: Line 16:
}}
}}


'''.fairwinds''' is a [[Brand TLD]] being proposed in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[FairWinds Partners, LLC]].<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>
'''.fairwinds''' is a [[Brand TLD]] delegated in [[ICANN]]'s [[New gTLD Program]]. [[FairWinds Partners, LLC]] manages the TLD. The company's application to ICANN succeeded and the extension was delegated to the [[Root Zone]] 13 November 2015.<ref>[http://newgtlds.icann.org/en/program-status/delegated-strings .FAIRWINDS Delegation. Retrieved 13 Nov 2015.]</ref><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>


==Application Details==
==Application Details==

Latest revision as of 23:22, 13 November 2015

Status: Delegated
Registry Provider: Verisign
Type: Brand TLD
Priority #: 1501 - FairWinds Partners, LLC

More information:

.fairwinds is a Brand TLD delegated in ICANN's New gTLD Program. FairWinds Partners, LLC manages the TLD. The company's application to ICANN succeeded and the extension was delegated to the Root Zone 13 November 2015.[1][2]

Application Details[edit | edit source]

The following is excerpted from the applicant's response to question #18:

"FairWinds Partners, LLC (“FairWinds”) is a leading domain name analysis and advisory firm that specializes in helping global brands optimize and protect their Web presence - and ultimately their bottom lines - through the development and implementation of domain name strategies that are tailored to each brandʹs opportunities and challenges. FairWindsʹ solutions grow online traffic, increase revenue, improve online customer experiences, and reduce unnecessary domain-related costs. FairWindsʹ customized strategies and domain name program management services have helped Global 500 and blue chip companies worldwide and FairWinds content is accessible in multiple TLDs, including the .COM, .NET, .ORG, .MOBI, and .XXX gTLDs, as well as the .CH, .CN, .DE, .JP, .CA, .CO, .CO.UK, .ES, .IT, .RU, and .US ccTLDs.

FairWinds will be analyzing and evaluating other .BRAND gTLD applications, as well as general market adoption, to determine the short- and long-term potential best-in-class use case options that will most effectively serve and enhance FairWindsʹ online strategy as a leading domain name analysis and advisory firm.

The intended future mission and purpose of the .FAIRWINDS gTLD is to serve as a trusted, hierarchical, and intuitive namespace provided by FairWinds for use by FairWinds and FairWinds-affiliated entities and, potentially, strategic partners and clients.

Although ICANN has not specifically recognized a .BRAND gTLD specification in the current version of the Applicant Guidebook, it is widely anticipated within the brand owner community that this will become a specialty subset of new gTLDs. The .FAIRWINDS gTLD is planned as a .BRAND gTLD, with the goal of protecting FairWindsʹ online presence and identity; expanding its marketing and promotional efforts; providing a secure channel for online content and services; and offering a platform through which to consolidate many of the intellectual property activities of FairWinds.

FairWinds intends to initially limit registration and use of domain names within the .FAIRWINDS gTLD to FairWinds and FairWinds-affiliated entities. This initial limited use will allow FairWinds to establish its operations and achieve full sustainability. This limited distribution, coupled with the other requirements set forth in Specification 9 of the template Registry Agreement, is anticipated to exempt FairWinds from its annual Code of Conduct Compliance requirements."[3]

References[edit | edit source]