Application Details
Last published on: 7 October 2026 at 15:37 UTC
Application Responses
Section: Applying Entity Information
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.
Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.
Nawang Heli(Xiamen) Network Service Co., LTD.
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.
Limited Liability Company
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.
No. 201, 45 Wanghai Road, Software Park, Xiamen, Fujian
Provide the website URL of the applying entity, if available.
https://nic.xn--g2xx48c
1. Choose Yes or No. 2. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement).
true
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. 2. 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. 3. If the applying entity is an ICANN accredited registrar, specify the registrar ID number.
IANA ID xn--g2xx48c
Choose Yes or No.
false
86
Provide the primary business phone number without including the country code.
13600939686
Provide the primary business email address of the applying entity.
contact1@nicgouwu.com
Enter the street address (no PO Box).
No. 201, 45 Wanghai Road, Software Park
Enter the city, village, municipality, etc.
Xiamen
Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.
Xiamen, Fujian
1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.
361000
CN
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.
Shangpinjie (Xiamen) Technology Co.,Ltd.
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.
Limited Liability Company
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.
Xiamen, Fujian
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.
Xiamen Nawang Technology Co.,Ltd
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.
Limited Liability Company
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.
Xiamen, Fujian
Section: Applying Entity Background and Organization
This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.
Shangpinjie(Xiamen)Technology Co., Ltd.
Xue Chai
Shangpinjie(Xiamen)Technology Co., Ltd.
Yingfeng Chen, Xue Chai
Shangpinjie(Xiamen)Technology Co., Ltd.
Section: Self-Certification
Provide a single document for Self-Certification question Q2.2-1. The document must include only the SC2.2-1.1, SC2.2-1.2, or SC2.2-1.3 statements. Do not modify any of the Self-Certification statements.
1. Provide a single document for Self-Certification question Q2.2-1. 2. The document must include only the SC2.2-1.1 through SC2.2-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. 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.
Section: Operational/Planning
The document for Q2.3.1 must be a PDF. The document for Q2.3-2 must be an Excel (.xlsx) file.
The document for Q2.3-1 must be a PDF.
Section: Security Policy and Planning
Provide a single document for Self-Certification question AGB Q220, Q5.1-1. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. Do not modify any of the Self-Certification statements. If 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.
1. Provide a single document for Self-Certification question Q5.1-1. 2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. 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.
Section: DNS Abuse
Provide a single document for Self-Certification question AGB Q221, Q5.2-1. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. Do not modify any of the Self-Certification statements. If 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.
1. Provide a single document for Self-Certification question Q5.2-1. 2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. 3. Do not modify any of the Self-Certification statements. 4. 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.
Section: Primary String
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.
xn--g2xx48c
购物
U+8D2D U+7269
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"
Shopping，E-commerce Gateway
If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)
Chinese (Han)
Provide a representation of the string according to the International Phonetic Alphabet.
[kɤʊ̯˥˩ u˥˩]
Confirm the statement using a checkbox.
true
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. 1a. 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. 2. Explain how this purpose is sustainable over time.
1. Mission and Purpose The 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. Intended 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. Intended 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. Related Activities: Innovative 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. Variant 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. 1a. Explanation of Variant TLDs The 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). All associated variant applications share an identical mission and purpose, irrespective of which specific string serves as the primary application. 2. Long-Term Sustainability The gTLDs’sustainability is driven by three core dimensions: Rigid 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. Win-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. Scenario 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.
Section: Variant String(s)
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.
xn--g2xv08c
購物
U+8CFC U+7269
Provide the script of the variant string (both in English and as referenced by the RZ-LGR/ISO 15924)
Chinese (Han)
Select an option.
Existing TLD
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".
Shopping，E-commerce Gateway
Provide at least three bona-fide examples to support the explanation. (for example, evidence of trademark use by showing real world use cases).
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.
1. Applying entities shall explain why one label is insufficient and two or more labels are necessary to satisfy regional, linguistic, or cultural drivers. 2. Identify the user communities served by primary and for each of the variant TLDs. 3. 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.
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.
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. Notes: Commitments 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.
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.
Confirm the statement using the checkbox.
true
Section: Safeguard Identification
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.
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
Yes
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
Select Yes or No. Notes: 1. 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). 2. 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. 3. 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).
No
Section: Registry Voluntary Commitments (RVCs)
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.
1. Select Yes or No. 2. 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). 3. 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. 4. 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). Notes: If 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.
No
Section: Brand & Code of Conduct Exemptions
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).
Select Yes or No
No
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.
No
Section: Additional Information and Supporting Materials
This question set collects any additional information that the applying entity would like to provide, including any supporting materials.
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: a) Individual registry policies; b) Separate agreement with a third-party to fulfill certain commitments; c) Terms of use; d) Additional Community Registration Policies not intended for RA inclusion; e) Other materials that clarify the applying entity’s mission, values, or intended use of the gTLD. Notes: 1. This question is optional and for informational purposes only. 2. The information provided here will not be evaluated as part of the application, or be contractually binding on the applying entity. 3. All submissions to this question will be posted for the public to review and comment.
Not Applicable
Section: Bona Fide Intent and Prohibited Communications
This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.
Confirm the statement using the checkbox.
true
Confirm the statement using the checkbox.
true