Latest news of the domain name industry

Recent Posts

Neustar loses most of its Amazon back-end biz to Nominet

Kevin Murphy, April 12, 2019, Domain Registries

Amazon has switched two thirds of its large portfolio of new gTLDs over to Nominet’s back-end registry services, replacing Neustar.

Judging by changes to IANA records this week, Amazon has moved 35 gTLDs to Nominet, leaving 17 at Neustar.

A Neustar spokesperson confirmed the changes, telling DI:

in an effort to diversify their back-end support, Amazon has chosen to move some, but not all, of their TLDs to another provider. Neustar will still manage multiple Amazon TLDs after the transition and we look forward to our continued partnership.

The switch more than doubles Nominet’s number of TLDs under management. Its biggest customer to date was MMX, which pushed 20 of its TLDs to the .uk registry in a restructuring a few years ago.

The Amazon loss, and a few others recently, also mean that Neustar is by my back-of-the-envelope calculation no longer the largest back-end when measured by the number of TLDs under management.

Those bragging rights would go to Donuts, which self-manages its own rather large portfolio of 241 TLDs. Neustar would remain the largest provider in terms of service provided to third-party clients.

The Neustar-to-Nominet technical migration appears to have kicked off a couple of weeks ago and emerged Wednesday when Nominet’s Technical Contact information replaced Neustar’s in most of Amazon’s IANA records.

Customers will not have noticed, because the TLDs in question barely have any customers.

The only one of the 35 affected TLDs with any registrations at all is .moi, which has just a couple hundred domains in its zone.

The other affected TLDs, none of which have launched, are: .moi, .yamaxun, .author, .book, .buy, .call, .circle, .fast, .got, .jot, .joy, .like, .pin, .read, .room, .safe, .smile, .tushu, .wanggou, .spot, .tunes, .you, .talk, .audible, .deal, .fire, .now, .kindle, .silk, .save, .hot, .pay, .secure, .wow and .free.

The TLDs remaining with Neustar are: .bot, .zero, .ポイント, .書籍, .クラウド, .ストア, .セール, .coupon, .zappos, .ファッション, .食品, .song, .家電, .aws, .imdb, .prime, and .通販.

Six of the TLDs staying with Neustar have launched, but only one, .bot, has more than 100 registrations.

.bot is a tightly restricted, experimental space currently in a long-term “limited registration period” which is not due to end until next January. It has around 1,500 names in its zone file.

Four of Amazon’s dot-brands are staying with Neustar, which is probably the most enthusiastic cheerleader for dot-brands out there, and four are going to Nominet.

Neustar appears to be keeping all of Amazon’s internationalized domain names. Nominet currently manages no IDNs.

How important the adjustment is from a dollar perspective would rather depend on what the per-domain component of the deals were, and whether Amazon ever plans to actually make its gTLDs commercially available.

In recent weeks, XYZ.com also moved its recently acquired .baby gTLD from Neustar, where it had been an unused dot-brand, to preferred provider CentralNic, while .kred and .ceo, both under the same ownership, also switched to CentralNic.

“Just give up!” ICANN tells its most stubborn new gTLD applicant

Kevin Murphy, April 8, 2019, Domain Policy

ICANN has urged the company that wants to run .internet as new gTLD to just give up and go away.

The India-based company, Nameshop, actually applied for .idn — to stand for “internationalized domain name” — back in the 2012 application round.

It failed the Geographic Names Review portion of the application process because IDN is the International Standards Organization’s 3166-1 three-letter code for Indonesia, and those were all banned.

While one might question the logic of applying for a Latin-script string to represent IDNs, overlooking the ISO banned list was not an incredibly stupid move.

Even a company with Google’s brainpower resources overlooked this paragraph of the Applicant Guidebook and applied for three 3166-1 restricted strings: .and, .are and .est.

But rather than withdraw its .idn bid, like Google did with its failed applications, Nameshop decided to ask ICANN to change its applied-for string to .internet.

There was a small amount of precedent for this. ICANN had permitted a few applicants to correct typos in their applied-for strings, enabling DotConnectAfrica for example to correct its nutty application for “.dotafrica” to its intended “.africa”.

But swapping out .idn for .internet was obviously not a simple correction but rather looked a complete upgrade of its addressable market. Nobody else had applied for .internet, and Nameshop was well aware of this, so Nameshop’s bid would have been a shoo-in.

To allow the change would have opened the floodgates for every applicant that found itself in a tricky contention set to completely change their desired strings to something cheaper or more achievable.

But Nameshop principal Sivasubramanian Muthusamy did not take no for an answer. He’s been nagging ICANN to change its mind ever since.

There’s a lengthy, rather slick timeline of his lobbying efforts published on the Nameshop web site.

He filed a Request for Reconsideration back in 2013, which was swiftly rejected by the ICANN board of directors.

In July 2017, he wrote to ICANN to complain that Nameshop’s string change request should be treated the same as any other:

It seems that if ICANN can allow string changes from a relatively undesirable name to a more desireable name based on misspelling, then ICANN should allow a change from a desireable name in three characters(IDN) to longer name in eight characters (Internet) based on confusion with geographical names

Meetings with ICANN staff, the Ombudsman, the Governmental Advisory Committee and others to discuss his predicament several times over the last several years have proved fruitless.

Finally, today ICANN has published a letter (pdf) it sent to Muthusamy on Friday, urging him to ditch his Quixotic quest and get his money back. Christine Willett, VP of gTLD operations, wrote:

Given we are unable to take further action on Nameshop’s application, we encourage you to withdraw the application for a full refund of Nameshop’s application fee.

I doubt this is the first time ICANN has urged Nameshop to take its money and run, but it seems ICANN is now finally sick of talking about the issue.

Willett added that ICANN staff and directors “politely decline” his request for further in-person meetings to discuss the application, and encouraged him to apply for his desired string in the next application round, whenever that may be.

Data beats Merdinger to head universal acceptance group

Kevin Murphy, March 12, 2019, Domain Policy

Email entrepreneur and internationalized domain name expert Ajay Data has been named as the new chair of the group that is struggling to promote the universal acceptance of top-level domains across the internet.

Data, who replaces Afilias COO Ram Mohan after a four-year term, beat GoDaddy’s VP of domains Rich Merdinger in a secret ballot of the Universal Acceptance Steering Group this week.

The number of votes each candidate received were not disclosed.

India-based Data is founder and CEO of Xgenplus, a developer of enterprise email servers with a focus on support for non-Latin scripts and internationalized domain names.

He’s been intimately involved in all things IDN for many years.

The UASG is an independent group, which receives funding from ICANN, dedicated to reaching out to software and web site developers to ensure their systems can support domain names in all scripts, including IDNs, as well as raise awareness of new gTLDs.

Neustar completes .in migration

The transfer of India’s suite of ccTLDs from Afilias to Neustar is done.

NIXI, the .in registry, announced today: “The transition of .IN to its new Neustar-backed Registry platform is now complete.”

With 2.2 million names, not counting names in NIXI’s plethora of localized transliterations, .in is the third-largest TLD migration, behind the 3.1 million .au names that made the reverse journey from Neustar to Afilias last year and the 2.7 million .org names that went from Verisign to Afilias in 2003.

The .in migration started yesterday. NIXI had expected up to 48 hours downtime at the registry EPP level, with obviously no DNS downtime.

The name servers for .in and its IDN equivalents currently all simultaneously include Afilias-owned and Neustar-owned servers.

An Afilias lawsuit against the Indian government, which claimed Neustar lacked experience with Indian scripts and attempted to block the transition, appears to have been dropped last week.

Neustar is reportedly charging NIXI $0.70 per transaction, $0.40 less than Afilias had bid to renew its contract. It won the contract after an open bidding process last August.

Right of the colon? IDN getting killed over dot confusion

Kevin Murphy, February 11, 2019, Domain Registries

An internationalized domain name ccTLD is reportedly getting buried because of a confusion about how many dots should appear.

Armenia’s .հայ (.xn--y9a3aq) today has fewer than 300 registered domains, well under 1% of the volume enjoyed by the Latin-script .am, apparently due to a unique quirk of the Armenian language.

According to a report in the local tech press, sourcing a registry VP, .հայ domains are not working because of how the Armenian script uses punctuation.

In Armenian, a full-stop or period is represented by two vertically aligned dots called a verjaket that looks pretty much identical to a colon in English and other Latin-based languages.

A single dot, looking and positioned exactly like a Latin period, is called a mijaket and is used in the same way English and other languages use a colon.

It’s not entirely clear whether the problem lies with the user, the keyboards, the browsers, or elsewhere, but it’s plain to see how confusion could arise when you have Armenian-script characters on both sides of a Latin-script dot.

The registry, ISOC Armenia, is today reporting just 298 .հայ domains, compared to 34,354 .am domains.

The Latin-script ccTLD has benefited in the past from its association elsewhere with AM radio. It’s also sometimes used as a domain hack, including by Instagram’s URL shortener.

It’s probably worth noting that while Armenia seems to have a unique problem, it’s far from unusual for an IDN ccTLD to perform poorly against its Latin stablemate.

.հայ, which transliterates to “.hay”, is an abbreviation of the Armenian name for Armenia, Հայաստան or “Hayastan”. It was delegated by ICANN in 2015 as part of its IDN ccTLD fast-track program.

Armenian has fewer than seven million speakers worldwide. Armenia has roughly three million inhabitants.