.购物

Q2.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) of the applying entity, 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: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.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.

Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).

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

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.

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.

Script of String

Chinese (Han)

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

Applied-for Primary String (U-Label)

购物

Applied-for Primary String (Code Points)

U+8D2D U+7269

Script of Variant String

Chinese (Han)

Is this variant string for an existing gTLD that is already operated by the applying entity or for a newly applied-for string in the 2026 Round?

Existing TLD

What is the meaning/definition of the variant string?

Shopping，E-commerce Gateway

Explain how the primary applied-for and variant strings are considered the same, including the meaning, by the relevant user communities.

1. Determination and Meaning of Sameness by the User Community In the global Chinese-speaking internet community, the Simplified string "购物" and the Traditional string "購物" are considered absolutely identical in meaning, pronunciation, and conceptual identity based on three dimensions:

Semantic Identity: Both combinations represent the exact same core commercial activity—"shopping"—regardless of whether Simplified or Traditional characters are used.

Typographical Mapping: They maintain a strict one-to-one character mapping. According to the IDN Chinese Variant Tables, they are technologically and cognitively treated as inseparable variants.

Interchangeability of User Habits: Chinese-speaking users naturally utilize either version based on regional habits (e.g., Simplified Chinese is predominant in Mainland China, while Traditional Chinese is widely used in Hong Kong, Macau, Taiwan, and certain overseas Chinese communities), and they firmly believe that both gTLDs point to the exact same brand.

Consequently, allowing separate registrations would inevitably lead to severe public confusion and phishing risks. The user community universally expects a "register-one-block-the-other" reservation policy.

2. Real-World Commercial Application Demands Case 1: Cross-Regional Operations of E-Commerce Platforms (e.g., Alibaba's "Taobao") Background: Platforms utilize the Simplified "淘宝购物" for Mainland China and switch to the Traditional "淘寶購物" for Hong Kong, Taiwan, and overseas markets. Protection Demand: Platforms maintain identical brand expectations for both variants. Without an automatic blocking mechanism, cybercriminals could easily register the unreserved Traditional .購物 to deploy phishing sites, harming overseas users. Thus, a compelling demand exists for cross-regional variant protection.

Case 2: Anti-Counterfeiting for High-Value Consumer Brands (e.g., "美宝莱.购物") Background: The well-known skincare brand "MEIBAOLAI" intends to launch an official portal under "美宝莱.购物" to securely guide consumers to authentic products online. Protection Demand: The Simplified "美宝莱.购物" and Traditional "美寶萊.購物" are cognitively identical to consumers. If the Traditional variant is not automatically blocked, counterfeiters could secure it to sell illicit products, tarnishing brand reputation and jeopardizing consumer safety. Hence, the enterprise has a powerful demand for absolute exclusivity.

Case 3: Unified Digital Asset Protection for International Luxury Brands (e.g., "宝马.购物") Background: To support online direct car sales and merchandise e-commerce, the German luxury automaker BMW requires a unified digital commercial space like "宝马.购物". Protection Demand: In the Chinese linguistic context, the combination of "宝马/寶馬" with "购物/購物" is instinctively recognized as an official commercial act by BMW. If the variant relationship is not technically synchronized, a third-party registration of the Traditional domain would create a severe vulnerability in BMW’s global trademark defense. Therefore, multinational giants have an uncompromising demand for the automatic reservation of variants.

Explain the benefits and the user communities who will benefit from the introduction of the applied-for variant string(s).

1. Insufficiency of a Single Label and Necessity of Variant Strings Introducing only a single form of the TLD (e.g., only .购物 in Simplified Chinese) is entirely insufficient. It is linguistically and culturally necessary to introduce both Simplified and Traditional versions (.购物 and .購物) as a complete package of mutual variants:

Bridging Regional Linguistic Divisions: Simplified Chinese is standard in Mainland China, while Traditional Chinese is preserved in Hong Kong, Macau, Taiwan, and many overseas communities. The two labels represent inseparable facets of input habits.

Preventing User Confusion: Without the corresponding Traditional TLD, Traditional Chinese users may experience a sense of regional exclusion or cognitive disconnect.

Thwarting Cybersquatting and Phishing: If the variant is unprotected, bad actors could easily exploit it to deceive users. Therefore, a variant mechanism must be introduced where registering one version automatically blocks and reserves the other, eliminating counterfeiting at the technical root to safeguard brands and consumers.

2. User Communities Served by the Primary and Variant TLDs Primary String (Simplified .购物): Serves Simplified Chinese internet users predominantly located in Mainland China, alongside commercial entities engaging in digital retail and marketing within these regions.

Variant String (Traditional .購物): Serves Traditional Chinese internet users primarily in Hong Kong, Macau, Taiwan, Southeast Asia, and major Chinese diaspora communities globally.

The Collectively Benefiting Core Community: The global Chinese-speaking populace and corporate brands operating in Chinese markets. When an enterprise registers either version, its variant is securely reserved, placing users and businesses across all regions into a confusion-free and fraud-resistant network.

3. Reflection of Community Needs in the Design of the IDN Tables To align with the community’s need for security and confusion prevention, the IDN tables exhibit a framework of "complete structural isomorphism at the foundational level, with strict mapping in status management":

Similarities in Foundational Mapping: The IDN tables for both TLDs strictly adhere to official Chinese character standards and IDN RFC standards. The second-level "Simplified-to-Traditional" and "Traditional-to-Simplified" character relationships are completely mirrored and consistent.

Differences and Synergies in Status Management (Blocking Strategy): When a specific second-level label under the primary TLD (Simplified, e.g., "宝马.购物") is registered and set to "Active," the policy engine of the IDN tables automatically flags the corresponding label under the variant TLD (Traditional, "寶馬.購物") as "Reserved".

This IDN design focuses on "synchronized technical blocking," addressing the community's desire to respect regional character preferences while eliminating security anxieties regarding third-party variant exploitation.

Describe the steps that the applying entity will take to minimize the operational and management complexities of variant gTLDs and variant domain names that impact registrars, resellers and/or registrants.

1.TLD Variant Bundling To minimize management costs for all stakeholders, the Registry treats .购物 (Simplified Chinese) and .購物 (Traditional Chinese) as an inseparable variant package in its top-level architecture. Registrar and Reseller Side: Registrars are not required to maintain two independent sales or billing systems. The Registry handles all underlying linkage between the Simplified and Traditional Chinese gTLDs automatically via backend technical integration. Variant Status Management: Strictly adhering to IDN variant management policies, whenever a second-level domain is activated under the primary TLD (e.g., 宝马.购物), the policy engine automatically sets all corresponding variants (e.g., 宝马.購物, 寶馬.购物, 寶馬.購物) to "Reserved" status. This eliminates third-party cybersquatting and phishing at the technical root, reducing brand protection complexities and dispute workloads. 2.Registrar and System Level: Mandatory Lifecycle Synchronization To prevent adding operational complexities like manual reconciliation or custom customer service logic for registrars, the Registry implements a comprehensive linkage mechanism for the entire variant package at the Registry Server layer: Bundled Lifecycle: All operational statuses—including creation, deletion, transfer, information updates (Update/WHOIS), and entry into the redemption period—are mandatorily synchronized using the entire variant package as a single unit. Transparent to Registrars: When a registrar renews the primary domain, all variant domains are extended automatically; when deleted, variant locks are lifted concurrently. Because all variant derivation and synchronization logic are executed automatically by the backend, it remains completely transparent to registrars, eliminating the need for custom synchronization code. 3.Registrant Side: "One-Stop Package" & Financial Simplification To eliminate financial and operational friction for registrants dealing with variant domains, the Registry enforces a "one-stop" policy: Single Payment, Multiple Protection: Registrants only pay a one-time registration or renewal fee for the original domain. Its corresponding standard Simplified and Traditional Chinese variant domains are automatically assigned to the same registrant without duplicative fees. Automatic Provision of Language Assets: Regardless of whether the registrant submits a Simplified-Chinese-only (SC-only), Traditional-Chinese-only (TC-only), or mixed domain string, the system automatically generates the standard SC-only and TC-only versions based on the official Variant Table and grants them to the registrant free of charge. 4.Resolution Control While minimizing management complexities, the Registry balances technical standardization with business flexibility to accommodate diverse application scenarios: Independent Control Over DNS Resolution: Under the premise of strict ownership bundling, the Registry fully delegates DNS configuration authority. Variant domains remain independent at the authoritative resolution layer, allowing registrants to configure distinct resolution records (such as A or MX records) independently. Key Business Scenarios: Traffic Splitting: Enterprises can split traffic based on user input habits. For example, typing the Traditional Chinese 香港某企業.购物 can resolve to a server in Hong Kong or overseas, while the Simplified 香港某企业.购物 resolves to a Mainland China server, delivering optimized loading speeds and a localized experience.

This applied-for TLD is not a “generic string” using the definition of "generic string" in Section 3(d) of Specification 11 of the Base RA (as described in Question 121).

true

Applied-for Variant(s)

xn--g2xv08c

Variant String (U-Label)

購物

Variant String (Code Points)

U+8CFC U+7269

If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.

Not Applicable

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

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