Application Details

Last published on: 7 October 2026 at 15:36 UTC

Application Type: Replacement String

Primary String: xn--uir314m (钱包)

TLD Variants:

xn--uirx50m (錢包)

TLD Types: IDN

Application ID: BGNT2696T-T95227-R

Application Priority Number: --

Application Status: Active

Processing Stage: Pre-Evaluation Processing

Comment Period: --

View:

Summary Responses Clarifying Questions Change Requests Documents Objections

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.

AGB Q1. Full Legal Name

Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.

Beijing Guoxu Network Technology Co., Ltd.

AGB Q2. Doing Business As

Provide the name under which the applying entity is doing business, if different from the full legal name answered in Question 1. Such a name must be registered with appropriate local jurisdiction or public authority.

Beijing Guoxu Network Technology Co., Ltd.

AGB Q3. Legal Entity Form/Business Structure

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.

Limited Liability Company (Invested or Controlled by Natural Person(s))

AGB Q4. Jurisdiction

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.

Beijing, China

AGB Q10. Website URL

Provide the website URL of the applying entity, if available.

https://www.xdns.cn/

AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?

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

AGB Q12. If "Yes", explain.

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 ICANN accredited registrar (IANA ID:1494).

AGB Q13. Is the applying entity a back-end registry service provider (RSP), an ICANN-approved data escrow agent, an emergency back-end registry operator, a Uniform Rapid Suspension (URS) service provider, an ICANN dispute resolution service provider, a Privacy or Proxy Service Provider, or a Reseller?

Choose Yes or No.

false

AGB Q17. Phone Country Code

AGB Q18. Primary Business Phone

Provide the primary business phone number without including the country code.

01051192213

AGB Q19. Primary Business Email Address

Provide the primary business email address of the applying entity.

overseas@guoxuwang.cn

AGB Q20. Address Line 1

Enter the street address (no PO Box).

No. 18 Zhongguancun East Road, Haidian District

AGB Q21. Address Line 2

Unit 02, 20F, Block C, Caizhi International Mansion, Building 1

AGB Q22. Locality

Enter the city, village, municipality, etc.

Beijing

AGB Q23. State/Province/Region

Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.

Beijing

AGB Q24. Postal Code

1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.

100083

AGB Q25. Country Code of Location

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

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.

AGB Q221. 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.

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.

Has Documents

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.

AGB Q116. Applied-for Primary String (ASCII Label)

xn--uir314m

AGB Q117.1 Applied-for Primary String (U-Label)

钱包

AGB Q117.2 Applied-for Primary String (Code Points)

U+94B1 U+5305

AGB Q118. What is the meaning/definition of the applied-for gTLD string?

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"

.钱包 represents a personal digital wallet and digital asset management, providing internet users with an exclusive and intuitive Chinese digital identity for managing personal digital storage, credentials, and online assets.

AGB Q119. Script of String

If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)

Chinese (Han)

AGB Q120. Phonetic Representation

Provide a representation of the string according to the International Phonetic Alphabet.

/tɕjɛn pɑʊ/

AGB Q121. 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.

Confirm the statement using a checkbox.

true

AGB Q133. What is the mission and purpose of the applied-for gTLD?

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.

1. Mission and Objectives of the .钱包 TLD (1) Mission The ".钱包" (Chinese for "wallet") is a personal digital asset namespace designed for global individual internet users. It focuses primarily on personal digital asset management, providing internet users with exclusive, intuitive, and Chinese digital identities to gather, present, and manage all types of personal online assets. The ".钱包" TLD enriches the diversity of the DNS ecosystem, promotes the UA of multilingual domains, and fully complies with ICANN’s core principles of Internet security, stability, and global public interest. (2) Objectives Personal Digital Asset Identification: Offer dedicated domain space for individuals to store and display full-spectrum personal digital assets, including digital collections, personal copyright works, online membership rights, virtual assets, digital certificates, personal cloud assets, and personalized digital portfolios. Digital Asset Transaction Scenario Building: Establish a credible, standardized personal digital asset trading portal for global internet users, realizing standardized online trading support for diverse digital assets. Lower Barriers for Individual Internet Users: Leverage the simple and intuitive Chinese word to eliminate language barriers, enabling ordinary users to own personal domains. Diversify Global DNS Ecosystem: Expand Chinese IDNs, enrich personalized domain resources in the global domain market. 2. Intended Registrants and Users Registrants: Global individual internet users, digital asset collectors, independent freelancers, personal brand operators, digital life enthusiasts, and internet users in all industries. End Users: Global internet visitors who browse, view, and verify personal digital assets, works, credential information, and digital portfolios of registrants. 3. Activities for Objective Realization Stable ICANN-Compliant Infrastructure: Maintain high-availability, fully redundant registry technical infrastructure with regular security audits and vulnerability inspections to sustain long-term stable DNS resolution for massive personal user access. Global Open Registration Channels: Cooperate with ICANN-accredited registrars worldwide to provide convenient, low-threshold, open registration services, ensuring universal public accessibility. Universal Acceptance Promotion: Continuously promote the compatibility and popularization of Chinese domains, advance UA implementation on mainstream browsers, search engines and internet platforms. Personal User Ecosystem Construction: Guide and encourage the use of ".钱包" domains for personal daily digital life management. Strict Anti-Abuse and Risk Control: Execute standardized Sunrise and Trademark Claims procedures, enforce UDRP and URS policies, and maintain real-time monitoring to prevent illegal abuse, fraud and malicious squatting, protecting the legitimate rights and interests of individual users. 4. Long-Term Sustainability Permanent Universal Personal Demand: With the continuous expansion of personal digital assets, individual demands for digital property sorting, personal identity aggregation and online asset display are long-term, rigid, and growing steadily, ensuring sustainable registration needs for the TLD. Wide Scenario Adaptability: The TLD is not limited to financial payment scenarios. It adapts to all personal digital life scenarios with strong market universality and anti-risk capability. Stable and Healthy Business Model: Sustainable revenue comes from public individual domain registrations and standardized value-added services for personal users. Sufficient financial reserves ensure long-term technical operation, security maintenance and ICANN compliance costs. Continuous Alignment with ICANN Public Interest Goals: The TLD continues to promote multilingual internet development, enrich personalized domain resources, protect individual user rights, and maintain fair and transparent domain market competition.

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.

AGB Q122. Applied-for Variant(s)

xn--uirx50m

AGB Q123.1 Variant String (U-Label)

錢包

AGB Q123.2 Variant String (Code Points)

U+9322 U+5305

AGB Q124. Script of Variant String

Provide the script of the variant string (both in English and as referenced by the RZ-LGR/ISO 15924)

Chinese (Han)

AGB Q125. 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?

Select an option.

New TLD

AGB Q126. What is the meaning/definition of the variant string?

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".

“.錢包” is the Traditional Chinese version of “.钱包”, meaning “wallet”, and represents the same personal digital wallet and digital asset management namespace with identical meaning, purpose, and intended use.

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

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 “.钱包” and its Traditional Chinese version “.錢包” represents the same Chinese lexical item. Both are standardized forms of written Chinese and are universally understood by Chinese-speaking communities to have the same pronunciation, semantic meaning, and conceptual reference. The distinction between the two strings exists solely because of the different writing systems adopted by different Chinese-speaking regions. Users in Chinese mainland generally use Simplified Chinese, whereas users in Hong Kong SAR, Macao SAR, Taiwan, and many overseas Chinese communities primarily use Traditional Chinese. Despite these orthographic differences, both user communities recognize the two strings as referring to the same concept. Consequently, users naturally perceive “.钱包” and “.錢包” as equivalent identifiers representing the same namespace in different writing systems. The relationship between Simplified and Traditional Chinese is well established within Unicode, IDNA implementation practices, and the Label Generation Rules (LGR) framework adopted for Chinese IDN variants. The introduction of the Traditional Chinese version does not introduce any semantic ambiguity but instead preserves linguistic consistency and improves usability across Chinese-speaking communities. Accordingly, we consider the two strings to be equivalent representations of the same TLD for linguistic, functional, and user-recognition purposes.

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

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.

The introduction of the applied-for variant string “.錢包”(Traditional Chinese version of “.钱包”) will enhance accessibility, inclusiveness, and usability for Traditional Chinese-speaking internet users while maintaining full consistency with the primary applied-for string. Chinese is one of the world's most widely used languages and exists in two officially recognized writing systems. Supporting both Simplified and Traditional Chinese reflects established linguistic practice and enables users to interact with the domain name system in the writing system that they naturally use. This improves readability, recognition, and user confidence while reducing potential confusion arising from script differences. The “variant” string will primarily benefit individuals, organizations, businesses, educational institutions, digital service providers, and online communities that communicate primarily in Traditional Chinese, including users in Hong Kong SAR, Macao SAR, Taiwan, and overseas Chinese communities around the world. The availability of this string also supports the broader goals of Universal Acceptance (UA) by encouraging wider adoption of multilingual domain names and promoting equal access to the Domain Name System regardless of language or script preference. We believes that introducing the Traditional Chinese version contributes to a more inclusive, multilingual, and user-friendly Internet while preserving the security and stability of the DNS.

AGB Q129. 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.

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 will operate the primary string ".钱包" and its allocatable version ".錢包" in accordance with the principles established for Chinese IDNs, including the recommendations described in RFC 4713 (Registration and Administration Recommendations for Chinese Domain Names), the applicable Chinese Label Generation Rules (LGR), and relevant ICANN policies governing variant gTLDs. Consistent with long-established practices for Chinese domain names, we will implement the principles of Simplified–Traditional equivalence, unified registration, mandatory variant allocation, and no additional registration fee for reserved or bundled variants. Registrants registering either the Simplified or Traditional form will obtain the corresponding variant under a single registration relationship, thereby preventing conflicting registrations, reducing user confusion, and providing a consistent user experience across both writing systems. Both strings will be operated under a single registry management framework with identical Registry Policies, Registration Policies, Rights Protection Mechanisms, Acceptable Use Policies, and technical standards. Variant domain names will follow synchronized lifecycle management throughout registration, renewal, transfer, deletion, restoration, and expiration. We will implement variant management in accordance with the applicable Chinese LGR and ICANN requirements. Registry systems will maintain consistent registration data, DNS and DNSSEC configuration, EPP services, RDAP/WHOIS services, abuse mitigation procedures, and reporting processes across both the primary and variant strings. To minimize operational complexity for registrars, resellers, and registrants, we will provide unified technical documentation, implementation guidance, and policy information. Operational procedures, staff training, and change management processes will also be managed consistently across both strings to ensure interoperability, minimize user confusion, and preserve the security, stability, and resiliency of the DNS.

AGB Q130. 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).

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.

AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

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.

AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q167. Would most people think that (domains in) the TLD(s) in the application are used for activities that require regular government reporting, inspections, and oversight in various countries? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

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.

AGB Q169. Would most people think that the TLD is used for something usually done by governments? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

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.

AGB Q170. Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Registry Agreement (RA) voluntarily regardless of ICANN’s Safeguard Assessment outcomes?

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).

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.

AGB Q172. Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Registry Agreement (RA) that are unique to your applied-for string?

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.

Application Details

Application Responses

Section: Applying Entity Information

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

Section: DNS Abuse

Section: Primary String

Section: Variant String(s)

Section: Safeguard Identification

Section: Registry Voluntary Commitments (RVCs)

Section: Brand & Code of Conduct Exemptions

Section: Additional Information and Supporting Materials

Section: Bona Fide Intent and Prohibited Communications