.io questions in sharp focus as UK signs Chagos treaty

The UK government has signed a treaty handing over sovereignty of the Chagos archipelago to Mauritius, which could eventually turn out to be bad news for .io domain name owners.

Currently known as the British Indian Ocean Territory, Chagos was seized in the 1960s and 1970s, its citizens deported, and is home to a strategically important UK-US military base.

The new treaty (pdf) is not of course interested in issues as small-beer as ownership of ccTLDs — it’s much more concerned with the control of spectrum critical to running the base — but there are some elements of the text that may be cause for concern.

• A name change now seems inevitable. With Mauritius now assuming full sovereignty of the whole archipelago, the name BIOT seems destined for the trash heap of history. The treaty does not refer to BIOT once.
• The treaty does explicitly grant Mauritius control over “regulation of commercial activities, including the provision of electronic communications services, unrelated to the operation of the Base”.
• The UK is to inform the United Nations that it no longer exercises sovereignty over Chagos and Mauritius will also gain full representation for Chagos at the International Telecommunications Union.

Who gets to talk to the UN on behalf of the islands is important because of how country names and the codes used for ccTLDs are assigned.

The Statistics Division of the United Nations Secretariat publishes a standard known as M49, “Standard Country or Area Codes for Statistical Use”. That’s where ccTLD codes first appear.

That list is used by the International Organization for Standardization when it builds its ISO 3166-1 alpha-2 list, which is in turn used by ICANN/IANA to decide which territories qualify for a ccTLD and what the ccTLD is.

If Chagos is no longer recognised by the UN as a separate territory for statistical purposes, that would set a chain of events in motion that would see .io removed from the DNS root in five to 10 years.

If Chagos retains its place on the various lists, and Mauritius changes not only the name but the two-letter code, that would see .io retired and replaced with the ccTLD matching the new code, again in five to 10 years.

Or Mauritius could change the name, but not the code, meaning .io registrants would be safe. The ccTLD is believed to have over a million registrations and is popular with tech companies as a domain hack for I/O or input/output.

Identity Digital runs .io via a UK-based shell company it acquired several years ago. Perhaps sensing which way the wind was blowing, the company recently made a deal to become the back-end registry operator for .mu, the Mauritian ccTLD, so it has a foot in the door in the country.

1 Comment Tagged: .io. icann, .mu, chagos, identity digital

Big .gdn registrar at risk

A registrar that exclusively sells .gdn domain names seems to have gone AWOL, and ICANN Compliance is on its case.

Dubai-based Intracom Middle East has been slapped with a breach notice alleging failures to operate a compliant RDAP server, publish the names of its officers, pay its ICANN fees, and escrow its registrant data.

Some of these breaches seem to be due to the fact that the company’s web site is missing in action, today returning NXDOMAIN errors, and has quite possibly been repeatedly hacked.

Archived versions of its site from last year show it was at various times a Polish risotto recipes splog, an Indian burger joint, and a manga cosplay porn site.

It’s Intracom’s second brush with Compliance. Three years ago the case was escalated to a three-month accreditation suspension for pretty much the same infractions.

Unlike most recent Compliance actions, which have been against registrars with essentially no domains under management, this times some domains are actually at risk — over 10,000 of them in fact.

Intracom specializes/d in selling .gdn domains for under a buck apiece. Apart from a few dozen registrations in a few other gTLDs, all of its 10,000 domains were in .gdn. It was once .gdn’s biggest registrar, though that’s no longer the case.

The company has been given to the end of the month to comply or risk termination.

Comment Tagged: breach, compliance, ICANN, intracom

ICANN “reaffirms its commitment to diversity and inclusion”

It’s not exactly a U-turn, but ICANN has issued a statement clarifying that it’s still committed to the values of “diversity and inclusion”, if perhaps not the words themselves.

CEO Kurt Lindqvist posted on the ICANN blog last night:

While some terminology may have changed, the values that guide our work have not. Our actions and commitments remain the same. We have not stepped back from, retreated from, or abandoned ICANN’s core values, or an environment where all voices are welcomed, respected, and valued.

The metadata summary of the post, which shows up in RSS feeds and such if not the visible components of the web page itself, reads: “ICANN reaffirms its commitment to diversity and inclusion amid recent updates to webpage language.”

There have been no changes to policy or ICANN programs like the Fellowship or NextGen, he wrote.

The post follows the revelation last Thursday that ICANN had expunged almost all references to “diversity” and “inclusion” from a page formerly called “Diversity at ICANN” and now called “Representation at ICANN”.

What Lindqvist’s clarification does not clarify, or even address, are the reasons why ICANN felt the need to suddenly and sharply distance itself from language it has been enthusiastically promoting for over a year.

But perhaps no explanation is necessary. Anyone paying a modicum of attention to US politics this year can’t have failed to notice that the abbreviation “DEI” — diversity, equity, inclusion — has become politically toxic and the target of attacks from the Trump administration and its loyal MAGA followers.

What we seem to be looking at here is the ICANN equivalent of the Department of Defense panickedly erasing the Enola Gay from its web site.

While ICANN’s structural ties to the US government have been pretty loose and minimal since the IANA transition in 2016, it really doesn’t need to find itself fighting off a Trump attempt to renationalize the root.

Comment Tagged: dei, ICANN

ICANN kills off diversity and inclusion

ICANN seems to have become the latest American organization to back away from commitments to “diversity” and “inclusion” in the wake of a universe now controlled by the whims of Donald Trump.

The Org has recently started removing references to the D-word from its web site, sloppily editing its diversity-related web pages, replacing it with the less politically loaded term “representation”.

The “Diversity at ICANN” page is now called the “Representation at ICANN” page, and ICANN’s stated commitments have been changed from:

ICANN is entrusted with ensuring the stability, resiliency, and interoperability of the Internet’s unique identifier systems in an open Internet, and was founded on the belief that it should reflect the diversity of the Internet community.

to:

ICANN is entrusted with ensuring the stability, resiliency, and interoperability of the Internet’s unique identifier systems Internet and was founded on the belief that it should represent the broad Internet community.

The words “inclusive” and “inclusion”, also from the now apparently toxic “DEI” abbreviation, also seem to be deemed inappropriate. ICANN has changed its web site language from:

To live up to this responsibility, ICANN is committed to promoting greater diversity and supporting broad, inclusive participation in its processes.

to the apparently hastily edited (random comma in original):

To live up to this responsibility, ICANN is committed to supporting broad, participation in its processes.

The page no longer contains links to ICANN’s Diversity & Inclusion Toolkit, a set of educational materials designed to tell people that asking other community members where they come from means they’re a racist.

Also gone is the link to an ICANN Learn course on “Unconscious Bias”, which teaches you that not all nurses are female and not all CEOs are white men and apparently ICANN has money to burn.

While ICANN previously said it offers its staff “Diversity & Inclusion Training”, it now says it offers “Culture Training”.

All six references to “inclusion” present in the November 2024 archived page have been removed from today’s live page. All five uses of the word “inclusive” have also been deleted.

The November archive uses the word “diversity” 32 times and “diverse” twice. On the live page, those counts are down to two (where the word was used to refer to a named group or report), and none, respectively.

The link to “Diversity at ICANN” in the web site’s site-wide footer has also been removed.

Some of the edits are incredibly sloppy. The old page had a bullet point that read:

Community-wide surveys on Age Diversity and Participation and Gender Diversity and Participation

The findings offer insights into perceptions of gender and age diversity in the community, potential and perceived barriers to participation, and the community’s support for initiatives to enhance age and gender diversity.

But that now reads:

Community-wide surveys and

The findings offer insights into perceptions of gender and age in the community, potential and perceived barriers to participation, and the community’s support for initiatives to enhance understanding.

ICANN’s backtracking from earlier virtue signalling comes at a point in history when corporate America is steering away from DEI initiatives lest they incur the wrath of US President Donald Trump.

The question is: is this all just cosmetic, or will it affect ICANN policy?

The Org is currently considering changes to its Community Anti-Harassment Policy that would change the boundaries of what is considered acceptable behavior at ICANN meetings.

The proposed changes would either, depending on your point of view, a) make life more comfortable for people with protected characteristics, or b) make it easier to get cancelled for a cultural faux pas.

It’s been a few months since the public comments closed on the policy changes, so ICANN board action shouldn’t be far off. Will the Org’s retreat from DEI have an impact on its decision?

8 Comments Tagged: dei, harassment, ICANN

Kaufmann picked for ICANN board

Christian Kaufmann from Akamai has been reselected to represent the Address Supporting Organization on ICANN’s board of directors.

He’s the incumbent in Seat 10, having first been picked by the ASO in 2022, but he faced competition this time from Australian Karl Kloppenborg of Reset Data.

Kaufmann’s current term ends at ICANN 84 in October, but will be immediately extended for another three years.

Comment Tagged: aso, board, ICANN

Conflicted? STFU under new ICANN rules

ICANN community members who refuse to disclose their conflicts of interest should keep their mouths shut during public meetings, according to a proposed new code of conduct now open for comment.

An updated Community Participant Code of Conduct Concerning SOIs was published this week, following an initial public comment period late last year, which saw some community members ask for more clarity on what the rules mean in practice.

A key change states that people who won’t disclose their potential conflicts shouldn’t even get up to the mic to express an opinion in public, even when they’re not directly participating in policy-making.

“When disclosure cannot be made, the participant must not participate in ICANN processes or make interventions at ICANN sessions on that issue,” the new draft states (changes in bold).

The change might lead to some community members staying in their seats or keeping their microphones muted during discussions at public ICANN meetings.

The policy is intended to improve the perceived legitimacy of ICANN’s processes and policies by forcing community volunteers to publish a statement of interest (SOI) naming who’s paying their wages.

The proposal has largely been championed by registries, registrars and governments, and opposed by lawyers in private practice, some of whom think they shouldn’t, or ethically can’t, name their clients.

The argument goes that if somebody is being paid by a company that wants to torpedo or delay the new gTLD program, or is working on a patent covering RDAP, you’d want to know if they were working on policies covering new gTLDs or RDAP.

The counter-argument goes that if an attorney is working on new gTLD policy on behalf of Coca-Cola, putting that information in an SOI would tip off Pepsi that a .coke gTLD application is in the works.

The updated policy draft clarifies what SOIs must disclose — it doesn’t just cover employers or clients — and provides lengthy guidance on specific scenarios where disclosures must be made.

The types of interests that should be disclosed are broad, and cover a variety of influences and relationships, both monetary and nonmonetary. These could include: familial relationships; employment relationships; agreements to represent a specific person, entity or group of entities; vendor or contracting relationships; stock/equity ownership (other than de minimis ownership); and all similar types of influences and relationships that impact the discloser’s participation within ICANN. Interests can be general or they can be issue-specific.

Working group chairs would get the right (though not, it seems, the obligation) to temporarily kick anyone found to be in violation of the rules. Complaints could also be escalated to the Ombuds, but she’s not getting any extra enforcement powers.

Lawyers have had their objections to the policy roundly rejected. The guidelines now state:

When an attorney is engaged to participate in ICANN on behalf of a client, while that attorney holds specific duties to their client, those duties do not override the need for others participating within ICANN to understand what other interests are advocating and participating within ICANN processes… when that attorney starts participating within processes, such as participating in mailing lists, making public comments, joining working groups, etc., on behalf of that client, the client’s and attorney’s obligations to the broader ICANN community emerge

The updated policy clarifies that governments enjoy some immunity — they don’t have to disclose who lobbied them on a particular issue they’re engaged with — with ICANN assuming their nations’ own transparency laws will cover that type of thing.

For the domain industry, volunteers will have to disclose all the roles their employer has. Nominet, for example, would have to disclose that it’s a ccTLD registry, a contracted gTLD registry, and a back-end registry services provider.

The policy now also provides guidance for trade groups, academics and IP owners.

The draft is now open for public comment until June 30. It’s possibly the last chance you’ll get to file a comment without disclosing your interests.

Comment Tagged: ICANN, sois, transparency

.hot is for hookers? Amazon’s first premium regs revealed

Amazon Registry made three new gTLDs available to non-trademark-holders on Monday, and so far a handful registrants have taken up the offer of premium Early Access Period pricing.

The five-day EAPs for .free, .hot and .spot see prices start high and decrease each day until May 17, when they’ll settle at standard general availability pricing.

While the wholesale prices have not been published by Amazon, the registrar 101domain was retailing them for $6,299 on day one, $3,299 on day two, $1,399 on day three, $799 on day four, and $199 on day five.

GA pricing for .hot at 101domain will be $59.99, while .free will be $44.99 and .spot will be $29.99.

The early adopter(s) in .hot seem to be viewing it as a sex-related TLD along the lines of .xxx, .sex or .sexy. All the day-one registrations (in multiple languages) look set to be used for escort services.

The domains that popped up for the first time in the May 13 zone files were:

be.free
bible.free
sql.free

acompanhantes.hot
escort.hot
escorts.hot
incontri.hot
prepagos.hot
trans.hot

high.spot
hub.spot

The only new domain in the May 14 zones appears to be live.free. They’re not exactly flying off the shelves so far.

Because the zone files are generated at midnight UTC and Amazon’s EAP daily price-increase cut-off is 1259 UTC, it’s not possible to say for sure how much each registrant paid for their domain names.

Comment Tagged: .free, .hot, .spot, amazon, eap

Gname adds another 200 registrars

Singaporean drop-catching registrar Gname has added another 200 shell registrars to its collection, bringing its total to over 500.

The 200 companies are named Gname 301 Inc through Gname 500 Inc. More accreditations means more connections to gTLD registries and a better chance to catch expired domains when they are deleted.

Gname last boosted its portfolio of shells in December 2023, when it doubled its number from 150 to 300.

The latest accreditations will have cost $700,000 in up-front application fees and will add an extra $800,000 to Gname’s costs due to ICANN’s $4,000 flat annual accreditation fee.

This of course has a positive effect on ICANN’s finances. Its fiscal 2025 budget predicted 40 new registrars, and even its high estimate was only for an increase of 57.

It had only accredited 24 new registrars in this fiscal year before Gname’s move.

An extra $1.2 million it wasn’t expecting is almost enough to cover its community volunteers’ hotels bill for a whole year.

Gname’s main accreditation had almost five million domains under management, making it the ninth-largest accreditation of the now over 3,000 on ICANN’s books.

Comment Tagged: accreditation, drop catching, gname, ICANN

New Pope’s .com domain was registered the day Francis died

A domainer snapped up the .com matching the new Pope’s name on the day the last Pope died.

Cardinal Robert Prevost was elected this evening and took the name Pope Leo XIV.

PopeLeoXIV.com was registered on the afternoon of April 21, a few hours after the news of Pope Francis’ death was announced and after I tweeted on Twitter:

Pope's dead. Let the domain speculation begin.

— Kevin Murphy (@DomainIncite) April 21, 2025

The name was highlighted by DomainGang the following day as a likely candidate for the next Pope’s name. But by then of course the domain had already been registered.

It’s currently parked, with no BIN price listed.

PopeLeo.com has been registered since 2002. LeoXIV.com was registered in 2005, on the day Pope John Paul II died.

Comment Tagged: pope

Two deadbeat registrars get their ICANN marching orders

ICANN has terminated the registrar accreditation agreements of two Chinese companies, which appear to be under common ownership, because they didn’t pay their bills.

EJEE Group Beijing and VIP Internet Industry are both losing their contracts, effective later this month. Both have common contact details, apparently run by the same person who had another registrar terminated in 2017.

EJEE does its business at category-killer domain domain.cn, though the registration storefront appears to be broken. VIP Internet’s web site appears to be down entirely.

While both companies have sold thousands of domains in their time, both have had just one or two gTLD domains under management for the last 12 months, according to my records. No registrants will be affected, in other words.

ICANN seems to have been chasing the registrars for their overdue fees since March 2023, over two years ago, according to the termination notices.

Comment Tagged: compliance, ejee, ICANN, termination, vip internet