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

DotMusic has sold a lot of names, but not many are turned on

DotMusic, the company that started selling .music domains seven months ago, has had a relatively successful launch, but one in four domains sold have not yet gone live.

The latest registry transaction reports show that there were just over 30,000 registered .music domains at the end of January. Registry CEO Constantine Roussos tells us it’s over 31,000 today.

“We have more registrations than any community TLD and it is not even close,” Roussos said.

It’s certainly true that .music is already the largest generic-term Spec 12 Community gTLD from the 2012 application round.

But while 31,000 in six months is a good start for a 2012-round gTLD, there are currently only about 7,500 domains in the .music zone file, showing that about three quarters of names have not been activated.

It’s not the lowest unactivated domains rate in gTLDs — only about 15% of .xxx’s registered names are in its zone file, for example — but it’s pretty low. The similarly-sized .baby has about 84% utilization.

A low utilization rate usually means a high proportion of defensive registrations — registrants have no intention of ever using their domains but want to keep them out of the hands of others — but something different might be going on here.

As a Community gTLD, .music has extra hoops to jump through before registrants can activate their domains.

They have to have their identity and nexus to the music industry verified and obtain a special code called a Music ID from the registry, which can also be used for future registrations.

Roussos said that “the majority of the registrants have never owned a domain name before, which is great news for us”. He added: “My other guess is that most just wait until they are ready to use the domain to get verified”.

He said that many registrants are choosing to take advantage of a feature called SmartPage, which gives bands a template-driven profile page containing basic information and links to their socials and such.

1 Comment Tagged: .music, dotmusic, smartpage

.med is a deeply weird gTLD, but it wants to be more normal

Medistry, the .med registry with a really strange business model, is looking to normalize its practices and start competing with the cluster of healthcare-related gTLDs already on the market.

The gTLD launched in 2016 and had almost 42,000 domains under management at the last count, which may sound like a pretty decent showing for a 2012-round niche registry (comparable to the likes of .beauty and .chat).

But there are a few caveats. For starters, only one non-registry .med domain has been indexed by Google, and it redirects to a .com web site.

Delve into the .med zone file, and you’ll discover that almost all of those 42,000 domains are 12 characters long and each comprises entirely numbers and hyphens. Doesn’t sound very sexy, does it?

Furthermore, delve into the Whois, and you’ll discover that all of those domains are registered via the registry’s in-house registrar, Name Share, to an entity affiliated with the registry itself.

A couple of years ago, having not sold more than a handful of .med domain names (I’ll get to the reasons for that in a moment), Medistry seems to have decided to reinvent .med as a directory for medicines.

In the US, all human medicines approved by the Food and Drug Administration are given a National Drug Code, a 10-digit unique identifier that the manufacturers are required to print on the packaging.

So, the domain name 55150-250-50.med refers to a bupivacaine hydrochloride injection, a surgical anaesthetic made by Eugia US LLC. Almost all .med domains follow this three-part NDC structure.

The domains seem to have been registered in service of Trust.med, another entity affiliated with the registry, which says it offers supply chain management services to the US healthcare industry.

Why the DNS is the best place to store this NDC information isn’t clear to me. All the .med names I checked came back NXDOMAIN and were marked as pendingDelete in the Whois despite being months away from expiration.

So… Plan C? Sell .med domains to any Tom, Dick or Harry who wants one, on a first-come, first-served basis.

Medistry says that, as of now:

A registrant of a .med domain name can be an individual or organization. All available domain names in .med are approved for registration on a first come, first serve basis through .med accredited registrars. .med domain names can also be purchased in the domain name aftermarket.

That’s hell and gone from the mission outlined in Medistry’s 2012 new gTLD application and its current Registry Agreement with ICANN, both of which outline some of the harshest registration restrictions of any TLD.

Its current ICANN contract states, in the Public Interest Commitments:

The lone method of domain name allocation in the TLD will be by Request for Proposal (RFP) under guidelines, rules and criteria as set forth by the Advisory Board in its sole discretion.

RFP for domain name registration in the TLD will be reviewed for approval by the Advisory Board, in its sole discretion, independent of Registry Operator.

PICs are enforceable by ICANN Compliance under the rarely used PIC Dispute Resolution Process, should there be a view that a registry is violating the contract.

Could Medistry be heading into stormy waters with Compliance? The company does have form in that regard — it’s owned by the same people who run .jobs registry Employ Media.

Employ Media got into a protracted fight with ICANN in 2012 over a service called Universe.jobs, which saw it register 40,000 generic .jobs domains to a close partner in order to turn the gTLD into a structured taxonomical jobs board.

ICANN thought the service was a breach of the .jobs RA and the two parties ended up in arbitration. ICANN eventually let Universe.jobs go ahead but it fizzled out a few years later when Employ Media came to blows with its partner.

Is history repeating itself with .med’s sudden change of business model?

Medistry says that full general availability for .med names will begin on September 2, but it’s telling registrars (pdf) they can “Pre-Register any domain to guarantee registration beginning on September 2” by emailing them a list of names.

It’s also looking to on-board more registrars. As of the end of January, the only registrars to ever sell a .med domain were owned by the registry. It uses Nominet as its back-end.

.med would compete against the likes of .doctor, .surgery, .health and .clinic.

3 Comments Tagged: .jobs, .med, compliance, employ media, medistry, new gTLDs

ICANN cuts off money to UASG

ICANN is the stop funding and supporting the Universal Acceptance Working Group, an independent outside group tasked with making sure domain names work everywhere on the internet regardless of TLD or language.

With no money or staff support, Org has likely signed the death warrant for the UASG, but ICANN insists it’s not turning its back on UA as a general principle.

“With the focus changing to implementation work, ICANN will no longer provide funding or staff support to the UASG after June 2025,” ICANN CEO Kurt Lindqvist wrote in a blog post today.

I don’t believe ICANN has ever revealed publicly how much money it was giving the group, but it was clearly significant enough to warrant review at a time when ICANN is tightening its belt in the face of budget pressures.

Budgets published in previous years have put UASG’s spending at anywhere from $500,000 to $1.4 million a year.

The move probably shouldn’t come as a huge surprise. A close reading of a board resolution from ICANN 82 in March strongly suggests ICANN was gently breaking the news that it planned to wind down the group.

Lindqvist’s post and the resolution both point out that UASG’s founding charter, written in 2015, called for it to be a 10-year awareness-raising project, and that 10 years is now up.

Lindqvist said ICANN will create a UA Expert Working Group of “invited members and nominated representatives” from across the community to “provide guidance for ICANN’s work on UA adoption”.

While the UASG has been mainly focused on internationalized domain names and awareness-raising in parts of the world that might not track ICANN very closely, much of the hands-on work has been done by ICANN itself.

Last year, Twitter and Meta-owned platforms like Whatsapp updated their linkification code base to more effectively support UA, but that seems to have happened largely due to ICANN engineers battering on their doors.

ICANN has also taken to directly engaging with smaller open source projects, many of which develop libraries used in much larger platforms, to make sure they support the freshest TLDs, regardless of script.

Lindqvist said ICANN will to continue to support UA Day, a series of educational gatherings held around the world each year.

Comment Tagged: ICANN, uasg, universal acceptance

Web.com getting dumped

Registrar group Newfold Digital is killing off the Web.com brand after 18 years as part of its strategy to consolidate its diverse array of brands.

Customers will soon by migrated to the larger and older Network Solutions registrar, but the company said that they should not notice much difference.

“We’re committed to making the transition to Network Solutions seamless and convenient. That means no downtime or interruptions to your existing services. Simply put, you won’t have to do anything,” Web.com said.

Pricing, features, and user credentials will not change, it said.

Web.com had about 818,000 gTLD domains under management at the end of 2024, down from its peak of over 2 million during the early days of the Covid-19 pandemic, but was growing every month last year.

Network Solutions, which was the gTLD monopoly registrar until ICANN came along to introduce competition a quarter century ago, had gTLD DUM of over 5 million at the last count.

Web.com was actually the acquiring party in the original merger, paying over $561 million in cash and stock for NetSol back in 2011.

There’s no word on when or if other ancient Nefold brands, such as Register.com, will be similarly retired.

The retirement raises the intriguing possibility of the web.com domain hitting the market at some point in the (far) future.

Comment Tagged: network solutions, newfold, web.com

.es and .pt riding out massive power outage

A lesson in the importance of redundancy in your DNS architecture?

The ccTLDs for Spain and Portugal seem to be largely unaffected by an ongoing power cut that has seen both countries go into blackout (metaphorically) for the last several hours.

At time of writing, no explanation for the outage, which has also affected parts of France, has been given by authorities. Traffic lights, public transport, airports, radio stations and telecommunications networks have all reportedly been affected.

But .es and .pt domains appear to be resolving just fine, at least from where I’m sitting.

Both registries — DNS.pt and Red.es — have DNS resolution services distributed across multiple nameservers managed by multiple providers in multiple global locations.

As well as at home in Lisbon, .pt’s nameservers can be found as far afield as California and Brazil through partners Packet Clearing House and Nic.br. Red.es also uses PCH in California, though its remaining nodes are in Madrid.

Any data center worth a damn has an uninterruptable power supply and backup generators, so one assumes the local DNS nodes are up and running too.

DNS.pt has posted a notice on its web site saying that customer services are currently unavailable due to “circumstances beyond our control”.

It’s not clear if other registry systems have been affected by the outage, but presumably with a total lack of electricity registrants have more pressing things to worry about, like how to get home from work and whether the food in their freezers will be edible when they get there.

Comment Tagged: .es, .pt, dns, dns.pt, outage, red.es