Summary

  • ICANN's Board denied Reconsideration Request 26-4 on 18 October 2026, upholding the staff decision to mark Nameshop's 2012 .IDN application terminated.
  • The requested change from .IDN to .INTERNET had been denied in 2013. The Board says the old application never became a claim to .INTERNET; its refusal to withdraw after a final refund opportunity did not keep the failed application alive.
  • The Board also said any future reconsideration request concerning this same application will be deemed frivolous and summarily dismissed. That is a limit on this file, not on the general right to seek reconsideration.

An application can be dead in substance and still occupy a chair at the administrative table. Nameshop's .IDN file did that for fourteen years. ICANN had ruled out the string under the 2012 round's country-name rule, denied an attempted switch to .INTERNET, and repeatedly offered a refund route. Yet the file remained open enough to produce another formal dispute. On 18 October, the Board finally decided both the file and the next attempt to relitigate it.

This is the unglamorous side of domain governance. A registry must keep an accurate history of who applied for what and how the decision was made. It need not give a rejected application an indefinite procedural life. The difference became urgent when the 2026 round began to accept new claims to domain strings.

A three-letter trap, followed by a second string

Nameshop applied for .IDN on 13 June 2012. In domain engineering, IDN is a familiar shorthand for internationalized domain name. In the application, however, .IDN was the exact three-letter string requested. It is also Indonesia's ISO 3166-1 alpha-3 country code. The 2012 Applicant Guidebook barred country and territory names from approval in that round. The Board Accountability Mechanisms Committee's record says ICANN told the applicant the string could not pass in June 2012.

The applicant sought to change the string to .INTERNET that September. ICANN denied the change on 19 February 2013; a reconsideration challenge failed that year too. The distinction is tedious only until someone claims priority in a new round. A request to amend an application is evidence that a request was made. It is not an approved amendment. ICANN's October decision rests on that simple separation: the file was always for .IDN, whatever later correspondence called it.

The record also shows a long conversation, not a sudden trapdoor. According to the committee, a 2019 ICANN letter proposed withdrawal with a full US$47,000 application-fee refund and suggested that Nameshop could apply for .INTERNET in a later round. That was a route back into competition, carrying the price and uncertainty of a new application. Nameshop wanted the old file to supply the bridge instead. ICANN never agreed to build it.

ICANN had to write an ending it had omitted

The 2012 Guidebook lacked a specific way to terminate unsuccessful applications that their holders would not withdraw. In September 2025, the Board made one: final notice, 90 days to withdraw and claim any eligible refund, forfeiture of the refund if no valid request arrived, and administrative closure. The Board identified .IDN among applications that had already been determined unable to proceed. It cited the need to stop maintaining old files as the next round approached.

There is a documentary wrinkle worth keeping visible. The published 2025 resolution says that a non-withdrawn file would be moved to withdrawn status. The committee's later account and the Board's October decision call Nameshop's actual portal status terminated. Both documents describe the same closure sequence. The public text does not explain the difference in labels. It supplies no basis to infer that the old .IDN filing turned into a valid .INTERNET claim during the handoff.

ICANN gave Nameshop a final withdrawal deadline of 15 May 2026. Nameshop expressly declined on 13 May. Staff notified it in June that termination would follow, then changed the status on 14 July. Nameshop challenged that action in August. The committee separated the claims: allegations about Board inaction were dismissed as insufficiently stated or late; the challenge to staff's status change received a merits review. The Ombuds recused herself. Nameshop submitted a rebuttal in October. The Board's eventual denial was not a refusal to open the envelope.

The second lock is the consequential one

The Board found that .IDN failed the original evaluation rule, the .INTERNET switch had been denied, and staff followed the 2025 closure procedure. It refused the requested restoration and the proposed advance delegation of .INTERNET. Then it went a step further: future reconsideration requests related to this same application ID would be treated as frivolous under ICANN's bylaws and summarily dismissed.

That sentence changes the economics of persistence. An applicant can still put an argument in public, seek a fresh application under the current rules, or use whatever other avenue is actually available. It cannot make the same rejected 2012 file into a permanent option on a valuable new string by filing the same reconsideration again. ICANN is defending the boundary between a preserved record and a live entitlement.

There is a cost to such finality. When an institution that judges an application also writes the rule for closing it, readers should demand a traceable notice, a chance to respond, and a clear account of what was decided. The public record here provides dates, a 90-day procedure, the applicant's refusal, a committee analysis, a rebuttal, and a Board decision. It also leaves that withdrawn/terminated wording seam. That seam deserves an explanation in the registry record; it does not supply fourteen more years of priority.

The 2026 round can proceed only if a failed 2012 application stays failed. ICANN's October decision says so in unusually blunt language. It closes one file and stops the process that kept giving the file another chair.