Latest news of the domain name industry

Recent Posts

.tech gTLD startups “raise $2 billion”

Kevin Murphy, August 28, 2019, Domain Registries

Tech startups using domain names in the .tech gTLD have raised $2 billion in venture capital financing over the last two years, according to Radix.

The registry looked at startups listed on Crunchbase as of June and found 650 companies using .tech domains. Of these, 170 of them had raised $2 billion in funding.

About 250 TLDs are in use by Crunchbase-listed startups, according to Radix.

According to a list provided by the company, funding amounts range from a modest $50,000 (obtained by the likes of the VR firm at virtualspaces.tech) to $620 million (obtained by the self-driving car company at aurora.tech).

Not every company on the list is still in business (if name resolution is any guide), and some of the .tech names bounce visitors to longer .com domains.

Meanwhile, domainer Morgan Linton has done a bit of similar research and discovered that 43% of the “top pick” startups appearing at Disrupt, the conference that like Crunchbase is owned by TechCrunch, are not using .com domains.

It’s a smaller sample size, but according to Linton, 18% of them use .io names. Most of the non-coms are on ccTLDs, in fact. The only new gTLD on his list is Google’s .app.

Disrupt made headlines in the domain world in 2010 when it launched its first conference web site on a .co domain, to coincide with the international launch of Colombia’s ccTLD by .CO Internet.

But that marketing deal lapsed after a year. Disrupt is back on techcrunch.com and disrupt.co is back in registry hands as a “premium” reserved name.

.co still appears on Linton’s list, however, so the initial partnership may still be bearing fruit.

1 Comment Tagged: , , , , , , , ,

Whois killer deadline has passed. Did most registrars miss it?

Kevin Murphy, August 28, 2019, Domain Registrars

The deadline for registrars to implement the new Whois-killer RDAP protocol passed yesterday, but it’s possible most registrars did not hit the target.

ICANN told registrars in February (pdf) that they had six months to start making RDAP (Registration Data Access Protocol) services available.

RDAP is the replacement for the age-old Whois protocol, and provides virtually the same experience for the end user, enabling them to query domain ownership records.

It’s a bit more structured and flexible, however, enabling future services such as tiered, authenticated access.

Despite the August 26 deadline coming and going, ICANN records suggest that as many as three quarter of accredited registrars have not yet implemented RDAP.

The IANA department started publishing the base URLs for registrar RDAP servers recent.

According to this list, there are 2,454 currently accredited registrars, of which only 615 (about 25%) have an RDAP server.

But I’m not convinced this number is particularly useful.

First, just because a registrar’s RDAP server is not listed, does not mean it does not have one.

For example, the two largest registrars, Tucows and GoDaddy, do not have servers on the list, but both are known to have been working on RDAP services for a long time through public pilots or live services. Similarly, some CentralNic registrars have servers listed while others do not.

Second, of the 1,839 accreditations without servers, at least 1,200 are DropCatch.com shells, which tips the scales towards non-compliance considerably.

Still, it seems likely that some registrars did in fact miss their deadline. How stringently ICANN chooses to enforce this remains to be seen.

ICANN itself replaced its “Whois” service with a “Lookup” service last month.

According to Michele Neylon of the registrar Blacknight, contracted parties can also discover RDAP URLs via ICANN’s closed RADAR registrar information portal.

RDAP and Whois will run concurrently for a while before Whois takes its final bow and disappears forever.

Comment Tagged: , ,

CIRA replaces CORE as emergency backup registry

Kevin Murphy, August 28, 2019, Domain Registries

ICANN has switched around its line up of emergency registry providers, swapping out CORE Association for CIRA.

The organization last night announced that its three newly contracted Emergency Back-End Registry Operators are Nominet, CNNIC, and CIRA.

EBEROs are failsafe registries that will take over any gTLD that has failed or is on the verge of failing outright, putting its customers domains at risk.

The EBERO is responsible for winding down these gTLDs in an orderly fashion, giving registrants the chance to migrate to a different TLD.

So far, only .wed has entered the program, when the project with the imaginative business model of making it impractical to renew domains went out of business in 2017.

Nominet now caretakes .wed under the EBERO program.

Both Nominet (.uk) and CNNIC (.cn) have been approved EBEROs since 2013, under five-year contracts with ICANN.

CORE was also approved in 2013, but appears to have lost its contract. It’s been replaced by CIRA, the Canadian Internet Registry Association.

“We are honoured to be among this select group of trusted registry operators,” Dave Chiswell, VP of product development for CIRA, said in a statement. He said CIRA only suffered eight hours of downtime when it migrated .ca to a new back-end platform recently.

A key reason for CIRA replacing CORE is very likely geography. When ICANN put out its request for proposals last year, it made a big deal about how it wanted coverage in Europe, Asia and North America — where most gTLD registries are concentrated.

CORE is based in Switzerland. CIRA is obviously based in Canada and CNNIC is Chinese.

Another side-effect of the contract renegotiations is that ICANN is now paying 30% less for the services of the three providers, according to a recent board resolution.

The three providers are contracted for five years.

Whether, and to what extent, they’ll ever actually be triggered to provide EBERO services is open to debate.

Currently, there are six gTLDs in advanced stages of ICANN compliance proceedings, putting them at risk of having their contracts revoked: .whoswho, and five Persian-themed strings.

It’s not inconceivable than one or more of these gTLDs could wind up in EBERO, but ICANN appears to be cutting the registries a lot of slack to resolve their issues.

6 Comments Tagged: , , , , ,

The Amazon is burning. Is this good news for .amazon?

Kevin Murphy, August 26, 2019, Domain Policy

With the tide of international opinion turning against Brazil due to the ongoing forest fires in the Amazon, could we see governments change their tune when it comes to Amazon’s application for .amazon?

A much higher number of forest fires than usual are currently burning in the region, largely in Brazil, which critics led by environmentalists and French president Emmanuel Macron have blamed on relaxed “slash and burn” farming policies introduced by new Brazilian president Jair Bolsonaro.

The rain forest is an important carbon sink, said to provide 20% of the world’s oxygen. The more of it is lost, the harder it is to tackle climate change, the argument goes.

It’s been an important topic at the Macro-hosted G7 summit, which ends today. Even the bloody Pope has weighed in.

Arguably, the stakes are nothing less than the survival of human civilization and life on Earth itself.

And this is a story about domain names. Sorry. This is a blog about domain names. My hands are tied.

Amazon the company has been fighting governments over its application for .amazon, along with the Chinese and Japanese translations, for over six years.

ICANN’s Governmental Advisory Committee was responsible for killing off .amazon in 2013 after it decided by consensus that Amazon’s application should not proceed.

That decision was only reached after the US, under the Obama administration, decided to abstain from discussions.

The US had been protecting Amazon by blocking GAC consensus, but changed its tune partly in order to throw a bone to world leaders, including then-president of Brazil Dilma Rousseff, who were outraged by CIA analyst Edward Snowden’s revelations of widespread US digital espionage.

After ICANN dutifully followed the GAC advice and rejected Amazon’s gTLD applications, Amazon appealed via the Independent Review Process and, in 2017, won.

The IRP panel ruled that the GAC’s objection had no clear grounding in public policy that could be gleaned from the record. It told ICANN to re-open the applications and evaluate them objectively.

Ever since then, the GAC’s advice to ICANN has been that it must “facilitate a mutually acceptable solution” between Amazon and the eight nations of the Amazon Cooperation Treaty Organization.

ICANN has been doing just that, or at least attempting to, for the last couple of years.

But the two parties failed to come to an agreement. ACTO wants to have essential veto power over Amazon’s use of .amazon, whereas Amazon is only prepared to offer lists of protected names, a minority position in any policy-setting body, and some sweeteners.

In May this year, ICANN’s board of directors voted to move .amazon along towards delegation, noting that there was “no public policy reason” why it should not.

In June, the government of Colombia filed a Request for Reconsideration with ICANN, demanding it reevaluate that decision.

The RfR was considered by ICANN’s Board Accountability Measures Committee at its meeting August 14, but its recommendation has not yet been published. I’m expecting it to be posted this week.

There’s still opportunity for the GAC to cause mischief, or act as a further delay on .amazon, but will it, in light of some country’s outrage over Brazil’s policy over the rain forest?

One could argue that if the nation that has the largest chunk of Amazon within its borders seems to have little regard to its international importance, why should its claim to ownership of the string “amazon” get priority over a big brand that has offered to protect culturally significant words and phrases?

Remember, as the example of the US in 2012/13 shows us, it only takes one government to block a GAC consensus. If Brazil or Peru continue to pursue their anti-Amazon path, could France throw a spanner in the works, smoothing .amazon’s road to delegation?

Anything’s possible, I suppose, but my feeling is that most governments back ACTO’s position largely because they’re worried that they could find themselves in a similar position of having to fight off an application for a “geographic” string in the next gTLD application round.

Comment Tagged: , , , , , , , , , , , ,

China’s MySpace trainwreck sells its gTLD

Kevin Murphy, August 23, 2019, Domain Registries

A once-hot Chinese social networking company that now sells used cars instead has offloaded its gTLD.

The registry contract for .ren, the Pinyin for the Chinese “人”, meaning “people”, has been transferred from Beijing Qianxiang Wangjing Technology Development Co to ZDNS International.

The original registry is better known by the name Renren.

At the time the new gTLD was applied for in 2012, Renren was at the peak of its powers, discussed in the same breath as Facebook.

A social networking site with close to 60 million active monthly users in China, it had recently raised $800 million by floating on the New York Stock Exchange.

But it has fallen on hard times since, and the site was sold for just $20 million in cash and $40 million of stock last November.

A number of articles around the same time chart its downfall, calling it a “trainwreck”, a “digital ghost town” and, even more embarrassingly, “China’s answer to MySpace”

You get the idea.

Renren the company is still a going concern due to its now-core business of selling used cars in China, but the NYSE threatened to delist its stock a couple of weeks ago because its share price had been below $1 for more than 30 days.

Now, it seems it’s getting rid of its gTLD too.

.ren has been bought (presumably) by ZDNS International, the Hong Kong-based arm of DNS service provider ZDNS.

It’s not a dot-brand. The space is open to all-comers and is currently priced competitively with .com.

The gTLD’s fortunes tracked the site’s declining popularity. It’s been on the slide, volume-wise, for years.

It peaked at around 320,000 zone file domains in November 2016, comparable to other TLDs popular in China, but today stands at around 17,000.

It’s the second registry contract ZDNS has taken over recently. A month ago, I reported it has taken over .fans from CentralNic.

ZDNS was already providing back-end services for .ren.

1 Comment Tagged: , , , , ,