{"applicationHumanReadableId":"IDOL2621T-T27980","applicationDetails":{"applicationHumanReadableId":"IDOL2621T-T27980","applicationType":"New gTLD with Variants","primaryString":{"aLabel":"xn--kbt444f","uLabel":"官网"},"tldVariants":[{"aLabel":"xn--kbto70f","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:58.774Z"},"questionAndResponses":{"applicationHumanReadableId":"IDOL2621T-T27980","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":"Internet DotTrademark Organisation Limited","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":"Private Limited Company/Body Corporate","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":"Hong Kong, China","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://www.trademarkdomain.com/","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":"The applying entity is an existing registry operator for the TLDs .xn--czr694b and .xn--imr513n.\nThe applying entity (Internet DotTrademark Organisation Limited, Hong-Kong SAR) and ShangYu Global Technology Co., Ltd. are entities subject to the same ultimate controlling party. Both entities are ultimately controlled by the same natural-person controller through an intermediate Cayman Islands holding company.\nShangYu Global Technology Co., Ltd. (IANA ID 3813) is an ICANN-accredited registrar. Jiang Yu Liang Cai Technology Company Limited, a wholly-owned subsidiary of ShangYu Global Technology Co., Ltd., acts as the registry operator for the delegated gTLD .xn--otu796d.\nThere is no direct shareholding between the Hong Kong-based applicant entity and either the accredited registrar or its registry operator subsidiary. Ultimate control is exercised via the top-level Cayman Islands holding platform.","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":"13521738308","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":"sunxuejie@tdnnic.org","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":20,"questionText":"AGB Q20. Address Line 1","instructions":"Enter the street address (no PO Box).","responseText":"Rm 1502, Building 7, No. 9 Shouti South Road, Haidian District","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":22,"questionText":"AGB Q22. Locality","instructions":"Enter the city, village, municipality, etc.","responseText":"Beijing","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":"Beijing","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":"100037","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":"DotTrademark Holding Limited","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":"Business Company Limited by Shares/Body Corporate","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":"British Virgin Islands","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":"DotTrademark Holding Group","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":"Exempted Company Limited by Shares/Body Corporate","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":"Cayman Islands","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":"Xiongwei Huang","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB 105. List all officers & partners of the applying entity.","instructions":"","responseText":"Xiongwei Huang, Yangyi Wu","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB 106. List all Material Shareholders","instructions":"","responseText":"DotTrademark Holding Limited","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB 107. List Individuals with Executive Responsibility","instructions":"","responseText":"Xiongwei Huang","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB 108. Disclose Ultimate Control of applying entity","instructions":"","responseText":"Xiongwei Huang","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":"official website, the authorised official web portal for an enterprise, organisation or brand.","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":"/ku̯an˥˥ wɑŋ˨˩˦/","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":"Mission and Purpose of the 官网 gTLD\nThe IDN gTLD \"官网\" (Chinese for \"official website\") is a purpose-driven, Chinese-script generic top-level domain created to serve as a certified namespace for verified official digital presences worldwide. Its mission is to serve the global Chinese-speaking community by providing a trusted digital identity layer. The structural integrity and eligibility policies of the 官网 TLD aim to ensure that hosted platforms represent authenticated, authorized websites, thereby protecting consumers from phishing, counterfeit sites, and deceptive online fraud.\nTarget Registrants\nThe 官网 TLD is accessible to legally established businesses, government agencies, non-profit organizations, educational institutions, and individuals operating verified digital platforms. All registrants must comply with mandatory third-party validation procedures, proving legitimate entitlement to or authorization of the corresponding brand, trade name, or legal entity name. This mechanism ensures that every active 官网 domain represents a genuine official presence, ranging from multinational corporations to local community groups.\nTarget Users\nPrimary users are Chinese-speaking consumers worldwide seeking safe, unambiguous access to official websites for purchases, professional services, information, or government transactions. By navigating to a domain such as brand.官网, users can confidently rely on its authenticity as an official channel, significantly reducing risks of financial loss, identity theft, and counterfeit goods. Secondary users include the registrants themselves, who gain enhanced brand credibility, heightened consumer confidence, and a distinct competitive advantage through a verified \"official website\" identifier, ultimately boosting customer retention and user conversion.\nActivities to Fulfill the Mission\n1.\tRigorous Verification Framework: Develop and enforce an objective registration policy requiring independent third-party validation of legal identity, trademark rights, or official authorizations, leveraging strategic partnerships with accredited certification and registration authorities.\n2.\tPublic Awareness Campaigns: Collaborate with consumer rights protection organizations, cybersecurity bodies, and global Chinese-language media to promote 官网 as a recognizable seal of digital authenticity, educating internet users on utilizing the TLD to mitigate online scams.\n3.\tSecurity Best Practices: Provide registrants with standardized implementation guidelines for DNSSEC, HTTPS deployment, and advanced anti-phishing technologies to maintain the long-term integrity and trustworthiness of the certified namespace.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":1,"questionText":"AGB Q116. Applied-for Primary String (ASCII Label)","instructions":"","responseText":"xn--kbt444f","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+5B98 U+7F51","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":"New 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":"official website, the authorised official web portal for an enterprise, organisation or brand.","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":"The primary string 官网 (guān wǎng) and its variant string 官網 (guān wǎng) are identical in meaning, pronunciation, and semantic function within the global Chinese speaking user community. They represent the exact same concept: “official website”—a trusted, authoritative online presence of an entity (government, enterprise, institution, or organization).\n\nWhy the User Community Treats Them as the Same\n1.\tLinguistic & Orthographic Equivalence\no\tBoth strings share the identical pronunciation /ku̯än⁵⁵ wɑŋ²¹⁴⁻²¹⁽⁴⁾/ (guān wǎng) in Mandarin Chinese.\no\tThey are simplified traditional character variants of the same lexical item, recognized as equivalent in all Chinese language standards (e.g., CDNC IDN tables, Unicode, and ICANN RZ LGR for Chinese).\no\tThe Chinese script community universally accepts simplified traditional pairs as interchangeable for the same meaning.\n2.\tUser Expectation & Practical Use\no\tChinese Internet users (in mainland China, Hong Kong, Macau, Taiwan, Singapore, and global diaspora) automatically interpret 官网 and 官網 as referring to the same authoritative namespace.\no\tNo semantic distinction exists between the two strings; both signal “official website” with identical trust and recognition cues.\no\tThe variant exists solely to accommodate regional script preferences (simplified in mainland China; traditional in Hong Kong, Macau, Taiwan, etc.) while preserving the core meaning.\n3.\tICANN & IDN Framework Recognition\no\tUnder ICANN’s IDN variant rules and Chinese LGR guidelines, simplified traditional character pairs like 官网 / 官網 are formally classified as equivalent variant strings with identical semantic intent.\no\tThe Chinese Domain Name Consortium (CDNC) and ICANN’s Chinese script community explicitly validate such pairs as “same meaning variants” for IDN deployment.\n________________________________________\nThree Bona Fide Real World Examples\nThese examples demonstrate actual, widespread use where 官网 and 官網 are treated as interchangeable, equivalent identifiers for official websites:\nExample 1: Government & Public Institution Usage\n•\tPrimary: 中华人民共和国外交部官网 (Ministry of Foreign Affairs, PRC Official Website)\n•\tVariant: 中華人民共和國外交部官網\n•\tContext: Both strings are used interchangeably across mainland China (simplified) and Hong Kong/Taiwan (traditional) government portals, press releases, and official communications. Users in all regions recognize both as referring to the same authoritative foreign ministry website.\nExample 2: Corporate Brand & Trademark Use\n•\tPrimary: 华为官网 (Huawei Official Website)\n•\tVariant: 華為官網\n•\tContext: Huawei uses both strings in global marketing, domain registrations, and user interfaces. Consumers and business partners in mainland China (simplified) and Taiwan/Hong Kong/Southeast Asia (traditional) instantly associate both with Huawei’s official online platform, with no perception of difference in meaning or authority. This is consistent with standard multinational brand practice for Chinese IDNs.\nExample 3: Media & Public Service Platforms\n•\tPrimary: 央视网官网 (CCTV Official Website)\n•\tVariant: 央視網官網\n•\tContext: China Central Television (CCTV) employs both strings in cross region content delivery. Viewers and users across all Chinese speaking regions accept both as the official, trusted domain for CCTV’s online services, with the variant only reflecting script preference—not a change in the website’s official status or identity.\n________________________________________\nIn summary, the global Chinese user community unambiguously regards 官网 and 官網 as the same string in meaning and function, with the variant serving only regional script accessibility while preserving the core purpose of identifying official websites.","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":"The variant string 官網 provides critical linguistic, regional, and usability benefits by supporting the traditional Chinese writing system, while maintaining the same semantic meaning of “official website” as the primary string 官网. This variant ensures that Chinese speaking users who read and write in traditional characters can easily recognize, trust, and register the authoritative label for official websites, without confusion or barriers caused by script differences. The introduction of the variant enhances inclusivity, improves user experience, strengthens online trust, and reduces the risk of misregistration or user confusion across different Chinese speaking regions.\nBeneficiary user communities include:\n•\tInternet users in regions using traditional Chinese, including Taiwan, Hong Kong, Macau, and related overseas communities.\n•\tEnterprises, brands, and institutions operating in traditional Chinese markets.\n•\tGovernments, public institutions, and media agencies publishing content in traditional Chinese.\n•\tGlobal Chinese users, registrars, and Internet service providers seeking consistent and authoritative “official website” identifiers across both simplified and traditional Chinese environments.\n1. Why One Label Is Insufficient and Multiple Labels Are Necessary\nA single label is insufficient because simplified and traditional Chinese are two distinct but equivalent writing systems used across separate major user communities, with strong regional, linguistic, and cultural expectations.\n•\tThe primary string 官网 is optimized for regions using simplified Chinese.\n•\tThe variant string 官網 is required to serve regions using traditional Chinese.\nUsing only one script would create significant user barriers: users would fail to recognize the string in their native writing system, reducing usability, credibility, and adoption. Cultural and linguistic drivers demand both forms to ensure equal access, clarity, and authenticity for all Chinese speaking users. The two strings are necessary to fulfill regional language practices and ensure the “official website” meaning is universally understood across the entire Chinese speaking Internet community.\n\n2. User Communities Served by Primary and Variant TLDs\nUser Community for Primary String 官网 (Simplified Chinese)\n•\tMainland China users, enterprises, governments, and institutions.\n•\tGlobal users and organizations that use simplified Chinese in their digital services.\nUser Community for Variant String 官網 (Traditional Chinese)\n•\tUsers, businesses, and organizations in Taiwan, Hong Kong, Macau.\n•\tTraditional Chinese speaking communities in Southeast Asia and global overseas regions.\n•\tInstitutions and brands operating multilingual / multi script Chinese websites.\n3. How User Needs Are Reflected in IDN Table Design\nThe IDN tables for the primary string 官网 and variant string 官網 are structurally consistent and semantically aligned, reflecting shared user needs for a secure, authoritative “official website” namespace. At the same time, the tables support the separate simplified and traditional character forms to match regional script preferences.\n•\tSimilarities: Both strings share identical meaning, pronunciation, purpose, and registration policies. The IDN tables enforce the same valid character set structure, variant logic, and community based usage rules to preserve the authoritative identity of the “official website” label.\n•\tDifferences: The IDN tables separately encode the simplified character 网 and traditional character 網 to comply with Unicode standards, ICANN LGR principles, and regional script conventions.\nThis design ensures that:\n•\tUser trust and recognition are preserved in each region.\n•\tBoth communities receive a native script label that matches their linguistic habits.\n•\tThe overall mission, security, and authority of the gTLD are maintained consistently across both primary and variant strings.","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":"Steps to Minimize Operational and Management Complexities\n1. Unified Registry Backend System & Single EPP Interface\nThe applicant will operate 官网 and 官網 on a single, shared technical platform with a unified EPP server interface.\n•\tA single set of EPP commands and response codes will apply to both TLDs.\n•\tRegistrars will not need separate API integrations, separate connections, or separate technical configurations.\n•\tDomain lifecycle operations (create, renew, transfer, delete, update) will behave identically across both strings.\nThis reduces integration complexity for registrars.\n2. Consistent Policies & Eligibility Rules Across Both TLDs\nThe applicant will maintain identical registration policies, eligibility requirements, and terms of service for 官网 and 官網.\n•\tSame registration eligibility (official institutions, enterprises, government bodies, verified organizations).\n•\tSame registration periods, renewal rules, transfer policies, and dispute resolution mechanisms.\n•\tSame sunrise, land rush, and general availability periods.\nRegistrants and resellers will not need to learn or comply with divergent rules between the primary and variant TLD.\n3. Unified Pricing Structure\nPricing will be fully aligned between 官网 and 官網，including:\n•\tIdentical wholesale pricing for registrars.\n•\tIdentical premium domain naming conventions and pricing logic.\n•\tIdentical fees for registration, renewal, redemption, and restore.\nThis eliminates financial complexity and removes pricing confusion across the two strings.\n4. Shared WHOIS / RDAP Service & Data Model\nA unified query service will be deployed for both TLDs:\n•\tSame data fields, output format, and access mechanisms in WHOIS and RDAP.\n•\tConsistent data display, privacy controls, and query rate limits.\nUsers, registrars, and third party services will experience no functional difference in querying domains under either TLD.\n5. Synchronized Abuse Management & Compliance Processes\nAbuse handling, takedown procedures, suspension policies, and compliance reviews will be identical:\n•\tSame reporting channels.\n•\tSame review timelines and decision criteria.\n•\tSame escalation and notification workflows.\nThis ensures registrars and resellers follow a single compliance playbook for both TLDs.\n6. Unified Registrar Accreditation & Onboarding\nAccreditation will cover both TLDs under a single agreement.\n•\tOne application, one review, one accreditation status.\n•\tOne set of training materials, documentation, and support portal.\nNo separate onboarding or contractual arrangements are required for the variant string.\n7. Simplified Reseller & Registrant Experience\nFrom the perspective of registrants and resellers:\n•\tBoth TLDs represent the same semantic meaning (“official website”).\n•\tBoth follow identical validation and authentication steps.\n•\tDashboard interfaces, management tools, and customer support will treat the two TLDs as equivalent offerings.\nThis minimizes user confusion and supports intuitive adoption.\n8. Dedicated Support & Documentation Framework\nUnified technical documentation, FAQs, guides, and support services will be maintained:\n•\tSingle knowledge base covering both TLDs.\n•\tSingle support contact for technical and policy issues.\n•\tRegular joint notifications for system maintenance, policy updates, or operational changes.\n9. Monitoring & Continuous Improvement\nThe applicant will regularly monitor registrar feedback and operational metrics to identify and eliminate unnecessary frictions. Any future system updates or policy changes will be applied consistently to both TLDs to preserve operational simplicity.\nCommitment\nAll measures described above constitute binding commitments. The applicant will include these obligations in the Registry Agreement to ensure long term operational consistency, reduce complexity, and protect registrars, resellers, and registrants from unnecessary burden related to the variant string.\n","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--kbto70f","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+5B98 U+7DB2","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":"Yes","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":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}]}]}}