.lan Applied For as New Top-Level Domain in 2026 Round
Coffee Danger, LLC has applied for “lan” as a New gTLD, a new ending to the right of the dot. The filing carries ID CD2694T-T26351, with status listed as Active and processing stage listed as Pre-Evaluation Processing ICANN application summary. The application type is listed as New gTLD. It is part of ICANN’s New gTLD Program: 2026 Round.
ICANN lists the applicant location as US in the NA region. The applicant website is listed as https://www.identity.digital. The record was last published on 7 October 2026 at 15:32 UTC.
Program-wide counts provide the envelope for that filing. ICANN reports 481 total applicants and 1,615 total applications in the 2026 Round ICANN program statistics. All 1,615 applications are listed as Active, with zero listed as Withdrawn. The statistics overview was last published on 7 October 2026 at 15:41 UTC.
Regional counts differ. ICANN reports 198 applicants from North America, 156 from Asia/Australia/Pacific, 111 from Europe, 9 from Latin America/Caribbean, and 7 from Africa. Those five figures sum to the 481 total. That places the “lan” application in the North America cohort.
The broader context here is what an Active, pre-evaluation filing does and does not establish. It secures a place in the queue. It does not grant delegation, which is approval to enter the internet’s root directory, nor does it set launch timing or registry policy. Applied-for strings can be watched early by teams that run DNS, the system that turns names into addresses, plus automation, TLS certificates and input checks. They cannot yet support live systems. The next filters are procedural and technical evaluation, potential string contention where two or more applicants seek the same text, objections and contracting, each with its own timeline.
In my view, short strings deserve disproportionate attention from enterprise operators. They are easy to type. They are easy to remember. They are also easy to collide with in configuration files, scripts and documentation where short tokens already carry local meaning. That does not prejudge this string. It defines the operational checklist if it advances: resolver behavior, search-list handling, certificate issuance rules, brand protection mechanics, and clear communication about intended use.
Looking at what this means for teams planning ahead, the rational posture is watchful preparation without commitment. Inventory where a new three-letter namespace could create ambiguity in existing tooling. Track the evaluation docket for status changes. Hold off on user-facing promises until delegation and launch parameters are fixed. If “lan” clears evaluation and moves toward the root, its brevity could make it useful for compact, memorable names. The value will depend on execution discipline more than on the letters themselves.
