tld.report · La ronde 2026

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

Candidatures / .xiaomi / XI2635T-T61918 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.xiaomi

TLD de marque · Spec 13Active

Xiaomi Inc., CN Q1·Q25

Contrôle ultime déclaré : Xiaomi Corporation, JUN LEI Q108 · Fiche ICANN ↗

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

No English Translation

[ɕiɑʊmi]

§ 2 — Mission et objet Q133

Xiaomi is a consumer electronics and smart manufacturing company centered on smartphones, smart hardware, and the IoT platform. Embracing the vision, "Make friends with users and be the coolest company in the users’ hearts," Xiaomi is committed to continuous innovation, relentlessly pursuing the ultimate product and service experience and operational efficiency, and diligently fulfilling its corporate mission: "to consistently deliver good products that are heartwarming and fairly priced, so that everyone in the world can enjoy a better life through technology."

1. Mission and Purpose (1) Mission The mission of ".xiaomi" is to create a secure, trusted, and exclusive digital space that brings together and supports all users, developers, and partners within Xiaomi and its extensive ecosystem. Its core purpose is to consolidate and extend the online influence of the Xiaomi brand identity. (2) Objectives 1) Provide an exclusive digital identity for intended registrants a. Intended registrants: Xiaomi Group and its affiliated entities. b. Specific objectives: To provide trusted domains for the aforementioned registrants, enabling them to distinguish official services, product launch channels, and brand official entry points. 2) Provide trusted access for intended users a. Intended users: global user base. b. Specific objectives: Users will be able to access authenticated official stores, technical support, and community services through the ".xiaomi" domain. This domain will serve as a key identifier for users to recognize genuine Xiaomi services amidst vast online information, reducing the risk of phishing websites and enhancing user experience and trust. (3) Ongoing and Planned Activities 1) Brand protection and ecosystem security: Leverage the control capabilities of an exclusive TLD to establish effective brand protection mechanisms and maintain the security and order of the brand's online ecosystem. 2) Empowering products and ecosystem: Xiaomi has built a vast ecosystem centered on smartphones, smart hardware, and the IoT platform. Through this brand digital space, various products and services can be provided with more unified online entry points. 3) Enhancing brand credibility: Provide unified and trusted digital entry points for various services under the Xiaomi brand, strengthening user trust in brand-related content and services.

2. Long-term Sustainability of the Objectives The long-term sustainability of these objectives is grounded in Xiaomi's established business entity, robust financial performance, and healthy business development trajectory: (1) The applicant is a legal entity with a clear long-term business plan, which provides the most fundamental legal guarantee for the long-term holding and operation of the TLD. (2) As of Q1 2026, its smartphone business has ranked among the global top three for 23 consecutive quarters, with revenue from innovative businesses such as smart electric vehicles and AI reaching RMB 19.9 billion. This sound financial performance provides solid funding support for the long-term operation and maintenance of the TLD. (3) Xiaomi's global influence continues to expand, ranking among the top three in shipment volume in 47 countries and regions and among the top five in 65 countries and regions. Its monthly active users in the Chinese mainland reached 196 million, a record high. This vast user base provides a continuous source of vitality for the long-term value of ".xiaomi". (4) The applicant possesses a stable and legitimate governance structure. Clear decision-making mechanisms ensure that the TLD's operational strategies can be implemented consistently and coherently over the long term.

Based on our long-term business planning, sound financial performance, thriving user ecosystem, and stable and legitimate governance structure, the objective of applying for and operating ".xiaomi" is clear and possesses long-term sustainability.

§ 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 the planned operation of the .xiaomi TLD fully complies with Section 3(d) of Specification 11 of the Registry Agreement and does not present any conflict. The rationale is as follows:

I. ".xiaomi" qualifies as a .Brand TLD String and Is Not Subject to the Restrictions under Section 3(d) of Specification 11

Pursuant to the express definition set forth in Section 3(d) of Specification 11, the prohibitive provision—which restricts a registry operator from imposing eligibility criteria that limit registrations exclusively to a single person or entity and/or that person's or entity's "Affiliates"—applies only to "Generic String" TLDs. A "Generic String" is defined as "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."

".xiaomi" is unequivocally a brand string, rather than a generic string, based on the following grounds: Legal Status and Public Perception: "xiaomi" is a core registered trademark of the Applicant, with legal effect across multiple jurisdictions. In public perception, .xiaomi distinctly identifies Xiaomi Group and its specific branded products and services, rather than describing any general class of goods or services such as "smartphones," "consumer electronics," or "internet services."

Application Category and Policy Basis: This application has been submitted in accordance with the .Brand TLD application category and requirements set forth in the ICANN Applicant Guidebook, and will undergo the corresponding eligibility evaluation. The very purpose of establishing the .Brand TLD category within ICANN's policy framework is to permit brand owners to operate an exclusive namespace that corresponds to their registered trademarks, with registrations limited to the brand owner and its Affiliates.

Consequently, the fundamental restrictive condition under Section 3(d) of Specification 11 does not apply to this application.

II. The Operational Model Fully Aligns with the Purpose of .Brand TLDs and ICANN Policy

As an ICANN-recognized .Brand TLD, ".xiaomi" will be operated in compliance with the design intent and requirements for such TLDs, with the following specific operational arrangements:

Registration Eligibility Restrictions: Domain name registrations within this TLD will be limited to Xiaomi Group and its Affiliates worldwide. This model is fully consistent with the definition of a .Brand TLD.

Transparent Registration Policies: Clear and transparent registration and management policies will be developed and publicly posted within the scope described above, ensuring that all eligible entities may apply for and use domain names fairly through a unified internal governance process.

Enhanced DNS Security: By confining domain name usage to known and trusted legal entities, the risk of DNS Abuse is fundamentally and significantly reduced, which aligns with ICANN's core mission to maintain the security and stability of the Domain Name System.

Conclusion

In summary, .xiaomi, as a brand string, represents a normal and legitimate use of a .Brand TLD and is entirely exempt from the restrictions set forth in Section 3(d) of Specification 11 of the Registry Agreement. The Applicant commits to operating this TLD in accordance with the operational plan described above, and to ensuring its continued compliance with all relevant provisions of the Registry Agreement throughout the term of operation.

§ 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