.music has competition as .mu repositions

Identity Digital and it.com Domains are to market the Mauritius ccTLD, .mu, as an open alternative to the .music gTLD.

According to it.com, the ccTLD will be marketed internationally as “Everyone’s Music Domain”, starting with outreach at the trademark-focused INTA Annual Meeting in London this week.

It’s a non-sunrise sunrise period, being called the Trademark Priority Period, though this seems to be a case of branding rather than the imposition of any strict rules — .mu has been around for decades and domains there are already available to buy.

It’s rather a headsup period, it seems, with trademark owners being marketed to before the general public. This period will run from May 15 to June 28, it.com said.

Policies and launch details are expected to be announced soon.

There is already a domain for music, of course — .music. It’s a latecomer from the 2012 application round. It launched in late 2024 and had fewer than 30,000 domains under management at the end of 2025, and fewer than 7,500 names in its zone file today.

The issue with .music is that it’s a “community” gTLD, conceived at a time when concerns about music piracy online were a lot more acute than they are today, and it has registrant eligibility restrictions.

While .music domains have standard shopping cart friction and can begin resolving immediately, registrants are asked to complete a post-reg identity verification process that looks like a bit of a faff. Presumably, .mu domains will be less restrictive.

Pricing for the repurposed .mu has yet to be announced, but it’s on sale today with retail renewal pricing appearing to start at about $75 a year. That’s in the same ball-park as .music.

While rebadging .mu as a domain for music may initially hit like another case of a ccTLD trying to shoehorn itself into a meaning it was not intended to have, the use case is not without precedent. The rock band Muse has long used muse.mu for its web site, for example.

The rebranding of .mu comes about a year after Identity Digital took over the back-end registry services for the ccTLD in partnership with the Government of Mauritius.

.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.

Is .io safe now? Identity Digital now running Mauritian ccTLD

Identity Digital appears to have taken over the back-end registry for Mauritian ccTLD .mu, potentially improving the company’s chances of future-proofing at-risk .io.

IANA records show that .mu has started using Identity Digital’s nameservers and Whois service. Registrars say the migration to ID’s EPP system happened last week.

Mauritius is poised to be given sovereignty of the Chagos archipelago, formally known as the British Indian Ocean Territory, from the UK, assuming the still-unpublished treaty is approved by both governments.

BIOT is assigned the popular .io ccTLD which may have more than a million registrations and makes Identity Digital, which acquired the UK-based registry operator a few years ago, about $40 million a year.

The change of control of Chagos, which would certainly come with a name change for the territory, puts the future of .io at risk, as I have been reporting for the last several months.

But with Identity Digital now in bed with the .mu ccTLD manager — a private company named Internet Direct that also goes by MU-NIC — it has a foot in the door for improving relations with the country, should .io come under threat in future.

I believe MU-NIC was previously using CoCCA’s software to manage .mu.

(Hat tip: DI reader “Tom”)