tld.report · La ronde 2026

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

Candidatures / .huawei / HTCL2692T-T25968 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.huawei

TLD de marque · Spec 13Active

Huawei Technologies Co., Ltd., CN Q1·Q25

Contrôle ultime déclaré : Huawei Investment & Holding Co., Ltd. Q108 · Fiche ICANN ↗

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

No English Translation

/hwɑːˈweɪ/

§ 2 — Mission et objet Q133

I. Mission and Objectives Mission: As the Applying Entity and Registry Operator of the .huawei TLD, our mission is to build a secure, trusted, and unified global digital identity infrastructure for Huawei. Through centralized management, we aim to drive the standardized development of the Huawei ecosystem and global collaboration, in support of the company's vision and mission to "bring digital to every person, home and organization for a fully connected, intelligent world". Objectives: To establish .huawei as an exclusive and authoritative digital identifier for Huawei's internal operations. Registration rights will be restricted to the Group and its subsidiaries, enabling centralized control and compliant use of the brand domain name worldwide, thereby enhancing brand asset value and digital operational efficiency. II. Intended Registrants Intended registrants are limited to entities within the Huawei Group and its subsidiaries, including Group headquarters, core business divisions, global R&D institutions, subsidiaries, representative offices, and other affiliated entities. III. Intended Users Intended users primarily consist of Huawei's global employees (approximately 213,000), global consumers (serving more than three billion people), enterprise customers, carrier partners, and ecosystem partners. Through the .huawei domain, they will access reliable information channels for Huawei's official products and services, technical support, all-scenario smart experiences, cloud services, and more, and obtain a secure and intelligent official experience. IV. Related Activities 1. Adopt .huawei as Huawei's unified internal brand TLD globally, integrating digital identifiers across the Group's various business units, regional representative offices, and R&D systems to achieve centralized brand asset management. 2. Leverage the .huawei domain to convey to global users Huawei's commitments and service values in ICT infrastructure, smart devices, cloud, and AI through a unified digital gateway. 3. Build a digital bridge connecting businesses and information across more than 170 countries and regions, driving standardized operations and collaborative development of the brand worldwide, and accelerating industry intelligence and the democratization of technology. V. Statement of Long-Term Sustainability 1. Founded in 1987, Huawei is a leading global provider of information and communications technology (ICT) infrastructure and smart devices. The company has approximately 213,000 employees and operates in more than 170 countries and regions, serving more than three billion people around the world. Its solid business footprint and sustained market growth provide a stable foundation and ongoing business demand for the long-term operation of .huawei. 2. We have deployed a professional technical and management team, backed by ample financial support from the Group, and have established a comprehensive internal domain name registration, resolution, management, and security protection system. Through continuous investment of internal Group resources, we ensure that the domain name system evolves in tandem with the Group's business development, guaranteeing the financial sustainability of operations. 3. Huawei consistently strengthens technological innovation, upholds open collaboration, and practices the democratization of technology. As of the end of 2025, the company held a total of 165,000 active granted patents globally, with 114,000 employees working in R&D, accounting for 53.7% of the total workforce. The company's deep brand heritage and globally leading intellectual property portfolio provide strong reputational assurance for the sustainable development of the domain system. 4. We will comply with all ICANN regulations, ensuring operational compliance and technical system security, thereby effectively mitigating various risks and building a secure, reliable, and trustworthy long-term digital home for Huawei's global digital strategy.

§ 3 — Engagements et sauvegardes Q164–Q188

Confiance accrue, risque pour le consommateur, secteur réglementé, déclarations à l'État, préjudice, fonction régalienne Q164–Q169Oui à : confiance accrue (Q164), risque pour le consommateur en cas d'abus (Q165)
PIC de sauvegarde volontaires Q170·Q171

• Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring registrants to comply with all applicable laws, including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct), fair lending, debt collection, organic farming, disclosure of data, and financial disclosures. • Registry Operators will include a provision in their Registry-Registrar Agreements that requires registrars at the time of registration to notify registrants of the requirement to comply with all applicable laws. • Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring that registrants who collect and maintain sensitive health and financial data implement reasonable and appropriate security measures commensurate with the offering of those services, as defined by applicable law.

Registry Voluntary Commitments Q172·Q173Aucun · 5 en proposent
Critères de TLD de marque confirmés, certificat de marque joint Q180·Q181Oui · certificat non publié
Confirme que la chaîne n'est pas une « generic string » Q183Oui
Déclaration Spec 11 §3(d) Q184

The Applying Entity confirms that .huawei is not subject to the restrictions set forth in Specification 11, Section 3(d) of the Registry Agreement. The text of that provision is as follows: (d) Registry Operator of a "Generic String" TLD 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". "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.

Based on the above definition, .huawei clearly qualifies as a brand string rather than a generic string, for the following reasons: I. .huawei is a clear brand string and is not subject to Specification 11, Section 3(d) 1."huawei" is a valid registered trademark, referring specifically to the HUAWEI Group and its branded products and services, rather than to any general category. 2.This application is submitted under the ICANN category specifically established for brands, which was designed to allow brand owners to register and operate an exclusive domain space corresponding to their own trademarks. Therefore, the restriction in Specification 11, Section 3(d) that prohibits limiting registration eligibility to a single entity or its affiliates does not apply to this application.

II. The planned operational model is consistent with the purpose of brand TLD and ICANN policy As a brand TLD, the operational model for ".huawei" will follow the core purpose of brand TLDs and the relevant ICANN policy framework: 1.The Applying Entity plans to use ".huawei" as an internal digital asset exclusively for the HUAWEI Group. Registration eligibility will be limited to the HUAWEI Group and its affiliates worldwide. This closed operational model is a typical feature of brand TLD, designed to maintain brand consistency and integrity, and is consistent with ICANN's policy objectives in establishing the brand TLD category. 2.Within the defined internal scope, we will establish clear and transparent registration and management policies, ensuring that all eligible affiliates can apply for and use domain names fairly under a uniform internal governance process. 3.This model, by keeping the domain space within known and trusted legal entities, reduces the risk of the TLD being used for DNS abuse such as phishing and malware distribution, thereby contributing to the security and stability of the domain name system.

In summary, as a brand string, .huawei's planned operational model, which limits registrations to the brand owner and its affiliates, is an inherent attribute of brand TLDs and is not subject to the constraints of Specification 11, Section 3(d).

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

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

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.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Q220Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Q221Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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

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