Fifth-largest gTLD not dead after all

ICANN has assured users of its zone file distribution service that the .top gTLD is not dead, after an unspecified snafu earlier this week suggested it was.

On Wednesday, users of the Centralized Zone Data Service received an automated email stating: “Your zone data access for .top has been revoked… Reason: Request revoked as TLD has been made inactive.”

That would be a pretty big deal, as .top is the fifth-largest gTLD by volume and the second-largest new gTLD after .xyz, with something like 5.7 million names in its zone.

It might also carry a ring of truth for CZDS users who don’t track ICANN activities very closely, as .TOP Registry has recently been on the Compliance naughty step over DNS abuse allegations.

But affected users were assured yesterday that .top is not inactive and that an “issue” was to blame.

An email read: “an issue that temporarily marked the .TOP generic top-level domain (gTLD) as inactive… As a result, your previously approved CZDS access request for the .TOP zone file was revoked.”

The email goes on to say that users can wait for their access to be restored “in the next few days” or manually initiate a new CZDS request for the .top zone, which requires approval from the registry.

Half of registrar’s domains are abusive, ICANN says

A fast-growing registrar seems to be experiencing its growth spurt due to extremely high levels of DNS abuse, including phishing, according to the latest public breach notice from ICANN Compliance.

More than half of Bulgarian registrar MainReg’s domains under management are abusive, judging by the notice, which alleges MainReg’s unwillingness to investigate abuse reports in violation of its accreditation contract.

The notice is the first I can recall seeing that cites data from Domain Metrica, an ICANN service that aggregates abuse data from third-party block-lists. An unspecified third-party reporter (hands up in the comments if it was you!) is also cited.

“ICANN Domain Metrica data indicates that in November 2025 approximately 48% of MainReg’s DUMs were reported for phishing, with the figure at 45% as of 5 January 2026,” the notice says.

“The complaining party stated that its own independent analysis identified an even higher proportion of the Registrar’s DUMs engaged in scam‑related activity,” it adds.

MainReg isn’t a huge registrar, but transaction reports show that its DUM tripled between September 2024 and September 2025, from about 10,000 names to about 30,000. The company registered its first name in 2015. Almost all of its names are in .com, .net and .org.

The notice alleges other breaches, such as failing to migrate from Whois to RDAP, and gives MainReg until January 28 to come in compliance or risk termination.

Refunds galore as gTLD losers finally bow out

There’s been a wave of withdrawals of new gTLD applications over the last couple of months after ICANN gave 15 companies their final notice that it was time to ask for a refund or lose their money forever.

But so far just seven unsuccessful applications from the 2012 round have been withdrawn, from the 19 that were eligible, according to my records.

Notably, all of the remaining applications for .mail, .corp and .home, strings that were banned on account of name collision risks, have been pulled. Google, Amazon and GMO Registry will all get partial refunds of their application fees.

Two applications for the fiercely contested .hotel have also been yanked, with Identity Digital and Radix getting their refunds. GRS Domains, Despegar and Fegistry still have not withdrawn, according to ICANN records.

ICANN had classed .hotel as a “already been delegated to other applicant” gTLD, which isn’t completely accurate. The gTLD is currently in pre-delegation testing, however.

There are plenty of other applications from 2012 that have not been withdrawn, despite the fact that the gTLD in question is already live and freely available for registration.

L’Oreal, for example, is still clinging on to its bid for .salon, despite the fact that Identity Digital has been running it for years and has about 4,000 names in its zone.

Similarly, Planet Dot Eco, DotConnectAfrica and Commercial Connect do not appear to has asked for refunds for their respective bids for .eco, .africa and .shop, despite all three being live and run by successful rival applicants for years.

Asia Green IT System has not withdrawn its bids for .islam, .halal, and .persiangulf, which were banned following government objections. AGIT was essentially kicked out of the industry when its business with five other Middle-East themed gTLDs comprehensively failed.

The 2012 round’s most-stubborn applicant, Nameshop, still has a live bid for .idn. Indian conglomerate Tata has also not pulled its bid for .tata, which failed on geographic similarity grounds.

In a resolution passed last September, ICANN’s board decided to give all of its remaining 2012-round applicants 90 days notice that they could withdraw or lose their money. It’s not clear when that 90-day period began.

.goo terminated as search engine closes down

The .goo gTLD is among a pair of dot-brand gTLDs to recently self-terminate.

goo was a 1990s-style search portal focused on the Japanese market and owned by local incumbent telco NTT. It eventually lost relevance and finally closed down for good at short notice last November.

Despite the similar branding, goo was unrelated to Google and in fact predated Google’s foundation by about a year, according to some accounts. It eventually turned to Google to power its search functionality.

NTT has asked ICANN to terminate its .goo registry contract and ICANN has given it the nod.

There was one active .goo domain, www.goo, which redirected to goo.ne.jp, its primary domain.

Joining .goo in self-termination is .wolterskluwer, one of those gTLDs that really makes me scratch my head for having never noticed its existence despite my daily exposure to vast amounts of gTLD data.

It’s owned by Wolters Kluwer, a large Dutch company that provides software for professionals such as doctors and lawyers. Unlike goo, the company appears to be in robust health but it never used its gTLD.

GoDaddy to offer domain blocking to people who don’t have trademarks

GoDaddy’s registry arm wants to offer registrants the ability to block others from registering their brands in other TLDs, even if they don’t own a registered trademark.

In what could be a game-changer for the industry, the company has proposed a service called Domain Options, which could allow registrants to eventually claim rights to their domain across dozens or hundreds of gTLDs.

“The service will allow registered name holders to prevent registration of certain labels,” GoDaddy explained in a Registry Services Evaluation Process request filed with ICANN just before Christmas.

“Labels will be an exact match of the registered name holder’s second-level domain name label,” the RSEP says. “The number of labels a registrant can protect under Domain Options is limited to the following: only exact match labels, and only for registered domain names held by the registrant.”

Simply put, if you have registered example.beer, you would be able to pay a fee to prevent other people from registering domains such as example.biz, example.cooking and example.photo.

The latest RSEP covers 34 GoDaddy-run gTLDs: .abogado, .beer, .biz, .blackfriday, .boston, .casa, .club, .compare, .cooking, .courses, .dds, .design, .fashion, .fishing, .fit, .garden, .gay, .health, .ink, .law, .luxe, .miami, .photo, .rodeo, .select, .study, .surf, .tattoo, .vip, .vodka, .wedding, .wiki, .work, and .yoga.

But ICANN has already approved the Domain Options service for use in GoDaddy’s .horse gTLD, which was floated (presumably humorously) as a trial balloon earlier in December. The .horse contract has already been amended to include the service.

Registrants would be able to convert the blocked domains into actual registrations at a later date, or cancel the service altogether.

Third parties would also be able to request blocked domains to be unblocked through worryingly unspecified means.

Domain Options appears to be essentially a simplified clone of two-year-old GoDaddy-led service GlobalBlock, known in ICANN contractual parlance as the Label Blocking Service.

GlobalBlock enables trademark owners to pay substantial fees — from $6,499 a year at 101domain, for example — to block their marks across 710 extensions as a cheaper alternative to buying 710 defensive registrations at full price.

Registry pricing for Domain Options is not revealed in the RSEP, but it’s hard to imagine it enormously undercutting and therefore cannibalzing GlobalBlock.

Now that ICANN has given GoDaddy the nod for .horse, it seems inevitable that the other 34 gTLDs will also be approved, and I’d be very surprised if we don’t see a wave of similar RSEPs from other registries over the coming months.

Happy new year expected for domain industry, says ICANN

ICANN’s revenue for 2026 is expected to be significantly above its earlier predictions, and it isn’t just because the Org cranked up its registry and registrar fees last year.

The budget for fiscal 2027, published shortly before Christmas, paints a picture of a much healthier domain industry than earlier thought.

The budget revises expectations for the Org’s current fiscal 2026 upwards in terms of transactions (meaning registrations, renewals and transfers) for gTLDs both new and old.

ICANN now expects legacy gTLD transactions for FY26, which ends June 30, to come in 7.7 million or 4.3% ahead of the predictions contained in the budget for the period its board approved last May.

Transactions are now expected to be 187.5 million versus the earlier estimate of 179.8 million.

It’s a similar story in new gTLDs, where transactions are now predicted at 43.1 million versus 33.1 million, a 10 million or 30.2% difference in estimates December versus May.

ICANN says in its draft FY27 budget (pdf) that the uptick became apparent about a year ago:

Beginning in the second half of FY25 [about a year ago], domain name transaction volumes began to increase, which was unexpected at the time of budgeting for FY25. Continued transaction volume growth and upward guidance from the industry resulted in an increased funding forecast for FY26, a trend that is expected to continue in FY27.

Due to this bullishness, the Org has no plans to raise its fees in FY27.

The growth spurt means that ICANN now thinks FY26 funding for operations will come in $11.6 million ahead of budget — $161.4 million compared to the $149.8 million it budgeted for six months ago.

The Org also expects to end its FY26 with about 400 more accredited registrars and about 20 more contracted registries than it thought. Likely due to drop-catcher registrars and dot-brand registries.

None of these figures include the upcoming new gTLD application round, which will not create any new fee-paying registries for some time.

For FY27, which begins July 1, ICANN is expecting transactions to hit 191.9 million and 44.4 million, growth of 2% and 3%, for legacy and new gTLDs respectively. That’s compared to the newly updated FY26 guidance.

ICANN is budgeting for $161.1 million in operations funding for FY27, down a bit on the $161.4 million it’s now predicting for FY26, due to lower application fees from new registrars seeking accreditation.

The draft budget is open for public comment until February 12.

Salesforce to apply for a dot-brand

Salesforce has become the most significant company to date to announce it plans to apply to ICANN for a new gTLD.

Specifically, the company plans to apply for a dot-brand, according to a disclosure made by David Lawrence, software engineering architect at Salesforce and IETF liaison on ICANN’s board of directors.

The disclosure came when the board approved the new gTLD program’s latest Applicant Guidebook at the conclusion of the ICANN 84 public meeting in Dublin last month.

While the IETF liaison is a non-voting role, he nevertheless recused himself from the AGB discussion, saying: “I work for an employer to apply for a brand TLD.”

While there are dozens of companies and organizations with public plans for new gTLDs, most of them are little-known brands associated with the blockchain space.

By contrast, Salesforce is, according to Wikipedia, the 61st-largest company in the world, with a market cap of $238 billion.

Rubens Kühl has died

Rubens Kühl, a mainstay of the ICANN community and prolific commentator on the domain name industry, has died tragically young.

According to Brazilian ccTLD registry NIC.br, Rubens died November 3 at the age of 55, survived by his wife and two children.

Rubens was at NIC.br for 16 years, mostly at the registrar arm Registro.br, where he was product marketing manager.

He was a regular presence at ICANN meetings and served on the GNSO Council for a term from 2016.

“Rubens was a kind person, a brilliant technical guy, always open to sharing his extensive knowledge with anyone,” one Brazilian friend wrote on social media. “He will be missed not only here but by the whole Internet community around the world.”

“We will remember Rubens as an exceptional professional and a generous colleague who greatly contributed to our community,” said LACTLD, the regional ccTLD registry association.

ICANNWiki notes that he was known by some as “Mestre dos Magos” or “Dungeon Master”, due to his “vast knowledge, sharpness, and dry humor.”

I really liked Rubens. We only met in person a handful of times but he was by far the most prolific commenter on this blog and I always enjoyed reading what he had to say, even when we disagreed. This is the first time I’ve had to write an obituary with tears in my eyes.

Sinha angry with Chapman’s firing as ICANN vice chair

ICANN chair Tripti Sinha appears to be a little pissed off that one of her fellow directors was essentially fired by the Nominating Committee, sparking a public confrontation with NomCom’s current chair.

Chris Chapman was replaced by the independent NomCom at the conclusion of his first three-year term earlier this year, which seems have prompted Sinha to voice her frustration.

Over the course of the week at ICANN 84 in Dublin, Sinha and Chapman himself have made a number of disparaging remarks about NomCom’s work, referring to it variously as “not impressive”, “disruptive” and “unpleasant”.

It has also transpired that Sinha and Chapman both abstained in protest at the October 14 board resolution that confirmed NomCom’s leadership for the 2026 round of selections.

Sinha made her first terse remark about Chapman’s departure on the stage at the welcoming ceremony at on Monday, calling it “premature”, but expanded on her comments during a meeting with the ccNSO on Tuesday and today’s open-mic public forum.

Saying she was reading out her abstention statement — censored so far by ICANN from its web site — she told the ccNSO that she was “disappointed” that the NomCom had not returned her vice chair for the second year in a row.

She said NomCom should put “board leadership experience, longevity, and continuity” as strong enough criteria when weighing its director options. She accused NomCom of “disregarding” the board’s guidance in this regard.

She alluded to her last vice chair Danko Jevtović, who was replaced in 2024 by that year’s iteration of NomCom after six years on the board.

“I abstain in protest to these decisions in back-to-back years, and implore that the NomCom re-evaluate its criteria for returning seasoned board leaders,” she concluded.

She repeated some of her comments at today’s public forum session, and backed up by former director Edmon Chung, who lost his seat after three years in 2024 due to NomCom’s selections.

But they were challenged by Tom Barrett, who was chair-elect of NomCom when Chapman was fired and was named chair earlier this month and who pointed out that the committee is independent and suggested ICANN should keep its nose out.

“I’m not going to discuss how the 2025 NomCom made its decisions, but without knowing why and how I think it is inappropriate for any board member, especially the chair, to question its due diligence or the fact that they have chosen incorrectly,” he said.

NomCom gives the board’s guidance an “enormous amount of weight”, he said, “but it is not exclusive.”

“No one that applies to the NomCom gets a golden ticket,” he said. “Reapplying candidates do not get a golden ticket, even if they have been appointed by two previous NomComs. Board leadership does not get a golden ticket even if they have been chair or vice chair.”

As for Chapman, he gave a bitter but detail-light recounting of his NomCom experience at a session with Asia-Pacific community members on Tuesday, bemoaning the fact that he wasn’t even picked for the back-up list.

“I think there is something fundamentally wrong with the accountability for NomCom,” he said, describing the circumstances surrounding his non-selection this year as “very odd” and that his interaction with NomCom “wasn’t pleasant”.

Glitch redux: ICANN screws up new gTLD security again

No lessons learned from 2012? ICANN admitted this morning that a glitch in its Registry Service Provider Evaluation Program exposed the identities of more than a dozen companies to their rivals.

The Org fessed up that some companies looking to get pre-approved as RSPs were able to see “identifiable organizational information” belonging to another user when using ICANN’s technical testing system.

“A total of 14 of 26 organizations using RST OT&E were affected. All affected organizations have been notified,” ICANN said. “No personal data was exposed, with the exception of a single minor and limited instance.”

It doesn’t sound like any gTLD application intentions were revealed — that part of the program doesn’t open until next year.

There were probably not too many surprises among the leaks. The landscape of the RSP market is well understood.

The only exceptions that spring to mind would be ccTLD registries that have not yet revealed their plans for the gTLD space, and completely new market entrants that have not yet tipped their hand.

The glitch sounds remarkably familiar for ICANN watchers with long memories. A bug discovered in 2015 exposed much more data, and about applicants themselves, but it was only exploited by one person on a handful of occasions.

That “glitch” led to allegations of hacking and trade secret theft and a long-running Independent Review Process case that wasn’t resolved until October 2023.

ICANN said it has taken down its testing environment to fix the bug and has hired an outside consultant to kick the tires.

This delay means testing will be offline for around two weeks, coming back November 12 at the earliest, and the reveal date for the list of participating RSPs has been pushed back from December 9 to an unspecified future date we realistically have to assume will be in the new year.

It’s not expected to delay the April 2026 opening of the next application round.