TLD Registry sells 20k+ IDN gTLD names to Chinese gov

TLD Registry has sold 20,452 new gTLD domain names to the Chinese government as it prepares to launch .中文网 (“.chinesewebsite”) and .在线 (“.online”) tomorrow.
The deal, signed this week with the Service Development Center of the State Council Office for Public Sector Reform (SCOPSR) is for 10,226 names in each gTLD.
The domains include the Chinese-script names of every city in China with a population of over 200,000, as well as counties, municipalities and other regional names.
Strings that translate to things like “invest in [place name]” and “tourism [place name]” have also been registered to the government in both TLDs, according to the company.
It looks like this is the first significant anchor tenant deal we’ve seen in the new gTLD program.
Assuming China actually uses these names, it could be great publicity for the new registry’s gTLDs. The government has a policy of transitioning all of its services to fully IDN.IDN domains.
If not, it still means that both gTLDs stand to launch with over 10,000 names in each zone file on day one, even before regular registrants have had a chance to buy them.
The company is also set to auction a bunch of premium names in both namespaces on Friday simultaneously via Sedo and a live event at a private members’ club in Macau.
I’m posting this from Hong Kong airport, en route to the Macau event. As a matter of disclosure: TLD Registry is paying for my flights and accommodation.

Google’s first new gTLD racks up 2,300 domains

Google’s Charleston Road Registry reached 2,300 .みんな domain names on the new gTLD’s first day of general availability, immediately making it the biggest IDN gTLD by volume so far.
The string is Japanese for “everyone”. As you might expect, it’s an unrestricted space.
About 230 names — 10% of the TLD — are non-IDNs. I believe the number also includes some sunrise registrations.
It actually went into GA on Tuesday, but data was not available yesterday.
While it’s not in the same ballpark as the likes of .guru, it nevertheless overtook the only other IDN gTLD to launch so far, dotShabaka’s شبكة. (Arabic for “web”), which has 1,643 names.
Google sold the names via 17 accredited registrars, only one of which appears to be Japanese. The list excludes most of the biggest registrars.
.みんな is unusual in that Google intends to run its Trademark Claims service forever, rather than turning it off after the 90 days required by its Registry Agreement with ICANN.

First new gTLD Sunrise ends with “very few” registrations

The first new gTLD Sunrise period was not a success, according to dotShabaka Registry.
The 60-day Sunrise for شبكة. (.web in Arabic) ended yesterday with “very few” registrations, the company told us today, due largely to poor promotion of the Trademark Clearinhouse in Arabic-speaking regions.
The gTLD is restricted to Arabic strings, and therefore Sunrise was restricted to Arabic trademarks.
dotShabaka said in a statement:

We always knew – with the convoluted process for registration and lack of information out to the MENA [Middle-East/ North Africa] region on the Trademark Clearinghouse – that this was going to be a quiet time for us. We have seen very few applications through the Sunrise period.
We know that the managers of the TMCH and ICANN are working hard to promote the TMCH. However, as a pioneer we have unfortunately not enjoyed the fruits of this labour. At the same time it should be noted that we have been buoyed by the level of interest from trademark holders and businesses in the region and expect this interest to translate into registrations once we move into Landrush and are free of the TMCH sunrise eligibility requirements.

The company did not provide exact numbers, but my guess is that we might be looking at single figures here.
According to today’s شبكة. zone file, there are no active third-party domains in the شبكة. namespace. Zero. None. The only live sites are “nic.” and its Arabic equivalent, which both belong to the registry.
That may quickly change, of course, as registrations don’t always immediately translate into zone file entries.

Google’s first new gTLD hits the root

Google has become the latest new gTLD registry with a string live in the DNS root.
Its .みんな — Japanese for “everyone” — was delegated by ICANN last night. The URL nic.みんな resolves already to charlestonroadregistry.com, the name of Google’s registry subsidiary.
Google plans to operate it as an open, unrestricted namespace, aimed at Japanese-speaking registrants.
It’s the fifth internationalized domain name to go live and one of only three IDN applications from Google.
Google has 96 more active new gTLD applications, 57 of which are contested.

Almost 15,000 trademarks registered in TMCH

The new gTLD program’s Trademark Clearinghouse has almost 15,000 trademarks registered, according to a spokesperson.
We’re told today that there’s an average of about two labels for each registered mark, and that about half of all the marks have been registered for multiple years.
The TMCH offers registrations for one, three or five years.
Trademarks in non-Latin scripts currently account for just 3% (so roughly 450) of the registrations, which may be a cause for concern given that IDNs gTLDs will be many of the first to launch Sunrise periods.
The TMCH spokesperson added that registrations of “previously abused labels”, under what we used to call the Trademark+50 policy, are currently “low” because the service was only recently launched.

Here’s how to display new IDN gTLDs in Chrome

A lot of people have noticed since the first four new gTLDs were delegated yesterday that Google’s Chrome browser doesn’t seem to handle internationalized domain names.
In fact it does, but if you’re an English-speaking user you’ll probably need to make a few small configuration changes, which should take less than a minute, to make it work.
If you’re using Chrome and you click this link http://nic.сайт chances are your address bar is going to automatically translate it and display it as http://nic.xn--80aswg/.
As far as the DNS is concerned, these are the same URLs. They’re just displayed differently by Chrome, depending on your browser’s display languages settings.
If you want to see the Cyrillic version in your address bar, simply:

• Go to the Chrome Settings menu via the toolbar menu or by typing chrome://settings into the address bar.
• Click the “Language and input settings” button. It’s in the Advanced options bit, which may be hidden at first. Scroll all the way down to unhide.
• Click the Add button to add the languages you want to support in the address bar.

Right now, you can see all three active IDN gTLDs in their intended scripts by adding Arabic, Chinese (Simplified Han) and Russian. As gTLDs in other scripts are added, you’ll need to add those too.
Simple.
Thanks to DNS jack o’ all trades Jothan Frakes for telling me how to do this.

Let’s Learn IDNs!

The eagle-eyed regular DI reader will have noticed earlier today that I published an article claiming the first new gTLD had already gone live. Not only that, it already had a resolving web site!
That was dead wrong. The story lasted about a minute before I yanked it.
I won’t go into all the details, but suffice it to say that the confusion arose because I don’t read a word of Arabic.
I don’t read a character of Arabic either. I don’t even know where one character ends and the next begins. Or, given the way the script functions, where one begins and the next ends.
So I thought today would be an excellent time to launch Let’s Learn IDNs!, an irregular series of posts in which I, with a significant amount of help from new gTLD registries, attempt to explain IDN strings.
I’m guessing there are a large number of readers out there whose eyes, like mine, glaze over whenever they see an IDN.
We can’t tell one Chinese (or Arabic, Cyrillic, Hebrew…) TLD from another, but it would probably make our professional lives a fair bit easier if we could.
Let’s Learn IDNs! will therefore contain just enough information to help DI’s largely Latin-script-using readers recognize an IDN when they see one.
I’m not going to attempt to teach anyone Greek, but hopefully you’ll be able to come away from the series with a better chance of telling the difference between .新闻 and .八卦.
Which is obviously hugely, hugely important.
(That’s DI’s first joke in Chinese. Thanks.)
The first post, coming later today or tomorrow, will focus on TLD Registry’s .中文网 (“.chinesewebsite”).
If you’re an IDN gTLD registry and I’ve not reached out to you already, feel free to get in touch to find out how to get a Let’s Learn IDNs! post for your own string.

Third Bulgarian new gTLDs conference planned

Domain Forum, the Bulgarian new gTLDs conference, will run for a third time on November 1 in Sofia.
The one-day event, which will be free to attend and conducted in English, will have a focus this year on Cyrillic internationalized domain names, according to organizers.
Much of the agenda has yet to be finalized but confirmed speakers include consultant Stephane Van Gelder, Blacknight CEO Michele Neylon and Afilias business development director Francesco Cetraro.
Organizer UNINET also hopes to have an ICANN VP keynoting.
Domain Forum will take place at the National Palace of Culture in central Sofia.

Eleven TLDs get removed from the DNS

ICANN will soon remove 11 experimental internationalized domain name TLDs from the domain name system.
The TLDs, which represent “.test” in nine scripts and 10 languages, were added to the root almost exactly six years ago in preparation for ICANN’s IDN ccTLDs program.
Now that the program is quite mature, with a few dozen IDN ccTLDs live on the internet with no major reported problems, ICANN has decided that the test TLDs are no longer required.
They will be removed from the DNS root zone on October 31, ICANN said.

dotShabaka Diary — Day 15, Iran and Name Collisions

The fifteenth installment of dotShabaka Registry’s journal, charting its progress towards becoming one of the first new gTLDs to go live, written by general manager Yasmin Omer.

Thursday 3 October 2013
At a time when ICANN has hit the ‘pause’ button on the new gTLD program in order to assess the impact of “name collisions” on the security and stability of the DNS, we were surprised to see the ICANN Board approve the delegation of ایران., the IDN ccTLD for the Islamic Republic of Iran. While we understand the many distinctions between a ccTLD and a gTLD, the DNS does not make any such distinction.
As we’ve heard from Paul Mockapetris and John Crain recently in their interviews posted on the ICANN website, name collisions (or, more accurately, NX Domain responses) is not a new phenomenon; they have been evident with the introduction of any TLD and with existing TLDs in the root. Experience has shown that steps have been taken to successfully resolve the issues. We understand that ICANN is concerned that the use of NX Domain responses has the potential to create confusion with the introduction of new TLDs into the DNS.
As a contracted party with ICANN, شبكة. (an IDN gTLD) is unable to be delegated as we wait the outcomes of ICANN’s deliberations on name collisions. We have paid our $185,000 application fee, we have undertaken a very resource intensive exercise to ensure a compliant application, we have passed Initial Evaluation, we have signed a registry agreement with ICANN, we have passed pre-delegation testing and yet we sit and wait.
Our understanding of the IDN ccTLD fast track process is that it is much less rigorous, the application fee is voluntary, there is no requirement to enter into a contract with ICANN, the TLD can develop a launch strategy that is not restricted by ICANN mandated rights protection mechanisms, and any contribution to ICANN’s budget is voluntary. But because this is a ccTLD and not a new gTLD, the Board has seen fit to approve this delegation request at this time despite the serious conversation going on in the community about name collisions.
As we said previously, the DNS does not distinguish between a ccTLD or a gTLD, or for that matter an IDN ccTLD or an IDN gTLD. We would appreciate an explanation as to why we sit and wait for delegation while the IDN ccTLD is approved.

Read previous and future diary entries here.