Snapshot of 8 October 2026 · ICANN APS, public fields

Applications / .官网 / HERI2445-T27601 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.官网

IDNActive

A-label xn--kbt444f Q116

Hangzhou E-commerce Research Institute, CN Q1·Q25

ICANN record ↗

§ 1 — Meaning of the string Q118·Q120

An authoritative and official public independent website established on the Internet by different categories of all organizations, teams, enterprises or individuals.

/kwán.wàŋ/

§ 2 — Mission and purpose Q133

The intended users of the main string "官网" applied by the applicant cover the global, including potential users in Chinese Mainland, Hong Kong, Macao and Taiwan, and other countries around the world who like Chinese characters. The mission and goal of the applied gltd is to enable more users in non English speaking regions around the world to access the Internet in their native language by introducing new suffixes, including multilingual domain names (IDNs), so as to truly realize the localization and diversity of domain names. It aims to establish authoritative and official public independent websites for various organizations, teams, enterprises or individuals on the global Internet, so that various organizations, teams, enterprises or individuals no longer need to rely on other third-party platforms to carry out business and operate their own brands. By using the applied gltd domain name to establish user independent websites, more users can get independent traffic from customers. The applicant will pay more attention to the actual use of the GTLD domain name in the future, and focus on conducting market promotion activities for the practical application of registered domain names, promoting the diversified development of their own brand among end users. The domain name applied for gltd registration can get more practical applications on the global Internet. The direction itself is sustainable, greatly reducing the risk of domain name abuse, and promoting the healthy and stable development of the Internet.

§ 3 — Commitments and safeguards Q164–Q188

More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169Yes to: more trustworthy (Q164)
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.

Q212Q4.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), 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: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.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.

Q4.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), 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: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.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.

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+5B98 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?

New TLD

Q126What is the meaning/definition of the variant string?

What is the meaning/definition of the variant string?

An authoritative and official public independent website established on the Internet by different categories of all organizations, teams, enterprises or individuals.

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.

The primary string applied by the applicant is "官网", where "官网" is a simplified Chinese character and its traditional Chinese character "官網" is a variant string. The character '官' was not simplified during the process of Chinese character simplification, and its simplified and traditional forms are the same, both being '官'. There is only one traditional Chinese spelling for the character '网', which is'網'. Traditional and simplified Chinese characters are both part of the Chinese character system, deeply rooted in Chinese cultural traditions, and important carriers for inheriting and promoting Chinese culture. Simplified characters and traditional characters are two forms of the writing system of Chinese characters. Simplified characters are formed by simplifying the strokes of traditional characters. Simplified characters are used as standard characters in Chinese Mainland, and traditional characters are still used in Hong Kong, Macao and Taiwan. Hong Kong, Macao, and Taiwan are an inseparable part of China's territory. In order to meet regional, linguistic, cultural, and customary considerations and facilitate the widespread operation of strings, we hereby apply for a traditional Chinese string "官網". Therefore, the primary "官网" applied-for and variant strings "官網" are the same, including the meaning.

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

First of all, simplified characters and traditional characters are two forms of Chinese character writing system. Users in Chinese Mainland use simplified characters as the standard, while users in Hong Kong, Macao and Taiwan still use traditional characters. Therefore, in order to meet regional, language, culture, habits and other factors, the primary string is mainly used by all users in Chinese Mainland and potential users in other countries around the world who like Chinese characters, while the variant string is used by all users in Hong Kong, Macao and Taiwan. Due to the habit of using traditional Chinese characters in Hong Kong, Macao, and Taiwan, variant strings are more conducive to easy understanding and convenient operation of domain names for all users in Hong Kong, Macao, and Taiwan. Users in Hong Kong, Macao, and Taiwan will not be confused as a result.

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.

This primary string only has one variant string, which greatly reduces the complexity of management in practical operation. The applicant plans to provide variant strings directly to users in all regions when applying for registration of the primary string, in order to minimize the complexity caused by variant strings in registration or management for domain name registrars, resellers, and/or registrants. At the same time, it supports domain name resolution function for variant strings.

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

Q123.1Variant String (U-Label)

Variant String (U-Label)

官網

Q123.2Variant String (Code Points)

Variant String (Code Points)

U+5B98 U+7DB2

Q222If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.

If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.

None.

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