.CLUB
Status: | Delegated |
Type: | Generic |
Category: | Lifestyle |
More information: |
.club is a proposed new gTLD in ICANN's new gTLD program. .CLUB Domains LLC, has been public about their application from the beginning, and won their contention set via an auction performed by Innovative Auctions for an undisclosed amount. .Club was one of the first six TLD contention sets to be allocated via private auctions. All told, the six auctions brought in $9mm.[1]
The proposed application succeeded and was delegated to the Root Zone on 18 January 2014.[2]
.CLUB Domains LLC filed the application on the first possible day, January, 12, 2012.[3] Former applicants include Merchant Law Group LLP, a Canadian law-firm that applied for eight new gTLDs; and Donuts (Koko Manor, LLC), a start-up company co-founded by domain industry veterans that applied for 307 domain names strings, each via a different LLC.
Application Details edit
.CLUB Domains LLC edit
The .club domain appears to be a unrestricted gTLD intended for use by the many professional and amateur clubs found around the world. .CLUB Domains LLC has publicly stated that they have secured funding for their application and the potential auction that may ensue, and also that they have no intention of negotiating with any other company applying for .club but intend to win the auction. Apparently, they have already been approached by other .club applicants and have decided the best way to secure the domain is in open auction.[4] The company will use the digital archery solutions of its business affiliate, the Digital Archery Experts to ensure its inclusion in the first batch of applications to be initially evaluated by ICANN. [5]
In May 2013, ahead of a possible private auction for the string, .Club LLC filed with the United States' SEC as it was seeking to raise up to $7 million USD for the presumed auction. [6]
Watch the .CLUB Domains LLC team as they realize they won the .club TLD via private auction: <videoflash>Wu38PkeyF0M</videoflash>
Developments edit
Name Collision edit
Many applications for new gTLDs have raised security concerns because the applied-for strings are already in wide use on internal networks in certain areas of the world.[7] This would create a name collision if the new gTLD were to be delegated and could cause serious security concerns for some strings. The remaining application for .club has been deemed an "uncalculated risk" by ICANN because of name collision with existing internal networks, which means the application will face delays until the issues are resolved. However, in a letter that .CLUB Domains LLC CTO Dirk Bhagat sent to ICANN on September 16, 2013, .CLUB Domains has proposed a solution to the name collision issue. The company hired the same firm that ICANN hired ([Interisle Consulting]) to report on the proposed .club gTLD, and are proposing to reserve the top 50 name collisions of .club, which is available knowledge now due to Interisle's report. The top 50 name collisions would be blocked from registration, and according to .CLUB Domains LLC would create a number of queries to the gTLD that it would be deemed by ICANN as "low risk."[8]
Contract Signed edit
On 08 November 2013, .CLUB Domains LLC received a Registry Agreement signed by ICANN for .club after passing all the required processes needed to become a Registry Operator for the string.[9]
Delegation and Availability edit
.club was delegated to the Root Zone of the DNS on January 18, 2014, completing the successful application for the string.[2]
References edit
- ↑ Six Private New gTLD Auctions Raise 9m, DomainIncitePublished 7 June 2013, Retrieved 10 June
- ↑ 2.0 2.1 New gTLDs Top 100, DomainIncite Retrieved 21 Jan 2014
- ↑ Blog, DotClub.com
- ↑ Tucows coFounder Takes hard Line on Club gTLD
- ↑ .Club Blog-Why is .Club going to be in the first batch? — A response from DigitalArcheryExperts.com
- ↑ Club Applicant Seeks to Raise up to 7 million, DomainNameWire.com Retrieved 29 May 2013
- ↑ New gTLDs are the New Y2K, Domain Incite Retrieved 12 Sept 2013
- ↑ .club Offers Solution to Name Collision Risks Retrieved 16 Sept 2013
- ↑ Registry Agreements, ICANN.org Retrieved 11 Nov 2013