Amazon has started using hard-won .amazon

Amazon has started using its controversial dot-brand gTLD, .amazon.

Six domains — ads.amazon, alexa.amazon, echo.amazon, kindle.amazon, prime.amazon and primevideo.amazon — appear to have come online in the last month or so and all resolve.

Proponents of the dot-brand concept may be mildly disappointed to note that they’re all currently just redirects to the regular amazon.com site. There’s no .amazon branding in the URL bar.

The redirects do not appear to be geo-targeted. Even in the UK, I get punted to the US site.

Still, it’s a rare example of a gTLD in Amazon’s portfolio that’s actually being used. Others, such as .book, have been in the root for many years but have yet to launch.

You’ll recall that Amazon applied for .amazon in 2012 but it was not until last year that it was finally delegated.

The company encountered serious push-back from the Amazon Cooperation Treaty Organization, representing the South American nations in the Amazonia region.

Amazon has offered each nation and ACTO itself the opportunity to register names for their own use in .amazon, but none have yet taken up the offer.

ICANN chair reins in new gTLD timeline hopes

Don’t get excited about the next round of new gTLDs launching any time soon.

That’s my takeaway from recent correspondence between ICANN’s chair and brand-owners who are apparently champing at the bit to get their teeth into some serious dot-brand action.

Maarten Botterman warned Brand Registry Group chair Cole Quinn that “significant work lies ahead” before the org can start accepting applications once more.

Quinn had urged ICANN to get a move on last month, saying in a letter that there was “significant demand” from trademark owners.

The last three-month application window ended in March 2012, governed by an Applicant Guidebook that said: “The goal is for the next application round to begin within one year of the close of the application submission period for the initial round.”

That plainly never happened, as ICANN proceeded to tie itself in bureaucratic knots and recursive cycles of review and analysis.

Any company that missed the boat or was founded in the meantime has been unable to to even get a sniff of operating its own dot-brand, or indeed any other type of gTLD.

Spelling out some of the steps that need to be accomplished before the next window opens, Botterman wrote:

the 2012 Applicant Guidebook must be updated with more than 100 outputs from the SubPro PDP WG; we will need to apply lessons learned from the previous round, many of which are documented in the 2016 Program Implementation Review, and appropriate resources for implementing and conducting subsequent rounds must be put in place. At present it appears that WG recommendations will benefit from an Operational Design Phase (ODP) to provide the Board with information on the operational implications of implementing the recommendations. As part of such an ODP, the Board may also task ICANN org to provide an assessment of some of the issues of concern that the Board raised in its comments on the Draft Final Report, as well as those topics that did not reach consensus and were thus not adopted by the GNSO Council. The outcome of such an assessment could also add to the work that would be required before launching subsequent rounds.

…

The Board notes your views regarding SAC114. We are aware of discussions that took place during ICANN70 and the Board is in communication with the Security and Stability Committee (SSAC) and its leadership, as per the ‘Understand’ phase of the Board Advice Process. As with all advice items received, the Board will treat SAC114 in accordance with that process.

Breaking that down for your convenience…

The reference to “more than 100 outputs from the SubPro PDP WG” refers to the now six-year old Policy Development Process for New gTLD Subsequent Procedures working group of the GNSO.

SubPro delivered its final report in January and it was adopted by the GNSO Council in February.

ICANN asked the Governmental Advisory Committee for its formal input a few weeks ago, has opened the report for a public comment period that ends June 1, and will accept or reject the report at some point in the future.

SubPro’s more significant recommendations include the creation of a new accreditation mechanism for registry back-end service providers and a gaming-preventing overhaul of the contention resolution process.

The “the 2016 Program Implementation Review” is a reference to a self-assessment of the 2012 round that the ICANN staff carried out six years ago, producing a 215-page report (pdf).

That report contains about 50 recommendations covering areas where staff thought the system of actually processing new gTLD applications could possibly be improved or streamlined in subsequent rounds.

The Operational Design Phase (ODP) Botterman refers to is a brand-new phase of ICANN bureaucracy that is currently untested. It fits between GNSO Council approval of recommendations and ICANN board consideration.

The ODP is basically a way for ICANN staff to insert itself into the process, between community policy-making and community policy-approval, to make sure the GNSO’s tenuous consensus-building exercise has not produced something too crazily complicated, ineffective or expensive to implement.

Staff denies this is a power-grab.

The ODP is currently being deployed to assess proposed changes to Whois privacy policy, and ICANN has already stated multiple times that it will also be used to vet SubPro’s work.

Botterman’s reference to “issues of concern that the Board raised in its comments on the Draft Final Report” seems to mean this September 2020 letter (pdf) to SubPro’s chairs, in which the ICANN board outlined some of its initial concerns with SubPro’s proposed policies.

One fairly important concern was whether ICANN has the power under its bylaws (which have changed since 2012) to enforce Public Interest Commitments (now called Registry Voluntary Commitments) that SubPro thinks could be used to make some sensitive gTLDs more trustworthy.

The reference to SAC144 may turn out to be a big stumbling block too.

SAC114 is the bombshell document (pdf) submitted by the Security and Stability Advisory Committee in February, in which ICANN’s top security community members openly questioned whether allowing more new gTLDs is consistent with ICANN’s commitment to keep the internet secure.

While SAC114 seems to reluctantly acknowledge that the program will likely go ahead regardless, it asks that ICANN do more to address so-called “DNS abuse” before proceeding.

Given that the various factions within the ICANN community can’t even agree on what “DNS abuse” is, how ICANN chooses to “understand” SAC114 will have a serious impact on how much further the runway to the next round gets extended.

In short, Botterman is warning brand owners not to hold their breath anticipating the next application window. I think I even detect some serious skepticism as to whether demand is really as high as Quinn claims.

And quite beyond the stuff Botterman outlines in his letter, there’s presumably going to be at least one round of review and revision on the next Applicant Guidebook, as well as the time needed for ICANN to build or upgrade the systems it needs to process the applications, to hire evaluators and resolution providers, and to make sure it conducts a sufficiently long and broad global marketing program so that potential applicants in the developing world don’t feel left out. And that’s a non-exhaustive list.

Introducing competition into the registry space is of course one of ICANN’s foundational raisons d’être.

After the org was founded in September 1998, it took less than two years before it opened up the first new gTLD application round.

It was another three years before the second round launched.

It then took eight and a half years for the 2012 window to open.

It will be well over a decade from then before anyone next gets the opportunity to apply for a new gTLD. It’s entirely feasible that we’ll see an applicant in the next round headed by somebody who wasn’t even born when the first window opened.

Two world wars and one dot-brand? Americans beat Germans in long-running gTLD fight, kinda

A chemicals company called Merck has beaten another chemicals company called Merck for the right to run .merck as a dot-brand gTLD.

But it looks like we may be looking at an unprecedented case of a shared dot-brand.

US-based Merck Registry Holdings and Germany-based Merck KGaA appear to have resolved their long-running battle over the string, with the German company recently withdrawing its application, enabling its rival to sign a contract with ICANN and go live on the internet.

But it’s not as straightforward as one applicant emerging victorious over the other. Recent changes to the American company’s winning gTLD application strongly suggest that the two companies intend to share the space.

The application was substantially rewritten in March to make it clear that American Merck plans to allow unaffiliated third parties to register .merck names, and that it may substantially change its eligibility policies not long after launch.

Whereas its original 2012 application was pretty much boilerplate dot-brand territory, the March 2021 version is more nuanced. It now talks about extending eligibility to “other registrants” rather than merely “licensees”, for example.

The application now says it “reserves the right to consider allowing third party registrants outside of current affiliate or subsidiary relationships to own .MERCK domains at a future date.”

But, more importantly, it now also says that it intends to transfer its .merck Registry Agreement to a new shell company, London-based MM Domain Holdco Ltd, shortly after ICANN signs it off.

Company records show that MM Domain Holdco has directors — trademark lawyers — from both the American and German companies.

So we’re looking at some kind of shared dot-brand, it seems. If you don’t count Amazon’s uneasy deal with South American governments, that’s pretty much unprecedented for new gTLDs.

The US applicant is a subsidiary of Merck & Co Inc, a New York-listed company with a market cap of $197 billion. The German company is listed in Frankfurt with a market cap of €17 billion.

The German firm is 350 years old and was the parent of the American company until it was seized, and eventually re-privatized as a separate entity, by the US government during World War I.

Both have trademark rights to the term “Merck” and a decades-old cooperation agreement, but have nevertheless been in legal disputes over the mark in recent years.

It will be interesting to see whether the two Mercks ultimately share and actively use .merck, or like so many other dot-brands merely own a defensive, inactive gTLD.

The resolution of the contention set comes after the better part of a decade and many years of negotiations and legal tussles with ICANN.

ICANN had been bent on forcing the companies to a last-resort auction of which it would be the financial beneficiary. Whether this was because it wanted to force the Mercks to the negotiating table to resolve their differences amicably, or because it saw dollar signs… you decide. Maybe both.

The Mercks have in recent years repeatedly delayed the auction, using different ICANN appeals mechanisms. The contention set had been in a Cooperative Engagement Process since late last year, but had been slated to go to auction yesterday, May 12.

The settlement occurred before that date, however, so ICANN won’t be getting any auction money this time.

Donuts adds another TLD to its stable as Richemont finally bows out of new gTLD program

Luxury goods maker Richemont, an early and strong proponent of the new gTLD concept, has got rid of the final string of the 14 it originally applied for.

According to ICANN records, the registry agreement for .watches was officially transferred to Afilias at the end of December, one day before it was in turn acquired by Donuts.

The domain nic.watches current resolves to a placeholder bearing the Afilias branding.

Richemont, the company behind luxury brands such as Cartier and Piaget, now has no TLDs left.

It had applied for nine dot-brands, along with five generic dictionary terms that it at first intended to maintain as single-registrant spaces, before that use case was banned by ICANN.

At the start of the decade, the company was an enthusiastic endorser of new gTLDs, even sending speakers to conferences to promote the concept.

Richemont was also the first registrant of second-level domains in third-party new gTLDs, when it registered Arabic versions of some of its famous brands in December 2013.

But its enthusiasm waned gradually over the last eight years.

Its dot-brands were discarded in tranches, either during the application process or after contracting. Donuts beat it to .jewelry at auction, and it terminated its contracts for Chinese versions of .jewelry and .watches last year.

There’s not much money in internationalized domain names, so now it seems likely these Chinese IDNs were shopped around but failed to find a buyer.

.watches, however, is right in Donuts’ wheelhouse, a niche generic English string related to a specific product or service.

Last month, I reported that Donuts had acquired .markets, .forex, .broker and .trading from Boston Ivy as it exited the new gTLD game, while letting the less-attractive .spreadbetting die on the vine.

ICANN purges another dormant dot-brand

The 89th unwanted dot-brand has filed with ICANN for voluntarily contract termination.

Iveco, an Italian industrial vehicle manufacturer, has told ICANN it no longer wishes to run the .iveco dot-brand.

As is the case with self-terminations more often than not, the gTLD was almost completely unused, with only the obligatory nic.example domain active.

Iveco is a big ole company, with revenue of €4.9 billion ($5.9 billion) a year, so it appears to be a case of a lack of enthusiasm rather than a lack of resources.

Two more dot-brands take the easy way out

A US insurance giant with close to $50 billion in annual revenue has taken the decision to kill off its two dormant dot-brand gTLDs.

Nationwide Mutual Insurance has informed ICANN that it wants to cancel its .nationwide and .onyourside gTLD contracts.

Neither was being used beyond the obligatory nic.example web sites.

In fact, it appears that Nationwide cared so little about its dot-brands that both NIC sites inadvertently plug another, unaffiliated gTLD.

The text on both sites reads:

To better serve our members, Nationwide has secured a top-level domain.

Now, when you visit a Nationwide.Insurance website, you can have confidence that it’s from the company you trust – Nationwide.

But Nationwide does not run .insurance, that’s owned by fTLD. It does however have nationwide.insurance registered and parked with the same messaging.

They’re the 87th and 88th dot-brands to cancel their ICANN registry agreements.

Fuji Xerox kills off gTLD after rebrand

Fuji Xerox has become the latest multi-billion-dollar company to ditch its dot-brand gTLD.

The Japanese-American company, a joint venture of Xerox and Fuji, has told ICANN it wants to terminate its registry contract for .fujixerox, and ICANN has indicated its intention to let the string die.

The gTLD was not in use, beyond the mandatory nic.fujixerox placeholder site.

That said, the termination appears to be primarily due to a rebranding as the joint venture fizzles out.

Fuji Xerox is, according to Wikipedia, the world’s oldest Japanese-American joint-venture company, at 59 years old. It’s in the document processing space and had $11 billion in annual revenue.

But the companies said last year they would end the relationship, with Xerox no longer providing its tech, leading to rebranding the company Fujifilm Business Innovation. The dot-brand is clearly no longer needed.

Xerox also owns .xerox, and it’s not using that either. There is no .fuji or .fujifilm.

.fujixerox the first dot-brand to jump off the cliff this year, and the 86th in total.

Three more new gTLDs blink out of existence

Another new gTLD registry operator, representing three dot-brands, has told ICANN that they want their contracts scrapped.

The registry is CNH Industrial, and the gTLDs are .case, .caseih and .newholland.

To be honest, if you’d asked me yesterday whether these TLDs existed or not, I would have guessed not.

But CNH is a pretty big deal — a New York-listed multinational maker of construction and agricultural equipment and vehicles with over $28 billion in revenue last year. Case and New Holland are two of its brands.

The brands do not appear to have been discontinued, so this seems to be a typical case of company simply deciding against using its TLDs, which it probably shouldn’t have applied for in the first place.

None of them has any domains beyond the mandatory nic.example site.

Interestingly, it has a fourth dot-brand, .iveco, representing a vehicle brand, that so far it does not seem to have terminated, judging by ICANN records. But that’s not in use either.

The terminations bring the total dead dot-brands to 85, 16 of which died this year.

Big pharma firm dumps its gTLD

Indian pharmaceuticals company Lupin has become the latest new gTLD registry to drop its dot-brand.

The firm told ICANN recently that it no longer wishes to continue running .lupin, which it has never actually used.

It’s the 82nd dot-brand to self-terminate, the 13th this year.

Lupin is one of the world’s largest manufacturer of generic medicines, with revenue in excess of $2 billion per year.

Amazon waves off demand for more government blocks

Amazon seems to have brushed off South American government demands for more reserved domains in the controversial .amazon gTLD.

VP of public policy Brian Huseman has written to Amazon Cooperation Treaty Organization secretary general Alexandra Moreira to indicate that Amazon is pretty much sticking to its guns when it comes to .amazon policy.

Moreira had written to Huseman a few weeks ago to complain that the Public Interest Commitments included in Amazon’s registry contract with ICANN do not go far enough to protect terms culturally sensitive to the Amazon region.

She wanted more protection for the “names of cities, villages, mountains, rivers, animals, plants, food and other expressions of the Amazon biome, biodiversity, folklore and culture”.

ACTO also has beef with an apparently unilateral “memorandum of understanding” (page 8 of this PDF) Amazon says it has committed to.

That MoU would see the creation of a Steering Committee, comprising three Amazon representatives and nine from ACTO and each of its eight member states, which would guide the creation and maintenance of .amazon block-lists.

ACTO is worried that the PICs make no mention of either the committee or the MoU, and that Huseman is the only signatory to the MoU, which it says makes the whole thing non-binding.

Moreira’s August 14 letter asked for Amazon and ACTO to “mutually agree on a document”, and for the PICs to be amended to incorporate the MoU, making it binding and enforceable. She also asked for potentially thousands of additional protected terms.

Huseman replied August 28, in a letter seen by DI, to say that Amazon is “committed to safeguard the people, culture, and heritage of the Amazonia region” and that the PICs and MoU “have the full backing and commitment” of the company.

He added:

We are disappointed that we have not yet received the names and contact information of those within ACTO who might serve on the Steering Committee contemplated in the MOU because their knowledge and help could be very beneficial as we move forward to implement the PICs.

The letter does not address ACTO’s demand for a binding bilateral agreement, nor the request for additional blocks.

ICANN itself is no longer a party to these negotiations, having washed its hands of the sorry business last month.