“No timeline” to retire Soviet Union from the DNS

There is currently “no timeline” to remove the Soviet Union’s ccTLD from the internet, according to ICANN’s new CEO.

Asked by yours truly during the Public Forum at ICANN 82 whether retirement proceedings had been initiated against .su, Kurt Lindqvist responded, according to the real-time transcript:

ICANN has been in discussions with the managers of .su regarding retirement of the ccTLD for many, many years. There has not been sent a formal notice of removal to the ccTLD manager and no timeline for sending one, discussions will be keep on going and following the ccNSO retirement policy.

The words “formal notice of removal” might be doing a lot of heavy lifting there.

Domain Name Wire scooped earlier this week that on February 8 ICANN had privately told Russian Institute for Development of Public Networks (ROSNIIROS), the .su registry, that it planned to retire the ccTLD by 2030.

DNW noted that a formal notice of removal had been due to be sent and published February 13, but had not.

With Lindqvist today saying that there is “no timeline for sending one”, it seems the matter might have been put to bed for now.

It would have been an incredibly ballsy move to start the process of taking down .su — beloved by Russians and groups in Russian-occupied Ukraine — at this particular point in history.

At the time DNW reported ICANN’s letter to ROSNIIROS was sent, US president Donald Trump had yet to publicly begin peace talks with Russia and Ukraine, but his openly pro-Russian statements on the conflict since his February 12 phone call with Vladimir Putin have alarmed many.

Trump probably isn’t an FSB asset, but he certainly plays one on TV.

Would ICANN want to risk pissing off the unpredictable leader of the country whose jurisdiction it lies within? Or Russia, which might try to make its life difficult in other internet governance fora?

Three years ago, at ICANN 73, ICANN’s then-chair said that the Soviet Union, which disbanded over 30 years ago, is “no longer considered eligible for a ccTLD”.

I first floated the idea of ICANN taking down .su the day after the 2022 Ukraine invasion.

1 Comment Tagged: .su, cctld, ICANN, retirement, ROSNIIROS

ICANN to kill off 60-day domain transfer lock

ICANN is set to kill off its unpopular 60-day transfer lock policy, following a vote at ICANN 82 in Seattle this week.

The GNSO Council yesterday voted to accept the final report of its Transfer Policy working group, a mammoth 163-page document that contains 47 recommendations affecting all areas of domain transfers.

The removal of the transfer lock is perhaps the biggest change to the 20-year-old policy for domain registrants.

Under the current policy, when you buy a domain name from another registrant or change your name, organization or email address, you trigger a lock that prevents you transferring your domain to another registrar for 60 days.

It was designed as an anti-fraud measure, stopping domain thieves bouncing their stolen names to sleazy registrars to avoid them being recovered by their victims.

But is has proved unpopular over the years with registrants that want to consolidate their portfolios under their preferred registrar and the new policy would remove the lock entirely.

It would also remove the requirement for both gaining and losing registrants (ie buyer and seller) to be notified when a change of registrant occurs, on the basis that notifications don’t provide much protection when the losing registrant’s email has already been compromised.

The whole process governing changes to registrant data is going to be spun out into a separate Change of Registrant Data Policy, because maybe it didn’t belong in the Transfer Policy in the first place.

The newly approved changes will also introduce two new locks that registrars currently may, but are not required to, impose — there’s going to be mandatory 720-hour (30-day) locks on domains that have just been created or just transferred in.

Any registrars that currently impose a longer lock will have to reduce it to 720 hours and any registrar that does not have such a lock will be required to implement one.

The GNSO says these month-long locks will help reduce credit card fraud and help comply with trademark complaints such as UDRP.

There are dozens of other changes coming that do not relate to locks.

For example, the list of reasons a registrar may deny a transfer has been updated to include a reference to DNS abuse, as currently defined in the ICANN registry and registrar contracts.

There are numerous changes of terminology, required notifications, and instructions for handling Transfer Authorization Codes, all of which registrars and registrars will have to implement if they want to stay compliant with their ICANN contracts.

There are also changes to bulk portfolio transfers, limiting registries to a charge of $50,000 for portfolios over 50,000 domains.

The changes would also incorporate an updated Bulk Transfer After Partial Portfolio Acquisition (BTAPPA) directly into the Transfer Policy, meaning registries no longer have to request it from ICANN via the Registry Services Evaluation Process.

The recommendations, unanimously approved by the GNSO Council yesterday, will now go to ICANN’s board of directors for final approval. The final updated Transfer Policy will then be written by an ICANN/GNSO team.

Registries and registrars will then presumably be given time to implement the policy before it becomes law and Compliance comes sniffing around for infractions. We’re talking about at least 18 months before the changes go live, I reckon.

If you have a high tolerance for boredom, the full list of recommendations can be read in this PDF.

2 Comments Tagged: gnso, ICANN, icann 82, transfers policy

Lancaster bags up its dot-brand

A French leather goods company is trashing its lightly-used dot-brand gTLD.

Lancaster has told ICANN that it wants to terminate its Registry Agreement for .lancaster.

The company added half a dozen names to the gTLD in 2016 — things like bag.lancaster and fashion.lancaster — but they always just redirected to its primary web site at lancaster.com.

Lancaster used AFNIC as its back-end registry services provider.

The string “Lancaster” has many uses, from other brands to geographic locations, so it’s not impossible .lancaster might return in another guise in a future new gTLD application round.

Comment Tagged: dot-brands, ICANN, lancaster, new gTLDs, termination

Google readying its next batch of gTLD launches?

Three more of Google’s stockpile of long-dormant gTLDs showed signs of activity recently, strongly suggesting the company may be preparing to launch them.

The domains get.eat, get.fly and get.here were all registered February 20, according to zone files and Whois records. While none yet resolve, Google typically uses “get” domains for its customer-facing registry web sites.

Other than nic.[tld] and domaintest.[tld], none of the three had previous registrations apart from .here, which had on.here registered back in 2016. That domain resolves for me, but to an infinitely reloading blank page.

Google is currently fresh from the launch of .channel, which went into general availability February 11 and currently has 1,451 names in its zone file.

Comment Tagged: .eat, .fly, .here, google

NomCom confirms Americans rejected from ICANN board

North American candidates for ICANN’s board of directors are having their applications politely rejected, the Nominating Committee has confirmed.

Speaking to the GNSO Council at ICANN 82 in Seattle yesterday, NomCom chair-elect Tom Barrett said ICANN’s rules forbid the committee from now considering candidates from the region.

“When we opened the application window, January 15, there were no geographic restrictions for these three positions,” he said. “As you know, that has now changed…. We’ll be maxed out terms of the geographic limitation for North America.”

The specific changes of circumstance are the recent elections of Canadian Byron Holland by the ccNSO and American Greg DiBiase by the GNSO.

ICANN’s bylaws state that no more than five voting members of the board, excluding the CEO, may be from the same region. The board already has three other North Americans.

Candidates from North America who had already applied for the three open board seats will be emailed to inform them they are no longer eligible, Barrett said.

Candidates that had identified as North American but have dual citizenship with a country in a different region are eligible to reapply under their other affiliation, he said.

Comment Tagged: ICANN, nomcom

Nova announces $45 million of new gTLD applications

Nova Registry, which runs .link, has announced it plans to apply for 200 new gTLDs when ICANN opens up the next application window about a year from now.

It’s the first time in this round a company has announced plans to build a huge TLD portfolio. It would cost around $45.4 million in application fees alone, if ICANN’s guide price of $227,000 stays true.

It would make Nova the second-largest applicant by gTLD count to date, dwarfed only by the over 300 Donuts applied for in 2012. It would be about twice as large as the 101 Google applied for last time.

In the 2026 round, only Unstoppable Domains has announced a large number of applications — more than 50 — but those are all with partners that would presumably eventually become the contracted registry.

It’s not entirely clear from today’s announcement whether Nova is financing this project, which it calls SuperNova200, alone, or whether it’s looking for business partners.

“We will apply for 200 new Generic Top-Level Domains (gTLDs),” the registry says. “A new breed of gTLDs to drive innovation, competition, and consumer choice while enhancing the utility of the DNS.”

Nova entered the market in 2022 when it acquired .link from UNR. It appears to be ultimately owned by domainer Yonatan Belousov and is managed by ICM Registry alum Vaughn Liley.

Comment Tagged: ICANN, new gTLDs, next round, nova

Registry makes .ai an option for Koreans

South Korea’s ccTLD registry is seeking to borrow from the success of repurposed ccTLDs, including .ai, with the release of four new third-level namespaces under .kr.

This week local registry KISA started selling names in .ai.kr, .it.kr, .me.kr, and .io.kr, following the growth of the ccTLDs .ai, .it, .me and .io, which have all seen sales because they mean other stuff in English as well as being geographic identifiers.

The company acknowledged its inspiration for the new products in a recent press release:

Recently, as overseas country domains such as ‘.ai (Anguilla)’, ‘.io (British Indian Ocean Territory)’, ‘.it (Italy)’, and ‘.me (Montenegro)’ have been actively used among the AI ​​field, startups, IT companies, and bloggers, a policy was developed to allow our citizens to use the domains they want by creating a new 3-level country domain that reflects the latest trends.

The domains are only available to registrants with a presence in Korea.

KISA said the new namespaces are priced more competitively than the two-level equivalents, with .ai.kr selling for the KRW equivalent of $14 a year, compared to .ai’s $70.

Comment Tagged: .ai.kr, .io.kr, .it.kr, .kr, .me.kr, kisa

it.com now bigger than Guatemala

There are now more than 25,000 registered it.com domain names, according to it.com Domains.

The company said earlier this week that it recently crossed that milestone, about two years after it went to general availability.

it.com sells third-level names under the .it.com domain, much like XYZ.com sells .uk.com domains, representing information technology, Italy, or just the pronoun “it”.

The 25,000-name milestone means .it.com now has comparable domains under management to cTLDs such as Guatemala’s .gt, as well as 20-year-old .travel and new gTLD first-mover .ninja.

It would be ranked around 230th by size if it was included on the list of TLDs that DI tracks.

Comment Tagged: it.com

ICANN turns to AI and crowdsourcing for new gTLD program

ICANN says it will use a combination of AI and crowdsourcing to translate new gTLD program materials on the cheap.

Org said in a blog post that when a community member trying to drum up interest in new gTLDs in their local community needs some official ICANN documents in an unsupported language, ICANN will prepare a translation on demand.

The first run will be done with AI machine translation, and the draft will be posted on a community wiki for review by volunteers who can read the relevant language before ICANN finalizes and publishes a final PDF.

ICANN seems ready to post drafts of documents such as FAQs and info sheets in languages such as Hindi, Italian and Portuguese after next week’s ICANN 82 public meeting.

Program documents are usually only available in the six official UN languages — Arabic, Chinese, English, French, Spanish, and Russian — so this project should bring the new gTLD program to a much wider audience.

Using AI and volunteers should mean it costs almost nothing beyond the work hours ICANN staff put in to administer it.

ChatGPT tells me that there are 195 to 200 official national languages in the world and 3,500 to 4,000 written languages altogether, but I didn’t check whether those numbers are correct.

If the AI is wrong, let me know in the comments.

3 Comments Tagged: ICANN, new gTLDs

Amazon lawyer DiBiase elected to ICANN board

Greg DiBiase, senior corporate counsel at Amazon, has been elected to serve on ICANN’s board of directors, representing registries and registrars.

He beat Reg Levy, associate general counsel at Tucows, in the two-horse second round of voting, and five other candidates overall, to become the Contracted Parties House selection for Seat 13 on the board.

He will replace Becky Burr, an ICANN community lifer formerly with Neustar, who is term-limited and will leave the board after nine years at the Org’s Annual General Meeting in Muscat, Oman, this October.

DiBiase is currently chair of the GNSO Council and identifies as a registrar rather than a registry (Amazon is both).

He said in his candidate statement (pdf) late last year that ICANN today is too “risk-averse”, focussing too much on its fear of lawsuits, and that it should be more accountable when responding to community complaints.

DiBiase told DI:

I look forward to serving the Contracted Parties in this role and am honored by their trust in me. During the course of the election, my fellow candidates articulated a wealth of ideas on how to improve ICANN and multi-stakeholder model. These perspectives will guide me as a member of the ICANN Board.

The election result needs to be given the nod by the GNSO Council and the ICANN Empowered Community, both of which are usually pretty much formalities, before he can formally take on his board role.

1 Comment Tagged: board, elections, gnso, ICANN