tld.report · La ronde 2026

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

Candidatures / .bilibili / SHH2688T-T89320 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.bilibili

TLD de marque · Spec 13Active

Shanghai Hode Information Technology Co., Ltd., CN Q1·Q25

Contrôle ultime déclaré : Bilibili Inc. Q108 · Fiche ICANN ↗

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

No English Translation

/ˌbɪliˈbiːli/

§ 2 — Mission et objet Q133

Bilibili is a leading cultural community for young people and a comprehensive video platform in China. As of the first quarter of 2026, Bilibili had 115 million daily active users and 376 million monthly active users. Our brand proposition is: "The videos you are interested in are all on Bilibili." The community covers a wide range of fields including lifestyle, gaming, entertainment, anime, technology, knowledge, and many others. 1. Mission and Purpose of the Applied-for gTLD (1) Mission The mission of the applied-for TLD ".bilibili" is to create a secure, trustworthy, and exclusive digital space that brings together and supports all users, creators, brands, and partners within Bilibili and its broader ecosystem. Its core purpose is to consolidate the online presence of the "Bilibili" brand identity and strengthen brand credibility and user trust. (2) Objectives 1) Provide an exclusive digital identity for intended registrants a. Intended registrants: Primarily Bilibili Group and its affiliated entities. The ".bilibili" domain will not be open for registration to third parties without a direct brand or business affiliation with Bilibili. b. Specific objective: To provide these registrants with trustworthy domains to distinguish official services and exclusive content distribution channels, thereby reinforcing unified management of the brand's digital assets. 2) Provide trusted, high-quality content gateways for intended users a. Intended users: Bilibili's global user base. b. Specific objective: This domain will serve as a critical identifier for users to recognize "genuine Bilibili services" amid the vast amount of online information, reducing the risk of encountering phishing websites or fraudulent information. (3) Ongoing or Planned Activities 1) Brand protection and ecosystem security: Leverage the control capabilities of the exclusive TLD to safeguard the security and order of the community ecosystem. 2) Empowering creators and the community: Bilibili's digital space can provide creators with creative support and brand endorsement, facilitating the continued production and dissemination of high-quality content. 3) Enhancing brand credibility: Provide unified and trusted digital gateways for various services under Bilibili and reinforce user trust. 4) Promoting cultural dissemination: Leverage ".bilibili" to further consolidate its position as an emerging cultural dissemination platform, support the exchange and integration of diverse cultures. 2. Explanation of Long-Term Sustainability of the Objectives The long-term sustainability of these objectives is underpinned by: (1) Long-term operational continuity: The applicant is a legal entity with a clear long-term business plan, providing the fundamental legal foundation for the long-term operation of the TLD. (2) Sustainable financial support capability: The applicant has sustained profitability and provides the most solid financial foundation to support the long-term operation and maintenance of the TLD (including technical, human resources, marketing, and other expenses). (3) Stability of governance structure: The applicant has a clear and long-term stable shareholding structure, which ensures that the TLD operational strategy can be implemented consistently. (4) Clear decision-making mechanisms: The executive director of the applicant entity is responsible for determining the company's operational plans and investment plans. Applying for and operating a TLD can be categorized as a brand strategy investment for the company, with a clear, lawful decision-making path that avoids operational risks arising from ambiguous authority.

Based on our long-term business planning, sustained and stable profitability, stable and lawful governance framework, and increasingly vibrant content and commercial ecosystem, the objective of applying for and operating the ".bilibili" TLD is clear, and this initiative demonstrates 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 applying entity confirms that the proposed “.bilibili TLD fully complies with the requirements of Section 3(d) of Specification 11 of the Registry Agreement and there would not exist any such conflict. The reasons are as follows:

I.“.bilibili is a brand string and does not fall under Section 3(d) of Specification 11

According to the explicit definition in Section 3(d) of Specification 11, its restrictive provisions apply only to generic strings, i.e., strings consisting of a word or term that denotes or describes a general category of goods, services, groups, organizations, or things. “.bilibili is clearly a brand string, based on the following grounds:

1. “bilibili” is a valid registered trademark that refers to the BILIBILI Group and the specific products and services it provides, rather than a generic name for a class of goods or an industry.

2. This application is submitted under the application category established by ICANN for brands, which is specifically designed to allow brand owners to operate an exclusive domain name space consistent with their trademarks.

Therefore, the provision in Section 3(d) of Specification 11 regarding the prohibition of restricting registration eligibility to a single entity or its affiliates does not apply in this application.

II. The Operational Model Aligns with the Purpose of Brand TLD and ICANN Policies

As a brand TLD, the operational arrangements for “.bilibili are as follows:

1. This TLD will serve as a digital asset exclusively for internal use by the BILIBILI Group. Registration eligibility will be limited to BILIBILI Group companies and their affiliates, wholly-owned subsidiaries, or controlled subsidiaries worldwide.

2. Within the aforementioned scope of use, clear and transparent registration and management policies will be established to ensure that all eligible affiliates can register and use the domain fairly in accordance with unified internal governance procedures.

3. This registration model ensures that domain usage is controlled by known, trusted legal entities, effectively reducing the risk of DNS abuse and meeting the security and stability requirements of the domain name system.

In summary, as a brand string, the operational model of “.bilibili constitutes a standard use of a .brand TLD and is not subject to the restrictions of Section 3(d) of Specification 11. We will operate this TLD in accordance with the above guidelines to ensure its continued compliance with the relevant provisions of the Registry Agreement.

§ 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