Snapshot of 8 October 2026 · ICANN APS, public fields

Applications / .中文网 / BTRT2633T-T38161 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.中文网

IDNActive

A-label xn--fiq228c5hs Q116

Beijing TLD Registry Technology Limited, CN Q1·Q25

Ultimately controlled by Infinitld (Beijing) Technology Co., Ltd., Infinitld (Beijing) Technology Co., Ltd. Q108 · ICANN record ↗

Existing registry operator, registrar or affiliate, as declared: Q12

Applying entity is an existing registry operator.

§ 1 — Meaning of the string Q118·Q120

website

/ʈʂʊŋ wən waŋ/

§ 2 — Mission and purpose Q133

Mission and Purpose The core mission of xn--fiq228c5hs(中文网) is to focus on developing Chinese top-level domain names that conform to the cultural and language habits of Chinese users, promote the comprehensive localization of the Chinese network, and enable global Chinese netizens to freely choose and use their native language to access the internet without barriers. It can serve as an important way to spread Chinese culture and demonstrate cultural confidence in cyberspace, playing a prominent role in identifying and effectively protecting the legitimate rights and intellectual property of users.

Expected registrant and user 1. Enterprise users (especially brand owners): including enterprises in China. 2. Government and public institutions: State agencies, public institutions, and other institutions used to build authoritative and trustworthy digital identities and provide government or public services. 3. Individual users and creators: including personal blogs, self media creators, etc., used to showcase unique personal brand and cultural positioning. 4. The vast number of Chinese netizens

Related activities that have been or will be carried out 1. Technical research and development and standard setting: Continuously committed to the development of international standards (such as IETF standards) and national standards, solving technical problems such as simplified and traditional Chinese equivalence and encoding resolution, and laying the technical foundation for the global interconnection of Chinese domain names. 2. Application environment optimization and popularization: Promote comprehensive compatibility and support for Chinese domain names in mainstream browsers, search engines, input methods, email, and AI models, and achieve barrier free use. 3. Collaborative protection of intellectual property rights: In response to national policies, promote the establishment of a "trademark+domain name" collaborative protection system for enterprises, incorporate Chinese domain names into the full chain management of enterprise intellectual property rights, and prevent malicious registration and infringement risks. 4. Build a benchmark for demonstration applications: Promote typical application cases, collaborate with various sectors to carry out science popularization and technical training, and explore long-term mechanisms. 5. Embrace AI and intelligent upgrading: Accelerate the deep integration of artificial intelligence models with the Chinese domain name system, and build Chinese domain names into "intelligent entrances" and trusted data sources that connect AI models with digital brands.

Sustainability analysis of the purpose With the full implementation of national and international standards for Chinese domain names, and the continuous improvement of the application environment, its stability as the bottom layer of the Internet infrastructure has been guaranteed, and it can develop healthily and sustainably at its own pace. With the development of the digital economy, Chinese domain names have transformed from early "cultural symbols" to key strategic assets for enterprises to build digital moats and optimize AI semantic retrieval. In the era of artificial intelligence, Chinese domain names are upgrading from static "digital doorplates" to dynamic "brand agents". Its natural semantic expression ability gives it an irreplaceable advantage in information retrieval and authoritative source determination of AI models, and this technological evolution endows it with long-term vitality and commercial value.

§ 3 — Commitments and safeguards Q164–Q188

More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169Yes to: more trustworthy (Q164), consumer risk if abused (Q165)
Voluntary Safeguard PICs Q170·Q171None · 90 applications in the round offer some
Registry Voluntary Commitments Q172·Q173None · 5 do
Code of Conduct exemption requested Q185·Q188No

§ 4 — All other published answers

Every other answer ICANN published for this application, in the order of the form. Contact details (Q17–Q24) are left to the ICANN record.

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.

Answered with a document. Attachments are not published by ICANN.

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

Answered with a document. Attachments are not published by ICANN.

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.

Answered with a document. Attachments are not published by ICANN.

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.

Answered with a document. Attachments are not published by ICANN.

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+4E2D U+6587 U+7F51

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?

website

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.

Chinese has both simplified and traditional characters. ’中文网‘(xn--fiq228c5hs) are simplified characters. ’中文網‘(xn--fiq228cl8q) is the traditional spelling of ’中文网‘(xn--fiq228c5hs) .

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

Benefits 1. Covering the markets of Hong Kong, Macao, Taiwan, and overseas Chinese, achieving global brand unity Traditional Chinese is the main writing habit of Chinese people in Hong Kong, Macau, Taiwan, and overseas. Registering traditional Chinese domain names can accurately cover the user groups in these regions, eliminate language barriers, and help businesses achieve a unified display of global brands. 2. Meet native language input habits, improve user experience and conversion rate Traditional Chinese domain names allow users familiar with traditional Chinese to access websites directly by entering their native language in the browser address bar without switching input methods. This seamless access experience can greatly reduce the internet barrier, improve user access efficiency and brand trust. 3. Gain the semantic advantage of search engine optimization (SEO) In the Chinese search engine ecosystem such as Baidu Search, domain names containing Chinese keywords have significant semantic advantages. When users search for traditional Chinese keywords, pages containing corresponding traditional Chinese characters in the URL often receive higher relevance ratings, resulting in higher rankings and click through rates in search results.

Who will benefit from it 1. Enterprises expanding their business in Greater China and overseas Traditional Chinese domain names are highly valuable digital assets for multinational corporations, e-commerce and service organizations that hope to deeply cultivate the Hong Kong, Macao and Taiwan markets or attract overseas Chinese customers. It not only intuitively reflects the legitimacy and localization sincerity of the enterprise, but also significantly improves conversion rates through offline advertising placement (such as QR code access). 2. Institutions that focus on intellectual property protection and brand defense Due to the visual differences between traditional and simplified Chinese characters, if not registered in a timely manner, the brand is highly susceptible to malicious registration by others. By registering a traditional Chinese domain name, enterprises can build a complete brand protection system of "simplified Chinese+traditional Chinese", avoiding endless domain name disputes and legal disputes in the later stage, and reducing the cost of rights protection. 3. Traditional Chinese users (netizens) The popularity of traditional Chinese domain names has broken the language barrier caused by pure English or simplified Chinese domain names. Hundreds of millions of netizens around the world who are accustomed to using traditional Chinese will be able to use their mother tongue to access the Internet more conveniently and safely, and enjoy a smoother online experience.

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.

1. Simplify the registration process using the "Simplified Chinese Equivalent Protection" mechanism At the domain name registration level, simplified and traditional equivalent protection mechanisms are adopted to avoid duplicate registration or abuse of the same semantic domain name from the source. Single registration rule: It stipulates that the same domain name can only be registered in one of the simplified and traditional forms. For example, if a user has already registered the simplified form of a domain name, they cannot register its traditional form again, and vice versa. Automatic Equivalent Protection: When a user registers a simplified or traditional domain name, the registration system should automatically provide equivalent protection for the other form, thereby reducing the management burden on both the registrar and registrant in brand defense registration. 2. Adopt standardized character encoding and preprocessing mechanisms In terms of technical implementation, ensure the uniqueness and compatibility of domain names in the DNS system, and reduce the difficulty of technical adaptation for distributors and registrants. Strictly speaking, Simplified Chinese and Traditional Chinese are different, but they are mapped to the same set of resources in DNS resolution and registration policies. 3. Drawing on existing mechanisms for handling traditional Chinese strings, formulate various specific policies and carry out technical processing to minimize the impact on the operation and management of registrants, distributors, and/or registrants.

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--fiq228cl8q

Q123.1Variant String (U-Label)

Variant String (U-Label)

中文網

Q123.2Variant String (Code Points)

Variant String (Code Points)

U+4E2D U+6587 U+7DB2

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