{"applicationHumanReadableId":"NHXN2684T-T27476","applicationDetails":{"applicationHumanReadableId":"NHXN2684T-T27476","applicationType":"Existing gTLD with Variants","primaryString":{"aLabel":"xn--g2xx48c","uLabel":"购物"},"tldVariants":[{"aLabel":"xn--g2xv08c","uLabel":"購物","isWithdrawn":false}],"originalTldVariants":[],"tldTypes":["IDN"],"priorityNumber":-1,"applicationStatus":"Active","processingStage":"Pre-Evaluation Processing","hasClarifyingQuestions":false,"hasChangeRequests":false,"hasObjections":false,"lastPublishedAt":"2026-10-07T15:37:49.924Z"},"questionAndResponses":{"applicationHumanReadableId":"NHXN2684T-T27476","sections":[{"displayOrder":1,"sectionId":"1","sectionTitle":"Applying Entity Information","sectionInstructions":"This question set collects information regarding the legal entity that would enter into a Registry Agreement with ICANN upon successful completion of all relevant application processes. The information collected is intended to be used for background screening.","questions":[{"displayOrder":1,"questionText":"AGB Q1. Full Legal Name","instructions":"Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.","responseText":"Nawang Heli(Xiamen) Network Service Co., LTD.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q3. Legal Entity Form/Business Structure","instructions":"Provide the long form (no acronyms) of the legal entity form/business structure of the applying entity as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation. No additional information should be provided as this will be used for the automatic population of the Registry Agreement.","responseText":"Limited Liability Company","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB Q4. Jurisdiction","instructions":"The jurisdiction indicates the location in which the business of the applying entity is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the applying entity is registered. No additional information should be provided as this will be used for the automatic population of the Base Registry Agreement. Examples include \"Delaware\", \"Germany\", etc.","responseText":"No. 201, 45 Wanghai Road, Software Park, Xiamen, Fujian","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":10,"questionText":"AGB Q10. Website URL","instructions":"Provide the website URL of the applying entity, if available.","responseText":"https://nic.xn--g2xx48c","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":11,"questionText":"AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?","instructions":"1. Choose Yes or No. \n2. Use the definition of Affiliate from the Base Registry Agreement (see  https://www.icann.org/en/registry-agreements/base-agreement).","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":12,"questionText":"AGB Q12. If \"Yes\", explain.","instructions":"1. Specify if the applying entity is an existing registry operator, ICANN accredited registrar, and/or an Affiliate of a registry operator and/or registrar.\n2. If the applying entity is an Affiliate, provide the details of such Affiliate relationship, including the name of the affiliated registry operator and/or registrar.\n3. If the applying entity is an ICANN accredited registrar, specify the registrar ID number.","responseText":"IANA ID xn--g2xx48c","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":13,"questionText":"AGB Q13. Is the applying entity a back-end registry service provider (RSP), an ICANN-approved data escrow agent, an emergency back-end registry operator, a Uniform Rapid Suspension (URS) service provider, an ICANN dispute resolution service provider, a Privacy or Proxy Service Provider, or a Reseller?","instructions":"Choose Yes or No.","responseText":"false","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":17,"questionText":"AGB Q17. Phone Country Code","instructions":"","responseText":"86","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":18,"questionText":"AGB Q18. Primary Business Phone","instructions":"Provide the primary business phone number without including the country code.","responseText":"13600939686","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":19,"questionText":"AGB Q19. Primary Business Email Address","instructions":"Provide the primary business email address of the applying entity.","responseText":"contact1@nicgouwu.com","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":20,"questionText":"AGB Q20. Address Line 1","instructions":"Enter the street address (no PO Box).","responseText":"No. 201, 45 Wanghai Road, Software Park","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":22,"questionText":"AGB Q22. Locality","instructions":"Enter the city, village, municipality, etc.","responseText":"Xiamen","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":23,"questionText":"AGB Q23. State/Province/Region","instructions":"Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.","responseText":"Xiamen, Fujian","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":24,"questionText":"AGB Q24. Postal Code","instructions":"1. Enter the postal code, if applicable.\n2. If a postal code does not exist, type “Not Applicable”. ","responseText":"361000","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":25,"questionText":"AGB Q25. Country Code of Location","instructions":"","responseText":"CN","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":26,"questionText":"AGB Q26. Full Legal Name","instructions":"If applicable, provide the full legal name as it appears on the official registration documents of the Direct Parent Company of the applying entity. Do not use abbreviations. ","responseText":"Shangpinjie (Xiamen) Technology Co.,Ltd.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":28,"questionText":"AGB Q28. Legal Entity Form/Business Structure","instructions":"Provide the long form (no acronyms) of the legal entity form/business structure of the Direct Parent Company as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation.","responseText":"Limited  Liability Company","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":29,"questionText":"AGB Q29. Jurisdiction","instructions":"The jurisdiction indicates the location in which the business of the Direct Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include \"Delaware\", \"Germany\", etc.","responseText":"Xiamen, Fujian","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":36,"questionText":"AGB Q36. Full Legal Name","instructions":"If applicable, provide the full legal name as it appears on the official registration documents of the Ultimate Parent Company of the applying entity. Do not use abbreviations. \"Ultimate Parent Company\" means, with respect to an Applicant (and, if applicable, a Direct Parent Company), the top-level entity that directly or indirectly possesses the power to direct the management and policies of such Applicant (and, if applicable, a Direct Parent Company) through the ownership of voting securities, as a general partner, as a managing member, by contract, or otherwise. An Ultimate Parent Company is not controlled by any other entity. If there are no intermediary entities between the Applicant and the Ultimate Parent Company, the Ultimate Parent Company would be the same entity as the Direct Parent Company.","responseText":"Xiamen Nawang Technology Co.,Ltd","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":38,"questionText":"AGB Q38. Legal Entity Form/Business Structure","instructions":"Provide the long form (no acronyms) of the legal entity form/business structure of the Ultimate Parent Company as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation.","responseText":"Limited Liability Company","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":39,"questionText":"AGB Q39. Jurisdiction","instructions":"The jurisdiction indicates the location in which the business of the Ultimate Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include \"Delaware\", \"Germany\", etc.","responseText":"Xiamen, Fujian","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":2,"sectionId":"1","sectionTitle":"Applying Entity Background and Organization","sectionInstructions":"This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.","questions":[{"displayOrder":1,"questionText":"AGB 104. List all directors of the applying entity.","instructions":"","responseText":"Shangpinjie(Xiamen)Technology Co., Ltd.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB 105. List all officers & partners of the applying entity.","instructions":"","responseText":"Xue Chai","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB 106. List all Material Shareholders","instructions":"","responseText":"Shangpinjie(Xiamen)Technology Co., Ltd.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB 107. List Individuals with Executive Responsibility","instructions":"","responseText":"Yingfeng Chen, Xue Chai","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB 108. Disclose Ultimate Control of applying entity","instructions":"","responseText":"Shangpinjie(Xiamen)Technology Co., Ltd.","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":4,"sectionId":"6","sectionTitle":"Self-Certification","sectionInstructions":"Provide a single document for Self-Certification question Q2.2-1.\r\nThe document must include only the SC2.2-1.1, SC2.2-1.2, or SC2.2-1.3 statements.\r\nDo not modify any of the Self-Certification statements.","questions":[{"displayOrder":1,"questionText":"AGB Q199. 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:\nSC2.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). \nSC2.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.\nSC2.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.","instructions":"1. Provide a single document for Self-Certification question Q2.2-1.\n2. The document must include only the SC2.2-1.1 through SC2.2-1.3 statements.\n3. Do not modify any of the Self-Certification statements.\n4. If the applying entity cannot Self-Certify the SC2.2-1.1 through SC2.2-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC2.2-1.1 through SC2.2-1.3 statements.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":5,"sectionId":"7","sectionTitle":"Operational/Planning","sectionInstructions":"The document for Q2.3.1 must be a PDF.\r\nThe document for Q2.3-2 must be an Excel (.xlsx) file.","questions":[{"displayOrder":1,"questionText":"AGB Q200. 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).","instructions":"The document for Q2.3-1 must be a PDF.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":6,"sectionId":"8","sectionTitle":"Security Policy and Planning","sectionInstructions":"Provide a single document for Self-Certification question AGB Q220, Q5.1-1.\r\nThe document must include only the SC5.1-1.1 through SC5.1-1.3 statements.\r\nDo not modify any of the Self-Certification statements.\r\nIf the applicant cannot Self-Certify SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements.","questions":[{"displayOrder":1,"questionText":"AGB Q220. 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:\nSC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services.\nSC5.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.\nSC5.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.","instructions":"1. Provide a single document for Self-Certification question Q5.1-1.\n2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements.\n3. Do not modify any of the Self-Certification statements.\n4. If the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1.1-3 statements.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":7,"sectionId":"9","sectionTitle":"DNS Abuse","sectionInstructions":"Provide a single document for Self-Certification question AGB Q221, Q5.2-1.\r\nThe document must include only the SC5.2-1.1 through SC5.2-1.7 statements.\r\nDo not modify any of the Self-Certification statements.\r\nIf the applicant cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.","questions":[{"displayOrder":1,"questionText":"AGB Q221. 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:\nSC5.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.\nSC5.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.\nSC5.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).\nSC5.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.\nSC5.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.\nSC5.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.\nSC5.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.","instructions":"1. Provide a single document for Self-Certification question Q5.2-1.\n2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements.\n3. Do not modify any of the Self-Certification statements.\n4. If the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements,  provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":8,"sectionId":"16","sectionTitle":"Primary String","sectionInstructions":"This question set collects basic information regarding the string that is being applied for (for example, a-label, meaning, script). If the applying entity opts to designate a replacement string, it must answer the same set of questions for the replacement string from the AGB Question Set 5 on.","questions":[{"displayOrder":4,"questionText":"AGB Q118. What is the meaning/definition of the applied-for gTLD string?","instructions":"Provide the meaning, or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applying entity. If there is no literal meaning in English (for example, a brand name or a proper noun without a translation) simply state \"No English Translation\"","responseText":"Shopping，E-commerce Gateway","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q119. Script of String","instructions":"If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)","responseText":"Chinese (Han)","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q120.  Phonetic Representation","instructions":"Provide a representation of the string according to the International Phonetic Alphabet.","responseText":"[kɤʊ̯˥˩ u˥˩]","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q121. 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.","instructions":"Confirm the statement using a checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":8,"questionText":"AGB Q133. What is the mission and purpose of the applied-for gTLD?","instructions":"1. Describe the mission and purpose of the applied-for gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose.\n\n1a. If applying for a variant of an existing gTLD, please also describe the mission and purpose of the existing gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose.\n\n2. Explain how this purpose is sustainable over time.","responseText":"1. Mission and Purpose\nThe fundamental mission of the .购物 and .購物 top-level domains (gTLDs) is to establish an intuitive, global dedicated gateway for Chinese e-commerce (E-commerce Gateway). Leveraging the localized contextual advantages of Chinese generic top-level domains, these gTLDs aim to construct a highly recognizable digital channel rooted in a bond of trust between e-commerce enterprises and consumers through a strict Simplified and Traditional Chinese variant protection mechanism alongside an exclusive industry identity.\nIntended Registrants: Global e-commerce platforms, brick-and-mortar retailers, cross-border e-commerce enterprises, independent D2C (Direct-to-Consumer) brand websites, as well as supply chain service providers offering e-commerce payment, logistics, and marketing solutions.\nIntended Users: Global Internet users, online consumers, and corporate buyers who utilize Chinese (including both Simplified and Traditional scripts) as their primary language for communication or consumption.\n\nRelated Activities:\nInnovative Application: The Registry innovatively integrates .购物 / .購物 domain names with QR codes to introduce the \"ShopCode\" (购物码) service. By scanning a ShopCode, consumers are directed seamlessly to a merchant's private-domain store or a specific product details page. Furthermore, the binding verification between the domain name and the private-domain store serves as a reliable mechanism to authenticate the genuineness of the ShopCode, effectively preventing counterfeiting.\n\nVariant Protection: Establish a linked protection mechanism that recognizes the Simplified and Traditional Chinese domain names (.购物 / .購物) as mutual variants. Upon a user's successful registration of either the Simplified or Traditional character domain string, its corresponding variant domain will automatically transition to an \"Reserved\" status under the ownership of the original registrant. Registration of this variant domain by any third party shall be strictly prohibited, fundamentally eliminating the risks of typosquatting and counterfeiting, and safeguarding the uniqueness of domain assets and brand security.\n\n1a. Explanation of Variant TLDs\nThe applicant is simultaneously submitting applications for .购物 (Simplified Chinese) and .購物 (Traditional Chinese), which are mutual variants of each other. Due to the unique linguistic characteristics of the Chinese language, Simplified and Traditional scripts are deeply rooted in the usage habits of different regions (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).\nAll associated variant applications share an identical mission and purpose, irrespective of which specific string serves as the primary application.\n\n2. Long-Term Sustainability\nThe gTLDs’sustainability is driven by three core dimensions:\nRigid Market Demand: Driven by the massive global Chinese digital retail market, the demand for trustworthy, sector-specific domain names remains long-term and continuously expanding.\nWin-Win Ecosystem: Registrants reduce marketing costs and enhance credibility via industry-specific extensions, while consumers easily identify legitimate storefronts. This bidirectional value ensures high renewal rates and a prolonged domain lifecycle.\nScenario Empowerment via \"ShopCode\": As a core innovation, \"ShopCode\" seamlessly embeds domains into merchants’ omni-channel operations. It shortens the consumer journey and unlocks value-added revenue streams through a closed-loop \"Domain-to-Code\" ecosystem, translating domain assets into commercial growth.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":1,"questionText":"AGB Q116. Applied-for Primary String (ASCII Label)","instructions":"","responseText":"xn--g2xx48c","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q117.1 Applied-for Primary String (U-Label)","instructions":"","responseText":"购物","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q117.2 Applied-for Primary String (Code Points)","instructions":"","responseText":"U+8D2D U+7269","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":9,"sectionId":"10","sectionTitle":"Variant String(s)","sectionInstructions":"This question set collects basic information regarding any variants of the primary string (AGB Question Set 5) that are being applied for. Loop over multiple variant strings if the string has multiple variant strings.","questions":[{"displayOrder":4,"questionText":"AGB Q124. Script of Variant String","instructions":"Provide the script of the variant string (both in English and as referenced by the RZ-LGR/ISO 15924)","responseText":"Chinese (Han)","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q125. 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?","instructions":"Select an option.","responseText":"Existing TLD","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q126. What is the meaning/definition of the variant string?","instructions":"Provide the meaning or intended meaning (for non-dictionary words) of each of the applied-for variant string(s), including sources. If there is no literal meaning in English (for example, a brand name or a proper noun without a translation) simply state \"no English Translation/Meaning\".","responseText":"Shopping，E-commerce Gateway","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q127. Explain how the primary applied-for and variant strings are considered the same, including the meaning, by the relevant user communities.","instructions":"Provide at least three bona-fide examples to support the explanation. (for example, evidence of trademark use by showing real world use cases). ","responseText":"1. Determination and Meaning of Sameness by the User Community\nIn 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:\n\nSemantic Identity: Both combinations represent the exact same core commercial activity—\"shopping\"—regardless of whether Simplified or Traditional characters are used.\n\nTypographical 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.\n\nInterchangeability 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.\n\nConsequently, 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.\n\n2. Real-World Commercial Application Demands\nCase 1: Cross-Regional Operations of E-Commerce Platforms (e.g., Alibaba's \"Taobao\")\nBackground: Platforms utilize the Simplified \"淘宝购物\" for Mainland China and switch to the Traditional \"淘寶購物\" for Hong Kong, Taiwan, and overseas markets.\nProtection 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.\n\nCase 2: Anti-Counterfeiting for High-Value Consumer Brands (e.g., \"美宝莱.购物\")\nBackground: The well-known skincare brand \"MEIBAOLAI\" intends to launch an official portal under \"美宝莱.购物\" to securely guide consumers to authentic products online.\nProtection 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.\n\nCase 3: Unified Digital Asset Protection for International Luxury Brands (e.g., \"宝马.购物\")\nBackground: To support online direct car sales and merchandise e-commerce, the German luxury automaker BMW requires a unified digital commercial space like \"宝马.购物\".\nProtection 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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":8,"questionText":"AGB Q128. Explain the benefits and the user communities who will benefit from the introduction of the applied-for variant string(s).","instructions":"1. Applying entities shall explain why one label is insufficient and two or more labels are necessary to satisfy regional, linguistic, or cultural drivers. \n2. Identify the user communities served by primary and for each of the variant TLDs.\n3. How are these user community needs reflected by differences or similarities in the design of the IDN tables offered for the primary and the each variant TLD.","responseText":"1. Insufficiency of a Single Label and Necessity of Variant Strings\nIntroducing 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:\n\nBridging 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.\n\nPreventing User Confusion: Without the corresponding Traditional TLD, Traditional Chinese users may experience a sense of regional exclusion or cognitive disconnect.\n\nThwarting 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.\n\n2. User Communities Served by the Primary and Variant TLDs\nPrimary String (Simplified .购物): Serves Simplified Chinese internet users predominantly located in Mainland China, alongside commercial entities engaging in digital retail and marketing within these regions.\n\nVariant String (Traditional .購物): Serves Traditional Chinese internet users primarily in Hong Kong, Macau, Taiwan, Southeast Asia, and major Chinese diaspora communities globally.\n\nThe 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.\n\n3. Reflection of Community Needs in the Design of the IDN Tables\nTo 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\":\n\nSimilarities 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.\n\nDifferences 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\".\n\nThis 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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":9,"questionText":"AGB Q129. 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.","instructions":"Provide steps and descriptions that adequately demonstrate all defined criteria are met. See Section 7.6 Variant String Evaluation and Section 3.1.9.2.1 Application Submission of New Primary IDN and its Variant Strings.\n\nNotes:\nCommitments made by an applicant to minimize the noted operational and management complexities will form the basis of contractual requirements to be included in the applicable Registry Agreement.","responseText":"1.TLD Variant Bundling\nTo minimize management costs for all stakeholders, the Registry treats .购物 (Simplified Chinese) and .購物 (Traditional Chinese) as an inseparable variant package in its top-level architecture.\nRegistrar 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.\nVariant 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.\n2.Registrar and System Level: Mandatory Lifecycle Synchronization\nTo 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:\nBundled 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.\nTransparent 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.\n3.Registrant Side: \"One-Stop Package\" & Financial Simplification\nTo eliminate financial and operational friction for registrants dealing with variant domains, the Registry enforces a \"one-stop\" policy:\nSingle 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.\nAutomatic 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.\n4.Resolution Control\nWhile minimizing management complexities, the Registry balances technical standardization with business flexibility to accommodate diverse application scenarios:\nIndependent 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.\nKey Business Scenarios:\nTraffic 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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":10,"questionText":"AGB Q130. 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).","instructions":"Confirm the statement using the checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":1,"questionText":"AGB Q122. Applied-for Variant(s)","instructions":"","responseText":"xn--g2xv08c","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q123.1 Variant String (U-Label)","instructions":"","responseText":"購物","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q123.2 Variant String (Code Points)","instructions":"","responseText":"U+8CFC U+7269","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":13,"sectionId":"2","sectionTitle":"Safeguard Identification","sectionInstructions":"This question set collects information related to determining whether certain Safeguard Public Interest Commitments (Safeguard PICs) are required for the applied-for gTLD string. See Section 7.8.2.3 Safeguard PICs. Answers to these questions will inform assessment by ICANN on whether and which Safeguard PICs must be incorporated in the applicable Registry Agreement (RA) if the string proceeds to delegation. The answers themselves will not automatically make such a determination.","questions":[{"displayOrder":1,"questionText":"AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD?\r\nThink about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"Yes","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused?\r\nThink about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business?\r\nThink about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB Q167. Would most people think that (domains in) the TLD(s) in the application are used for activities that require regular government reporting, inspections, and oversight in various countries?\r\nThink about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment?\r\nThink about how the TLD string(s) in the application will be understood globally, including different languages and cultures.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\nI-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q169. Would most people think that the TLD is used for something usually done by governments?\r\nThink about how the TLD string(s) in the application will be understood globally, including different languages and cultures.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\na. Literally as described in the application\nb. Literally in any other language in which the string is a recognized word or phrase.\nc. Informally in any language or regional variant, where alternative meanings exist.\nI-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q170. Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Registry Agreement (RA) voluntarily regardless of ICANN’s Safeguard Assessment outcomes?","instructions":"Select Yes or No.\n\nNotes:\n1. ICANN will evaluate whether an applied-for gTLD string requires one or more Safeguard Public Interest Commitments (Safeguard PICs) to be included in the Base RA).\n2. In addition to the Mandatory Public Interest Commitments (PICs) that must be included in each Base RA, a subset of Base RAs must include Safeguard PICs based on ICANN’s Safeguard Assessment. See Section 7.8.2.3 Safeguard PICs.\n3. Applying entities for TLDs that are not found to require Safeguard PICs can elect to add them to the applicable Base RAs voluntarily to, for example, further their business objectives, help address issues or concerns that are raised or could be raised with respect to their applications, or avoid the need for the evaluation and implementation of customized Registry Voluntary Commitment (RVC). See Section 7.8.3 Registry Voluntary Commitments (RVCs).","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":14,"sectionId":"12","sectionTitle":"Registry Voluntary Commitments (RVCs)","sectionInstructions":"This question set collects information related to any Registry Voluntary Commitments (RVCs) that the applying entity is submitting. The decision to submit an RVC is typically voluntary, except for those recognized by ICANN to resolve an objection or to address GAC Consensus Advice. See Section 7.8.3 Registry Voluntary Commitments for more information.","questions":[{"displayOrder":1,"questionText":"AGB Q172. Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Registry Agreement (RA) that are unique to your applied-for string?","instructions":"1. Select Yes or No.\n2. In addition to Safeguard Public Interest Commitments (PICs), an applying entity will be permitted to propose one or more Registry Voluntary Commitments (RVCs) to provide additional safeguards with regard to the registry operator’s operation of an applied-for gTLD string. See Section 7.8.3 Registry Voluntary Commitments (RVCs).\n3. RVCs are separate from Community Registration Policies. See Section 7.8.3 Registry Voluntary Commitments (RVCs) and Section 7.8.4 Community Registration Policies for more information. If you are applying for a Community gTLD, please submit the Community Registration Policies by answering Questions 150-155. However, if you propose to include additional Registry Voluntary Commitments in the RA beyond the Community Registration Policies, you may answer \"yes\" and proceed to answer the following questions.\n4. You are encouraged to consider whether there are other means, separate from including commitment(s) in the Base RA, that could be used to further your business objectives or help resolve any anticipated or actual issue(s) raised regarding the applied-for gTLD string or application. See Section 7.8.3 Registry Voluntary Commitments (RVCs).\n\nNotes:\nIf you select “yes” to this question, you are required to pay the conditional Registry Commitments Evaluation fee, and commitments that are approved by ICANN will be included in Specification 11 of the applicable Base RA as specific voluntary public interest commitments as contractual obligations.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":16,"sectionId":"11","sectionTitle":"Brand & Code of Conduct Exemptions","sectionInstructions":"This question set collects information related to whether the applied-for gTLD string is a .Brand (see Section 7.3) or if the applying entity is seeking a Code of Conduct exemption (see Section 7.4).","questions":[{"displayOrder":1,"questionText":"AGB Q179. Are you applying for a Brand TLD?","instructions":"Select Yes or No","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q185. Does the applying entity request a Code of Conduct Exemption?","instructions":"This serves as an indication of intent to apply for an exemption to Specification 9 and that the applying entity is NOT requesting to be designated a .Brand TLD, pursuant to Specification 13.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":17,"sectionId":"13","sectionTitle":"Additional Information and Supporting Materials","sectionInstructions":"This question set collects any additional information that the applying entity would like to provide, including any supporting materials.","questions":[{"displayOrder":1,"questionText":"AGB Q222. 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.","instructions":"1. An applying entity may use this response field to submit any additional, optional information or documentation that the applying entity believes enhances understanding of its application or may be of interest to the general public. This could include, but is not limited to, the applying entity’s: \r\na) Individual registry policies;\r\nb) Separate agreement with a third-party to fulfill certain commitments; \r\nc) Terms of use; \r\nd) Additional Community Registration Policies not intended for RA inclusion; \r\ne) Other materials that clarify the applying entity’s mission, values, or intended use of the gTLD. \r\n\r\nNotes:\r\n1. This question is optional and for informational purposes only. \r\n2. The information provided here will not be evaluated as part of the application, or be contractually binding on the applying entity. \r\n3. All submissions to this question will be posted for the public to review and comment. ","responseText":"Not Applicable","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":18,"sectionId":"14","sectionTitle":"Bona Fide Intent and Prohibited Communications","sectionInstructions":"This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.","questions":[{"displayOrder":1,"questionText":"AGB Q223. 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.","instructions":"Confirm the statement using the checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q224. 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.","instructions":"Confirm the statement using the checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]}]}}