Is a .tree gTLD very cool or very silly?

.tree is one of the first-ever publicly announced gTLD applications, predating even the 2012 application round, and it seems to have been proposed for a second time.

A web site using dottree.org, registered a week ago, is saying there’s a plan to apply for .tree in the forthcoming ICANN application round, with a charitable goal.

The project says it will donate a dollar from every .tree domain registration and annual renewal to a charity that plants trees in Dubai, with each $1 donation putting one tree in the ground.

At first glance, it seems like a nice idea, but I’m not sure it holds up to closer inspection.

There may be virtue-signalling advantages to running a site on a .tree domain if you’re in the environmental game or lumber business.

But if a registrant’s primarily interest is getting trees planted, why not just donate a buck to a reforestation charity directly? Why not donate the full amount you would otherwise have spent on the domain? Or more?

And how much demand would there be for .tree domains on their own merits?

Fortunately, DI’s new Stringtel tool has some data there. According to Stringtel, about 47,000 current .com/.net/.org domain names end in the substring “tree”, which may give an indication of potential registrations. About 2,000 of those end in “familytree”.

That’s the same frequency as we see domains end in “wine”, “dog”, or “paris”, and the three gTLDs matching those strings each have 17,000 to 18,000 domains under management, which is not terrible.

Should .tree perform just as well, envelope-based calculation suggest it would create the equivalent of a smallish forest that could be traversed on foot in minutes and not really suck much CO2 out of our increasingly fragile atmosphere.

But the .tree proposal would have a second forest of the same size planted in the second year (assuming 100% domain renewals) and so on. The effect would stack up over time, so maybe the idea does have merit.

The internet just got its first new TLD since 2022

There’s a new gTLD in the root, the first time ICANN has added a string in over four years.

Don’t get too excited though: it’s a dot-brand, kinda.

As of the weekend, .merck is live and resolving, though only the mandatory nic.merck registry domain exists right now.

The gTLD is interesting because it seems to be a rare example of two companies with the same name sharing a dot-brand.

The only other such arrangement I’m aware of is .sas, which is shared by the SAS Institute and SAS Airline, neither of which actually use it.

.merck seems to be jointly controlled by two pharmaceutical companies, one American and one German, both called Merck, which were under common ownership until World War I split them apart.

After they both applied for .merck in ICANN’s 2012 application round, over a decade of lawyering followed before they finally came to an arrangement.

There’s no Specification 13 in the .merck Registry Agreement, so it’s not technically an exclusive-use dot-brand at this time.

The back-end registry services provider, perhaps surprisingly, is South Africa-based DNS Africa, in what seems to be the company’s first deal outside its home continent.

Kid-friendly domains could be reborn

With governments around the world increasingly looking at reducing the harmful effects on the internet on children, it seems child-friendly domain name projects may see a resurgence.

The US government’s new hunt for a registry operator for .us, launched this week, contains a fairly explicit call for whichever company wins the contract to “revitalize” the long-dormant .kids.us space.

And I’m aware of one potential new gTLD applicant that wants to apply for a regulated kid-friendly gTLD when ICANN opens up its application window at the end of the month.

The US National Telecommunications and Information Administration said in its .us RFP:

The Contractor shall offer one or more innovative approaches to revitalize the use of the kids.us domain that are consistent with its objective of providing a safe space on the internet for children age 13 or younger, as intended by the Dot Kids Act. In the event a decision is made to reactivate the kids.us domain without any changes to the Dot Kids Act or selection of alternative uses, the Contractor shall be prepared to maintain and operate the second-level kids.us domain as specified by the Dot Kids Act.

It’s not the first time NTIA has tried to get the .us registry operator — now GoDaddy, formerly Neustar — to exhume the .kids.us project, which was closed down in 2012 after fewer than 1,000 registrations and half a dozen active web sites. Prior attempts were unsuccessful.

.kids.us was created by US legislation in 2002, largely as a way for legislators could feel good about themselves in an era when the web was still quite new and frightening and a lot wilder than it is today.

But that was before the dawn of social media and smartphones, the two technology trends driving much of the political focus on child online safety in the 2020s.

At least one new gTLD applicant intends to apply for a child-friendly gTLD this year, known as The Reservoir Project or (preliminarily) the Child Online Safety Association, run by lawyer S Harrison Knudson. The gTLD in question would be .haven.

The early-stage concept would see the registry work patent-pending technology and with ISPs, which would charge customers service fees and split the profit with the registry.

There are already two kid-oriented gTLDs out there — .kids itself and the Russian-language .дети (“.children”).

DotKids launched .kids in late 2022 and has so far accumulated 6,368 domains in its zone file. That’s actually not bad for a niche new gTLD, and based on some of the most uncomfortable Google searches I’ve ever done it looks like the registry is doing a pretty good job of keeping the namespace clean.

.дети has been around longer but has sold fewer domains, with just 1,358 names in its zone file today.

Amazon sells three gTLDs to Identity Digital

Amazon appears to have offloaded three of its dormant gTLDs to Identity Digital, judging by ICANN records.

While no formal notices of registry contract reassignment have yet been posted, elsewhere ICANN shows the official registry for .circle, .got, and .jot is now Jolly Host LLC.

Jolly Host is a new Identity Digital affiliate that appeared last year and already took over the .onl gTLD contract from iRegistry a couple months ago.

.circle, .got and .jot are all greenfield namespaces. Unlaunched, they have no registered names beyond the mandatory nic.example domain. They are unencumbered by legacy dot-brand restrictions, which should make for smoother launches.

Amazon appears to have originally intended .circle to play somehow with its Circle brand of home parental control technology, but the 2012 applications for .got and .jot don’t give much of a description of its plans beyond boilerplate text.

The transfers are likely slightly bad news for Nominet, which is Amazon’s primary back-end registry services provider. Identity Digital runs its own back-end (appropriately, on Amazon’s AWS).

.radio’s new owners might have a fight on their hands

Should gTLD registries that avoid costly auctions by promising to serve special limited communities be allowed to later change their business models to improve sales?

That’s the question being asked of .radio, which recently was taken over by a new owner and might be on track to liberalize its registration policies in the near future.

.radio is what is called a “Community” or “Spec 12” gTLD, meaning it has Specification 12 — which imposes eligibility and content rules on registered domains — in its ICANN registry contract.

Four organizations applied for .radio in 2012, but the European Broadcasting Union prevailed, avoiding a potentially expensive auction, by filing a Community application and winning a Community Priority Evaluation.

Afilias, Donuts and BRS Media — all commercial, non-Community applicants — lost out on their chances to run .radio, or make money losing a private auction, because of this successful CPE.

While .radio launched in 2017, it’s never had more than about 3,000 domains under management and earlier this year the EBU sold its contract to Digity, an emerging registry operator with ties to Sav.com.

The suspicion is that Digity is planning to abandon .radio’s community roots and make it more of a mass-market proposition.

That concern was recently expressed by Craig Schwartz, president of fTLD Registry Services, which runs the Spec 12 gTLDs .bank and .insurance, in a letter (pdf) to ICANN’s chair.

Schwartz noted that Digity, unlike the EBU, “appears to have no existing relationship with the originally stated radio community” and said that registries should not be allowed “to game ICANN by preferentially acquiring these assets under one premise and then blindsiding Registrants at a later date.”

ICANN should audit Spec 12 registries for community compliance and open to public comment any attempt to transfer ownership of the contracts, he wrote.

Schwartz reiterated these concerns during a call of the ICANN At-Large community yesterday, adding that ICANN should come up with a way to “wind down” failing Spec 12 gTLDs, rather than transferring them to a liberalizing successor.

He — saying he is supported by other community registries — appears concerned that if ICANN allows registries to play fast and loose with their original commitments, it could not only enable gaming but also tarnish the reputation of other Spec 12s such as .bank.

Consultant Michael Palage, on the same At-Large call, said the the “cheat code” for registries is to get their Spec 12 removed during bilateral negotiations with ICANN Org at the time of contract renewal. He pointed to the liberalization of GoDaddy’s .xxx as an example.

Probably not coincidentally, the current 10-year .radio Registry Agreement is due to expire this July and is currently up for renewal.

ICANN has yet to publicly respond to Schwartz’s letter.

ICANN to throw millions more at cheapo gTLDs

ICANN wants to increase the number of new gTLD applications it will subsidize from its own coffers, as well as the size of the discounts it will provide.

The Applicant Support Program was originally budgeted at $10 million, with half coming from application fees and half coming from the proceeds of auctions from the 2012 application round.

The plan was to offer up to 45 qualifying applicants a 75% discount on their application fees, along with a collection of other perks such as hookups with pro-bono consultants.

But it turns out the ASP was oversubscribed — there are currently 75 organizations vying for the discount, and ICANN seems to suspect most or all will be found eligible for support.

About a month ago, after public comment, the ICANN board of directors requisitioned an extra $4.9 million from the auction proceeds war chest to cover the extra subsidies.

But the Governmental Advisory Committee and At-Large Advisory Committee have both recently recommended that ICANN increases the discount to 85% — about $192,500 of the $227,000 base evaluation fee.

So now the board wants to know if the community is cool with it dipping into the auction proceeds to cover the difference to the tune of an extra $3.2 million.

It’s asking for feedback via correspondence, outside of the usual more formal public comment process, by April 12.

Introducing Stringtel, my new free new gTLD tool

I’ve launched Stringtel, a free, industry-first string discovery and risk mitigation tool for new gTLD applicants.

Stringtel is designed to help applicants reduce the risk of their chosen gTLD strings being banned or incurring extra costs during the application process, as well as helping them discover potentially valuable undelegated strings.

The TL;DR

Stringtel gives you data that will help you pick a good string to apply for, and tells you some of the risks that string might present during the application process.

The goal is to help applicants avoid wasting tens or hundreds of thousands of dollars on crappy applications.

Risk mitigation

Stringtel implements the string-related rules in the latest version of ICANN’s New gTLD Applicant Guidebook, along with other risk factors, leveraging a database of almost a million possibly problematic strings, to offer applicants a quick look into issues that could kill or complicate their applications.

Enter a string and Stringtel will tell you if it would be blocked outright under AGB rules, or could trigger additional analysis, objections, fees, or contention with other applicants.

Stringtel does dozens of risk checks, along with countless associated string similarity checks, to give you a shortlist of the most likely reasons your application might fail.

Opportunity identification

New gTLDs might have a better chance of succeeding when they reflect how domains are already being used.

Stringtel analyzes over 180 million domains across .com, .net and .org, counting how often specific strings appear immediately to the left of the dot.

If a string is already widely used as a domain ending, that’s a signal of existing demand. For example, if tens of thousands of domains already end in “bakery”, that suggests a .bakery gTLD could have a ready-made market.

Essentially, Stringtel shows you where registrants are already behaving as if the dot were somewhere else — and where a new gTLD could turn that behavior into shorter domains.

It also helps filter out strings that look appealing but have little real-world usage, reducing the risk of applying for a gTLD nobody actually wants.

And because everyone keeps asking…

No, Stringtel does not record your searches. The data would be useless. I have no visibility whatsoever into what you’re searching for. Neither does anybody else.

Thanks to the sponsors

Many thanks go to Stringtel’s two launch sponsors: Hello Registry and John Matson Consulting.

Hello Registry, a venture of leading ccTLD registries CIRA (.ca) and SIDN (.nl) hosted a webinar on March 31 explaining how to apply for and operate a new gTLD.

Matson has launched TLD.fit, a financial modelling tool that helps new gTLD applicants build their business cases before they pull the trigger on an application.

.latino gTLD to launch soon

The long-dormant .latino gTLD is set to launch soon, targeting the global Spanish-speaking diaspora.

Registry DISH DBS had originally planned for .latino to be a dot-brand for its Spanish-language satellite TV services, but it’s had a change of heart and now expects it to launch fully open and unrestricted.

General availability has been pencilled in for June 12, according to the registry’s web site and ICANN documents, with sunrise running for the 30 days immediately prior.

It will be the registry’s second launch this year. It went to GA with .mobile last month, so far racking up a modest roughly 4,000 registrations.

.latino will compete against .lat, part of XYZ.com’s stable, which sells for under $2 for a first-year reg and currently has about 125,000 names in its zone.

Amazon readies .pay gTLD

Amazon’s gradual trickle of gTLD releases nlooks set to continue this year, with the company publishing plans for .pay this week.

But it appears that the space will be strictly controlled at first, with general availability not coming until well into 2027.

Amazon’s planning to take .pay to its obligatory 30-day sunrise period, where only registered trademark holders may register names, from April 13, according to ICANN documentation.

From May 13, the company is planning a Limited Registration Period, during which eligibility is restricted to those “that conduct payment transactions online using an approved Payment Service Provider or Third-Party Payment Processor.”

Registrants will have to use their domains “in connection with payment-related services, including but not limited to processing payments, facilitating e-commerce transactions, or providing payment gateway services” or risk suspension.

General availability is not expected until February next year.

ICANN maps out new gTLD timeline

ICANN’s 85th public meeting kicked off in Mumbai at the weekend, the last community face-to-face before the next round of new gTLDs kicks off, and the Org took the time to spell out exactly what is expected to happen and when.

Surprisingly, given ICANN’s track record, it will hit its target of April 2026 to open the doors to applications. Unsurprisingly, given ICANN’s track record, it’s picked April 30 — the last possible day of its promised window — to do so.

The application window will remain open for 104 days. Applicants will have until August 12 to file their paperwork. It doesn’t matter when they hit submit; it’s not first-come, first-served.

Then, the process goes into quiet mode for at least two months while ICANN filters through the applications. If there’s about the same number of applications at the 2012 round — about 2,000 — ICANN reckons Reveal Day could come before ICANN 87, which begins in Muscat October 17.

So far, the timeline closely follows the 2012 round, but this time there’s a new wrinkle — applicants can change their gTLD strings to preselected “replacement strings” if they want to.

From Reveal Day, they’ll have 14 days to swap their strings if, for example, they find themselves in a contention set they don’t like the look of or if they get the vibe that they’re probably face objections.

After those two weeks are up, its String Confirmation day, expected some time in November. From that moment, the applicants are locked into their string of choice.

That’s also the day when the timer starts on the objections period, 104 days in which companies and organizations can object to applications based on criteria such as intellectual property rights, the public interest, and community rights.

Governments can also object on essentially any basis, as long as it’s well-articulated. Unilateral GAC Early Warnings are available, but a full consensus of the Governmental Advisory Committee would be needed to stand a chance at nuking an application outright.

The objection period should end some time next February. While that’s going on, some time in December, ICANN will conduct the Prioritization Draw, a lottery to decide the order in which applications will be processed.

The 2012 draw was important because the gTLDs that were first out of the traps had a measurable first-mover advantage in terms of speculative registrations. With hundreds of gTLDs now on the market, I believe it will be less important this time around.

After the draw, applicants will have to wait half a year before they are finally notified which contention sets, if any, they fit into, after the results of the String Similarity Review have been published.

ICANN has yet to select the panel for this review or create its detailed guidelines, but it’s expect to name it chosen vendor some time in Q2.