.horse: Difference between revisions
No edit summary |
Changed language in first sentence to reflect delegation as opposed to proposition. |
||
Line 18: | Line 18: | ||
}} | }} | ||
'''.horse''' is a | '''.horse''' is a delegated [[Community gTLD]] with [[ICANN]]'s [[New gTLD Program|new gTLD expansion program]] for the horse industry. The proposed application succeeded and was delegated to the [[Root Zone]] on 31 March 2014.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated Strings, ICANN.org] Retrieved 15 April 2014</ref> | ||
The [[Dot Horse Project LLC]] applied for the .horse string and became the registry operator of the string. [[Top Level Domain Holdings Ltd.]] (TLDH) applied for the gTLD in behalf of the company and its subsidiary, [[Minds + Machines]] is providing the back-end registry solutions for the .horse TLD.<ref>[http://www.dothorseproject.com/ Dot Horse Project]</ref> <ref>[http://www.tldh.org/ ANNOUNCED TLDH GTLDS]</ref> | The [[Dot Horse Project LLC]] applied for the .horse string and became the registry operator of the string. [[Top Level Domain Holdings Ltd.]] (TLDH) applied for the gTLD in behalf of the company and its subsidiary, [[Minds + Machines]] is providing the back-end registry solutions for the .horse TLD.<ref>[http://www.dothorseproject.com/ Dot Horse Project]</ref> <ref>[http://www.tldh.org/ ANNOUNCED TLDH GTLDS]</ref> |
Revision as of 16:02, 23 March 2015
Status: | Delegated |
Manager: | Dot Horse Project LLC |
Registry Provider: | Minds + Machines |
Type: | Community gTLD |
Category: | Lifestyle |
PIC Submitted: | Download Here |
Priority #: | 1317 - Top Level Domain Holdings |
More information: |
.horse is a delegated Community gTLD with ICANN's new gTLD expansion program for the horse industry. The proposed application succeeded and was delegated to the Root Zone on 31 March 2014.[1]
The Dot Horse Project LLC applied for the .horse string and became the registry operator of the string. Top Level Domain Holdings Ltd. (TLDH) applied for the gTLD in behalf of the company and its subsidiary, Minds + Machines is providing the back-end registry solutions for the .horse TLD.[2] [3]
The application for the .horse TLD is supported by the Lexington Fayette Urban County Government, Keeneland Pony Club,Lexington Convention and Visitors Bureau, The Greater Lexington Chamber of Commerce, Inc., Kentucky Equine Humane Center and the Inforatag Racing Stable LLC. [4]
Application Details[edit | edit source]
The following is excerpted from the applicant's response to question #18:
"The purpose of the .HORSE gTLD is to offer horse owners, service providers, horse industry employees and volunteers the opportunity to clearly define their presence on the Internet and to help potential customers gain access to content about horses.
As horse owners begin to take advantage of ecommerce and other Internet technologies, horse enthusiasts are looking for easier ways to find equine information and products online. The .HORSE domain will serve as the definitive home of horse-related content online.
There are 9.2 million horses in the United States alone, or roughly 3 horses per hundred people. 4.6 million Americans are involved directly in the industry as service providers or owners--tens of millions more participate as spectators. The horse industry directly provides more than 416,000 jobs and represents an overall market of $39 Billion. (Source: http:⁄⁄www.theequestrianchannel.com⁄id3.html)
In the United Kingdom, 43 percent of households have at least one member with some form of interest in equestrianism. This interest is also growing. In 1999, only 2.4 million UK residents had ridden in the last 12 months. In 2011, that number had almost doubled to 4.2 million. According to the British Horse Industry Confederation, the equestrian sector is the single largest sporting employer in the UK. .. We specifically examined more restrictive registration policies, such as limiting registration to members of organizations with a specific tie to horses. We rejected such limitations because they would interfere with .HORSE’s primary mission, purpose and goals--which is to encourage as many registrants as possible to associate themselves with horses for any legal purpose. Factors that we took into account when considering a more restrictive registration policy included:
- Our recognition that registrants of a .HORSE domain name will self-select because they have an interest in horses, naturally reducing the number of potential registrants; and, because restrictive policies such as, for example, requiring membership in a specific organization or organizations, would exclude many legitimate registrants from obtaining a .HORSE domain name. For example, and by way of illustration, if membership an organization were required for registration, businesses and charitable organizations that would find a .HORSE top-level domain name an effective marketing tool would be excluded from registering a .HORSE domain name as they might not be eligible to be members in an organization that accepted only natural persons for membership.
With respect to protecting registrant privacy and confidential information, we will comply with all applicable ICANN rules, including Whois policies, and all applicable laws, rules and regulations of appropriate jurisdictions. Registrant privacy and use of confidential information are set forth in our Privacy & Whois Policy. Information concerning updates and changes to the Privacy & Whois Policy will be promptly and prominently displayed on the .HORSE web site."[5]
Contract Signed[edit | edit source]
On November 21, 2013 TLDH received a Registry Agreement signed by ICANN for .horse after passing the Initial Evaluation.[6]
Delegation and Availability[edit | edit source]
.horse was delegated to the Root Zone of the DNS on 31 March, 2014, completing the successful application for the string.[1]
References[edit | edit source]
- ↑ 1.0 1.1 Delegated Strings, ICANN.org Retrieved 15 April 2014
- ↑ Dot Horse Project
- ↑ ANNOUNCED TLDH GTLDS
- ↑ Supporters
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 28 Feb 2013
- ↑ Registry Agreements, ICANN.org Retrieved 02 Dec 2013