Application Details

Last published on: 7 October 2026 at 15:37 UTC

Application Type: Existing gTLD with Variants

Primary String: xn--fiq228c5hs (中文网)*

TLD Variants:

xn--fiq228cl8q (中文網)

TLD Types: IDN

*This application is for a variant of an existing TLD only

Application ID: BTRT2633T-T38161

Application Priority Number: --

Application Status: Active

Processing Stage: Pre-Evaluation Processing

Comment Period: --

View:

Summary Responses Clarifying Questions Change Requests Documents Objections

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.

AGB Q1. Full Legal Name

Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.

Beijing TLD Registry Technology Limited

AGB Q3. Legal Entity Form/Business Structure

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.

Limited Liability Company

AGB Q4. Jurisdiction

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.

Beijing

AGB Q10. Website URL

Provide the website URL of the applying entity, if available.

https://tldland.cn/

AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?

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

AGB Q12. If "Yes", explain.

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.

Applying entity is an existing registry operator.

AGB Q13. Is the applying entity a back-end registry service provider (RSP), an ICANN-approved data escrow agent, an emergency back-end registry operator, a Uniform Rapid Suspension (URS) service provider, an ICANN dispute resolution service provider, a Privacy or Proxy Service Provider, or a Reseller?

Choose Yes or No.

false

AGB Q17. Phone Country Code

AGB Q18. Primary Business Phone

Provide the primary business phone number without including the country code.

010-62575825

AGB Q19. Primary Business Email Address

Provide the primary business email address of the applying entity.

support@tldland.cn

AGB Q20. Address Line 1

Enter the street address (no PO Box).

Room 760, 1st Floor, Building 5, No. 18 Cuicun Erli, Changxindian, Fengtai District

AGB Q22. Locality

Enter the city, village, municipality, etc.

Beijing

AGB Q23. State/Province/Region

Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.

Beijing

AGB Q24. Postal Code

1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.

100072

AGB Q25. Country Code of Location

AGB Q26. Full Legal Name

If applicable, provide the full legal name as it appears on the official registration documents of the Direct Parent Company of the applying entity. Do not use abbreviations.

Infinitld (Beijing) Technology Co., Ltd.

AGB Q28. Legal Entity Form/Business Structure

Provide the long form (no acronyms) of the legal entity form/business structure of the Direct Parent Company as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation.

Limited Liability Company

AGB Q29. Jurisdiction

The jurisdiction indicates the location in which the business of the Direct Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include "Delaware", "Germany", etc.

Beijing

AGB Q36. Full Legal Name

If applicable, provide the full legal name as it appears on the official registration documents of the Ultimate Parent Company of the applying entity. Do not use abbreviations. "Ultimate Parent Company" means, with respect to an Applicant (and, if applicable, a Direct Parent Company), the top-level entity that directly or indirectly possesses the power to direct the management and policies of such Applicant (and, if applicable, a Direct Parent Company) through the ownership of voting securities, as a general partner, as a managing member, by contract, or otherwise. An Ultimate Parent Company is not controlled by any other entity. If there are no intermediary entities between the Applicant and the Ultimate Parent Company, the Ultimate Parent Company would be the same entity as the Direct Parent Company.

Infinitld (Beijing) Technology Co., Ltd.

AGB Q38. Legal Entity Form/Business Structure

Provide the long form (no acronyms) of the legal entity form/business structure of the Ultimate Parent Company as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation.

Limited Liability Company

AGB Q39. Jurisdiction

The jurisdiction indicates the location in which the business of the Ultimate Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include "Delaware", "Germany", etc.

Beijing

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Operational/Planning

Section: Security Policy and Planning

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.

AGB Q221. Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: 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.

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.

Has Documents

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.

AGB Q116. Applied-for Primary String (ASCII Label)

xn--fiq228c5hs

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

中文网

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

U+4E2D U+6587 U+7F51

AGB Q118. What is the meaning/definition of the applied-for gTLD string?

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"

website

AGB Q119. Script of String

If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)

Chinese (Han)

AGB Q120. Phonetic Representation

Provide a representation of the string according to the International Phonetic Alphabet.

/ʈʂʊŋ wən waŋ/

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

Confirm the statement using a checkbox.

true

AGB Q133. What is the mission and purpose of the applied-for gTLD?

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.

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.

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.

AGB Q122. Applied-for Variant(s)

xn--fiq228cl8q

AGB Q123.1 Variant String (U-Label)

中文網

AGB Q123.2 Variant String (Code Points)

U+4E2D U+6587 U+7DB2

AGB Q124. Script of Variant String

Provide the script of the variant string (both in English and as referenced by the RZ-LGR/ISO 15924)

Chinese (Han)

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

Select an option.

Existing TLD

AGB Q126. What is the meaning/definition of the variant string?

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

website

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

Provide at least three bona-fide examples to support the explanation. (for example, evidence of trademark use by showing real world use cases).

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

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

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.

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.

AGB Q129. Describe the steps that the applying entity will take to minimize the operational and management complexities of variant gTLDs and variant domain names that impact registrars, resellers and/or registrants.

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.

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.

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

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.

AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

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.

Yes

AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

Yes

AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q167. Would most people think that (domains in) the TLD(s) in the application are used for activities that require regular government reporting, inspections, and oversight in various countries? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

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.

AGB Q169. Would most people think that the TLD is used for something usually done by governments? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

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.

AGB Q170. Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Registry Agreement (RA) voluntarily regardless of ICANN’s Safeguard Assessment outcomes?

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

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.

AGB Q172. Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Registry Agreement (RA) that are unique to your applied-for string?

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.

Application Details

Application Responses

Section: Applying Entity Information

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Operational/Planning

Section: Security Policy and Planning

Section: DNS Abuse

Section: Primary String

Section: Variant String(s)

Section: Safeguard Identification

Section: Registry Voluntary Commitments (RVCs)

Section: Brand & Code of Conduct Exemptions

Section: Additional Information and Supporting Materials

Section: Bona Fide Intent and Prohibited Communications