Application Details
Last published on: 7 October 2026 at 15:23 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--npqq54o
防伪
U+9632 U+4F2A
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 "Anti-counterfeiting" in Chinese. In our opinion, the string literally represents an official verification channel for product authenticity.
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.
/fɑŋ˧˥ weɪ˨˩˦/
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 This application for the IDN gTLD "防伪" aims to establish a DNS-native, dedicated namespace for product authenticity verification targeting the global Chinese-speaking community. This gTLD provides brand-owning enterprises with distinctive, highly recognizable domain-name identifiers, allowing consumers to seamlessly identify official verification channels directly from the domain string. The TLD serves three core functions: • Displaying official product anti-counterfeiting and traceability information. • Providing secure, encrypted channels for real-time authenticity verification. • Facilitating consumer complaint submissions regarding counterfeit goods to strengthen rights protection. Target Registrants: Eligibility is strictly restricted to verified organizational entities, including brand manufacturers, consumer-goods producers, intellectual property holders, brand operators, and qualified commodity-traceability service providers. General-purpose registrations by unaffiliated individuals are not permitted to ensure the ecosystem's integrity. Target Users: Global Chinese-speaking consumers, product purchasers, supply-chain distributors, authorized dealers, and intellectual property enforcement practitioners. Planned Activities to Achieve the Purpose 1. Registry Policy Development: Implement strict registration-eligibility rules restricting domain allocations exclusively to compliant enterprises, verified brand owners, and legitimate anti-counterfeiting service providers. Deploy dedicated abuse-handling workflows to mitigate impersonation, phishing, and fake-verification-site risks, while establishing expedited suspension and revocation procedures for malicious or infringing registrations. 2. Market Education and Industry Collaboration: Promote the strategic value of the 防伪 TLD within manufacturing and consumer-goods sectors. Partner with intellectual property protection and traceability-service organizations, publish real-world best-practice guidance, and encourage brands to print 防伪 domain references directly on product packaging, security tags, and user manuals. 3. Technical and Compliance Operations: Maintain highly stable and secure DNS resolution, fulfill all ICANN contractual and consensus policy obligations, and ensure registration data remains accessible via WHOIS/RDAP to brand owners and law enforcement agencies for swift asset verification and trace-back purposes. 4. Anti-Abuse Operations: Continuously monitor the namespace for potential misuse, actively accept trademark-holder complaints, and execute policy-aligned remedial actions against domains exploited for brand impersonation or fraudulent verification portals, thereby preserving the absolute trustworthiness of the TLD ecosystem. Long-Term Sustainability The 防伪 TLD directly addresses the systemic, long-term issues of product counterfeiting and trademark infringement within the global consumer goods sector. It fulfills the rigid, ongoing operational demand of brand enterprises to establish high-integrity verification channels and safeguards long-term consumer rights, anchoring its unique business value firmly in intellectual property protection. By implementing strict pre-registration gating alongside multi-layered anti-abuse protocols, the registry operator will secure the structural trustworthiness and market reputation of the namespace. As more brands adopt the TLD for counterfeit tracking and product authentication, it will further stimulate registration demand, creating a highly resilient positive feedback loop where "registration revenues sustain secure operations, and a trusted digital ecosystem attracts premier global brands," ensuring the stable, long-term sustainability of the gTLD.
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--czq521o
防偽
U+9632 U+507D
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".
The traditional‑Chinese character "防偽" means "Anti-counterfeiting". In our opinion, the string literally represents an official verification channel for product authenticity.
Provide at least three bona-fide examples to support the explanation. (for example, evidence of trademark use by showing real world use cases).
Linguistic Equivalence & Community Perception The primary applied-for string “防伪” (Simplified Chinese) and the variant string “防偽” (Traditional Chinese) are orthographically and semantically identical. Both represent the exact same lexical term meaning "anti-counterfeiting" across all Chinese-speaking communities globally (including Mainland China, Taiwan, Hong Kong, Macao, Singapore, and the global Chinese diaspora). In Chinese orthography: • “防” (fáng) is identical in both Simplified and Traditional Chinese scripts, meaning "to prevent, guard against, or protect". • “伪” (SC, U+4FAA) and “偽” (TC, U+50DE) are standard 1:1 simplified-traditional variant characters, both meaning "fake, counterfeit, or forged". Chinese-speaking internet users naturally recognize “防伪” and “防偽” as two script variations of the same underlying concept. Failing to delegate or bundle these strings together would cause severe user confusion, increase phishing risks, and fragment internet navigation for Chinese users. Furthermore, this relationship is formalized under the ICANN Root Zone Label Generation Rules for the Chinese Script (RZ-LGR) and RFC 3743, where “伪” and “偽” are officially defined as 1:1 allocatable/blocked variants of each other. Bona-Fide Examples Supporting Script & Semantic Equivalence: 1. Domain Name Registry IDN Variant Rules (CNNIC, TWNIC, & HKDNR): Domain registries servicing Chinese-speaking communities (such as CNNIC for .cn, TWNIC for .tw, and HKDNR for .hk) enforce mandatory IDN variant bundling. Under these registries' IDN tables, registering a second-level domain containing 防伪 in Simplified Chinese automatically reserves or maps the corresponding Traditional Chinese string 防偽 for the same registrant. This real-world registry policy proves that the domain industry and user communities treat them as the exact same string. 2. Cross-Regional Industry & Standard Usage (GS1 & National Standards): Global supply chain and product authentication bodies use both script forms interchangeably based on target geography. For example, GS1 (the global barcode and product traceability organization) promotes product authentication services as “防伪追溯” in Simplified Chinese (GS1 China) and as “防偽追溯” or “防偽標籤” in Traditional Chinese (GS1 Hong Kong / GS1 Taiwan). Both refer to identical anti-counterfeiting standards and verification services. 3. Search Engine & Knowledge Base Script Equivalency (Baidu, Google, Wikipedia): Major search engines (Baidu, Google) and universal reference platforms (Wikipedia) treat 防伪 and 防偽 as 100% equivalent keywords. Searching for 防偽 on Google or Baidu automatically matches and highlights indexed pages containing 防伪 without loss of relevance. Wikipedia maintains a single unified entry with real-time automatic script conversion (zh.wikipedia.org/wiki/防伪 ⇄ zh.wikipedia.org/wiki/防偽), confirming that the global internet community considers them semantically inseparable.
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. Regional, Linguistic, and Cultural Drivers A single label is insufficient due to distinct regional writing standards and critical security needs across Chinese-speaking markets: • Regional Orthographic Standards: o Simplified Chinese (SC): “防伪” is the official script in Mainland China, Singapore, and Malaysia. o Traditional Chinese (TC): “防偽” is the official script in Taiwan, Hong Kong, Macao, and overseas Chinese communities. • Semantic & Functional Equivalence: Both strings express the identical concept ("anti-counterfeiting" / "authentication"). Chinese speakers view them as interchangeable. Providing only one label creates technical barriers and DNS resolution failures for users typing in their native script. • Security & Homograph Protection: Anti-counterfeiting TLDs rely on user trust. Delegating only one label leaves the other open to IDN homograph attacks and phishing by malicious third parties. Offering both as a bound pair guarantees DNS integrity and brand security. 2. Benefiting user communities for primary string and its variant 1. Primary string (防伪，simplified Chinese): Target user groups comprise mainland China based trademark holders, domestic brands, local enterprises, individual merchants and mainland Chinese speaking online consumers. These stakeholders are accustomed to simplified character web addresses for anti counterfeit brand verification services. 2. Variant string (防偽，traditional Chinese): Its served communities cover enterprises, trademark owners and online users within Hong Kong, Macao, Taiwan area, alongside overseas ethnic Chinese communities who adopt traditional Chinese as their daily written script. Both local brand holders and overseas Chinese consumers prefer traditional character domain labels for brand authenticity checking. Shared general benefit: Both variants deliver a trusted dedicated namespace for trademark owners to run official anti counterfeit portals, and help global Chinese speaking end users to identify genuine brand websites and avoid phishing and counterfeit scam links. 3. IDN Table Design and Alignment with User Needs The IDN Tables for “防伪” and “防偽” strictly adhere to the ICANN Root Zone Label Generation Rules for Chinese (RZ-LGR) and RFC 3743 / RFC 4790: 1. Symmetric 1:1 Variant Mapping: Character 伪 (U+4F2A) and 偽 (U+50DE) are defined as mutually allocatable variants (防 U+9632 is a self-variant). Requesting “防伪” automatically defines “防偽” as an allowable variant label with symmetrical technical rules. 2. Same-Registrant & Bundling Enforcement: Registry policy mandates that “防伪” and “防偽” must be allocated exclusively to the same registrant and managed under a strict DNS bundling framework. This prevents third-party variant hijacking and satisfies the security requirements of anti-counterfeiting services. 3. Resolution & User Experience Consistency: The IDN table supports synchronized activation and redirection (e.g., CNAME/ALIAS), ensuring users reach the same underlying destination whether they type the Simplified or Traditional variant.
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.
The applicant has formulated a full set standardized operational policies, technical configurations and service rules for the simplified Chinese primary string 防伪 and its traditional Chinese variant string 防偽, to cut down administrative burden and operational complexity brought by dual character form gTLDs for registrars, resellers and domain name registrants. Detailed measures are listed below: Step 1: Enforce bundled registration policy for the paired variant domains The registry implements a rigid one owner binding mechanism. Whenever a registrant applies for the domain name under one character variant (防伪 or 防偽), its counterpart variant domain shall be allocated to the identical registrant compulsorily. Registrars and resellers do not need to handle separate applications, independent audits or scattered renewal procedures for the two variant domains. Bundled application, modification and renewal are processed as one single business package. It prevents separate ownership of simplified and traditional character domains and eliminates complicated cross variant ownership management work loads for all parties. Step 2: Unify verification standards, dispute resolution rules and charging rules for both variant gTLDs Both 防伪 and 防偽 share identical trademark right examination workflow, qualification review criteria, domain dispute resolution policies, price strategy, renewal cycle and service specification. Registrars, resellers and registrants only need to master one set of access rules. There will be no differentiated audit materials, variant specific fee schemes or exclusive operational processes between the two TLD labels. Unified standards reduce learning cost and daily management complexity for channel partners and brand owner registrants. Step 3: Deploy synchronized DNS resolution and automatic redirection to separate variant configuration pressure The registry configures unified DNS settings for the two variant top level domains and supports CNAME based alias forwarding. Traffic visiting either simplified character or traditional character domain will resolve toward the same official website. Registrants are allowed to manage one set of website resource rather than building up independent websites for two variants. Registrars and resellers receive consistent DNS operation guidelines without extra variant related technical configuration work. Step 4: Supply unified channel data interface, document and public guidance materials A single set of API interface, system access specification, operation manual and user guide will be provided for registrars and resellers. The registry marks the two strings as bound variant pairs inside the backend system, and adds clear variant pair identification tags. Channel side systems can identify and process both variants through one interface. No extra independent system adaptation is required for the traditional Chinese variant string. Regular training and announcements will help agents distinguish variant pair rules and cut down operational errors. Step 5: Carry out unified lifecycle management and one click batch operation for variant pairs All domain lifecycle procedures are designed for bundled operation. Once the registrant modifies information or triggers renewal for one domain, its paired variant executes synchronous changes automatically. This design avoids repetitive manual operations on two separate domains and lowers the risk of inconsistent status between simplified and traditional character domains. Step 6: Establish clear cut variant pair clauses inside the Registry Agreement All above mentioned binding registration, unified standard, synchronous resolution and bundled lifecycle management commitments shall be written into formal contractual terms of the Registry Agreement. Stable long term rules help registrars, resellers and registrants arrange daily term work with predictable, low complexity variant domain management rules.
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