.basketball: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = Proposed | |status = Proposed | ||
|manager = | |manager = | ||
|country = | |country = | ||
|language = | |language = | ||
|translation = | |translation = | ||
|stringcontention = | |stringcontention = | ||
|registryprovider = | |registryprovider = | ||
|registrations = | |registrations = | ||
|date = | |date = | ||
|type = | |type = [[gTLD|Generic]] | ||
|community = | |category = [[:Category:Sport New gTLDs|Sport]] | ||
|keypeople = | |community = | ||
|keypeople = | |||
}} | }} | ||
'''.basketball''' is a | '''.basketball''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. | ||
==Current Applicants== | |||
# The International Basket Federation ([[FIBA]]) in partnership with [[Top Level Domain Holdings Ltd.|TLDH]] and [[ROAR Domains]], LLC. It is intended to promote and protect the sport and the interests of its stakeholders, including entities and organizations affiliated with basketball, and its players and fans worldwide. [[Minds + Machines]] was selected at their back-end registry services provider.<ref>[http://www.fiba.com/pages/eng/fc/news/inte/p/newsid/51390/arti.html PR N°7 - FIBA files application for .BASKETBALL Generic Top-Level Domain]</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:Sport New gTLDs|basketball]] | [[Category:Sport New gTLDs|basketball]] | ||
Revision as of 21:06, 12 June 2012
| Status: | Proposed |
| Type: | Generic |
| Category: | Sport |
More information: 
| |
.basketball is a proposed TLD in ICANN's New gTLD Program.
Current Applicants
- The International Basket Federation (FIBA) in partnership with TLDH and ROAR Domains, LLC. It is intended to promote and protect the sport and the interests of its stakeholders, including entities and organizations affiliated with basketball, and its players and fans worldwide. Minds + Machines was selected at their back-end registry services provider.[1]