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.
Two new gTLD applicants would get the opportunity to formally appeal String Confusion Objection decisions that went against them, under plans laid out by ICANN today.
DERCars and United TLD (Rightside), which lost SCOs for their .cars and .cam applications respectively, would be the only parties able to appeal “inconsistent” objection rulings.
DERCars was told that its .cars was too similar to Google’s .car, forcing the two bids into a contention set. But Google lost similar SCO cases against two other .cars applicants.
Likewise, Rightside’s .cam application was killed off by a Verisign SCO that stated .cam and .com were too similar, despite two other .cam applicants prevailing in virtually identical cases.
Now ICANN plans to give both losing applicants the right to appeal these decisions to a three-person panel of “Last Resort” operated by the International Centre for Dispute Resolution.
ICDR was the body overseeing the original SCO process too.
Notably, ICANN’s new plan would not give Verisign and Google the right to appeal the two .cars/.cam cases they lost.
Only the applicant for the application that was objected to in the underlying SCO and lost (“Losing Applicant”) would have the option of whether to have the Expert Determination from that SCO reviewed.
There seems to be a presumption by ICANN already that what you might call the “minority” decision — ie, the one decision that disagreed with the other two — was the inconsistent one.
I wonder if that’s fair on Verisign.
Verisign lost two .cam SCO cases but won one, and only the one it won is open for appeal. But the two cases it lost were both decided by the same ICDR panelist, Murray Lorne Smith, on the same grounds. The decisions on .cam were really more 50-50 than they look.
According to the ICANN plan, there are two ways an appeal could go: the panel could decide that the original ruling should be reversed, or not. The standard of the review is:
Could the Expert Panel have reasonably come to the decision reached on the underlying SCO through an appropriate application of the standard of review as set forth in the Applicant Guidebook and procedural rules?
The appeals panelists would basically be asked to decide whether the original panelists are competent or not.
If the rulings were not reversed, the inconsistency would remain in place, making the contention sets for .car, .cars and .cam stay rather confusing.
ICANN said it would pay the appeals panel’s costs.
Google took part in dotShabaka Registry’s Sunrise period, according to today’s zone files.
The company registered جوجل.شبكة, in the .شبكة (Arabic “.web”) TLD, via MarkMonitor at some point prior to December 30.
“جوجل” seems to be the Arabic transliteration of “Google”.
The domain is not resolving, but Whois says it belongs to Google and it’s configured to use Google name servers.
It’s only the fifth confirmed Sunrise registration in the .شبكة space — the only new gTLD to so far conclude a Sunrise period.
Rolex registered its trademark and Richemont International registered three of its luxury goods brands. So far, Rolex is the only confirmed new gTLD registrant that is not also an applicant.
None of the registrants to date are from the Arabic-speaking regions.
These may all be defensive registrations, of course, and may never resolve to anything useful.
Microsoft seems to be ahead of its rival Google when it comes to recognizing new gTLDs in their respective search engines.
Doing an advanced search for sites within specific new gTLDs on Bing is returning results today. The same cannot be said for Google, however.
Here’s an example of a search results page limited to Uniregistry’s .sexy:
The same type of search seems to work for .tattoo (Uniregistry) and .ruhr (Regiodot) but not for .uno or for any of Donuts’ many Latin-script gTLDs (which all currently redirect to donuts.co).
Sometimes the searches work with a dot, sometimes they don’t.
New gTLD support appears to be a work in progress at Microsoft, in other words, but the company does seem to be further along than Google, which so far doesn’t return any results for the same queries.
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.
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.
Thanks to DNS jack o’ all trades Jothan Frakes for telling me how to do this.