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--imr513n
餐厅
U+9910 U+5385
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"
restaurant
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.
/tsʰan˥˥ tʰiŋ˥˥/
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.
1. Mission and Purpose of the applied-for variant gTLD 餐廳 The applied-for 餐廳 (Traditional Chinese) gTLD is the variant of the existing primary gTLD 餐厅 (Simplified Chinese), with identical core meaning, industry positioning and authoritative attributes. Its mission is to build an inclusive catering industry namespace adapting to traditional Chinese usage in Hong Kong, Macau, Taiwan and overseas Chinese communities. This variant eliminates simplified-traditional script recognition barriers, unifies the official digital identity of global catering enterprises, avoids public recognition confusion, and provides credible verified domain credentials for legitimate catering service providers across all Chinese-speaking regions. Intended Registrants Consistent with the primary gTLD, 餐廳 registration is catering entities, including restaurants, catering chains, catering groups, beverage service providers, hotel catering departments and catering industry institutions. Intended Users This variant serves traditional Chinese-speaking communities in Hong Kong, Macau, Taiwan and overseas regions, covering ordinary consumers, diners, tourism users, business partners and catering practitioners. It enables users to identify official catering websites via familiar traditional Chinese scripts, improving overall user recognition and trust in online catering services. Related Activities As the registry operator of the 餐厅 gTLD, the applicant will adopt fully unified rules for 餐廳, including consistent qualification verification, anti-abuse and anti-squatting policies, domain lifecycle management, and compliant WHOIS/RDAP services. Sunrise protection, brand right protection and ICANN-aligned dispute resolution mechanisms will be synchronized for both strings. The applicant will conduct continuous industry cooperation and standardized compliance management to sustain the integrity and authority of the unified catering industry namespace. 1a. Mission and Purpose of the existing primary gTLD 餐厅 The existing primary gTLD 餐厅 (Simplified Chinese) is an authoritative exclusive namespace for the global catering industry. It aims to provide legitimate catering businesses with official digital identities, standardize online brand display, curb counterfeit catering websites and online fraud, and enhance public trust in online catering services. Its registrants are limited to qualified catering legal entities under strict review mechanisms to prevent bad-faith registrations. Its target users are simplified Chinese-speaking consumers, catering customers and industry institutions seeking authentic catering service information. Since launch, the applicant has implemented standardized registration audits, long-term anti-abuse supervision, stable technical operation and unified policy execution, building a secure, standardized and authoritative ecosystem for the 餐厅 gTLD. 2. Long-term Sustainability of the Purpose The dual-string operation of primary 餐厅 and variant 餐廳 delivers sustainable long-term value. First, the catering industry is a fundamental people’s livelihood sector with steady digital transformation demands, sustaining permanent market needs for professional catering domain identifiers. Second, simplified and traditional Chinese script differentiation is a fixed long-term linguistic norm, making dual-string coverage essential to serve all Chinese-speaking communities. Third, unified registration rules and mature operational systems effectively avoid variant string abuse and value dilution. Fourth, the dual-string model fits cross-regional brand operation demands of global catering enterprises, ensuring continuous industry adoption. Finally, the applicant’s stable operation capability, standardized technical framework and compliant governance system support the long-term healthy and unified development of both gTLDs.
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--3zto70k
餐廳
U+9910 U+5EF3
Provide the script of the variant string (both in English and as referenced by the RZ-LGR/ISO 15924)
Chinese (Han)
Select an option.
Existing 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".
restaurant
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 餐厅 (Simplified Chinese) and variant string 餐廳 (Traditional Chinese) are universally recognized as identical in meaning, pronunciation, and industry reference by all Chinese-speaking user communities (Mainland China, Hong Kong, Macau, Taiwan, and overseas Chinese). They are standard script variants of the same term (referring to “restaurant/catering establishment”), differing only in written form—not in semantic value. This equivalence is rooted in linguistic norms, real-world usage, and legal precedents across Chinese regions. Three Bona-Fide Examples 1. ICANN-Recognized IDN Variant Precedent ICANN’s IDN Variant Framework explicitly classifies Chinese Simplified/Traditional pairs (e.g., 澳门 / 澳門, 中国 / 中國) as semantically identical variantsICANN. The 餐厅 / 餐廳 pair follows the same linguistic rule: both denote “catering/restaurant” and are treated as interchangeable in root zone label generation (RZ-LGR) and user experience. This is a formal industry standard for Chinese IDN gTLDs. 2. Trademark & Legal Precedent in Catering Industry Chinese judicial practice uniformly holds that Simplified/Traditional character pairs are identical for trademark and service identification. For example: • Courts ruled that 小龍坎 (Traditional) and 小龙坎 (Simpl) are identical trademarks for hot pot catering services—no confusion in meaning or source. • In catering disputes, 外婆橋 / 外婆桥 and 全築 / 全筑 are deemed equivalent service identifiers, with 繁简差异 not negating identity. This confirms 餐廳 / 餐厅 are legally and commercially the same to catering users and registrants. 3. Real-World Business & User Usage Global catering enterprises and Chinese-speaking users treat 餐厅 / 餐廳 as interchangeable: • Major chains (e.g., 海底捞 / 海底撈，麦当劳 / 麥當勞) use both forms in branding, menus, and domains—users recognize them as the same business. • In Hong Kong/Taiwan/overseas communities, 餐廳 is the standard term; in Mainland China, 餐厅 is used. Both refer to the same catering service, with zero semantic difference for consumers, businesses, and industry institutions. • Domain systems (e.g., CNNIC) resolve 餐厅。中国 and 餐廳。中國 to the same website, proving user-perceived identity. Conclusion All relevant Chinese user communities recognize 餐厅 and 餐廳 as the same term—only differing in script, not meaning. The three examples (ICANN IDN rules, legal precedents, real-world business usage) conclusively validate this equivalence.
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. Why one label is insufficient and two labels are necessary A single label is insufficient because Simplified Chinese and Traditional Chinese are distinct writing systems used in separate major regions with long-standing linguistic, cultural, and usage conventions. • 餐厅 (Simplified) is the standard in mainland China. • 餐廳 (Traditional) is the standard in Hong Kong, Macau, Taiwan, and most overseas Chinese communities. Using only one script would create usability barriers, lower user recognition, and reduce trust among communities accustomed to their native writing system. Two labels are necessary to fully serve all Chinese speaking users equally, respect regional linguistic preferences, and ensure intuitive, culturally appropriate access to the catering industry namespace. 2. User communities served by the primary and variant TLDs Primary TLD: 餐厅 (Simplified Chinese) Serves users in: • Mainland China • Platforms and users primarily using Simplified Chinese • Domestic catering businesses, consumers, tourism platforms, and industry users Variant TLD: 餐廳 (Traditional Chinese) Serves users in: • Hong Kong, Macau, Taiwan • Global overseas Chinese communities • International catering chains, regional users, and businesses operating in Traditional Chinese environments 3. How user community needs are reflected in the IDN tables The IDN tables for the primary 餐厅 and variant 餐廳 TLDs are structurally identical and semantically aligned, reflecting shared user needs across Chinese speaking communities: • Both use the same set of valid characters, registration rules, and eligibility policies. • Both support the same industry purpose (catering and restaurant services). • The only difference is the script form (Simplified vs. Traditional), which directly matches the linguistic needs of each regional user group. This design ensures consistent security, policy, and user experience while accommodating cultural and regional writing preferences. The IDN tables thus reflect both shared core needs and linguistic diversity across the global Chinese user community.
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.
To minimize operational and management complexities associated with the variant gTLD pair 餐厅 (Simplified) and 餐廳 (Traditional), the applicant will implement a series of unified, consistent, and streamlined administrative and technical measures across both TLDs. These measures reduce burdens for registrars, resellers, and registrants as follows: Unified Registry Platform and Single Point of Operation Both the primary TLD and variant TLD will be operated on the same technical backend platform, with shared systems for domain registration, renewal, modification, suspension, and revocation. Registrars will only need to maintain one set of integration connections and operational workflows, avoiding duplicate configuration or separate system access. Consistent Policies, Rules, and Eligibility Criteria All policies, including registration eligibility, verification standards, naming policies, anti-abuse rules, and dispute resolution mechanisms, will be fully identical between 餐厅 and 餐廳. No separate policy documents or review processes will apply to the variant string, ensuring registrars and registrants face no confusion or additional compliance burden. Unified WHOIS/RDAP Service and Data Structure Registration data output, query format, and RDAP/WHOIS display will follow a unified structure for both TLDs. Consistent data fields and output formats simplify system integration for registrars, resellers, and third-party service providers. Synchronized Launch, Sunrise, and Rights Protection Mechanisms Sunrise periods, trademark claims periods, registration phases, and rights protection mechanisms will run in parallel for both TLDs. This synchronization eliminates scheduling complexity and allows registrars to prepare and promote only one launch plan. Unified Pricing, Billing, and Registrar Settlement Pricing structure, billing cycles, discount policies, and financial settlement procedures will be identical for both TLDs. Registrars will manage only one set of price lists and financial processes, rather than separate arrangements for each string. Shared Customer Support and Service Framework A unified support system will handle inquiries, troubleshooting, and compliance matters for both TLDs. Registrants and registrars will receive consistent guidance and services, with no need to distinguish between the primary and variant string for assistance. Simplified Reseller Management and Channel Tools Reseller management systems, API interfaces, control panels, and promotional materials will be designed to support both TLDs simultaneously. Channel partners will use a single set of tools and materials, reducing operational workload and training costs. Unified Reporting, Compliance, and ICANN Reporting All regulatory reports, compliance data, statistics, and ICANN-mandated submissions will be compiled on a combined basis. The applicant will avoid separate reporting for each variant, reducing internal and external administrative overhead. Through the above measures, the applicant ensures that the operation of the variant TLD 餐廳 introduces minimal additional complexity. The unified architecture, policies, and processes protect registrars, resellers, and registrants from duplication, inconsistency, or unnecessary operational burden. These commitments will be formally incorporated into the Registry Agreement to ensure long-term stable and simplified management.
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