.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 cleaning house, cans four more registrars

ICANN has withdrawn the accreditations of four more long-defunct registrars, bringing this month’s terminations so far to 11.

They’re all Chinese, though they do not appear to be under common ownership. They are: Qinghai Yunnet Electronics Technology Co, Shandong Huaimi Network Technology Co, Xiamen Booksir Qiyoutong Technology Co and Xiamen Yuwang Technology Co․

What’s notable is how long it’s taken for ICANN to yank their accreditations. It’s been three or four years since Compliance opened tickets on each of them for non-payment of fees.

None of the four have any gTLD domains under management, and some don’t even seem to own their own original domains any more. One had its former web site turned into a blog in 2022. Another has its domain parked and listed for sale.

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.

Seven registrars get terminated

ICANN has terminated the accreditations of seven registrars for not paying their fees.

Haveaname, InstantNames, MisterNIC, NetEstate, Neudomain, OpenName, and TopSystem — all under common ownership in the US — have all been given their marching orders, effective April 17.

While Compliance said it will transfer the registrars’ domains to another registrar, in practice it seems that none of them actually have any remaining domains under management.

As I previously blogged, the seven all appear to have sacrificed their DUM when they lost their .com accreditations in late 2024. That’s about the same time as ICANN stopped receiving its fees.

ICANN hit with tinfoil-hat lawsuit

ICANN has been sued by a Louisiana woman who thinks the Org is surveilling her.

Wendy Renee’ Carlton (sic) filed a bizarre lawsuit last month claiming she “has experienced persistent and patterned interference affecting her cognitive processes, bodily integrity, and personal autonomy”.

Google, Microsoft, Wal-Mart and some John Does are also listed as defendants.

It’s difficult to describe the complaint (pdf), but here’s a chunk of it for flavor:

Plaintiff alleges that she has experienced persistent and patterned interference affecting her cognitive processes, bodily integrity, and personal autonomy, and that such interference is systemic in nature.

Plaintiff alleges that Defendants’ conduct resulted in the exploitation or misuse of her personal data and behavioral patterns, restricting her liberty interests and decision-making autonomy without notice, consent, or lawful authorization.

Plaintiff further alleges that Defendants collected, processed, analyzed, and/or derived her biometric, anatomical, and/or cognitive data through technological, commercial, and/or institutional frameworks without informed consent or procedural safeguards.

Plaintiff alleges that she experienced persistent surveillance, monitoring, and identity interference resulting in observable physical, cognitive, and biometric effects, including involuntary physiological responses and interference with normal bodily functions, consistent with assessment- or monitoring-based activity.

Carlton’s probably not far off — Google’s whole empire is based on mass surveillance after all — but it’s difficult to see what roles ICANN or Wal-Mart have in that enterprise.

The complaint doesn’t get into any factual specifics of what ICANN or any other defendant is supposed to have done, or what the effects on the complainant were.

ICANN has filed a motion to dismiss, claiming lack of jurisdiction and failure to state a claim.

ICANN boss: no plans to scrap Oman meeting

ICANN currently has no plans to cancel its 2026 Annual General Meeting, which is due to take place in Muscat, Oman, later this year, according to CEO Kurt Lindqvist.

Speaking at the public forum at ICANN 85 in Mumbai today, Lindqvist responded to a speaker who expressed concerns about the ongoing US-Israel war against Iran, which has seen Iran retaliate against neighbors including Oman.

“We’re obviously aware of the situation, and we’re monitoring it. The Oman meeting is 7 months out, so it’s still quite a long time to go, and a lot of things can change. So, at the moment, we are planning for this to go ahead,” he said.

The Muscat meeting was originally planned for October last year, but was called off due to Israel’s attacks on Iran in June, which affected flight corridors in the region.

Lindqvist added that ICANN always has contingency plans in case a venue becomes inappropriate. Last year, the Muscat meeting was rescheduled to Dublin, Ireland.

It seems likely that if the hostilities in the Middle East have not calmed down by June, ICANN could well pull the plug on Muscat for a second year, giving meeting participants about four months to plan their travel.

Previously, ICANN has relocated meetings due to be held in Puerto Rico and Panama due to hurricane damage and the Zika virus, and several were held entirely online during the Covid-19 pandemic.

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.

War disrupts ICANN 85

It seems a bit tasteless to whine about disrupted flights when the Middle-East is erupting into war; nevertheless, that’s the immediate issue facing would-be attendees at this week’s public ICANN meeting.

ICANN 85 is taking place at the Jio World Convention Centre in Mumbai, India from this coming weekend.

While Mumbai is over 2,000km from Tehran, Iran has been attacking many neighbouring nations in retaliation for the ongoing US-Israeli bombardment, which has resulted in the closure of several airports as missiles, drones and fighter planes invade their airspace.

Some ICANN travellers, mainly those traveling west-to-east, will find that hub airports in Dubai or Bahrain are in their connections itinerary. Those flying Emirates will be particularly affected.

ICANN said in a statement at the weekend that 85 “will proceed as planned” and that would-be attendees feeling uncomfortable traveling can take advantage of online participation if they prefer.

The Org and its travel agent are together responsible for funding and arranging the travel of hundreds of participants, and ICANN said they were working to route travellers around the affected airspace.

Namecheap abandons fight for .org price caps

Namecheap seems to have thrown in the towel in its long-running fight to get ICANN to cap the prices of .org and .info domain names.

The registrar terminated its Independent Review Process complaint against ICANN back in November, with the IRP panel formally closing the case December 16, according to documents ICANN published last week.

Namecheap said it “has decided to terminate these proceedings without prejudice”, meaning it would be free to re-file the IRP at a later date. The company and ICANN have agreed to pay their own costs.

It was the second Namecheap IRP related to ICANN’s decision to remove price caps from the .org and .info registry contracts when it renewed them in 2019, bringing the two gTLDs into line with almost all other registries.

Namecheap filed its first IRP in February 2020, and scored a stonking win in 2023, with the panel ruling that ICANN had breached its bylaws and behaved in an overly secretive manner when it approved the contract renewals.

But the panel offered up remedies that gave ICANN a lot of interpretative leeway and important did not mandate the reintroduction of price caps. The second, now-defunct IRP saw Namecheap trying to force ICANN to undo its price caps decision.

It also sued ICANN in Los Angeles two years ago for essentially the same purpose, but it lost the case last July.

Since the price caps were lifted, non-profit Public Interest Registry has not raised .org prices, while for-profit Identity Digital has raised .info prices from $10.84 in 2019 to $19 today.