.tokyo: Difference between revisions
No edit summary |
No edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = | |status = Delegated | ||
|manager = [[Tokyo Metropolitan Government]] | |manager = [[Tokyo Metropolitan Government]] | ||
|country = Japan | |country = Japan | ||
| Line 11: | Line 11: | ||
|date = | |date = | ||
|type = [[GeoTLD]] | |type = [[GeoTLD]] | ||
|priority = 199 | |||
|category = [[:Category:Culture New gTLDs|Culture]] | |category = [[:Category:Culture New gTLDs|Culture]] | ||
|community = | |community = | ||
| Line 16: | Line 17: | ||
}} | }} | ||
'''.tokyo''' is a new [[GeoTLD]] proposed by [[GMO Registry]], Inc., a subsidiary company of [[GMO Internet|GMO Internet Group]], dedicated to providing domain registry management services for new [[gTLD]]s. Their application is supported by the Tokyo Metropolitan Government, and the company is doing a number of Japanese GeoTLDs.<ref>[http://www.yomiuri.co.jp/dy/business/T120110006041.htm Domains with .tokyo could be available next year]</ref> <ref>[http://www.metro.tokyo.jp/INET/OSHIRASE/2011/11/20lbl500.htm Tokyo Metropolitan Government Announces Support for .tokyo TLD]</ref> | '''.tokyo''' is a new [[GeoTLD]] proposed by [[GMO Registry]], Inc., a subsidiary company of [[GMO Internet|GMO Internet Group]], dedicated to providing domain registry management services for new [[gTLD]]s. Their application is supported by the Tokyo Metropolitan Government, and the company is doing a number of Japanese GeoTLDs.<ref>[http://www.yomiuri.co.jp/dy/business/T120110006041.htm Domains with .tokyo could be available next year]</ref> <ref>[http://www.metro.tokyo.jp/INET/OSHIRASE/2011/11/20lbl500.htm Tokyo Metropolitan Government Announces Support for .tokyo TLD]</ref> The proposed application succeeded and was delegated to the [[Root Zone]] on 29 January 2014.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated Strings, ICANN.org] Retrieved 29 Jan 2014</ref> | ||
==Contract Signed== | |||
On 13 November 2013, [[GMO Registry]] received a [[Registry Agreement]] signed by [[ICANN]] for .tokyo after passing all the required processes needed to become a [[Registry Operator]] for the string.<ref>[http://www.icann.org/en/about/agreements/registries Registry Agreements, ICANN.org] Retrieved 15 Nov 2013</ref> | |||
==Delegation and Availability== | |||
.tokyo was delegated to the [[Root Zone]] of the [[DNS]] on January 29, 2014, completing the successful application for the string.<ref name="delegation"></ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:Culture New gTLDs|tokyo]] | [[Category:Culture New gTLDs|tokyo]] | ||
[[Category:TLDs with Registry Agreements|tokyo]] | |||
Latest revision as of 22:44, 29 January 2014
| Status: | Delegated |
| country: | Japan |
| Manager: | Tokyo Metropolitan Government |
| Registry Provider: | GMO Registry |
| Type: | GeoTLD |
| Category: | Culture |
More information: 
| |
.tokyo is a new GeoTLD proposed by GMO Registry, Inc., a subsidiary company of GMO Internet Group, dedicated to providing domain registry management services for new gTLDs. Their application is supported by the Tokyo Metropolitan Government, and the company is doing a number of Japanese GeoTLDs.[1] [2] The proposed application succeeded and was delegated to the Root Zone on 29 January 2014.[3]
Contract Signed
On 13 November 2013, GMO Registry received a Registry Agreement signed by ICANN for .tokyo after passing all the required processes needed to become a Registry Operator for the string.[4]
Delegation and Availability
.tokyo was delegated to the Root Zone of the DNS on January 29, 2014, completing the successful application for the string.[3]
References
- ↑ Domains with .tokyo could be available next year
- ↑ Tokyo Metropolitan Government Announces Support for .tokyo TLD
- ↑ 3.0 3.1 Delegated Strings, ICANN.org Retrieved 29 Jan 2014
- ↑ Registry Agreements, ICANN.org Retrieved 15 Nov 2013