A dot-brand that was actually used is shutting down

It’s been a slow year for self-terminating dot-brand gTLDs, but today we’ve seen our third.

Lipsy, a UK-based women’s fashion retail brand owned by Next, has told ICANN it wants to end its Registry Agreement for .lipsy, which it has operated since 2016.

What’s unusual about this termination is that Lipsy actually had quite a lot of registered domains — at least 133 over the years, of which 132 were still active a month ago.

My records show that all of its domains apart from the registry home page were deleted October 22, the day before the company sent its termination notice to ICANN.

The domains were generally product keywords which pretty much all redirected to next.co.uk or nextdirect.com; Lipsy’s own web site had also redirected to Next’s since 2018.

Almost all of its domains were registered between December 2020 and July 2022. It hasn’t registered any since.

.lipsy was on Verisign’s back-end until May 2023, when it switched to Identity Digital.

GoDaddy’s .xxx contract renewed

GoDaddy’s .xxx gTLD will no longer be “sponsored”, following a vote of ICANN’s board of directors last week.

At its ICANN 81 AGM in Istanbul, the board approved the renewal of GoDaddy subsidiary ICM Registry’s Registry Agreement.

The new deal closely follows the text of the standard RA most other gTLDs use, scrapping restrictions that GoDaddy found onerous but which were vital in getting the deal approved in the first place back in 2011.

It means the end of IFFOR, the International Foundation For Online Responsibility, the largely toothless oversight body that had been tasked with creating policies and issuing grants to worth causes but arguably did neither.

It also means less friction for the .xxx registration process, as registrants will no longer have to affirm they are members of the “sponsored community”, which never existed in any real sense anyway.

Some elements of the original sponsorship agreement, such as strict prohibitions on child sexual abuse material and the suggestion thereof, have been moved to Public Interest Commitments that ICANN could in theory enforce.

In its resolution text, ICANN noted that the Governmental Advisory Committee, which almost got .xxx killed off a couple decades ago, had not felt strongly enough about the new deal to publicly comment on it one way or the other.

.xxx makes most of its money from defensive registrations. It had almost 45,000 domains under management at the end of June, but barely 7,000 of those appeared in its zone file of the same date. That does not included domains blocked via the AdultBlock and GlobalBlock services, which are not counted in any public document but which I estimate are measured in five figures.

ICANN confirms two bans on new gTLD gaming

ICANN’s board of directors has just voted to approve two bans on practices in the new gTLD program that could be considered “gaming”.

It’s banned applicants for the same string from privately paying each other to drop out of contention, such as via private auctions, and has banned singular and plural versions of the same string from coexisting.

The plurals ban means that if, for example, one company applies for .podcast and another applies for .podcasts, they will go into the same contention set and only one will ultimately go live.

It also means that you can’t apply for the single/plural equivalent of an already-existing gTLD. So if you were planning to apply for, oh I dunno, .farms for example, you’re out of luck.

The move should mean that lazy applicants won’t be able to rely on piggybacking on the marketing spend of their plural/singular rivals, or on purely defensive registrations. I will also reduce end-user confusion.

The ban on private contention resolution means that contention sets will largely be resolved via an ICANN-run “auction of last resort”, in which ICANN gets all the money.

In the 2012 application round, private resolution was encouraged, and some companies made tens of millions of dollars from their rivals by losing auctions and withdrawing their applications.

Both bans had been encouraged by ICANN’s Governmental Advisory Committee and received the unanimous support of the board (excluding conflict-related abstentions) at the Org’s AGM in Turkiye this afternoon.

ICANN says it WILL raise its domain taxes soon

Prices in all gTLDs will go up after ICANN told registries and registrars last week that it plans to increase the fees it charges them, sometimes called its “tax”, next year.

The extra fee ICANN takes from registrars for each new domain registration and renewal will increase from $0.18 to $0.20, according to an email sent from ICANN VP Russ Weinstein to registrars Thursday evening.

This fee is typically passed on explicitly and directly to registrants in their registrar’s shopping cart.

Less-visible charges on registries will also go up. The fixed quarterly fee will go from $6,250 per quarter ($25,000 per year) to $6,450 per quarter ($25,800 per year) and the per-transaction fee will go up from $0.25 per year to $0.258 per year.

The registry fee changes will take effect January 1, but the registrar fee changes will not take effect until July 1, 2025, the start of ICANN’s next fiscal year, according to ICANN.

“After more than a decade of no changes to registry-level and registrar-level fees, ICANN would like to increase the fees it charges to both parties,” Weinstein wrote.

The two cents tax increase is big in percentage terms — about 11% — while the registry fee is more in line with US inflation at 3.20%.

The fixed registrar accreditation fee is to stay the same at $4,000 per year, while the variable accreditation fee, which is divided between registrars based on their transaction volume, is going up from a total of $3.42 million to $3.8 million per year.

The increases come as ICANN struggles to fill a $10 million hole in its budget — a situation that has already led to layoffs — and some back-of-the-envelope calculations suggest the combined fee increases are designed to raise annual revenue in that ball-park.

Due to the differences between the standard Registry Agreement and Registrar Accreditation Agreement, ICANN can push through the registry fee increases fairly quickly and unilaterally, while the registrar changes have some red tape.

The two-cent tax increase will be part of ICANN’s usual budget process, which includes a public comment period and consideration by the board of directors, while the variable fee increase will be subject to a registrar vote.

Note: an early, unfinished draft of this post was inadvertently published on Friday, for which I can only apologize.

bit.ليبيا? Libya to get its Arabic ccTLD

Libyan ccTLD .ly is to get an Arabic version, ICANN has said.

The TLD is ليبيا. (Arabic reads left to right, so the dot goes at the end), means “Libya”, and the ASCII Punycode that will actually show up in the DNS is .xn--mgbb7fyab.

ICANN said that the string has passed the String Evaluation phase of the IDN ccTLD Fast Track process and is now eligible for delegation.

It’s not entirely clear how long Libya was in the “Fast Track” process, but Wikipedia has records of requests for ليبيا. going back over a decade. That’s not unusual.

But ليبيا. is an unusual, though not unprecedented, case of an IDN ccTLD set to be delegated to a different manager than the existing Latin-script ccTLD’s registry.

The Arabic version is set to go to the General Authority of Communications and Informatics, Regulatory Affairs Directorate, while .ly is delegated to the General Post and Telecommunication Company.

.ly is of course well known on the Anglophone internet as a domain hack, with the best-known registrant probably URL shortening service bit.ly.

Verisign gets eight more years running the root

Verisign and ICANN have renewed their deal that sees Verisign run the DNS root, according to the company.

Verisign said the Root Zone Maintainer Agreement was renewed on October 20 for another eight-year term.

The RZMA is basically a technical services contract under which Verisign updates and publishes the root zone file (basically a list of TLDs and their nameservers) according to ICANN’s instructions. All the other root zone operators mirror that file.

It’s the first renewal since ICANN secured its independence from the US government in 2016, but Verisign and its predecessors have been managing the root since 1993.

The deal is separate from Verisign’s contracts to run .com and .net.

Two-horse race for open ICANN board seat

A Brit and a Canadian have been put forward to fill the seat on the ICANN board of directors that unexpectedly became vacant last month.

The ccNSO-appointed seat 12 was left empty with the abrupt resignation of Katrina Sataki in September.

Now, the ccNSO says two candidates will face election — Byron Holland, CEO of Canadian ccTLD registry CIRA, and Nick Wenban-Smith, general counsel of .uk registry Nominet.

The election is not expected to take place until next February, following due diligence and a ccNSO community Q&A with the candidates.

Sataki is European, so a Wenban-Smith win would keep the geographic mix on the board unchanged. A Holland win would tilt the balance towards North America.

Both candidates are men, so the result will not go towards balancing the gender mix. After ICANN 81 next month, there will be one additional woman on the board, but this gain will be reversed when the CEO changes in December.

Chinese say internet not ready for single-letter gTLDs

Several major Chinese tech organizations have urged ICANN not to lift its ban on single-character gTLDs, saying the risk of confusion is too great.

Allowing single-character gTLDs in Han script was the most objected-to part of the draft Applicant Guidebook in ICANN’s just-closed public comment period, with the objections all coming from China.

Han script is used in Chinese, Japanese and Korean languages. A single character can convey the same semantic impact as a whole multi-character word in European languages.

But the commenters warned that a single character can have multiple meanings, increasing the risk of confusion.

Rui Zhong of the Internet Society of China said for example that the Han character “新” can mean “new” but is also the abbreviation for the Chinese province of Xinjiang and the nation of Singapore.

Lang Wang of CNNIC warned: “the similarities in pronunciation, form, and meaning of Han script single-character gTLD could lead to the risks of phishing, homophone attacks, intellectual property disputes, etc”.

It seems the issue may be a bit more complex than visually identical words having multiple definitions in other languages, with multiple commenters saying that single-character words do not reflect the reality of modern Chinese usage.

Namecheap scores win in .org price-cap lawsuit

Namecheap’s lawsuit over ICANN’s decision to lift price caps in .org and .info will be allowed to proceed, a California judge has ruled.

The Superior Court in Los Angeles recently threw out ICANN’s attempt to get the case dismissed, according to court documents released by ICANN. There will now be a hearing in January.

Namecheap’s lawsuit concerns ICANN’s decision in 2019 to lift price caps in Public Interest Registry’s .org contract and the .info contract then with Afilias (now Identity Digital).

Both registries had previously been limited to a 10% price increase every year.

The registrar filed an Independent Review Process case against ICANN, which is mostly won. In 2022, the IRP panel slammed ICANN for its secrecy and lack of adherence to its bylaws and issued seven recommended actions the Org could take to rectify its transgressions.

In the current lawsuit, filed this January, Namecheap claims that ICANN “largely ignored” most of these recommendations. It wants the court to force the Org to abide by the IRP ruling, which among other things calls for ICANN to look into reinstituting price caps.

But ICANN objected, saying Namecheap “is asking this Court to convert recommendations into requirements”, adding that it “does not have an obligation to act in accordance with the ‘recommendations’ of an IRP Panel”.

It demurred, asking the court to throw out Namecheap’s complaint, but the court declined to do so on legal grounds, meaning the claims will be heard on the merits.

In the five years since the .org and .info price caps were lifted, non-profit PIR has not raised .org prices once.

For-profit Identity Digital has raised .info prices every year, by between 9.38% and 11.03%, raising the cost from $10.84 in 2019 to $17.50 today. The price will go up again by 8.57% to $19.00 in January.

Some Guy wants to take over .com and .net

Some Guy has noticed that domain name prices keep going up and has offered to take over the .com and .net registries from Verisign.

The Some Guy recently filed a formal Request for Reconsideration with ICANN, asking it to overturn its recent decision to renew Verisign’s .com contract and award it to him instead. The RfR reads:

I seek to become a registry operator committed to making .COM domains more affordable and accessible to students, startups, and developers. The decision to renew Verisign’s contract hinders competition, limiting opportunities for more innovative registry operators like Asxit LLC to contribute to the digital ecosystem.

The request is accompanied by a 25-page, ChatGPT-odored analysis of why Asxit LLC would be a better .com registry than Verisign, which concludes:

The introduction of Asxit LLC as a .COM registry operator would bring significant improvements in pricing, innovation, support, and accessibility compared to Verisign’s current management. By focusing on affordable and flexible solutions, Asxit LLC aims to create a more inclusive and competitive environment for all users. This change would enhance the value of the .COM domain and support the growth of a diverse and innovative digital community.

In August, Some Guy with the same last name, who said he is a student at Liberty University in Virginia, said Asxit LLC should take over .net as well.

They’re not the funniest or craziest submissions ICANN has received over the years, but they might be worth a chuckle if you’re clock-watching on a Friday afternoon.

The sad part is of course that ICANN is now duty-bound to commit legal and board resources preparing a response to this request before throwing it out entirely.