tld.report · La ronde 2026

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

Candidatures / .haier / QHZM2659T-T28230 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.haier

TLD de marque · Spec 13Active

Qingdao Haishang Zhicai Management Consulting Co., Ltd., CN Q1·Q25

Contrôle ultime déclaré : Qingdao Haironghui Holdings Co., Ltd. Q108 · Fiche ICANN ↗

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

No English Translation

/ˈhaɪ.ər/

§ 2 — Mission et objet Q133

1. Mission and Objectives As the applicant for the ".haier" registry, we aim to build a secure, trusted, and unified global digital identity infrastructure for Haier Group, promoting standardized development and global collaboration through centralized management. We will position these domains as the exclusive digital identifiers for the Group and its subsidiaries, restricting registrations accordingly. This enables unified global brand control, compliant usage, and a highly secure internal network, ultimately enhancing brand asset value and digital efficiency. 2. Intended Registrants Intended registrants are limited to Haier Group and its various affiliates, including: Haier Group headquarters, Haier Smart Home, Thunderobot, Haier Biomedical, INKON Life, Shanghai RAAS, STEP, Autohome, and ZHONGMIAO HOLDINGS – eight listed companies and their subsidiaries – as well as the operating entities of global premium brands such as Haier, Casarte, Leader, GE Appliances, Fisher & Paykel, AQUA, and CANDY. 3. Intended Users Intended users primarily include Haier Group employees, global consumers, enterprise customers, and ecosystem partners. Through these exclusive domains, they will access Haier Group's official services across six major industrial ecosystems – Smart Home Ecosystem, Comprehensive Healthcare Industry Ecosystem, Digital Economy Industry Ecosystem, Robotics Industry Ecosystem, New Energy Industry Ecosystem, and Automotive Industry Ecosystem – and obtain secure, tamper-proof official information and product experiences. 4. Relevant Activities (1)Use ".haier" as the unified internal brand TLD for Haier Group, integrating the digital identity framework to centralize brand asset management. (2)Leverage ".haier" to support digital collaboration across the ecosystem, enabling seamless user-device-service connectivity through various second-level domains. (3)Integrate with the COSMOPlat industrial internet platform to build a digital foundation for global enterprise collaboration and secure data exchange. (4)Provide intuitive, memorable domain access points to simplify multilingual and multi‑region access paths, improving user efficiency in accessing Haier's ecosystem services. 5.Long-Term Sustainability Statement (1)Since 1984, Haier Group has built a global brand, ranking first in major home appliance retail sales globally for 17 consecutive years (Euromonitor). With 10 R&D centers, 71 research institutes, 35 industrial parks, 173 manufacturing centers and a sales network of 230,000 touchpoints worldwide, this solid global presence ensures ongoing demand and a strong foundation for the long‑term use of the ".haier". (2)As the Group's internal dedicated registry, we have a professional team and sufficient funding, with comprehensive systems for registration, resolution, management, and security. Continuous investment ensures system evolution with business growth, forming a service loop and financial sustainability. (3)Upholding "Forever Sincere", we reinforce brand value through CSR initiatives like "Project Hope". This heritage and social responsibility provide a spiritual core and reputational guarantee for the domain system's sustainability. (4)We will comply with ICANN rules, implement security monitoring and emergency response, ensure compliance and technical security, mitigate risks, and uphold credibility—providing a secure, reliable digital platform for Haier's global digitalization.

§ 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 Applicant confirms that ".haier" TLD fully complies with the requirements of Specification 11, Section 3(d) of the Registry Agreement, and that no conflict exists. The core reason is that ".haier" is a clearly identifiable brand string, rather than a generic string, and therefore the restrictive provisions of that clause regarding registration eligibility do not apply to it.

I. ".haier" is a clearly identifiable brand string and does not fall within the scope of Specification 11, Section 3(d) Under the express definition of Specification 11, Section 3(d), its restrictive provisions apply only to generic strings—namely, strings composed of words or terms that denote or describe a general category of goods, services, groups, organizations, or things. By contrast, ".haier" fully meets the definition of a brand string—namely, a proprietary identifier used to distinguish a particular brand (Haier Group and its products and services) from other market entities. 1."haier" is a valid registered trademark, and it refers specifically to Haier Group Corporation and the branded products and services it provides, rather than to any general category. 2.This application was submitted under the specific application category established by ICANN for brands, the very purpose of which is to allow brand owners to register and operate an exclusive domain space corresponding to their own trademarks. Therefore, the prerequisite for applying the restriction set forth in Specification 11, Section 3(d)—which prohibits provisions that limit registration eligibility to a single entity or its affiliates—does not exist in this application.

II. The planned operation model is consistent with the purpose of Brand TLDs and ICANN policies As a Brand TLD, ".haier" will be operated in strict compliance with the core purpose of Brand TLDs and the relevant ICANN policy framework: 1.The Applicant plans to operate ".haier" strictly as an internal-use digital asset of the Haier Group. Registration eligibility will be limited to Haier Group Corporation and its affiliates, wholly-owned or majority-controlled subsidiaries worldwide. This closed operation model is a typical feature of Brand TLDs, designed precisely to maintain brand consistency and integrity and to prevent third-party misuse, which fully aligns with the policy objectives of ICANN's Brand TLD category. 2.Within the defined internal scope of use, we will establish clear and transparent registration and management policies, ensuring that all eligible affiliates can fairly apply for and use domain names under uniform internal governance procedures, without discrimination among internal entities. 3.This restrictive registration model does not undermine the public interest; on the contrary, by strictly confining the domain space to known and trusted legal entities, it greatly reduces the risk of DNS abuse—such as phishing and malware distribution—at the TLD level, thereby enhancing the overall security and stability of the domain name system.

In summary, as a brand string, ".haier" and its planned operation model—which limits usage to the brand owner and its affiliates—are inherent attributes of a Brand TLD, and this model is not subject to the constraints of Specification 11, Section 3(d). We undertake to operate this TLD strictly in accordance with this description and to ensure that it remains in full compliance with all terms of the Registry Agreement at all times.

§ 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