Instantané du 8 octobre 2026 · ICANN APS, champs publics

Candidatures / .网络 / CINI2622T-T81530 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.网络

IDNActive

A-label xn--io0a7i Q116

China Internet Network Information Center (CNNIC), CN Q1·Q25

Fiche ICANN ↗

Opérateur de registre, bureau d'enregistrement ou affilié existant, tel que déclaré : Q12

CNNIC is the registry of .xn--55qx5d and .xn--io0a7i.

§ 1 — Sens de la chaîne Q118·Q120

The TLD means “network” refers to a collection of hardware components and computers interconnected through communication channels, allowing them to share resources and information.

wɑŋluo

§ 2 — Mission et objet Q133

CNNIC is applying for the Chinese variant top-level domains (TLDs) of “.网络” to form, together with the existing “.网络”, a unified and trustworthy service system for global Chinese-language users. Both share identical semantics and public interest goals; the only difference lies in simplified and traditional script writing conventions. The variants aim to enable users to write, recognize, and remember domain names in their daily script, thereby preventing access barriers, confusion, or split registration. The existing “.网络” has been operated by CNNIC since 2014. Its mission is to serve the public interest with security, reliability, efficiency, and innovation, offering a borderless Chinese identifier for Internet and digital services. It serves enterprises, institutions, platforms, innovators, and individuals worldwide. Its goals are to lower language barriers for non-Latin-script users, provide intuitive and memorable online gateways, accurately represent Chinese names in the DNS, and promote universal acceptance of Chinese-language websites, emails, and intelligent applications, while safeguarding rights, data, and stability. CNNIC operates a full registry system covering registration, resolution, DNSSEC, data escrow, business continuity, abuse handling, and rights protection, and has long been engaged in Chinese IDN standards, variant management, and universal acceptance efforts. The variant TLDs extend this mission without creating new markets, offering an equivalent experience to variant script users. Intended registrants include organizations and individuals using the variant script, particularly in Hong Kong, Macao, Taiwan, and overseas Chinese communities, as well as those seeking unified brand protection across scripts. Intended users are those reading or using the variant script, or switching between Chinese writing systems. Authorizing variants reduces input errors, confusion, and semantic fragmentation, and advances universal acceptance across devices and platforms. CNNIC will govern “.网络” and its variants as a unified set: a single registry operator, backend provider, security framework, and IDN table, with single registrant control, variant label association, lifecycle synchronization, and conflict prevention. Clear guidelines and system upgrades will be provided; testing and monitoring will be continuous. On the application side, CNNIC will partner with registrars, browsers, email providers, and search providers for universal acceptance testing, technical training, and demonstrations targeting public services, SMEs, education, and digital brands. User feedback will be regularly collected and evaluated to refine policies and services. Sustainability rests on lasting linguistic demand: China had 1.125 billion Internet users by the end of 2025, and simplified and traditional scripts will coexist long-term. CNNIC’s existing infrastructure and expertise from operating “.CN”, “.中国”, and “.网络” allow for cost-efficient operation. The variant TLDs will be integrated into long-term budgeting, risk management, emergency response, and compliance systems. With reasonable, non-discriminatory policies, stable registrar channels, and reserved resources, critical functions such as DNS, DNSSEC, and data escrow will be maintained even under slower growth. Through unified governance, continuous technical improvement, ecosystem collaboration, user needs assessment, and full compliance with ICANN policies and the Registry Agreement, “.网络” and its variants will endure as sustainable infrastructure for global Chinese-language communities.

§ 3 — Engagements et sauvegardes Q164–Q188

Confiance accrue, risque pour le consommateur, secteur réglementé, déclarations à l'État, préjudice, fonction régalienne Q164–Q169Non à chacune
PIC de sauvegarde volontaires Q170·Q171Aucun · 90 candidatures de la ronde en proposent
Registry Voluntary Commitments Q172·Q173Aucun · 5 en proposent
Exemption du Code de conduite demandée Q185·Q188Non

§ 4 — Toutes les autres réponses publiées

Toutes les autres réponses que l'ICANN a publiées pour cette candidature, dans l'ordre du formulaire. Les coordonnées (Q17–Q24) sont laissées à la fiche ICANN.

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

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.

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

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.

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

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.

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

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.

Q119Script of String

Script of String

Chinese (Han)

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

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

Q117.1Applied-for Primary String (U-Label)

Applied-for Primary String (U-Label)

网络

Q117.2Applied-for Primary String (Code Points)

Applied-for Primary String (Code Points)

U+7F51 U+7EDC

Q124Script of Variant String

Script of Variant String

Chinese (Han)

Q125Is 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?

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

Existing TLD

Q126What is the meaning/definition of the variant string?

What is the meaning/definition of the variant string?

The TLD means “network” refers to a collection of hardware components and computers interconnected through communication channels, allowing them to share resources and information.

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

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

“.网络” and the applied-for variant strings represent the same Chinese word through combinations of corresponding Simplified Chinese characters and their variant forms. Replacing either one of the characters, or both characters simultaneously, does not alter the pronunciation, lexical identity, or meaning of the word. All of these strings mean “network,” including computer networks, telecommunications networks, the Internet, and related digital networks. The following bona fide examples demonstrate that the relevant Chinese-language user communities regard the Simplified and variant forms of the same Chinese word as different written representations of the same concept, rather than as independent concepts. Example 1. CNNIC’s Existing Operation of “.中国/.中國” CNNIC currently operates both the Simplified Chinese string “.中国” and its corresponding Traditional Chinese string “.中國” as different forms of the same Chinese country-code top-level domain. CNNIC’s official domain name service materials present “.中国/.中國” together and describe them collectively as the Chinese-language top-level domain representing China. This provides a directly relevant, real-world DNS precedent demonstrating that registrants and users regard Simplified and Traditional Chinese character forms as equivalent representations of the same domain name identifier. Example 2. Official Government Use of “网络” and “網絡” Government authorities in mainland China use the Simplified form “网络” in official expressions such as “网络安全” and in the name of the Central Cyberspace Affairs Commission. Information-security services of the Government of the Hong Kong Special Administrative Region use the Traditional form “網絡” in corresponding expressions such as “網絡安全,” “網絡保安,” “網絡威脅,” and “無線網絡.” In both regions, “网络” and “網絡” refer to the same underlying concept: an interconnected communications or computer network. The difference reflects the writing conventions adopted by the relevant user communities and does not indicate any difference in meaning or category of service. Example 3. Commercial Use by Cisco. Cisco’s official Simplified Chinese materials for mainland China use “网络” to describe its networking products and services, including enterprise networks, wireless networks, data-center networks, and network security. Cisco’s official Traditional Chinese website for Hong Kong uses “網絡” to describe the corresponding commercial field and product categories, including “無線網絡” and “網絡軟體.” Cisco markets the same types of networking technologies to different Chinese-language user communities. Its localized commercial use demonstrates that “网络” and “網絡” are corresponding market expressions for the same products and services, rather than separate trademarks or concepts. These examples demonstrate consistent treatment of the strings across the Domain Name System, public administration, and commercial markets. The relevant Chinese-language user communities understand the variant labels as different written forms of the same Chinese word. They have the same pronunciation and meaning and do not possess separate market, geographic, or service-category significance. Accordingly, treating these strings as a coordinated variant set reflects actual Chinese-language usage, helps reduce user confusion, and prevents semantically equivalent identifiers from being controlled by unrelated parties.

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

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

The introduction of the applied-for variant strings will provide linguistic, accessibility, consumer-protection, and operational benefits to Chinese-language communities worldwide. The variants will allow users to recognize, enter, remember, and use the “.网络” top-level domain in the Chinese character forms familiar to them, while preserving a unified identity and namespace across the primary and variant strings. The principal beneficiaries will be users who primarily read and write Traditional Chinese, including users in Hong Kong, Macao, Taiwan, and Chinese-speaking communities worldwide. These users commonly recognize “網絡” as the form corresponding to the Simplified Chinese word “网络.” Delegation of the variants will allow them to use a familiar written form without first converting it into another Chinese writing form. Registrants will benefit from the ability to maintain a consistent Chinese-language identity across the primary and variant strings. Beneficiaries include businesses, public institutions, schools, universities, cultural and media organizations, social organizations, Internet platforms, and providers of digital content, telecommunications, networking, and other online services. They will be able to present their names, brands, products, and services in the forms normally used by their audiences without creating separate or conflicting identities. Existing and future “.网络” registrants will receive particular protection. Coordinated variant management will reduce the risk that an equivalent form of a registered name could be allocated to an unrelated party. Under applicable ICANN requirements and CNNIC policies, related labels will be managed through same-entity control, coordinated variant relationships, and consistent registration data and lifecycle arrangements. This will help protect registrants’ identities and legitimate interests while reducing opportunities for impersonation, phishing, misdirection, and user confusion. End users will benefit from greater confidence that equivalent written forms lead to services controlled by the same registrant rather than to unrelated destinations. This is particularly important for public services, financial and commercial services, education, healthcare information, and other applications in which users rely on a domain name to identify the source of information or services. A coordinated variant set will therefore improve clarity, navigation consistency, and consumer trust without creating a separate market meaning or service category for each string. The variants will also support a more inclusive and multilingual Internet by allowing Chinese-language users to use their preferred writing conventions within the DNS. They will improve user choice and provide the DNS-level foundation for wider Universal Acceptance of Chinese domain names across browsers, email systems, mobile applications, search platforms, and other software and devices. Registrars, resellers, software developers, browser and email providers, search platforms, mobile application providers, and other ecosystem participants will benefit from a clearly defined and consistently managed variant set. CNNIC will apply coordinated IDN tables, registration policies, technical systems, and operational procedures to “.网络” and its variants, creating a predictable framework for registration, resolution, display, validation, customer support, and Universal Acceptance testing. Overall, the applied-for variants will benefit both Traditional Chinese users and Simplified Chinese users. Their coordinated introduction will improve linguistic accessibility, user choice, identity protection, navigation consistency, consumer trust, and the practical utility of “.网络” as long-term Internet infrastructure for Chinese-language communities worldwide.

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

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.

CNNIC will manage “.网络” and the applied-for variant TLDs as a coordinated variant set. All strings will be operated by the same registry operator and an approved back-end Registry Service Provider, using shared DNS, DNSSEC, EPP, RDAP, data escrow, security, monitoring, business continuity, and support systems. By using a unified platform, registrars will not need to connect separately to different systems or maintain multiple databases and operational processes. At the second level, CNNIC will apply same-entity control to ensure that corresponding labels under “.网络” and its variant TLDs are not allocated to unrelated registrants. Related labels will be associated with the same registrant in the registry database and, where applicable, sponsored by the same registrar. Automated validation will prevent inconsistent allocations or transfers. CNNIC will not require registrants to activate all allocatable variant labels. Unactivated labels will remain unavailable for allocation to unrelated parties, while registrants may choose which forms to activate based on the needs of their users. Fees will be transparent, and the strings will be treated as a coordinated variant set rather than as independent namespaces. Changes involving registrant identity or control will be validated across the entire variant set. Security measures, dispute resolution decisions, court orders, and confirmed domain name abuse cases will be assessed at the variant-set level and, where necessary, addressed consistently, subject to applicable procedures and policies. Before general availability, CNNIC will work with the back-end Registry Service Provider and participating registrars to complete testing of systems, security, billing, RDAP, data escrow, and domain name lifecycle management. Existing “.网络” registrations will be mapped to their related variant labels and protected against allocation to unrelated parties. Eligible registrants will receive clear advance notice and may activate relevant variants through an orderly opt-in process. Subject to applicable requirements, they will not be required to resubmit verification information already held by their registrar. After launch, CNNIC will continue to monitor transaction failures, support requests, data inconsistencies, abuse reports, registrar feedback, and Universal Acceptance issues. CNNIC will establish and maintain change-control procedures, provide advance implementation notice when policies or systems change, and promptly update relevant documentation and training materials. Through these measures, CNNIC will provide registrars, resellers, and registrants with a clear, unified, and predictable operational model while maintaining the security, stability, and integrity of the entire variant set.

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

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

Q122Applied-for Variant(s)

Applied-for Variant(s)

xn--od0alg

Q123.1Variant String (U-Label)

Variant String (U-Label)

網絡

Q123.2Variant String (Code Points)

Variant String (Code Points)

U+7DB2 U+7D61

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

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

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

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