tld.report · La ronde 2026

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

Candidatures / .doubao / BZNT2680T-T49729 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.doubao

TLD de marque · Spec 13Active

Beijing Zitiao Network Technology Co., Ltd., CN Q1·Q25

Contrôle ultime déclaré : Bytedance Ltd. Q108 · Fiche ICANN ↗

Opérateur de registre, bureau d'enregistrement ou affilié existant, tel que déclaré : Q12

There is an affiliated relationship with Beijing Volcano Engine Technology Co., Ltd. (Registrar IANA ID 4153).

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

No English Translation

/toʊ⁵¹ pɑʊ⁵⁵/

§ 2 — Mission et objet Q133

豆包 is a versatile AI-powered intelligent assistant developed by ByteDance. ("Doubao" is the Chinese pinyin for 豆包.) It serves as your AI chatbot for Q&A, dialogue, and interactive conversations, as well as a tool for writing, copywriting, translation, and programming. Doubao provides answers to your questions, sparks inspiration, and supports your creative endeavors.

1. Mission and Purpose of the Applied-for gTLD (1) Mission The mission of ".Doubao" is to create a secure, trusted, and exclusive digital space that unites and supports the entire Doubao ecosystem—including users, creators, brands, and partners. Its core purpose is to amplify and extend "Doubao" brand's online presence, transitioning its established community culture, creative ecosystem, and content services into a more controlled and vertical TLD framework, thereby reinforcing brand credibility and user trust.

(2) Objectives 1) Provide an exclusive digital identity for intended registrants a. Intended registrants: Doubao and its affiliated entities. In accordance with ICANN's Brand TLD framework, registration will not be available to third parties without a direct brand or business connection to Doubao. b. Specific objective: To equip these registrants with reliable domain names that clearly distinguish official services, proprietary content channels, and brand entry points. This helps build a transparent and verifiable "Doubao-branded ecosystem" across the Internet, ensuring coordinated management of the brand's digital assets.

2) Deliver trusted, high-quality content to end users a. Target users: Doubao's global audience b. Specific objective: Users will be able to seamlessly access platform-verified official content and services through the ".Doubao" domain.

(3) Ongoing and Planned Activities 1) Brand protection and ecosystem security: Leverage the exclusive TLD's governance capabilities to establish effective brand safeguards and uphold the security and order of the community ecosystem. 2) Creator and community enablement: As Doubao's creator ecosystem continues to expand, this branded digital space will provide creators with enhanced support and brand endorsement, promoting sustained production and dissemination of high-quality content. 3) Enhancing brand credibility: Provide a unified, trusted digital entry point for all Doubao-branded services, deepening user confidence in content and services associated with the brand.

2. Explanation of Long-Term Sustainability The long-term sustainability of these objectives is anchored in Doubao's mature commercial operations, sound financial standing, and resilient corporate governance:

(1) Operational continuity: The applicant is a legally established entity with a clear long-term business roadmap, offering the fundamental legal assurance for the enduring holding and operation of the TLD. (2) Financial strength: With a consistent record of profitability, the applicant has the financial capacity to cover the TLD's ongoing operational costs—including technical infrastructure, personnel, and marketing—over the long term. (3) Governance stability: The applicant maintains a clear and stable ownership structure and management team. This stability ensures that the TLD's strategic and operational direction can be executed consistently over time.

Based on our long-term corporate vision, sustained profitability, sound governance framework, and thriving content and commercial ecosystem, the objective of securing and operating ".Doubao" is both well-defined and enduringly sustainable.

§ 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 proposed operation of the ".Doubao" top-level domain fully complies with the requirements set forth in Section 3(d) of Specification 11 of the Base Registry Agreement and does not create any conflict. The rationale is as follows:

I. ".Doubao" is a Brand TLD String and Is Not Subject to Section 3(d) of Specification 11 Under the express definition provided in Section 3(d) of Specification 11, the restrictive provisions therein apply solely to generic strings, defined as strings 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. ".Doubao" is a clearly identifiable Brand TLD string, supported by the following grounds:

1. "Doubao" is a valid registered trademark, identifying Doubao and its specific products and services, rather than serving as a generic term for any class of goods or industry.

2. This Application is submitted under the application category established by ICANN specifically for brands, which is designed to permit brand owners to operate an exclusive domain space corresponding to their trademarks. Accordingly, the restriction set forth in Section 3(d) of Specification 11—which prohibits the imposition of eligibility criteria that limit registrations exclusively to a single person or entity and/or that person's or entity's affiliates—does not apply to this Application.

II. The Operational Model Is Consistent with the Purpose of a Brand TLD and ICANN Policy As a Brand TLD, the operational arrangements for ".Doubao" are as follows:

1. This TLD will serve as a dedicated digital asset for internal use by Doubao. Registration eligibility will be limited to the brand and its affiliates, wholly-owned subsidiaries, and majority-controlled subsidiaries worldwide.

2. Within the scope of use described above, clear and transparent registration and management policies will be established, ensuring that all qualified affiliates are able to register and use domain names fairly under a unified internal governance framework.

3. This registration model confines domain name usage to known and trusted legal entities, thereby effectively mitigating DNS abuse risks and aligning with the security and stability requirements of the Domain Name System.

In summary, as a Brand TLD string, ".Doubao" operates in a manner consistent with the normal use of a Brand TLD and is not subject to the restrictions of Section 3(d) of Specification 11. The Applicant will operate this TLD in accordance with the foregoing description, ensuring its continued compliance with all relevant provisions of the Base Registry Agreement.

Note de lecture

Cette candidature est commentée dans un focus :

§ 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