Amazon and Google among .internal TLD ban backers

Google and Amazon have publicly backed ICANN’s plan to reserve the top-level domain .internal for private behind-the-firewall uses.

ICANN picked the string “internal” as the one that it will promise to never delegate to the DNS root, allowing network administrators and software developers to confidently use it with a lower risk of data leakage should the TLD come under a registry’s control in future.

The public comment period over its choice is coming to a close tomorrow, with a generally supportive vibe coming from the 30-odd comments submitted so far.

Notably, tech giants Amazon and Google have both filed comments backing .internal, with both companies saying that they already use the TLD extensively for internal purposes (Google in its Cloud services) and that to allow it to be delegated in future would cause big problems.

Some commenters niggled that .internal is too long, and that something like .local or .lan, both already reserved, might be better. Others wondered why strings such as .corp or .home, which are already effectively banned due to the high risk of name collisions, were not chosen instead.

Amazon planning new push into registrar market?

Amazon has kept a pretty low profile to date both as a registry and registrar, but there are reasons to believe it’s on the verge of becoming a more visible player in the market.

The e-commerce and web services giant has secured a second ICANN registrar accreditation and appears to be readying a new domain-focused web site.

The subsidiary Amazon Domain Registrar US LLC picked up its accreditation this week, and its official web site domain is domains.amazon, which was registered November 29.

The domain does not currently resolve from where I’m sitting.

Amazon already uses the dot-brand domain registry.amazon for its 50-odd new gTLDs, almost all of which remain unlaunched.

In the registrar market, Amazon’s subsidiary Amazon Registrar Inc has been accredited for well over a decade and has been taking registrations since 2015 as part of its Route 53 managed DNS service.

It’s not a conventional registrar storefront by any stretch — registrations seem to be available only via the management console used by existing Route 53 customers — but it has amassed over 1.3 million gTLD registrations so far.

So could domains.amazon become the newest player in the retail registrar market? Smaller registrars that cheered the exit of the Google brand from the registrar space may soon have a new big boy to contend with.

Amazon governments not playing ball with Amazon’s .amazon

Governments in South America are refusing to play nicely with Amazon over its controversial .amazon dot-brand.

Speaking at ICANN 74 in The Hague this morning, Brazil’s representative on the Governmental Advisory Committee said that ICANN’s decision to delegate .amazon to the retail giant a couple of years ago contravenes the multi-stakeholder process and is “incompatible with the expectations and sovereign rights of the Amazon peoples”.

Luciano Mazza de Andrade said that the Amazon Cooperation Treaty Organization, which is membered by the eight governments of the Amazonia region, wrote to Amazon in December to decline an offer to reserve a number of .amazon domains.

Amazon’s contract with ICANN contains a Public Interest Commitment that grants ACTO and its members one usable .amazon domain each, and 1,500 blocks overall for culturally sensitive strings.

The company had given ACTO a December 19 deadline to submit its list of strings, but it seems its members do not acknowledge the contract’s validity.

“Among other points it underlined that ACTO member states did not give consent to the process of adjudication of the .amazon top-level domain and that they did not consider themselves bound by said decision or the conditions attached to it including the above mentioned Public Interest Commitment,” Brazil’s rep said.

He added that “the adjudication of the top-level domain to a private company without our approval and authorization does not respect the applicable rules, expressly contravenes the multistakeholder nature of ICANN’s decision-making process of interest, and is incompatible with the expectations and sovereign rights of the Amazon peoples.”

ACTO has previously described the delegation of .amazon as “illegal and unjust”.

Amazon has a handful of live .amazon domains, which redirect to various services on amazon.com.

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.

Amazon sold rights to .box gTLD for $3 million

Amazon relinquished its rights to the .box gTLD five years ago for $3 million, according to court documents seen by DI.

Amazon was one of two applicants for .box, the other being a company called NS1 (that’s the numeral 1; this has nothing to do with Network Solutions).

According to a complaint filed a couple of years ago that I came across today, Amazon agreed to withdraw its application, giving its rival an unobstructed shot at the gTLD, for $3 million.

It was a private settlement of the contention set and the payout was not publicly revealed at the time.

A $3 million deal puts .box in the same ballpark as public auctions such as MMX’s .vip and Johnson & Johnson’s (now XYZ.com’s) .baby.

While the deal is years old, I thought the data point was worth publishing.

NS1’s application suggests that its business plan was to offer registrants cloud storage services, along the lines of DropBox.

But the ICANN contract was sold to Intercap, which also runs .inc and .dealer, earlier this year. The plan now appears to be to operate it as an open niche gTLD, but no launch dates have been announced.

It’s not known how much the gTLD sold for second time around.

These eight companies account for more than half of ICANN’s revenue

While 3,207 companies contributed to ICANN’s $141 million of revenue in its last fiscal year, just eight of them were responsible for more than half of it, according to figures just released by ICANN.

The first two entries on the list will come as no surprise to anyone — they’re .com money-mill Verisign and runaway registrar market-leader GoDaddy, together accounting for more than $56 million of revenue.

Registries and registrars pay ICANN a mixture of fixed fees and transaction fees, so the greater the number of adds, renews and transfers, the more money gets funneled into ICANN’s coffers.

It’s perhaps interesting that this top-contributors list sees a few companies that are paying far more in fixed, per-gTLD fees than they are in transaction fees.

Binky Moon, the vehicle that holds 197 of Donuts’ 242 gTLD contracts, is the third-largest contributor at $5.2 million. But $4.9 million of that comes from the annual $25,000 fixed registry fee.

Only 14 of Binky’s gTLDs pass the 50,000-name threshold where transaction fees kick in.

It’s pretty much the same story at Google Registry, formally known as Charleston Road Registry.

Google has 46 gTLDs, so is paying about $1.1 million a year in fixed fees, but only three of them have enough regs (combined, about one million names) to pass the transaction fees threshold. Google’s total funding was almost $1.4 million.

Not quite on the list is Amazon, which has 55 mostly unlaunched gTLDs and almost zero registrations. It paid ICANN $1.3 million last year, just to sit on its portfolio of dormant strings.

The second and third-largest registrars, Namecheap and Tucows respectively, each paid about $1.7 million last year.

The only essentially single-TLD company on the list is Public Interest Registry, which runs .org. Despite having 10 million domains under management, it paid ICANN less than half of Binky’s total last year.

The anomaly, which may be temporary, is ShortDot, the company that runs .icu, .cyou and .bond. It paid ICANN $1.6 million, which would have been almost all transaction fees for .icu, which peaked at about 6.5 million names earlier this year.

Here’s the list:

[table id=62 /]

Combined, the total is over $70.5 million.

The full spreadsheet of all 3,000+ contributors can be found over here.

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.

Countries ask Amazon for thousands more domain blocks

The eight South American nations of the Amazon region are demanding Amazon block more domain names in the recently delegated .amazon gTLD.

Amazon Cooperation Treaty Organization secretary general Alexandra Moreira has written to Amazon VP of public policy Brian Huseman to complain that Amazon’s current set of “cultural” safeguards do not go far enough.

The August 14 letter, which was forwarded to DI, seems to mark a new phase of bilateral talks, after ICANN washed its hands of its reluctant role of third-party facilitator last month.

Currently, .amazon is governed by a set of Public Interest Commitments in its registry contract designed to protect the “Culture and Heritage specific to the Amazonia region”.

ACTO, as well as disagreeing with the use of the term “Amazonia”, has a narrow interpretation of the PICs that Moreira says is “insufficient to ensure respect for the historic and cultural heritage of the Amazon region”.

Under ACTO’s reading, Amazon is only obliged to block a handful of domains from use, namely the words “OTCA”, “culture”, “heritage”, “forest”, “river”, “rainforest”, the names of indigenous peoples and national symbols.

Moreira writes:

That would leave out a vast number of terms that can still cause confusion or mislead the public about matters specific to the Amazon region, such as the names of cities, villages, mountains, rivers, animals, plants, food and other expressions of the Amazon biome, biodiversity, folklore and culture.

ACTO wants the list of protected domains to be expanded to include these additional categories, and for Amazon and ACTO to sign a binding agreement to that effect.

Given that the Amazon forest is home to literally tens of thousands of distinct species and Brazil alone has over 5,500 municipalities, this could translate to a hell of a long list.

I should probably note that the .amazon PICs also offer ACTO the chance to block 1,500 strings of its own choosing, so ACTO’s narrow interpretation may not tell the whole story.

ICANN washes its hands of Amazon controversy

ICANN has declined to get involved in the seemingly endless spat between Amazon and the governments representing the Amazonia region of South American.

CEO Göran Marby has written to the head of the Amazon Cooperation Treaty Organization to say that if ACTO still has beef with Amazon after the recent delegation of .amazon, it needs to take it up with Amazon.

ACTO failed to stop ICANN from awarding Amazon its dot-brand gTLD after eight years of controversy, with ICANN usually acting as a mediator in attempts to resolve ACTO’s issues.

But Marby yesterday told Alexandra Moreira: “”With the application process concluded and the Registry Agreement in force, ICANN no longer can serve in a role of facilitating negotiation”.

She’d asked ICANN back in May, shortly before .amazon and its Japanese and Chinese translations hit the root, to bring Amazon back to the table for more talks aimed at getting ACTO more policy power over the gTLDs.

As it stands today, Amazon has some Public Interest Commitments that give ACTO’s eight members the right to block any domains they feel have cultural significance to the region.

Marby told Moreira (pdf) that it’s now up to ACTO to work with Amazon to figure out how that’s going to work in practice, but that ICANN’s not going to get involved.

Amazon finally gets its dot-brands despite last-minute government plea

Amazon’s three long-sought dot-brand gTLDs were added to the DNS root last night, despite an eleventh-hour attempt by South American governments to drag the company back to the negotiating table.

.amazon, along with the Japanese and Chinese translations — .アマゾン (.xn--cckwcxetd) and .亚马逊 (.xn--jlq480n2rg) — and its NIC sites have already gone live.

Visiting nic.amazon today will present you with a brief corporate blurb and a link to Amazon’s saccharine social-responsibility blog. As a dot-brand, only Amazon will be allowed to use .amazon domains.

The delegations come despite a last-minute plea to ICANN by the eight-government Amazon Cooperation Treaty Organization, which unsuccessfully tried to insert itself into the role of “joint manager” of the gTLDs.

ACTO believes its historical cultural right to the string outweighs the e-commerce giant’s trademark, and that its should have a more or less equal role in the gTLD’s management.

This position was untenable to Amazon, which countered with a collection of safeguards protecting culturally sensitive strings and various other baubles.

Talks fell through last year and ICANN approved the gTLDs over ACTO’s objections.

ACTO’s secretary-general, Alexandra Moreira, wrote to ICANN (pdf) May 21 to take one last stab at getting Amazon back in talks, telling CEO Göran Marby:

the name “Amazon” pertains to a geographical region constituting an integral part of the heritage of its countries. Therefore, we Amazonians have the right to participate in the governance of the “.amazon” TLD.

…

Our side is ready to resume negotiations on the TLD’s governance with the Amazon Corporation., from the point where their side interrupted it, with a view to arriving at a satisfactory agreement.

Her letter came in response to an earlier Marby missive (pdf) that extensively set out ICANN’s case that talks fell apart due to ACTO repeatedly postponing and cancelling scheduled meetings.

Despite the fact that Amazon’s basically got what it wanted, seven years after filing its gTLD applications, ACTO’s members didn’t get nothing.

The contracts Amazon signed with ICANN back in December have Public Interest Commitments in them that allow the governments to reserve up to 1,500 culturally sensitive strings from registration, as well as giving each nation its own .amazon domain.