Application Details
Last published on: 7 October 2026 at 15:35 UTC
Application Responses
Section: Applying Entity Information
This question set collects information regarding the legal entity that would enter into a Registry Agreement with ICANN upon successful completion of all relevant application processes. The information collected is intended to be used for background screening.
Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.
China Internet Network Information Center (CNNIC)
Provide the name under which the applying entity is doing business, if different from the full legal name answered in Question 1. Such a name must be registered with appropriate local jurisdiction or public authority.
China Internet Network Information Center
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.
Public Institution
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.
China
Provide the website URL of the applying entity, if available.
https://www.cnnic.cn
1. Choose Yes or No. 2. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement).
true
1. Specify if the applying entity is an existing registry operator, ICANN accredited registrar, and/or an Affiliate of a registry operator and/or registrar. 2. If the applying entity is an Affiliate, provide the details of such Affiliate relationship, including the name of the affiliated registry operator and/or registrar. 3. If the applying entity is an ICANN accredited registrar, specify the registrar ID number.
CNNIC is the registry of .xn--55qx5d and .xn--io0a7i.
Choose Yes or No.
true
1. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement). 2. Provide the type of the provider and the name of the applicable entity of which the applying entity is an Affiliate.
CNNIC is an ICANN-approved data escrow agent, an emergency back-end registry operator.
86
Provide the primary business phone number without including the country code.
01058813000
Provide the primary business email address of the applying entity.
service@cnnic.cn
Enter the street address (no PO Box).
Building 4, No.9 Beijing Auto Museum West Road, Fengtai District, Beijing
Enter the city, village, municipality, etc.
beijing
Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.
Fengtai District, Beijing
1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.
100070
CN
Section: Applying Entity Background and Organization
This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.
Yulin Liu, Xiao Zhang, Qiang Li, Jian Lv, Lidong Wang
Section: Self-Certification
Provide a single document for Self-Certification question Q2.2-1. The document must include only the SC2.2-1.1, SC2.2-1.2, or SC2.2-1.3 statements. Do not modify any of the Self-Certification statements.
1. Provide a single document for Self-Certification question Q2.2-1. 2. The document must include only the SC2.2-1.1 through SC2.2-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC2.2-1.1 through SC2.2-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC2.2-1.1 through SC2.2-1.3 statements.
Section: Operational/Planning
The document for Q2.3.1 must be a PDF. The document for Q2.3-2 must be an Excel (.xlsx) file.
The document for Q2.3-1 must be a PDF.
Section: Security Policy and Planning
Provide a single document for Self-Certification question AGB Q220, Q5.1-1. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements.
1. Provide a single document for Self-Certification question Q5.1-1. 2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1.1-3 statements.
Section: DNS Abuse
Provide a single document for Self-Certification question AGB Q221, Q5.2-1. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.
1. Provide a single document for Self-Certification question Q5.2-1. 2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.
Section: Primary String
This question set collects basic information regarding the string that is being applied for (for example, a-label, meaning, script). If the applying entity opts to designate a replacement string, it must answer the same set of questions for the replacement string from the AGB Question Set 5 on.
xn--io0a7i
网络
U+7F51 U+7EDC
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"
The TLD means “network” refers to a collection of hardware components and computers interconnected through communication channels, allowing them to share resources and information.
If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)
Chinese (Han)
Provide a representation of the string according to the International Phonetic Alphabet.
wɑŋluo
Confirm the statement using a checkbox.
true
1. Describe the mission and purpose of the applied-for gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 1a. If applying for a variant of an existing gTLD, please also describe the mission and purpose of the existing gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 2. Explain how this purpose is sustainable over time.
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.
Section: Variant String(s)
This question set collects basic information regarding any variants of the primary string (AGB Question Set 5) that are being applied for. Loop over multiple variant strings if the string has multiple variant strings.
xn--od0alg
網絡
U+7DB2 U+7D61
Provide the script of the variant string (both in English and as referenced by the RZ-LGR/ISO 15924)
Chinese (Han)
Select an option.
Existing TLD
Provide the meaning or intended meaning (for non-dictionary words) of each of the applied-for variant string(s), including sources. If there is no literal meaning in English (for example, a brand name or a proper noun without a translation) simply state "no English Translation/Meaning".
The TLD means “network” refers to a collection of hardware components and computers interconnected through communication channels, allowing them to share resources and information.
Provide at least three bona-fide examples to support the explanation. (for example, evidence of trademark use by showing real world use cases).
“.网络” 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.
1. Applying entities shall explain why one label is insufficient and two or more labels are necessary to satisfy regional, linguistic, or cultural drivers. 2. Identify the user communities served by primary and for each of the variant TLDs. 3. How are these user community needs reflected by differences or similarities in the design of the IDN tables offered for the primary and the each variant TLD.
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.
Provide steps and descriptions that adequately demonstrate all defined criteria are met. See Section 7.6 Variant String Evaluation and Section 3.1.9.2.1 Application Submission of New Primary IDN and its Variant Strings. Notes: Commitments made by an applicant to minimize the noted operational and management complexities will form the basis of contractual requirements to be included in the applicable Registry Agreement.
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.
Confirm the statement using the checkbox.
true
Section: Safeguard Identification
This question set collects information related to determining whether certain Safeguard Public Interest Commitments (Safeguard PICs) are required for the applied-for gTLD string. See Section 7.8.2.3 Safeguard PICs. Answers to these questions will inform assessment by ICANN on whether and which Safeguard PICs must be incorporated in the applicable Registry Agreement (RA) if the string proceeds to delegation. The answers themselves will not automatically make such a determination.
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
Select Yes or No. Notes: 1. ICANN will evaluate whether an applied-for gTLD string requires one or more Safeguard Public Interest Commitments (Safeguard PICs) to be included in the Base RA). 2. In addition to the Mandatory Public Interest Commitments (PICs) that must be included in each Base RA, a subset of Base RAs must include Safeguard PICs based on ICANN’s Safeguard Assessment. See Section 7.8.2.3 Safeguard PICs. 3. Applying entities for TLDs that are not found to require Safeguard PICs can elect to add them to the applicable Base RAs voluntarily to, for example, further their business objectives, help address issues or concerns that are raised or could be raised with respect to their applications, or avoid the need for the evaluation and implementation of customized Registry Voluntary Commitment (RVC). See Section 7.8.3 Registry Voluntary Commitments (RVCs).
No
Section: Registry Voluntary Commitments (RVCs)
This question set collects information related to any Registry Voluntary Commitments (RVCs) that the applying entity is submitting. The decision to submit an RVC is typically voluntary, except for those recognized by ICANN to resolve an objection or to address GAC Consensus Advice. See Section 7.8.3 Registry Voluntary Commitments for more information.
1. Select Yes or No. 2. In addition to Safeguard Public Interest Commitments (PICs), an applying entity will be permitted to propose one or more Registry Voluntary Commitments (RVCs) to provide additional safeguards with regard to the registry operator’s operation of an applied-for gTLD string. See Section 7.8.3 Registry Voluntary Commitments (RVCs). 3. RVCs are separate from Community Registration Policies. See Section 7.8.3 Registry Voluntary Commitments (RVCs) and Section 7.8.4 Community Registration Policies for more information. If you are applying for a Community gTLD, please submit the Community Registration Policies by answering Questions 150-155. However, if you propose to include additional Registry Voluntary Commitments in the RA beyond the Community Registration Policies, you may answer "yes" and proceed to answer the following questions. 4. You are encouraged to consider whether there are other means, separate from including commitment(s) in the Base RA, that could be used to further your business objectives or help resolve any anticipated or actual issue(s) raised regarding the applied-for gTLD string or application. See Section 7.8.3 Registry Voluntary Commitments (RVCs). Notes: If you select “yes” to this question, you are required to pay the conditional Registry Commitments Evaluation fee, and commitments that are approved by ICANN will be included in Specification 11 of the applicable Base RA as specific voluntary public interest commitments as contractual obligations.
No
Section: Brand & Code of Conduct Exemptions
This question set collects information related to whether the applied-for gTLD string is a .Brand (see Section 7.3) or if the applying entity is seeking a Code of Conduct exemption (see Section 7.4).
Select Yes or No
No
This serves as an indication of intent to apply for an exemption to Specification 9 and that the applying entity is NOT requesting to be designated a .Brand TLD, pursuant to Specification 13.
No
Section: Additional Information and Supporting Materials
This question set collects any additional information that the applying entity would like to provide, including any supporting materials.
Section: Bona Fide Intent and Prohibited Communications
This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.
Confirm the statement using the checkbox.
true
Confirm the statement using the checkbox.
true