.商标

Q2.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) of the applying entity, 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: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.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.

Answered with a document. Attachments are not published by ICANN.

Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).

Answered with a document. Attachments are not published by ICANN.

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.

Answered with a document. Attachments are not published by ICANN.

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.

Answered with a document. Attachments are not published by ICANN.

Script of String

Chinese (Han)

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

Applied-for Primary String (U-Label)

商标

Applied-for Primary String (Code Points)

U+5546 U+6807

Script of Variant String

Chinese (Han)

Is this variant string for an existing gTLD that is already operated by the applying entity or for a newly applied-for string in the 2026 Round?

Existing TLD

What is the meaning/definition of the variant string?

Trademark

Explain how the primary applied-for and variant strings are considered the same, including the meaning, by the relevant user communities.

The primary string 商标 (Simplified Chinese) and variant string 商標 (Traditional Chinese) are semantically identical, conceptually equivalent, and universally interchangeable within all global Chinese-speaking communities. The two strings solely differ in orthographic writing form, both exclusively representing the single legal and commercial meaning of “trademark”, with no distinction in definition, function, or public perception.

Three bona-fide real-world examples proving equivalence:

1. Cross-jurisdictional official IP regulatory usage Chinese Mainland official IP administrations uniformly adopt the Simplified form 商标 in laws, certificates and administrative documents, while Hong Kong, Macao, Taiwan and overseas Chinese regulatory authorities standardly use the Traditional form 商標. All regional IP institutions recognize the two terms as identical and interchangeable in trademark administration and legal affairs.

2. Global enterprise trademark publicity and brand practice Leading Chinese and multinational enterprises use 商标 for Mainland market announcements and 商標 for Hong Kong, Taiwan and overseas Chinese market statements. The two variants are applied in identical trademark protection declarations, brand disclaimer statements and IP publicity scenarios, serving exactly the same commercial purpose.

3. Judicial and legal recognition in trademark dispute cases Courts and judicial authorities across Greater China consistently treat 商标 and 商標 as equivalent legal concepts in trademark infringement litigation. Judicial rulings confirm that Simplified and Traditional versions of the term carry identical legal meaning, with no substantive difference in trademark identification and right protection.

Explain the benefits and the user communities who will benefit from the introduction of the applied-for variant string(s).

1. Why a single label is insufficient; why two labels are necessary The Chinese language employs two standard, culturally and regionally distinct writing systems: Simplified Chinese (used in Mainland China) and Traditional Chinese (used in Hong Kong SAR, Macao SAR, Taiwan region of China, and most overseas Chinese communities globally). These are not mere stylistic variants but official, legally recognized scripts with long-standing usage conventions in business, law, government, and brand identity. A single label (either 商标 or 商標) cannot adequately serve all Chinese speaking communities: • Users in Traditional Chinese regions and overseas communities strongly prefer and rely on 商標 for legal certainty, cultural familiarity, and brand consistency. • Using only Simplified 商标 would create linguistic, cultural, and practical barriers for trademark owners operating in Traditional Chinese markets. • Two labels are necessary to fully respect linguistic diversity, ensure regional inclusivity, and avoid disadvantaging large, distinct user groups that rely on Traditional Chinese for commercial and IP activities. 2. User communities served by primary and variant TLDs • Primary string: 商标 (Simplified Chinese) Serves: • Enterprises, brand owners, and IP users in Mainland China • Organizations using Simplified Chinese for domestic business and trademark protection • Variant string: 商標 (Traditional Chinese) Serves: • Trademark owners and businesses in Hong Kong SAR, Macao SAR, Taiwan region of China • Overseas Chinese communities across Southeast Asia, North America, Europe, and other regions using Traditional Chinese • Multinational brands targeting Traditional Chinese speaking markets • Legal and IP professionals specializing in cross-border Chinese trademark practice 3. How user needs are reflected in IDN table design The primary and variant TLDs share identical core purpose, registry policy, and registration rules (trademark focused, IP protection oriented). Their IDN tables are designed to: • Support equivalent semantic function while respecting script specific encoding and character conventions; • Maintain consistent eligibility, security, and rights protection mechanisms across both labels; • Differ only in the Simplified vs. Traditional character set to match the linguistic expectations of their respective user communities; • Ensure users in each region can register, use, and trust their preferred script without compromising policy consistency or security. This design ensures both TLDs serve the same global trademark protection mission while accommodating legitimate regional and linguistic user needs.

Describe the steps that the applying entity will take to minimize the operational and management complexities of variant gTLDs and variant domain names that impact registrars, resellers and/or registrants.

Steps to Minimize Operational & Management Complexities for Variant gTLDs 商标 / 商標 The applicant commits to implement the following binding measures to eliminate operational complexity for registrars, resellers, and registrants across the primary gTLD 商标 (Simplified) and variant gTLD 商標 (Traditional). These commitments will be formalized in the Registry Agreement per ICANN Section 7.6 and Section 3.1.9.2.1. 1. Unified Registry Platform & Shared Technical Infrastructure • Deploy a single, integrated registry system for both 商标 and 商標 with identical back-end architecture, EPP commands, DNSSEC, and registration data specs. • No separate systems or custom integrations; registrars use one set of technical interfaces to support both TLDs, eliminating dual-platform overhead. 2. Identical Policies, Eligibility & Registration Rules • Maintain fully aligned registration policies, eligibility criteria, TMCH checks, abuse mitigation, and dispute processes across both TLDs. • Registrants face identical terms; registrars avoid conflicting rule sets or divergent compliance burdens. 3. Synchronized Pricing, Promotions & Lifecycle Management • Align registration, renewal, transfer, and restore fees and timelines. • Use synchronized billing cycles and status codes to prevent operational drift and registrar reporting complexity. 4. Unified Registrar & Reseller Support Framework • Provide a single helpdesk, documentation portal, and training program covering both TLDs. • Publish one consolidated registrar manual and API guide to reduce training, integration, and query costs. 5. Consistent IDN Table Design & Script Alignment • Design IDN tables to be structurally parallel, differing only in Simplified vs. Traditional character sets while preserving identical logic, permitted characters, and variant handling. • Ensure uniform parsing, validation, and confusability controls to avoid user or system confusion. 6. Centralized Reporting, Data & Compliance Outputs • Generate consolidated monthly/quarterly reports, registry statistics, and compliance data in a single format. • Simplify ICANN reporting, audit, and reseller reconciliation through unified datasets. 7. Coordinated Brand, Abuse & Rights Protection Services • Operate a single trademark protection engine, abuse monitoring system, and takedown workflow for both TLDs. • Ensure consistent rights protection standards without duplicative processes for rights holders. 8. Binding Long-Term Operational Commitment • The applicant formally commits that the above unified model will be maintained for the full term of the Registry Agreement to ensure long-term stability and minimal complexity. • No divergent policies, systems, or fees will be introduced that would create disparity between the primary and variant TLDs. ________________________________________ Summary of Compliance with ICANN Criteria These measures directly address ICANN’s requirements to limit complexity by: • Using shared infrastructure to avoid redundant systems; • Applying uniform rules to eliminate registrar/registrant confusion; • Aligning IDN table design to reflect linguistic differences without operational divergence; • Establishing binding contractual commitments to sustain the simplified model long-term. This framework ensures stable, low-complexity operation that benefits all users while upholding DNS security, stability, and compliance with ICANN variant string rules.

This applied-for TLD is not a “generic string” using the definition of "generic string" in Section 3(d) of Specification 11 of the Base RA (as described in Question 121).

true

Applied-for Variant(s)

xn--czro89b

Variant String (U-Label)

商標

Variant String (Code Points)

U+5546 U+6A19

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

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