Application Details
Last published on: 7 October 2026 at 15:37 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--kbt444f
官网
U+5B98 U+7F51
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"
official website, the authorised official web portal for an enterprise, organisation or brand.
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.
/ku̯an˥˥ wɑŋ˨˩˦/
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 "official website") is a purpose-driven, Chinese-script generic top-level domain created to serve as a certified namespace for verified official digital presences worldwide. Its mission is to serve the global Chinese-speaking community by providing a trusted digital identity layer. The structural integrity and eligibility policies of the 官网 TLD aim to ensure that hosted platforms represent authenticated, authorized websites, thereby protecting consumers from phishing, counterfeit sites, and deceptive online fraud. Target Registrants The 官网 TLD is accessible to legally established businesses, government agencies, non-profit organizations, educational institutions, and individuals operating verified digital platforms. All registrants must comply with mandatory third-party validation procedures, proving legitimate entitlement to or authorization of the corresponding brand, trade name, or legal entity name. This mechanism ensures that every active 官网 domain represents a genuine official presence, ranging from multinational corporations to local community groups. Target Users Primary users are Chinese-speaking consumers worldwide seeking safe, unambiguous access to official websites for purchases, professional services, information, or government transactions. By navigating to a domain such as brand.官网, users can confidently rely on its authenticity as an official channel, significantly reducing risks of financial loss, identity theft, and counterfeit goods. Secondary users include the registrants themselves, who gain enhanced brand credibility, heightened consumer confidence, and a distinct competitive advantage through a verified "official website" identifier, ultimately boosting customer retention and user conversion. Activities to Fulfill the Mission 1. Rigorous Verification Framework: Develop and enforce an objective registration policy requiring independent third-party validation of legal identity, trademark rights, or official authorizations, leveraging strategic partnerships with accredited certification and registration authorities. 2. Public Awareness Campaigns: Collaborate with consumer rights protection organizations, cybersecurity bodies, and global Chinese-language media to promote 官网 as a recognizable seal of digital authenticity, educating internet users on utilizing the TLD to mitigate online scams. 3. Security Best Practices: Provide registrants with standardized implementation guidelines for DNSSEC, HTTPS deployment, and advanced anti-phishing technologies to maintain the long-term integrity and trustworthiness of the certified namespace.
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--kbto70f
官網
U+5B98 U+7DB2
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".
official website, the authorised official web portal for an enterprise, organisation or brand.
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 string 官网 (guān wǎng) and its variant string 官網 (guān wǎng) are identical in meaning, pronunciation, and semantic function within the global Chinese speaking user community. They represent the exact same concept: “official website”—a trusted, authoritative online presence of an entity (government, enterprise, institution, or organization). Why the User Community Treats Them as the Same 1. Linguistic & Orthographic Equivalence o Both strings share the identical pronunciation /ku̯än⁵⁵ wɑŋ²¹⁴⁻²¹⁽⁴⁾/ (guān wǎng) in Mandarin Chinese. o They are simplified traditional character variants of the same lexical item, recognized as equivalent in all Chinese language standards (e.g., CDNC IDN tables, Unicode, and ICANN RZ LGR for Chinese). o The Chinese script community universally accepts simplified traditional pairs as interchangeable for the same meaning. 2. User Expectation & Practical Use o Chinese Internet users (in mainland China, Hong Kong, Macau, Taiwan, Singapore, and global diaspora) automatically interpret 官网 and 官網 as referring to the same authoritative namespace. o No semantic distinction exists between the two strings; both signal “official website” with identical trust and recognition cues. o The variant exists solely to accommodate regional script preferences (simplified in mainland China; traditional in Hong Kong, Macau, Taiwan, etc.) while preserving the core meaning. 3. ICANN & IDN Framework Recognition o Under ICANN’s IDN variant rules and Chinese LGR guidelines, simplified traditional character pairs like 官网 / 官網 are formally classified as equivalent variant strings with identical semantic intent. o The Chinese Domain Name Consortium (CDNC) and ICANN’s Chinese script community explicitly validate such pairs as “same meaning variants” for IDN deployment. ________________________________________ Three Bona Fide Real World Examples These examples demonstrate actual, widespread use where 官网 and 官網 are treated as interchangeable, equivalent identifiers for official websites: Example 1: Government & Public Institution Usage • Primary: 中华人民共和国外交部官网 (Ministry of Foreign Affairs, PRC Official Website) • Variant: 中華人民共和國外交部官網 • Context: Both strings are used interchangeably across mainland China (simplified) and Hong Kong/Taiwan (traditional) government portals, press releases, and official communications. Users in all regions recognize both as referring to the same authoritative foreign ministry website. Example 2: Corporate Brand & Trademark Use • Primary: 华为官网 (Huawei Official Website) • Variant: 華為官網 • Context: Huawei uses both strings in global marketing, domain registrations, and user interfaces. Consumers and business partners in mainland China (simplified) and Taiwan/Hong Kong/Southeast Asia (traditional) instantly associate both with Huawei’s official online platform, with no perception of difference in meaning or authority. This is consistent with standard multinational brand practice for Chinese IDNs. Example 3: Media & Public Service Platforms • Primary: 央视网官网 (CCTV Official Website) • Variant: 央視網官網 • Context: China Central Television (CCTV) employs both strings in cross region content delivery. Viewers and users across all Chinese speaking regions accept both as the official, trusted domain for CCTV’s online services, with the variant only reflecting script preference—not a change in the website’s official status or identity. ________________________________________ In summary, the global Chinese user community unambiguously regards 官网 and 官網 as the same string in meaning and function, with the variant serving only regional script accessibility while preserving the core purpose of identifying official websites.
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 variant string 官網 provides critical linguistic, regional, and usability benefits by supporting the traditional Chinese writing system, while maintaining the same semantic meaning of “official website” as the primary string 官网. This variant ensures that Chinese speaking users who read and write in traditional characters can easily recognize, trust, and register the authoritative label for official websites, without confusion or barriers caused by script differences. The introduction of the variant enhances inclusivity, improves user experience, strengthens online trust, and reduces the risk of misregistration or user confusion across different Chinese speaking regions. Beneficiary user communities include: • Internet users in regions using traditional Chinese, including Taiwan, Hong Kong, Macau, and related overseas communities. • Enterprises, brands, and institutions operating in traditional Chinese markets. • Governments, public institutions, and media agencies publishing content in traditional Chinese. • Global Chinese users, registrars, and Internet service providers seeking consistent and authoritative “official website” identifiers across both simplified and traditional Chinese environments. 1. Why One Label Is Insufficient and Multiple Labels Are Necessary A single label is insufficient because simplified and traditional Chinese are two distinct but equivalent writing systems used across separate major user communities, with strong regional, linguistic, and cultural expectations. • The primary string 官网 is optimized for regions using simplified Chinese. • The variant string 官網 is required to serve regions using traditional Chinese. Using only one script would create significant user barriers: users would fail to recognize the string in their native writing system, reducing usability, credibility, and adoption. Cultural and linguistic drivers demand both forms to ensure equal access, clarity, and authenticity for all Chinese speaking users. The two strings are necessary to fulfill regional language practices and ensure the “official website” meaning is universally understood across the entire Chinese speaking Internet community. 2. User Communities Served by Primary and Variant TLDs User Community for Primary String 官网 (Simplified Chinese) • Mainland China users, enterprises, governments, and institutions. • Global users and organizations that use simplified Chinese in their digital services. User Community for Variant String 官網 (Traditional Chinese) • Users, businesses, and organizations in Taiwan, Hong Kong, Macau. • Traditional Chinese speaking communities in Southeast Asia and global overseas regions. • Institutions and brands operating multilingual / multi script Chinese websites. 3. How User Needs Are Reflected in IDN Table Design The IDN tables for the primary string 官网 and variant string 官網 are structurally consistent and semantically aligned, reflecting shared user needs for a secure, authoritative “official website” namespace. At the same time, the tables support the separate simplified and traditional character forms to match regional script preferences. • Similarities: Both strings share identical meaning, pronunciation, purpose, and registration policies. The IDN tables enforce the same valid character set structure, variant logic, and community based usage rules to preserve the authoritative identity of the “official website” label. • Differences: The IDN tables separately encode the simplified character 网 and traditional character 網 to comply with Unicode standards, ICANN LGR principles, and regional script conventions. This design ensures that: • User trust and recognition are preserved in each region. • Both communities receive a native script label that matches their linguistic habits. • The overall mission, security, and authority of the gTLD are maintained consistently across both primary and variant strings.
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.
Steps to Minimize Operational and Management Complexities 1. Unified Registry Backend System & Single EPP Interface The applicant will operate 官网 and 官網 on a single, shared technical platform with a unified EPP server interface. • A single set of EPP commands and response codes will apply to both TLDs. • Registrars will not need separate API integrations, separate connections, or separate technical configurations. • Domain lifecycle operations (create, renew, transfer, delete, update) will behave identically across both strings. This reduces integration complexity for registrars. 2. Consistent Policies & Eligibility Rules Across Both TLDs The applicant will maintain identical registration policies, eligibility requirements, and terms of service for 官网 and 官網. • Same registration eligibility (official institutions, enterprises, government bodies, verified organizations). • Same registration periods, renewal rules, transfer policies, and dispute resolution mechanisms. • Same sunrise, land rush, and general availability periods. Registrants and resellers will not need to learn or comply with divergent rules between the primary and variant TLD. 3. Unified Pricing Structure Pricing will be fully aligned between 官网 and 官網，including: • Identical wholesale pricing for registrars. • Identical premium domain naming conventions and pricing logic. • Identical fees for registration, renewal, redemption, and restore. This eliminates financial complexity and removes pricing confusion across the two strings. 4. Shared WHOIS / RDAP Service & Data Model A unified query service will be deployed for both TLDs: • Same data fields, output format, and access mechanisms in WHOIS and RDAP. • Consistent data display, privacy controls, and query rate limits. Users, registrars, and third party services will experience no functional difference in querying domains under either TLD. 5. Synchronized Abuse Management & Compliance Processes Abuse handling, takedown procedures, suspension policies, and compliance reviews will be identical: • Same reporting channels. • Same review timelines and decision criteria. • Same escalation and notification workflows. This ensures registrars and resellers follow a single compliance playbook for both TLDs. 6. Unified Registrar Accreditation & Onboarding Accreditation will cover both TLDs under a single agreement. • One application, one review, one accreditation status. • One set of training materials, documentation, and support portal. No separate onboarding or contractual arrangements are required for the variant string. 7. Simplified Reseller & Registrant Experience From the perspective of registrants and resellers: • Both TLDs represent the same semantic meaning (“official website”). • Both follow identical validation and authentication steps. • Dashboard interfaces, management tools, and customer support will treat the two TLDs as equivalent offerings. This minimizes user confusion and supports intuitive adoption. 8. Dedicated Support & Documentation Framework Unified technical documentation, FAQs, guides, and support services will be maintained: • Single knowledge base covering both TLDs. • Single support contact for technical and policy issues. • Regular joint notifications for system maintenance, policy updates, or operational changes. 9. Monitoring & Continuous Improvement The applicant will regularly monitor registrar feedback and operational metrics to identify and eliminate unnecessary frictions. Any future system updates or policy changes will be applied consistently to both TLDs to preserve operational simplicity. Commitment All measures described above constitute binding commitments. The applicant will include these obligations in the Registry Agreement to ensure long term operational consistency, reduce complexity, and protect registrars, resellers, and registrants from unnecessary burden related to the variant string.
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