.官网

Q2.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO, and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE) of the applying entity, the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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).

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Script of String

Chinese (Han)

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

true

Applied-for Primary String (U-Label)

官网

Applied-for Primary String (Code Points)

U+5B98 U+7F51

Script of Variant String

Chinese (Han)

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

New TLD

What is the meaning/definition of the variant string?

official website, the authorised official web portal for an enterprise, organisation or brand.

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

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).

Why the User Community Treats Them as the Same 1. Linguistic & Orthographic Equivalence o Both strings share the identical pronunciation /ku̯än⁵⁵ wɑŋ²¹⁴⁻²¹⁽⁴⁾/ (guān wǎng) in Mandarin Chinese. o They 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). o The Chinese script community universally accepts simplified traditional pairs as interchangeable for the same meaning. 2. User Expectation & Practical Use o Chinese Internet users (in mainland China, Hong Kong, Macau, Taiwan, Singapore, and global diaspora) automatically interpret 官网 and 官網 as referring to the same authoritative namespace. o No semantic distinction exists between the two strings; both signal “official website” with identical trust and recognition cues. o The variant exists solely to accommodate regional script preferences (simplified in mainland China; traditional in Hong Kong, Macau, Taiwan, etc.) while preserving the core meaning. 3. ICANN & IDN Framework Recognition o Under 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. o The Chinese Domain Name Consortium (CDNC) and ICANN’s Chinese script community explicitly validate such pairs as “same meaning variants” for IDN deployment. ________________________________________ Three Bona Fide Real World Examples These examples demonstrate actual, widespread use where 官网 and 官網 are treated as interchangeable, equivalent identifiers for official websites: Example 1: Government & Public Institution Usage • Primary: 中华人民共和国外交部官网 (Ministry of Foreign Affairs, PRC Official Website) • Variant: 中華人民共和國外交部官網 • Context: 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. Example 2: Corporate Brand & Trademark Use • Primary: 华为官网 (Huawei Official Website) • Variant: 華為官網 • Context: 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. Example 3: Media & Public Service Platforms • Primary: 央视网官网 (CCTV Official Website) • Variant: 央視網官網 • Context: 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. ________________________________________ In 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.

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

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. Beneficiary user communities include: • Internet users in regions using traditional Chinese, including Taiwan, Hong Kong, Macau, and related overseas communities. • Enterprises, brands, and institutions operating in traditional Chinese markets. • Governments, public institutions, and media agencies publishing content in traditional Chinese. • Global Chinese users, registrars, and Internet service providers seeking consistent and authoritative “official website” identifiers across both simplified and traditional Chinese environments. 1. Why One Label Is Insufficient and Multiple Labels Are Necessary A 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. • The primary string 官网 is optimized for regions using simplified Chinese. • The variant string 官網 is required to serve regions using traditional Chinese. Using 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.

2. User Communities Served by Primary and Variant TLDs User Community for Primary String 官网 (Simplified Chinese) • Mainland China users, enterprises, governments, and institutions. • Global users and organizations that use simplified Chinese in their digital services. User Community for Variant String 官網 (Traditional Chinese) • Users, businesses, and organizations in Taiwan, Hong Kong, Macau. • Traditional Chinese speaking communities in Southeast Asia and global overseas regions. • Institutions and brands operating multilingual / multi script Chinese websites. 3. How User Needs Are Reflected in IDN Table Design The 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. • Similarities: 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. • Differences: The IDN tables separately encode the simplified character 网 and traditional character 網 to comply with Unicode standards, ICANN LGR principles, and regional script conventions. This design ensures that: • User trust and recognition are preserved in each region. • Both communities receive a native script label that matches their linguistic habits. • The overall mission, security, and authority of the gTLD are maintained consistently across both primary and variant strings.

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.

Steps to Minimize Operational and Management Complexities 1. Unified Registry Backend System & Single EPP Interface The applicant will operate 官网 and 官網 on a single, shared technical platform with a unified EPP server interface. • A single set of EPP commands and response codes will apply to both TLDs. • Registrars will not need separate API integrations, separate connections, or separate technical configurations. • Domain lifecycle operations (create, renew, transfer, delete, update) will behave identically across both strings. This reduces integration complexity for registrars. 2. Consistent Policies & Eligibility Rules Across Both TLDs The applicant will maintain identical registration policies, eligibility requirements, and terms of service for 官网 and 官網. • Same registration eligibility (official institutions, enterprises, government bodies, verified organizations). • Same registration periods, renewal rules, transfer policies, and dispute resolution mechanisms. • Same sunrise, land rush, and general availability periods. Registrants and resellers will not need to learn or comply with divergent rules between the primary and variant TLD. 3. Unified Pricing Structure Pricing will be fully aligned between 官网 and 官網，including: • Identical wholesale pricing for registrars. • Identical premium domain naming conventions and pricing logic. • Identical fees for registration, renewal, redemption, and restore. This eliminates financial complexity and removes pricing confusion across the two strings. 4. Shared WHOIS / RDAP Service & Data Model A unified query service will be deployed for both TLDs: • Same data fields, output format, and access mechanisms in WHOIS and RDAP. • Consistent data display, privacy controls, and query rate limits. Users, registrars, and third party services will experience no functional difference in querying domains under either TLD. 5. Synchronized Abuse Management & Compliance Processes Abuse handling, takedown procedures, suspension policies, and compliance reviews will be identical: • Same reporting channels. • Same review timelines and decision criteria. • Same escalation and notification workflows. This ensures registrars and resellers follow a single compliance playbook for both TLDs. 6. Unified Registrar Accreditation & Onboarding Accreditation will cover both TLDs under a single agreement. • One application, one review, one accreditation status. • One set of training materials, documentation, and support portal. No separate onboarding or contractual arrangements are required for the variant string. 7. Simplified Reseller & Registrant Experience From the perspective of registrants and resellers: • Both TLDs represent the same semantic meaning (“official website”). • Both follow identical validation and authentication steps. • Dashboard interfaces, management tools, and customer support will treat the two TLDs as equivalent offerings. This minimizes user confusion and supports intuitive adoption. 8. Dedicated Support & Documentation Framework Unified technical documentation, FAQs, guides, and support services will be maintained: • Single knowledge base covering both TLDs. • Single support contact for technical and policy issues. • Regular joint notifications for system maintenance, policy updates, or operational changes. 9. Monitoring & Continuous Improvement The 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. Commitment All 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.

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

true

Applied-for Variant(s)

xn--kbto70f

Variant String (U-Label)

官網

Variant String (Code Points)

U+5B98 U+7DB2

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

true

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

true