.luckincoffee
Is .luckincoffee a real TLD? Who’s applying to run it?
Nobody has applied for .luckincoffee in its own right, as of 7 October 2026. Luckin Coffee Group Co., Ltd. named .luckincoffee as the replacement string of its .luckin application.
A single-company brand suffix for one coffee chain: useful to that company alone, with no open market and no resale value.
the applicant company itself and its own stores, apps and campaigns; no third party can register or buy a name under it
No applications recorded for this TLD yet.
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: a single company's own consumer-facing food-and-beverage chain brand as a closed TLD, where the only possible registrant is the chain itself and the value is controlling the brand's own namespace across stores, apps and campaigns.
Same construction and same job: a coined brand word fused to its own category noun, applied for by the operating group so one chain of physical outlets can put its primary identity on the string, with no third-party registrant ever contemplated.
Same bet from the same kind of buyer: an East Asian retail/F&B group claiming its house brand as a closed TLD primarily as a home-market brand-control asset rather than for any open registration demand.
What a .luckincoffee domain is
.luckincoffee is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. Nobody has applied for .luckincoffee in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .luckincoffee domain extension real yet?
.luckincoffee is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .luckincoffee domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .luckincoffee name can only be registered after that, once the string is delegated and its registry opens.
Is .luckincoffee a real TLD?
Not yet. .luckincoffee is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .luckincoffee as part of an application for another string. Every entry on this page links to its source.
- Luckin Coffee Group Co., Ltd. · first recordedICANN
“LCGC2612T-T93090 · Luckin Coffee Group Co., Ltd. · replacement string of .luckin”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows a single applicant, Luckin Coffee Group Co., Ltd., filed as a brand type with this string as the replacement for a primary application for .luckin; contention count on the record is 0. A brand TLD has exactly one registrant, so 'value to the best-fit buyer' collapses to the operator's own utility: a controlled namespace for store, loyalty, app and campaign addresses, plus defensive certainty that nobody else holds the string. By analogy (flagged as analogy) with the earlier wave of corporate brand TLDs, most such strings see light or purely defensive use, with a minority adopted as a customer-facing primary identity; a replacement string is by its nature the fallback when the shorter primary string cannot proceed, and a twelve-character string is less attractive as a primary identity than the six-character one it backs up. It is not in the 30-49 band because there are no volume registrations, no price-driven demand and no aftermarket of any kind. It is not in the 1-9 band because a corporate registrant has a real, if narrow, use for a secured brand namespace, and the string is unambiguous and recognisable within its own customer base. Main market uncertainty: whether the operator would actually route customer-facing traffic (apps, receipts, store signage, promotions) through the TLD or hold it defensively; geography and scale of the brand's customer base are unknown from the record and are not asserted here.