First company abandons .com for new dot-brand gTLD

Wow. Somebody actually did it.
CITIC, China’s biggest conglomerate, has started redirecting its established .com domain to its new dot-brand gTLD, .citic.
Specifically, it’s redirecting citic.com (go on, click it!) to limited.citic.
Almost everyone reading this post will agree that as a memorable, attractive domain it’s a step backwards.
But CITIC does seem to be the first dot-brand to make the leap from .com to dot-brand with both feet, and it seems to have done so with little to no penalty to its Google ranking (at least as far as searches for its company name go).
A Google search for “citic” here returns limited.citic as the third result, behind Wikipedia and one of CITIC’s sister companies.
The original citic.com doesn’t appear in the top results.
The company also has ranking for group.citic, one of the five second-level names active in the .citic zone file right now.
It’s not the first dot-brand to launch a web site at its new gTLD — destination.monash and annualreport.axa spring to mind — but it does seem to be the first to throw away its .com completely.
CITIC does not appear to have activated its matching Chinese-script gTLD, .中信, in the same way, however. Only nic.中信 appears in search results for sites under that TLD.
Thanks to Jothan Frakes of NamesCon for the tip.

Victims of first confirmed new gTLD collision respond: “Fuck Google”

A number of companies have experienced errors on their networks due to collisions with a newly introduced gTLD.
The initial outcry from victims can be characterized as a storm of profanity, which it could be argued is a good thing for security but not great for ICANN’s reputation.
The collisions, which I believe are the first to be publicly and widely reported, are due to Google’s new gTLD .prod, which was delegated September 1.
Google intends to use the TLD as a shorthand for “product”, but it seems some companies use it internally to mean “production”, meaning production servers rather than testing or development servers.
Issues started being reported on online fora on September 3, with Google unfairly bearing the brunt of the initial blame. Here are a few of the earliest examples from Twitter:

Hey Google, fuck you for making .prod a valid TLD, what the fuck is wrong with you

— eesperan (@eesperan) September 3, 2014

anyone else having fun name resolution issues because of the new .prod tld google just put online? http://t.co/jq104uAym0

— Chris Johnson (@point9repeating) September 3, 2014

.prod is now a TLD & basically broke the internet. (http://t.co/kB5JIZl1HE). This is why I didn't use prod as subdomain, @Drew_Stokes

— Allan Parsons (@allanparsons) September 3, 2014

Well .prod is now a TLD. Found out the fun way. #google #icann http://t.co/rbt4JIASgn

— jeremy avnet (@brainsik) September 3, 2014

A day later, Reddit user “cunttard”, under a post entitled “Fuck Google”, wrote:

Google recently activated prod. TLD.
They also decided to wildcard DNS all entries to 127.0.53.53 to resolve name collisions for internal organisations. All because they wanted .prod for product? Why not fucking request .product?
The implications have been fucking horrendous. I am in the process of helping a mate unfuck his organisations DNS, which heavily relied on resolver search $FQDN to map xyz.prod to xyz.prod.$FQDN. Note this wasn’t even used as an internal TLD. Now they’re all resolving short names to 127.0.53.53. Lesson learnt; always use FQDN everywhere.
I’m just fucking sick of ICANN / Google continuing to fuck DNS.

LinuxQuestions user “fantasygoat” started a thread entitled “New tLD .prod is messing with my configs”, in which he wrote:

I used to be able to refer to just the subdomain in a DNS lookup, like “www1.prod” and it would know I meant “www1.prod.example.com”, my local domain. I’ve been using prod.example.com for decades as the production subdomain for various things.
Now it resolves to 127.0.53.53, which I believe is ICANN’s hack DNS answer for tLDs.
So, I have a bunch of config files without the domain name and it’s messing stuff up. Does anyone have a workaround so I can have my DNS respond to .prod requests as a subdomain of my domain?

I’ve found a couple of other examples on various mailing lists and web forums with systems administrators experiencing similar issues over the last week.
This, it seems to me, shows that ICANN’s hack for mitigating the risks of name collisions, developed by JAS Advisors, is working as expected.
In each reported case of a .prod collision I’ve been able to find, the admin either had already worked out that he needed to use a fully-qualified domain name (eg www.prod.example.com instead of www.prod) or was swiftly advised to do so by those responding to his post.
Most seem to have spotted that instead of returning NXDOMAIN errors, Google is returning the IP address 127.0.53.53, which was chosen because it’s an internal IP and because 53 is the TCP/IP port number for DNS.
Diverting to 127.0.53.53 is designed to catch the eye, alerting admins to the need to correctly configure their networks.
It certainly seems to be doing that, but it’s not winning ICANN or new gTLD registries any new friends.
Nobody has yet reported death or injury due to a collision.
Update: There has been one previously reported collision, concerning .guru.

Community panel hands .radio to EBU because nobody objected

The European Broadcasting Union is likely to win the right to the .radio new gTLD, beating three portfolio applicants, after a favorable Community Priority Evaluation.
The main reason the EBU managed to score a passing 14 out of 16 points in the CPE is that there was no significant objection to the EBU’s bid on the public record.
The EBU managed to win, under ICANN’s complex scoring system, despite the fact that the CPE panel ruled that no one entity, not even the EBU, can claim to represent the “radio” community.
The win means that Donuts, Afilias and BRS Media, which all applied for open .radio gTLDs, will likely have to withdraw their bids and leave .radio in the hands of the EBU’s more restrictive policies.
The EBU’s bid envisages a post-registration enforcement regime, in which registrants’ web sites and Whois records are vetted to ensure they have a community “nexus” and are using their domains in the spirit of the community.
Registrants would have to provide a statement of their usage intent at the point of registration.
Domain investors are explicitly not welcome in the TLD, judging by the EBU’s application.
The EBU, as mentioned, scored 14 out of 16 points in the CPE. The threshold to pass is 14.
As I’ve been saying for years, passing a CPE should be very difficult because applicants can immediately lose two points if there’s any decent opposition to their applications.
The other three applicants for .radio could have easily beaten back the EBU had they managed to effectively organize just a single significant member of the radio community against the EBU’s bid.
However, they failed to do so.
The EBU scored the maximum of two points under the “Opposition” part of the CPE, because, in the words of the panel:

To receive the maximum score for Opposition, the application must not have received any opposition of relevance. To receive a partial score for Opposition, the application must have received opposition from, at most, one group of non-negligible size.
The application received letters of opposition, which were determined not to be relevant, as they were (1) from individuals or groups of negligible size, or (2) were not from communities either explicitly mentioned in the application nor from those with an implicit association to such communities.

Donuts, Afilias and BRS Media all submitted comments in opposition to the EBU application. As competing applicants, these submissions were (probably correctly) disregarded by the panel.
There were a small number of other objecting comments on the record that the CPE panel (again probably correctly) chose to disregard as coming from organizations of negligible size.
The was one comment, in Polish, from a Polish law firm. Another comment came from a something dodgy-looking calling itself the International Radio Emergency Support Coalition.
A third comment came from the Webcaster Alliance, a group that made a bit of a name for itself a decade ago but which today has a one-page web site that doesn’t even list its members (assuming it has any).
Attempts by BRS Media, which already runs .am and .fm, to orchestrate a campaign of opposition seem to have failed miserably.
In short, the panel’s decision that there was no relevant, on-the-record opposition seems to be on pretty safe ground.
What’s slightly disturbing about the CPE is that the panel seems to have decided that the EBU does not actually represent the radio community as described in its application.
It dropped one point on the “Community Establishment” criteria, and another on the “Nexus between Proposed String and Community” criteria.
Specifically, it lost a point because, as the panel stated:

Based on information provided in the application materials and the Panel’s research, there is no such entity that organizes the community defined in the application. Therefore, as there is no entity that is mainly dedicated to the community as defined in the .RADIO application, as the Panel has determined, there cannot be documented evidence of community activities.

In other words, there may be a “radio community”, but nobody, not even the EBU, is responsible for organizing it.
It also lost a point because while the string “radio” does “identify” the community, it does not “match” it.
The panel explained:

To receive the maximum score for Nexus, the applied-for string must “match” the name of the community or be a well-known short-form or abbreviation of the community name. To receive a partial score for Nexus, the applied-for string must “identify” the community. “Identify” means that the applied-for string should closely describe the community or the community members, without over-reaching substantially beyond the community.

Failing to get full marks on community and nexus would usually, in my view, indicate that an application would not succeed in its CPE bid.
However, the lack of any outcry from significant members of the community (either because there was no such opposition or the three rival applicants failed to muster it) seems set to allow .radio to be managed by the applicant with the most restrictive policies.

.global a victim of new gTLD launch cluster?

Poor GA-day results from .global are being blamed on registrars being swamped by a cluster of new gTLD launches occurring in close proximity.
Dot Global added 1,074 domains in the first seven hours of .global’s general availability, bringing its zone to 1,637 names in total.
CEO Rolf Larsen told us the number of registrations yesterday was actually closer to 1,200.
The numbers aren’t great for a first day, considering that .global is in place at about 80 registrars, but Larsen said that the lack of a long runway of pre-registrations was to blame.
“We are not unhappy with the 1,200, but unhappy to not have had months of pre-regs to make that number higher,” he said.
“Most registrars don’t even do pre-regs,” he said. “Those who do have had a hard time keeping up with all the launches. Our launch was in a very busy period, so difficult to get on board with all those registrars early. Some, including GoDaddy did pre-regs for us, but over just a few weeks instead of months like with many other launches.”
Go Daddy was the biggest registrar yesterday, he said.
Dot Global has a number of plans to increase its marketing over the coming weeks and months, by itself and in conjunction with its registrar partners.
These plans include broad promotions to registrars’ existing customer bases as well as targeted mailings to companies that already have the word “global” at the second level of their domains.

.london launch day biggest yet for new gTLDs, but did it miss targets?

Dot London Domains’ .london had just shy of 35,000 domains in its zone file this morning, after its first partial day of general availability.
That’s an addition of 12,421 domains over yesterday’s number, making .london the 11th most-registered new gTLD.
This makes .london — which in my opinion has had one of the best launch marketing campaigns we’ve seen this year — the most-successful gTLD, in volume terms, after its first GA day.
It has beaten the 33,012 names that .在线 (“.online” in Chinese) and the 31,645 names that .berlin had in their zone files at the end of their respective GA days.
.london domains are not particularly cheap, either. Minds + Machines sells at £30 ($48) a year and Go Daddy (which lists .london at the top of its UK home page today) sells at $59.99.
UK-based Domainmonster, part of Host Europe Group, performed well with a £34.99 ($56) annual fee.
There were 22,547 .london names claimed during the “London Priority Period”, a combined sunrise/landrush phase that gave first dibs on names to trademark owners followed by London residents.
The registry has not broken down the mix between sunrise and landrush, but I believe based on the paltry sunrise performance of every other new gTLD to date that the vast majority were landrush names.
The full priority period queue has not yet been processed — domains with more than one applicant are currently in auction.
Back-end provider Minds + Machines, recently told the markets that it expects about a quarter of landrush/sunrise names to go to auction, so we could be looking at something like 7,500 applications (as opposed to domains) currently in the auction queue.
What this may mean is that .london had roughly 30,000 applications during its priority period, about 20,000 less than it had predicted back in July.
Dot London Domains is closely affiliated with London & Partners, the PR machine for the Mayor of London, so it had resources and access to throw at an effective marketing campaign.

Donuts beats trademark owner to .coach

Donuts has won the right to the new gTLD .coach, after an exact-match trademark owner withdrew its bid.
Coach Inc is a chain of clothing and accessories outlets, best known for its handbags, founded in New York in 1941.
The company owns coach.com, but withdrew its application for .coach this week, leaving Donuts unchallenged.
Coach had filed a Legal Rights Objection against Donuts, claiming .coach would infringe its trademark, but the objection panelist disagreed (pdf).
The panelist agreed instead with Donuts that “coach” has multiple meanings, and that that was “a risk that the Objector assumed when it adopted as its trademark a common dictionary word.”

Uniregistry beats 1-800-FLOWERS.COM to .flowers

Uniregistry has won the contention set for .flowers, beating three other new gTLD applicants.
The company won the rights to the string after withdrawals from Donuts, Minds + Machines and a subsidiary of 1-800-FLOWERS.COM.
The price of forcing the withdrawals, as usual, has not been disclosed.
Uniregistry currently has 15 delegated new gTLDs and a handful of others, won at auction, that are in the contracting stage of the process.
The string “flowers” has a bit of a tainted history in the domain name space.
Investor Rick Schwartz famously paid $200,000 for flowers.mobi, only to sell it on a few years later to another investor for $6,500.
That domainer flipped it in 2012, and it ultimately wound up in the hands of 1-800-FLOWERS.COM for an undisclosed sum.

.club first new gTLD to sell 100,000 domains

.club hit a landmark this week with its 100,000th domain name registration, according to .CLUB Domains.
It’s the first new gTLD to get to this level of success without giving away names for free — .xyz and .berlin have over 460,000 and 130,000 names respectively but fall under 100k if you factor out the freebies.
The .club zone file showed 98,984 names (excluding swelling from the name collisions program) last night, and it’s been growing at steady rate of roughly 250-300 names per day.
It appears that there are 1,000 or so names that do not appear in the zone file, perhaps because they’re not configured yet.
.club hit general availability May 7, 114 days ago.

GAC kills .indians and two more dot-brands die

Reliance Industries, owner of the Mumbai Indians cricket team, has withdrawn its application for the new gTLD .indians after an objection from the Indian government.
ICANN’s Governmental Advisory Committee has said in formal advice several times, most recently in March, that India was not cool with the idea of a .indians TLD, but noted that the country stood alone.
Following the Singapore meeting this year, the GAC said: “the Government of India has requested that the application for .indians not proceed.”
As a piece of non-consensus advice, ICANN would have been able to more easily reject India’s objection, but the withdrawal means it will not have to make that decision.
India has a similarly dim view of .ram, which Chrysler has applied for to protect a car brand but which also matches an important deity in the Hindu pantheon. That bid is still active.
But recently we’ve seen two other dot-brand applicants get out of the new gTLD program.
Dun & Bradstreet has just withdrawn its bid for .dnb. Last week, Myriad International Holdings yanked its application for .mih.

After $1bn deal, Amazon registers Twitch domains in three gTLDs. Can you guess which three?

Amazon has paid almost a billion dollars for the gaming community Twitch and immediately set about defensively registering some domain names.
amazontwitch.com, amazontwitch.net, and amazontwitch.org were all registered via MarkMonitor on Monday, coinciding with the announcement of the acquisition.
The company even registered twitchamazon.com, but not the corresponding .net and .org.
But Amazon, a major new gTLD applicant itself, does not appear to have registered the string in any new gTLDs, despite being one of the most prolific defensive registrants.
The company owns the string “fire” in scores of new gTLDs and appears to have blanket-registered “prime” and “kindle” in pretty much every new gTLD sunrise to date.
Twitch, pre-acquisition, doesn’t seem to have involved itself in new gTLDs at all, though the string “twitch” has been registered in several.
Bad news for the owners of these domains?