Last published on: 7 October 2026 at 15:37 UTC
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.
Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.
Qingdao Haishang Zhicai Management Consulting Co., Ltd.
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.
Private Limited Company
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.
China
Provide the website URL of the applying entity, if available.
https://www.haier.com
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).
false
Choose Yes or No.
false
86
Provide the primary business phone number without including the country code.
0532-8893-1192
Provide the primary business email address of the applying entity.
niuhg@haier.com
Enter the street address (no PO Box).
Haier Industrial Park, No. 1 Haier Road, Laoshan District
Enter the city, village, municipality, etc.
Qingdao
Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.
Shandong Province
1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.
266101
CN
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.
Qingdao Haironghui Holdings Co., Ltd.
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.
Private Limited Company
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.
China
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.
HAIER GROUP CO.,LTD
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.
Public Limited Company
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.
China
This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.
YUNJIE ZHOU
YUNJIE ZHOU
Qingdao Haironghui Holdings Co., Ltd.
Qingdao Haironghui Holdings Co., Ltd.
Provide a single document for Self-Certification question Q4.2-1. The document must include only the SC4.2-1.1, SC4.2-1.2, or SC4.2-1.3 statements. Do not modify any of the Self-Certification statements.
1. Provide a single document for Self-Certification question Q4.2-1. 2. The document must include only the SC4.2-1.1 through SC4.2-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC4.2-1.1 through SC4.2-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC4.2-1.1 through SC4.2-1.3 statements.
Provide a single document for Self-Certification question AGB Q220, Q5.1-1. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements.
1. Provide a single document for Self-Certification question Q5.1-1. 2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1.1-3 statements.
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.
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.
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.
xn--3et971b
海尔
U+6D77 U+5C14
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"
No English Translation
If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)
Chinese (Han)
Provide a representation of the string according to the International Phonetic Alphabet.
/xaɪ˧˥ ɚ˨˩˦/
Confirm the statement using a checkbox.
true
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.
1. Mission and Objectives As the applicant for the ".海尔" (xn--3et971b) and its variant ".海爾" (xn--90ww5h) 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 ".海尔" (xn--3et971b) and its variant ".海爾" (xn--90ww5h) as the unified internal brand TLD for Haier Group, integrating the digital identity framework to centralize brand asset management. (2)Leverage ".海尔" (xn--3et971b) and its variant ".海爾" (xn--90ww5h) 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 ".海尔" and ".海爾". (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.
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.
xn--90ww5h
海爾
U+6D77 U+723E
Provide the script of the variant string (both in English and as referenced by the RZ-LGR/ISO 15924)
Chinese (Han)
Select an option.
New TLD
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".
no English Translation/Meaning
Provide at least three bona-fide examples to support the explanation. (for example, evidence of trademark use by showing real world use cases).
The primary applied‑for string "海尔" (xn--3et971b) in Simplified Chinese and its variant string "海爾" (xn--90ww5h) in Traditional Chinese are regarded as identical within the Chinese‑speaking user community. This equivalence is grounded in three core aspects: 1.Semantic and orthographic identity – The characters “尔” and “爾” are historically and lexically the same character, differing only in their written forms (simplified vs. traditional). In all Chinese dictionaries and everyday usage, they carry exactly the same meaning and pronunciation, and are mutually interchangeable without any change in semantics. 2.User community perception – For native Chinese speakers worldwide (including Mainland China, Taiwan, Hong Kong, Macau, and overseas Chinese communities), both forms are instantly recognised as representing the same entity. When users see “海尔” or “海爾” in branding, advertising, or digital environments, they universally understand it as the same well‑known household appliance brand. No confusion or ambiguity arises, as the two scripts are part of the same writing system and are used interchangeably in cross‑strait and cross‑regional contexts. 3.Regulatory and technical recognition – The Root Zone Label Generation Rules (RZ‑LGR) for the Chinese script explicitly group Simplified and Traditional character variants into the same variant set. Under ICANN’s variant management framework, these strings are treated as equivalent for domain registration and resolution purposes, ensuring that they point to the same logical namespace. This technical equivalence aligns perfectly with real‑world user expectations. Furthermore, Haier Group itself consistently uses both “海尔” and “海爾” across its official materials, product packaging, and global marketing campaigns, reinforcing the brand identity across different Chinese‑script regions. In practice, users accessing either domain would anticipate reaching the same online presence, making it both linguistically and technologically justified to treat them as identical. To further substantiate this claim, we have compiled a set of real‑world examples covering official websites, e‑commerce platforms, offline advertisements, trademarks, and social media usage, which are provided in the attached document for detailed reference.
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.
This document outlines the necessity, technical approach, and value of applying for the Traditional Chinese variant ".海爾" (xn--90ww5h) for the internal brand TLD ".海尔" (xn--3et971b). As the TLD is internal and not open to public registration, offering both Simplified and Traditional forms ensures global digital asset consistency and accessibility. 1.Simplified and Traditional Chinese are distinct writing systems used in different regions. To represent Haier's brand identity, both "海尔" (xn--3et971b) and "海爾" (xn--90ww5h) are required. Relying on a single string falls short of the Group's operational and cultural needs for two reasons: (1)With global branches and employees worldwide, a single‑script domain would hinder employees using Traditional Chinese systems in accessing internal resources, due to input habit mismatches, reducing efficiency. Beyond practicality, requiring employees to use a non‑customary script risks being perceived as culturally insensitive. Providing domains in local scripts fosters a sense of belonging and strengthens internal brand cohesion. (2)As a core digital asset, if any major script variant is omitted, it could, through internal oversight or lack of local awareness, be registered or misused outside the Group's control—fragmenting the brand image and creating asset management vulnerabilities. Therefore, applying for both "海尔" and "海爾" is essential to safeguard the integrity of Haier Group's global digital identity, support efficient international operations, and demonstrate responsible brand management. 2. User communities served by the primary TLD and all its variant TLDs (1)The primary TLD ".海尔" (xn--3et971b) serves the community of the Group's institutions and employees whose primary written language is Simplified Chinese. This includes headquarters and branches in mainland China, Simplified Chinese‑using teams in Singapore, Malaysia, and other locations, as well as employees and partners worldwide who are accustomed to Simplified Chinese systems. (2)The variant TLD ".海爾" (xn--90ww5h) serves the community of the Group's institutions and employees whose primary written language is Traditional Chinese. This mainly comprises branch offices and representative offices in the Taiwan, Hong Kong, and Macao regions of China, as well as Chinese employees and business partners in other global regions who are accustomed to Traditional Chinese systems. 3. How the similarities and differences in IDN table design reflect user community needs To balance internal user habits with technical consistency, the IDN tables for both ".海尔" (xn--3et971b) and ".海爾" (xn--90ww5h) follow these principles: (1)Both IDN tables are based on exactly the same character range, ensuring a consistent technical foundation, full compliance with international standards, and identical supported character sets. (2)Both are system‑designated registrable suffixes with identical registration policies. The only difference lies in default priority: Simplified Chinese users are preferentially recommended "example.海尔", while Traditional Chinese users are preferentially recommended "example.海爾". This respects regional writing conventions without creating any disparity in eligibility or policy. (3)When registering "example.海尔", the system can be configured to automatically register or preferentially reserve "example.海爾" for the same registrant; the same applies in reverse. This ensures that both variants are uniformly managed by the same entity, accommodating various business needs while preventing brand confusion and misuse.
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.
This application for the brand TLDs ".海尔" (xn--3et971b) and ".海爾" (xn--90ww5h) adopts a "Registry – brand Registrar – Internal Registrant" model. This model consolidates and simplifies registration channels and processes through a brand registrar, reducing operational and management complexity for the broader DNS ecosystem. The Applicant commits to implementing measures to ensure efficient and stable operation and to fulfill all obligations to ICANN. 1.Registration Channel Simplification. Unlike traditional gTLDs that need to interface with hundreds of registrars worldwide, we will streamline registration service channels to a brand registrar: (1)All policy dissemination, technical interfacing, financial settlement, and compliance collaboration will only be conducted with a single partner, avoiding the huge management overhead and potential inconsistency risks. (2) We can carry out deep system-level integration with the brand registrar, developing customized registration management interfaces and automated processes. (3) Ensure that all domain registrations through this channel follow unified service standards, pricing strategies, and customer support processes. 2.End-to-End Automation and Synchronization. We will offer the brand registrar a comprehensive set of technical and management solutions: (1)The Applicant will deliver to the brand registrar a management toolkit that encapsulates all variant synchronization logic. When the registrar system initiates registration, renewal, or DNS modification instructions for example.海尔, this toolkit will automatically complete the synchronous operations for example.海爾 and return an aggregated result to the registrar. The registrar does not need to develop additional logic for variants in its front-end system. (2) All complex variant management policies will be automatically enforced by the registry backend system. The brand registrar and their end users do not need to make extra choices or judgments during operations; the system guarantees consistency and compliance of results, eliminating the possibility of complex problems caused by human operational errors. (3) The brand registrar can obtain clear, aggregated domain asset reports through a dedicated management panel, simplifying reconciliation, management, and customer service work. 3.Internal Registration Policies and Processes. Since users are limited to internal group entities, we can implement simplified strategies: (1) The front-end system of the brand registrar will interface with the group's internal identity authentication or approval system. Only internal employees or departments can initiate applications. The application process can automatically trigger internal approval workflows; upon approval, the system automatically completes registration. (2) Domain fees will adopt a unified annual internal settlement model. (3) Since all registrants are affiliated entities, any disputes or change requests regarding domain usage will first be resolved through the group's internal administrative processes; only in extreme cases will external legal procedures need to be invoked. 4.Clear Responsibility Boundaries. We will ensure that complexity is contained within controllable limits through contract and process design: (1) For any operational issues arising from variant TLD design and the registry system itself, the applying entity will proactively assume responsibility and provide clear Service Level Agreement (SLA) guarantees to the brand registrar. (2) The brand registrar does not need to understand, explain, or handle the complex rules behind variant synchronization, but only needs to ensure that its interface accurately triggers the automated tools we provide. (3) This model ensures that public registrars, distributors, and public registrants will have no contact with this brand TLD, and therefore will not incur any additional technical, policy, or economic burden or complexity from it.
Confirm the statement using the checkbox.
true
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.
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
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
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.
No
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.
No
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.
No
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.
No
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).
Yes
Choose the applicable Safeguard PICs from the provided list (more than one option can be selected).
• 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.
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.
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.
No
This question set collects information related to whether the applied-for gTLD string is a .Brand (see Section 7.3) or if the applying entity is seeking a Code of Conduct exemption (see Section 7.4).
Select Yes or No
Yes
Select Yes or No. Notes: If the applying entity selects “no,” it will be required to provide additional documentation describing which criteria is not met as well as a justification for the TLD to nonetheless qualify as a .Brand TLD.
Yes
Attach an accurate and complete copy of the applicable trademark registration that forms the basis of the request for .Brand TLD qualification.
Confirm statement with a checkbox.
true
Explain how the applying entity intends to operate the TLD such that there would not exist any such conflict with Section 3(d) of Specification 11.
The Applicant confirms that “.海尔” (xn--3et971b) and its variant “.海爾” (xn--90ww5h) fully comply with the requirements of Specification 11, Section 3(d) of the Registry Agreement, and that no conflict exists. The core reason is that they are clearly identifiable brand strings, rather than generic strings, and therefore the restrictive provisions of that clause regarding registration eligibility do not apply to them. I. “.海尔” (xn--3et971b) and its variant “.海爾” (xn--90ww5h) are clearly identifiable brand strings and do 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, “.海尔” (xn--3et971b) and its variant “.海爾” (xn--90ww5h) fully meet 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."海尔" and “海爾”are valid registered trademarks, and they refer 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 Brand TLDs, “.海尔” (xn--3et971b) and its variant “.海爾” (xn--90ww5h) 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 “.海尔” (xn--3et971b) and its variant “.海爾” (xn--90ww5h) strictly as the internal-use digital assets 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 brand strings, “.海尔” (xn--3et971b) and its variant “.海爾” (xn--90ww5h) – and the 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 the TLDs strictly in accordance with this description and to ensure that they remain in full compliance with all terms of the Registry Agreement at all times.
This question set collects any additional information that the applying entity would like to provide, including any supporting materials.
This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.
Confirm the statement using the checkbox.
true
Confirm the statement using the checkbox.
true