tld.report · The 2026 Round

Snapshot of 8 October 2026 · ICANN APS, public fields

Applications / .luckin / LCGC2612T-T93090 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.luckin

Brand TLD · Spec 13Active

Luckin Coffee Group Co., Ltd., CN Q1·Q25

Ultimately controlled by Luckin Coffee Inc. Q108 · ICANN record ↗

§ 1 — Meaning of the string Q118·Q120

No English Translation

/ˈlʌkɪn/

§ 2 — Mission and purpose Q133

I. Mission and Objectives

Mission: As the applying entity and potential Registry Operator of the “.luckin” TLD, our mission is to build a secure, trustworthy, and unified global digital identity infrastructure. Through centralized management, we will promote the standardized development and global collaboration of the Luckin ecosystem, thereby supporting our brand’s mission to “create moments of luck and inspire a passion for a better life.”

Objectives: We aim to establish “.luckin” as Luckin Coffee’s authoritative, exclusive internal digital identifier. We will restrict registration rights to the Group and its subsidiaries to ensure unified global management and compliant use of brand domains, thereby enhancing our brand asset value and digital operational efficiency.

II. Intended Registrants

We intend registrants to be limited to entities within the Luckin Coffee Group and its subsidiaries, specifically including our Group headquarters, core business departments, subsidiaries, and affiliated companies. This ensures the consistency and security of our brand usage.

III. Intended Users

Our intended users primarily include Luckin Coffee employees, global consumers, corporate clients, and ecosystem partners. Through these exclusive domains, they will access Luckin Coffee’s official store network, brand services, and official information channels to obtain a reliable, authentic experience.

IV. Related Initiatives

We will operate “.luckin” as our globally unified internal brand TLD. We will use it to integrate the digital identity systems of our core operating entities and achieve centralized management of our brand assets.

Leveraging the “.luckin” domain, we will support the realization of our brand mission — “Creating moments of luck and inspiring a passion for a better life” — and our vision of “Building a world-class coffee brand.” Through a unified digital entry point, we will convey Luckin Coffee’s brand values and service commitments to users worldwide.

By establishing a digital bridge that connects our global operations and information through the domain, we will promote standardized operations and coordinated development of our brand on a global scale.

V. Explanation of Long-Term Sustainability

Luckin Coffee has established a global brand network and has become one of China’s largest coffee chains by number of stores. Our physical footprint and market position provide a solid foundation and sustained business demand for the long-term use of the TLD.

We have assembled a professional technical and management team, backed by ample financial support from the Group, and have established a comprehensive internal system for domain registration, resolution, management, and security protection. Through continuous investment of our internal resources, we ensure that the domain system is upgraded in tandem with our business development, guaranteeing the financial sustainability of our operations.

We consistently uphold our core philosophy of “creating moments of luck and inspiring a passion for a better life.” Through ongoing brand-building efforts and corporate social responsibility initiatives, we continuously strengthen our brand’s social value recognition. This deep-rooted brand heritage not only ensures the long-term vitality of the Luckin brand but also infuses our domain system with a lasting spiritual core and a guarantee of credibility for sustainable development.

We will strictly adhere to all ICANN regulations and global internet governance standards, establishing rigorous domain security monitoring and emergency response mechanisms. By ensuring high operational compliance and the security of our technical systems, we will effectively mitigate various risks, uphold the credibility of our domain system, and provide a secure, reliable, and trustworthy long-term digital home for Luckin Coffee’s global digital strategy.

§ 3 — Commitments and safeguards Q164–Q188

More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169Yes to: more trustworthy (Q164), consumer risk if abused (Q165)
Voluntary Safeguard PICs Q170·Q171

• Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring registrants to comply with all applicable laws, including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct), fair lending, debt collection, organic farming, disclosure of data, and financial disclosures. • Registry Operators will include a provision in their Registry-Registrar Agreements that requires registrars at the time of registration to notify registrants of the requirement to comply with all applicable laws. • Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring that registrants who collect and maintain sensitive health and financial data implement reasonable and appropriate security measures commensurate with the offering of those services, as defined by applicable law.

Registry Voluntary Commitments Q172·Q173None · 5 do
Brand TLD criteria confirmed, trademark certificate attached Q180·Q181Yes · certificate not published
Confirms the string is not a “generic string” Q183Yes
Spec 11 §3(d) statement Q184

The applying entity confirms that the proposed “.luckin” TLD fully complies with the requirements of Section 3(d) of Specification 11 of the Registry Agreement and there would not exist any such conflict. The reasons are as follows:

I.“.luckin” is a brand string and does not fall under Section 3(d) of Specification 11

According to the explicit definition in Section 3(d) of Specification 11, its restrictive provisions apply only to generic strings, i.e., strings consisting of a word or term that denotes or describes a general category of goods, services, groups, organizations, or things. “.luckin” is clearly a brand string, based on the following grounds:

1. “luckin” is a valid registered trademark that refers to the Luckin Group and the specific products and services it provides, rather than a generic name for a class of goods or an industry.

2. This application is submitted under the application category established by ICANN for brands, which is specifically designed to allow brand owners to operate an exclusive domain name space consistent with their trademarks.

Therefore, the provision in Section 3(d) of Specification 11 regarding the prohibition of restricting registration eligibility to a single entity or its affiliates does not apply in this application.

II. The Operational Model Aligns with the Purpose of Brand TLD and ICANN Policies

As a brand TLD, the operational arrangements for “.luckin” are as follows:

1. This TLD will serve as a digital asset exclusively for internal use by the Luckin Group. Registration eligibility will be limited to Luckin Group companies and their affiliates, wholly-owned subsidiaries, or controlled subsidiaries worldwide.

2. Within the aforementioned scope of use, clear and transparent registration and management policies will be established to ensure that all eligible affiliates can register and use the domain fairly in accordance with unified internal governance procedures.

3. This registration model ensures that domain usage is controlled by known, trusted legal entities, effectively reducing the risk of DNS abuse and meeting the security and stability requirements of the domain name system.

In summary, as a brand string, the operational model of “.luckin” constitutes a standard use of a .brand TLD and is not subject to the restrictions of Section 3(d) of Specification 11. We will operate this TLD in accordance with the above guidelines to ensure its continued compliance with the relevant provisions of the Registry Agreement.

§ 4 — All other published answers

Every other answer ICANN published for this application, in the order of the form. Contact details (Q17–Q24) are left to the ICANN record.

Q212Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.

Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.

Answered with a document. Attachments are not published by ICANN.

Q220Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Answered with a document. Attachments are not published by ICANN.

Q221Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Answered with a document. Attachments are not published by ICANN.

Q121As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.

As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.

true

Q223By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

true

Q224By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

true