Latest news of the domain name industry

Recent Posts

.music gets its first live web site

Kevin Murphy, December 20, 2022, Domain Registries

The .music gTLD may be still officially unlaunched, but it got its first live anchor tenant this week after the DotMusic registry joined a partnership aimed at making translated lyrics more accessible.

DotMusic said it has become part of an initiative called BELEM, for “Boosting European Lyrics and their Entrepreneurial Monetisation”. Given that the entire namespace of .music is currently available, one wonders why such a contrived acronym was chosen.

The project, which is funded with €2 million of European Union money, has a live web site managed by DotMusic at belem.music. It’s the first .music site to go live other than the mandatory nic.music registry hub.

BELEM is out to get lyrics in various European languages translated by humans and the translations licensed to streaming services.

It has 14 other partners, including Canadian lyrics licensing company LyricFind and French streaming service Deezer, which plans to roll out one-click translations based on the new service.

The aim, the group says, is to “break down cultural barriers and further support artists’ monetisation of their works”.

For DotMusic, it’s an anchor tenant perhaps more noticeable to the music industry than to the public at large.

The .music gTLD has been live in the root for over two years now, and there’s still no published launch plan.

Content police? ICANN mulls bylaws change

Kevin Murphy, December 14, 2022, Domain Policy

ICANN could change its bylaws to allow it to police internet content to an extent, it emerged this week with the publication of the Operational Design Assessment for the next stage of the new gTLD program.

Currently, ICANN’s bylaws state that the Org may not “regulate (i.e., impose rules and restrictions on) services that use the Internet’s unique identifiers or the content that such services carry or provide”, and it’s been adamant that it is not the “content police”.

But the community has recommended that future new gTLD applicants should be able to agree to so-called Registry Voluntary Commitments, statements of registry policy that ICANN would be able to enforce via contract.

RVCs would be much like the Public Interest Commitments many registries agree to in the 2012 application round, implemented before ICANN’s current bylaws were in effect.

As an example I’ve used before, Vox Populi Registry has PICs that ban cyberbullying and porn in its .sucks gTLD, and in theory could lose its contract if it breaks that rule by allowing .sucks sites to host porn (like this NSFW one, for example).

ICANN’s board of directors expressed concern two years ago that its bylaws may prevent it from approving the RVC recommendation.

But Org staff have now raised, in writing and on a webinar today, the prospect that the board could change the bylaws to permit RVCs to go ahead. The ODA published on Monday states:

The Board may wish to consider how and whether it can accept the recommendations related to PICs and RVCs. One option may be to amend the Bylaws with a narrowly tailored amendment to ensure that there are no ambiguities around ICANN’s ability to agree to and enforce PICs and RVCs as envisioned

How worrying this could be would depend on the wording, of course, but even the chance of ICANN meddling in content is usually enough to raise eyebrows at the likes of the Electronic Frontier Foundation, not to mention supporters of blockchain alt-roots, many of whom seem to think ICANN is already censoring the internet.

It’s not clear whether the change is something the board is actively considering, or just an idea being floated by staff.

ICANN bloat to continue as new gTLD program begins

Kevin Murphy, December 13, 2022, Domain Policy

ICANN expects to hire so many new staffers over the next few years that it’ll need to rent a second office in Los Angeles to store them all in, according to a newly published new gTLD program planning document.

We’re looking at about 100 more people on the payroll, about 25% above the current level, judging by ICANN figures.

The Org said in the Operational Design Assessment published last night that the next new gTLD round will need it to hire another 25 to 30 dedicated staff during implementation of the program, along with 10 to 15 contractors, and then an additional 50 to 60 permanent staff to help manage the program going forward.

The number could be even higher if the board of directors and community encourage ICANN to speed up the roll-out of the round by reducing automation and relying more on the manual processing of applications.

The ODA says that ICANN has already identified an option to lease more office space close to its LA headquarters, to house the newcomers.

The budget for ICANN’s current fiscal year expects the Org to average 423 operational staff and another 25 employees dedicated to the new gTLD program.

ICANN reckons that the next round will require 125 full-time equivalents (FTE) during the implementation phase, reduced to 114 after the application phase kicks off.

For comparison, in May 2012, shortly after ICANN closed the application window for the last round, the whole organization comprised just 143 people. A year later, it had grown to 239.

The ODA does not break down how many additional staffers it will need to hire if the community plumps for the low-automation “Option 2”.

ICANN spunks a year, $9 million, on new gTLD plans destined for trashcan

Kevin Murphy, December 13, 2022, Domain Policy

ICANN has published the Operational Design Assessment for the next round of the new gTLD program, a weighty tome of 400 pages, most of which are likely destined to be torn up, burned, or used as toilet paper.

The ODA is the document, prepared by staff for board consideration, that lays out how the Org could implement the community’s policy recommendations for the next application round, how much it would cost, and how long it would take.

As I wrote last week, the paper outlines two options, the more expensive of which would take five years and cost $125 million before a single application fee is collected.

This option “reflects the goal of delivering on all outputs of the SubPro Final Report [the community’s 300-odd policy recommendations] to the maximum extent possible”.

This would see the clock ticking the moment ICANN gets the board’s nod and begins the implementation work — best case scenario, probably the first half of next year — and the first applications accepted at least five years later.

So, no new gTLD applications would be received until the first half of 2028 at the earliest. The first registry go-live would not happen until the 2030s, three decades after the first application window closed.

The second option, which was discussed on a webinar last week, would take about 18 months to roll out and cost half as much in up-front costs, but would not necessarily give the community every last thing it has asked for.

In this scenario, the next application window could open as early as 2025, followed by windows in 2026, 2027 and 2028. There’d be no per-window limit on applications, but ICANN would only start to process 450 each year, with the lucky applications selected by lottery.

What’s surprising about the ODA is how little airtime is given to the second option — known as the “cyclical” or “batching” option — which doesn’t really get a serious look-in until page 354.

The large majority of the document is devoted to the single-round, long-runway, more-expensive option, which Org surely knows will prove repellent to most community members and would, if approved, surely confirm that ICANN is mortally unfit for purpose.

Yet ICANN has nevertheless spunked over a year and $9 million of domain buyers’ money assessing an operational design it surely knows has no chance of ever going operational. It’s pure, maddening, bureaucratic wheel-spinning.

ICANN will hold two webinars tomorrow to discuss the document, so if you’re interested in the debate, best settle in for a night of tedious and rather frustrating reading.

The ODA itself is here (pdf).

New gTLD applications to cost about $250,000

Kevin Murphy, December 8, 2022, Domain Policy

Getting hold of a new gTLD could cost applicants well north of a quarter million dollars in base application fees alone in the next round, according to ICANN.

Presenting the results of its year-long Operational Design Phase to the GNSO Council via Zoom last night, staffers said application fees are likely to be either around $240,600 or $270,000 next time, higher than the $185,000 it charged in 2012.

Those would be the base fees, not including any additional evaluations or contention-related fees.

The Org next week is set to present its board and the community with a stark choice — one big expensive round along the lines of 2012, with a potential five-year wait for the next application window to open, or a cheaper, staggered four-stage round with maybe only 18 months of development time.

The Operational Design Assessment — a 400-page tome the Org has spent the last 14 months developing — is set to be published early next week, outlining two options for how ICANN should proceed on the next round.

One option is to build a highly automated system that fully implements all of the GNSO’s policy recommendations but costs up to $125 million up-front to build and roll out over five years. Application fees would be about $270,000.

The other would cut some bells and whistles and require more human intervention, but would be cheaper at up to $67 million up-front and could be rolled out within 18 months. Application fees would be about $240,600.

ICANN CFO Xavier Calvez, responding to exclamations of surprise via Zoom chat, said that a decade of inflation alone would lead to a 28% price increase to $237,000 if the next round were opened today, but in two or three years the price could be even higher if current economic trends continue.

While many expected the fact that technical evaluations will be conducted on a registry service provider basis rather than a per-application basis would wipe tens of thousands from the application fee, ICANN pointed out that building and executing this RSP pre-evaluation process will also cost it money.

ICANN wants to operate the program on a “cost-recovery basis”, so it neither makes a profit nor has to dig into its operational budget. It expects “more than three dozen vendors will be required” to help run the round.

It seems that the portion of the fee set aside to deal with “risks” — basically, anticipated litigation — is expected to be around a fifth of the total, compared to about a third in the 2012 round.

ICANN is asking its board and the community to decide between what it calls “Option 1 — One Big Round” and “Option 2 — Four Annual Cycles”.

Option 1 would essentially be a replay of 2012, where there’s a single unlimited application window, maybe a couple thousand applications, and then ICANN processes them all in a highly automated fashion using custom-built software.

Option 2 would allow unlimited applications once a year for four years, but it would cap the number processed per year at 450 and there’d be a greater degree of manual processing, which ICANN, apparently unfamiliar with its own history of software development, thinks poses additional risk.

My hot take is that the Org is presenting a false choice here, much like it did in January with its ODA on Whois reform, where one option was so unpalatably time-consuming and expensive that it had most of the community retching into their soy-based lattes.

There’s also an implicit criticism in both ODAs that the community-driven policy-making process has a tendency to make big asks without adequately considering the resources required to actually get them done.

I might be wrong, but I can’t at this early stage see much support emerging for the “One Big Round” option, except perhaps from the most ardent opponents of the new gTLD program.

ICANN expects to deliver the ODA — 100 pages with 300 pages of appendices — to its board on Monday, with wider publication not long after that. It will hold two webinars for the community to discuss the document on Wednesday.

Macy’s scraps .macys gTLD

Kevin Murphy, December 7, 2022, Domain Registries

US retailer Macy’s has dumped its dot-brand gTLD .macys.

The company told ICANN recently that it no longer wishes to hold a registry contract, noting that it never used the gTLD.

ICANN last week agreed that as a dot-brand with no third-party users, the domain will not be redelegated to another registry.

It’s the seventh gTLD to scrap its contract this year, lower than ICANN’s budget estimates.

Elon Musk chaos credited with surge in .social regs

Kevin Murphy, December 7, 2022, Domain Registries

Elon Musk’s chaotic takeover of Twitter has been credited with leading to a surge in .social domain registrations last month, according to registry Identity Digital.

.social leaped into the top 10 of the company’s most-registered TLDs at number five internationally and number two in North America, second only to legacy .info, the company reported this week.

ID said that month-over-month .social regs increased 435% in the first two weeks of November.

It’s a pretty small TLD, so the boost only equated to an increase of about 5,000 domains in November, according to zone files, which put the current count at about 35,000.

Musk closed his acquisition in late October, and he started Trussing it into the ground the following week, laying off thousands of employees and cack-handedly attempting to monetize the “blue check mark”.

ID reckons this is behind the increase in .social sales, with CEO Akram Atallah saying in a press release: “Volatility in social platforms that people rely on leads users to take action to own their digital identity and content, which often starts with finding a domain name.”

He pointed to Twitter alternative Mastadon, which is a decentralized, open-source platform and uses a .social domain, as a driver for the growth. Some of the new .social regs point to Mastadon installs, ID said.

ID also sold premium names arts.social, lol.social and justice.social during the month, but no .social domains appear on its top 20 sales in its most-recent monthly report.

New new gTLD registry in town as Rostam buys UNR

Kevin Murphy, December 1, 2022, Domain Registries

UNR, the former Uniregistry, has emerged under new ownership, new leadership, and with another new name, apparently finalizing Frank Schilling’s piecemeal exit from the domain name industry.

The nine gTLD contracts remaining with UNR following its fire-sale auction 18 months ago are now owned by Internet Naming Company, which like UNR is based in Grand Cayman.

The new company, which appears to be a continuation of UNR yet promising a “clean slate”, is owned and run by Shayan Rostam, who was UNR’s chief growth officer and previously worked for XYZ.com and Intercap.

INC’s portfolio comprises .click, .country, .help, .forum, .hiv, .love, .property, .sexy, and the unlaunched .trust, which together have over 350,000 registered domains.

Registry-recommended retail pricing varies wildly between TLDs, from the .com-competitive, such as .click at $9.99, to the wallet-busting, such as .sexy at $2,999 and .forum at $1,199.

INC is also offering consulting, auction and management services for other TLDs, including dot-brands.

The emergence of INC means we now know where all 23 of the gTLDs UNR auctioned off last year ended up. XYZ.com wound up with 10, with GoDaddy, Top Level Design, Nova Registry and Dot Hip Hop all grabbing one or two each.

UNR sold its registrar business to GoDaddy and its registry back-end business to Tucows (which is supporting INC’s portfolio) last year, giving INC the ability to talk about going “back to basics”, unencumbered by any conflicts of interest.

The new company is using inaming.co for its web site. The individual TLDs’ sites still use UNR landing pages.

Unstoppable Domains stops over 116,000 domains as alt-root TLD goes dark

Kevin Murphy, October 20, 2022, Domain Registries

Blockchain alt-root provider Unstoppable Domains has taken a huge credibility hit with its decision to essentially turn off one of its TLDs, rendering over 116,000 domains pretty much useless.

Unstoppable said Tuesday that it has stopped selling .coin domains and would immediately stop supporting their resolution. The names would no longer work with the over 500 cryptocurrency wallets, apps and services that integrate with Unstoppable, the company said.

“As of today, we’ve disabled .coin resolution in our libraries and services. Unstoppable domains are self-custodied NFTs, so you still own your .coin domain, but it won’t work with our resolution services or integrations,” Unstoppable said in a blog post.

According to AltRoots.com, there were almost 117,000 .coin domains at the time they were turned off.

That’s about the same size as Identity Digital’s .email gTLD, and the shutdown is the equivalent of ID telling its registrants that they can keep their domains, but it’s deleting the .email zone file.

The decision drew immediate critical reaction on social media, with many users pointing out that the Unstoppable system doesn’t sound particularly “decentralized” or censorship-resistant any more.

“Doesn’t sound too decentralized or empowering. Hopefully this will wake people up,” one Twitter user wrote.

“So many people literally just had to change their identity due to incompetency. Basically like visa saying you can keep the card but it wont work anywhere anymore,” wrote another.

Users also criticized the company’s decision to offer compensation in the form of store credit — three times what they paid for the domains they return — instead of a cash refund.

Unstoppable said the decision was made after it discovered another blockchain project, Emercoin, has been selling .coin domains since 2014, whereas its own .coin was launched in 2021.

“We’re committed to protecting our customers from the risk of functional collision,” Unstoppable said. “The Emercoin team are pioneers in our industry and we regret that we weren’t aware of this naming collision earlier.”

Name collisions are of course a big deal in the regular DNS, but cohesion around a single consensus root allows risk to be managed and mitigated, as we saw in ICANN’s 2012 new gTLD roll-out.

And in the ICANN system, a TLD would not simply be shut off overnight. Rather, it would transition to an emergency back-end operator for three years until it is either taken over by another permanent registry or wound down in an orderly fashion.

As Domain Name Wire notes, Unstoppable is currently trying to get the operator of a competing .wallet blockchain alt-root TLD shut down in court on the basis of the name collision, and it would have been hypocritical to continue offering its own colliding TLD.

Identity Digital publishes treasure trove of abuse data

Kevin Murphy, October 3, 2022, Domain Registries

Identity Digital, the old Donuts, has started publishing quarterly reports containing a wealth of data on reported abuse and the actions it takes in response.

The data for the second quarter, released (pdf) at the weekend, shows that the registry receives thousands of reports and suspends hundreds of domains for DNS abuse, but the number of domains it takes down for copyright infringement is quite small.

ID said that it received 3,007 reports covering 3,816 unique domains in the quarter, almost 93% of which related to phishing. The company said the complaints amounted to 0.024% of its total registered domains.

Most cases were resolved by third parties such as the registrar, hosting provider, or registrant, but ID said it suspended (put on “protective hold”) 746 domains during the period. In only 11% of cases was no action taken.

The company’s hitherto opaque “Trusted Notifier” program, which allows the Motion Picture Association and Recording Industry Association of America to request takedowns of prolific piracy sites resulted in six domain suspensions, all as a result of MPA requests.

The Internet Watch Foundation, which has similar privileges, resulted in 26 domains being reported for child sexual abuse material. Three of these were suspended, and the remainder were “remediated” by the associated registrar, according to ID.

The report also breaks down how many requests for private Whois data the company received, and how it processed them. Again, the numbers are quite low. Of requests for data on 44 domains, 18 were tossed for incompleteness, 23 were refused, and only three resulted in data being handed over.

Perhaps surprisingly, only two of the requests related to intellectual property. The biggest category was people trying to buy the domain in question.

This is a pretty cool level of transparency from ID and it’ll be interesting to see if its rivals follow suit.