Application Details
Last published on: 7 October 2026 at 15:25 UTC
Application Responses
Section: Applying Entity Information
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.
Internet DotTrademark Organisation Limited
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/Body Corporate
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.
Hong Kong, China
Provide the website URL of the applying entity, if available.
https://www.trademarkdomain.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).
true
1. Specify if the applying entity is an existing registry operator, ICANN accredited registrar, and/or an Affiliate of a registry operator and/or registrar. 2. If the applying entity is an Affiliate, provide the details of such Affiliate relationship, including the name of the affiliated registry operator and/or registrar. 3. If the applying entity is an ICANN accredited registrar, specify the registrar ID number.
The applying entity is an existing registry operator for the TLDs .xn--czr694b and .xn--imr513n. The applying entity (Internet DotTrademark Organisation Limited, Hong-Kong SAR) and ShangYu Global Technology Co., Ltd. are entities subject to the same ultimate controlling party. Both entities are ultimately controlled by the same natural-person controller through an intermediate Cayman Islands holding company. ShangYu Global Technology Co., Ltd. (IANA ID 3813) is an ICANN-accredited registrar. Jiang Yu Liang Cai Technology Company Limited, a wholly-owned subsidiary of ShangYu Global Technology Co., Ltd., acts as the registry operator for the delegated gTLD .xn--otu796d. There is no direct shareholding between the Hong Kong-based applicant entity and either the accredited registrar or its registry operator subsidiary. Ultimate control is exercised via the top-level Cayman Islands holding platform.
Choose Yes or No.
false
86
Provide the primary business phone number without including the country code.
13521738308
Provide the primary business email address of the applying entity.
sunxuejie@tdnnic.org
Enter the street address (no PO Box).
Rm 1502, Building 7, No. 9 Shouti South Road, Haidian District
Enter the city, village, municipality, etc.
Beijing
Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.
Beijing
1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.
100037
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.
DotTrademark Holding Limited
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.
Business Company Limited by Shares/Body Corporate
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.
British Virgin Islands
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.
DotTrademark Holding Group
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.
Exempted Company Limited by Shares/Body Corporate
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.
Cayman Islands
Section: Applying Entity Background and Organization
This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.
Xiongwei Huang
Xiongwei Huang, Yangyi Wu
DotTrademark Holding Limited
Xiongwei Huang
Xiongwei Huang
Section: Self-Certification
Provide a single document for Self-Certification question Q2.2-1. The document must include only the SC2.2-1.1, SC2.2-1.2, or SC2.2-1.3 statements. Do not modify any of the Self-Certification statements.
1. Provide a single document for Self-Certification question Q2.2-1. 2. The document must include only the SC2.2-1.1 through SC2.2-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC2.2-1.1 through SC2.2-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC2.2-1.1 through SC2.2-1.3 statements.
Section: Operational/Planning
The document for Q2.3.1 must be a PDF. The document for Q2.3-2 must be an Excel (.xlsx) file.
The document for Q2.3-1 must be a PDF.
Section: Security Policy and Planning
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.
Section: DNS Abuse
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.
Section: Primary String
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--gmq502atzh
数字人
U+6570 U+5B57 U+4EBA
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"
"数字人" means "Digital Human" in Chinese ("数字"=digital; "人"=human). In our opinion, the string literally represents an intelligent virtual avatar, AI-powered agent, or digital identity.
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.
/ʂu˥˩ tsɿ˥˩ ʐən˧˥/
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.
Mission and Purpose of the 数字人 gTLD The IDN gTLD "数字人" (Chinese for "digital human") is a purpose-driven generic top-level domain created as a secure, dedicated namespace for digital humans, AI agents, and virtual identities worldwide. Its mission is to provide an intuitive, culturally resonant digital identity layer for the global Chinese-speaking community. By establishing a reliable naming system for everything from brand virtual spokespersons to personal AI companions, the 数字人 TLD fosters consumer trust, streamlines access to AI services, and proactively protects against impersonation in an era of proliferating synthetic media. Target Registrants The TLD serves two core registration groups: 1. Enterprises and Organizations: Companies deploying brand digital humans, business AI agents, virtual customer-service assistants, or virtual influencers. Registrants must demonstrate legitimate ownership or authorized development of the associated digital asset. 2. Individual Creators and Users: Persons creating personal digital twins, virtual avatars, AI companions, or personal AI assistants. Appropriate identity verification and proof of connection to the digital asset will be enforced to mitigate domain abuse. Target Users Primary users are Chinese-speaking consumers worldwide interacting with these digital humans for customer support, entertainment, information, or companionship. Accessing a 数字人 domain assures them of an authentic, secure endpoint rather than a spoofed interface. Secondary users include the registrants themselves, who gain a memorable, trusted channel to manage and promote their AI entities. Developers and platform providers also benefit from a standardized namespace that facilitates discovery and interoperability across the growing digital human ecosystem. Activities to Fulfill the Mission To realize this mission, the registry will undertake the following activities: 1. Strict Registration Verification: Enforce eligibility policies requiring registrants to substantiate ownership or authorized representation of the claimed digital asset, deterring cybersquatting. 2. Awareness and Promotion: Collaborate with AI industry alliances, virtual human conferences, and Chinese-language tech media to position the 数字人 TLD as the definitive trust mark for AI identities. 3. Security and Trust Guidelines: Provide best-practice documentation covering anti-phishing, anti-spoofing, and secure API connections, ensuring only legitimate entities control AI endpoints. 4. Abuse Mitigation: Operate 24/7 monitoring and a rapid suspension mechanism to address malicious activities such as fraudulent customer-service bots or deceptive virtual influencers. 5. Advisory Panel: Establish a cross-sector advisory body comprising AI ethics and identity experts to guide policy evolution as synthetic media technologies advance. 6. Pioneer Program: Launch an initiative with leading brands and virtual influencers, publishing case studies that demonstrate measurable improvements in consumer trust and operational efficiency. Long-Term Sustainability The 数字人 TLD leverages the secular growth of the digital human economy across customer service, live commerce, and personal AI companionship. As AI agents become ubiquitous, the risks of phishing and deceptive look-alike interfaces intensify; a dedicated namespace acts as a critical authenticity anchor to protect consumers. Steady registration and renewal revenue from a growing pool of enterprise and individual users will fund ongoing security enhancements, policy updates, and global outreach. The registry operator, leveraging cultural insights and technical agility, will ensure the namespace remains secure, relevant, and robust over the long term.
Section: Variant String(s)
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--gmq502ai0h
數字人
U+6578 U+5B57 U+4EBA
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".
"数字人" means "Digital Human" in Chinese ("数字"=digital; "人"=human). In our opinion, the string literally represents an intelligent virtual avatar, AI-powered agent, or digital identity.
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 数字人 (Simplified‑Chinese) and its variant 數字人 (Traditional‑Chinese) carry exactly the identical literal‑meaning of “digital‑human, computer‑generated virtual‑human avatar”. Simplified‑Chinese and Traditional‑Chinese are two standardized character forms sharing the same origin within the Chinese‑language system. Chinese‑speaking communities across mainland‑China, Hong‑Kong, Macao, Taiwan and overseas‑Chinese societies universally regard these two character variants as one single vocabulary term. Net‑users treat them as interchangeable when searching for digital‑human‑related brands, technical‑services and industrial‑information. Three bona‑fide real‑world use‑cases are listed below： Major‑AI‑tech‑enterprises including Baidu Xiling, iFlytek and Silibase‑Intelligent use both simplified‑character “数字人” and traditional‑character “數字人” on official‑websites, social‑media channels and overseas‑business materials, naming their virtual‑avatar‑product. Commercial‑service scenarios, such as airport‑guide digital‑staff, exhibition‑host virtual‑presenters and live‑streaming avatars, adopt both‑character forms for market‑promotion targeting mainland‑users and traditional‑Chinese‑speaking overseas‑clients. Industry‑media, intellectual‑property‑documents and cross‑border‑trademark‑registrations treat “数字人 / 數字人” as the‑same‑vocabulary, applying the‑same‑brand‑name for AI‑virtual‑human‑business layout in Chinese‑speaking‑regions.
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.
1. Reasons why a single label cannot satisfy multi‑region Chinese‑speaking demands Simplified‑Chinese and Traditional‑Chinese are two mainstream, widely‑used writing systems of the same Chinese language. Simplified characters are the official script in mainland China, while Traditional‑Chinese characters are the standard written form adopted in Hong Kong SAR, Macao SAR, Taiwan region and numerous overseas‑Chinese communities across Southeast Asia, Europe and North America. One single simplified‑Chinese label “数字人” cannot accommodate the reading habit, local language custom and brand‑asset demands of traditional‑Chinese‑using groups. Two variant domain‑name labels are required to cover segmented Chinese‑language markets and meet regional‑linguistic‑cultural requirements. 2. Beneficiary user‑communities for primary and variant string Primary string 数字人 (Simplified‑Chinese) Target‑user groups: mainland‑China‑based AI‑tech firms, virtual‑human operators, brand‑owners, intellectual‑property agencies and local internet visitors who use simplified‑Chinese in daily browsing and brand layout. Variant string 數字人 (Traditional‑Chinese) Benefiting communities: enterprises and internet users from Hong‑Kong, Macao, Taiwan, overseas‑Chinese‑funded companies, cross‑border brands and Chinese‑speaking overseas‑netizens accustomed to traditional‑character writing habits. 3. IDN table design similarities and differences Similarity Both the primary and variant TLDs share the identical registry‑service framework, anti‑cybersquatting mechanism, sunrise registration policy for trademark holders, technical operation standard and intellectual‑property‑protection rule. Their core positioning is to serve the digital‑human‑related brand‑domain‑name protection. Difference Their IDN character sets are configured separately: the primary TLD applies simplified‑Chinese character table, and the variant TLD loads the traditional‑Chinese character set. The independent character‑scheme design avoids character‑confusion and provides script‑adapted domain‑name resources for different Chinese‑script‑using regions.
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.
We adopt a full set of standardized, coordinated management measures to reduce operational burdens for registrars, resellers and domain name registrants, and lower the management complexity brought by the two variant gTLDs. Detailed arrangements are listed as below: 1. Unified technical registry system and consistent service specification The primary .数字人 and variant .數字人 share one set backend technical infrastructure, domain name query system, WHOIS service, DNS server cluster and system maintenance workflow. Identical API interfaces are supplied for all cooperating registrars and resellers. Registrars do not need to deploy two separate sets of access programs, which cuts technical access costs. 2. Unified registration policy, fee standard and business rule We keep consistent regulations covering sunrise period, trademark claim procedure, domain name price, renewal fee, transfer rule, redemption period policy and anti cybersquatting mechanism for both variant top level domains. Registrars and registrants follow the same business rules when handling simplified Chinese and traditional Chinese domain resources. 3. Synchronized variant domain reminder and bundled registration service We supply clear reminder notices for simplified traditional Chinese variant pairs in the registration page. When a registrant applies for one domain name variant, the system will remind the applicant of its corresponding Chinese character variant resource. We support one click bundled registration, helping trademark owners to complete the layout of both variant domains conveniently. 4. Unified channel for complaint, rights protection and customer service We build one stop service channels including work orders, customer support mailbox and trademark dispute processing workflow. Registrars and registrants can submit domain related applications, abuse reports and rights protection demands via a single entrance for both two variant gTLDs. 5. Unified training, official document and public notice system for partners All registrars and resellers receive the same operational guide, policy update notification and business training. We will release synchronous policy announcements, so partners are kept informed of adjustments for both variant TLDs at the same time. 6. Independent character set isolation while avoiding cross variant disturbance Two IDN character tables are reasonably configured. We set character recognition isolation to prevent garbled code and character confusion failures, and we will strictly abide by ICANN variant string management requirements throughout the whole life cycle of domain name operation.
Confirm the statement using the checkbox.
true
Section: Safeguard Identification
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).
No
Section: Registry Voluntary Commitments (RVCs)
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
Section: Brand & Code of Conduct Exemptions
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
No
This serves as an indication of intent to apply for an exemption to Specification 9 and that the applying entity is NOT requesting to be designated a .Brand TLD, pursuant to Specification 13.
No
Section: Additional Information and Supporting Materials
This question set collects any additional information that the applying entity would like to provide, including any supporting materials.
Section: Bona Fide Intent and Prohibited Communications
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