{"applicationHumanReadableId":"NA2631T-T26855","applicationDetails":{"applicationHumanReadableId":"NA2631T-T26855","applicationType":"New gTLD","primaryString":{"aLabel":"dna","uLabel":""},"tldVariants":[],"originalTldVariants":[],"tldTypes":[],"priorityNumber":-1,"applicationStatus":"Active","processingStage":"Pre-Evaluation Processing","hasClarifyingQuestions":false,"hasChangeRequests":false,"hasObjections":false,"lastPublishedAt":"2026-10-07T15:31:06.893Z"},"questionAndResponses":{"applicationHumanReadableId":"NA2631T-T26855","sections":[{"displayOrder":1,"sectionId":"1","sectionTitle":"Applying Entity Information","sectionInstructions":"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.","questions":[{"displayOrder":1,"questionText":"AGB Q1. Full Legal Name","instructions":"Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.","responseText":"Registry Services, LLC","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q3. Legal Entity Form/Business Structure","instructions":"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.","responseText":"Limited liability company","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB Q4. Jurisdiction","instructions":"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.","responseText":"Delaware","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":10,"questionText":"AGB Q10. Website URL","instructions":"Provide the website URL of the applying entity, if available.","responseText":"https://registry.godaddy/","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":11,"questionText":"AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?","instructions":"1. Choose Yes or No. \n2. Use the definition of Affiliate from the Base Registry Agreement (see  https://www.icann.org/en/registry-agreements/base-agreement).","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":12,"questionText":"AGB Q12. If \"Yes\", explain.","instructions":"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.\n2. 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.\n3. If the applying entity is an ICANN accredited registrar, specify the registrar ID number.","responseText":"1. Existing Registry Operator and Affiliate of Registrars\n2. Affiliated Registrars: \nGoDaddy.com, LLC (IANA 146) \nBombora Technologies Pty Ltd (IANA 353) \nWild West Domains, LLC (IANA 440) \nBlue Razor Domains, LLC (IANA 612) \nGo China Domains, LLC (IANA 1149) \nGo Canada Domains, LLC (IANA 1150) \nGo Australia Domains, LLC (IANA 1151) \nGo Montenegro Domains, LLC (IANA 1152) \nGo France Domains, LLC (IANA 1153) \nMesh Digital Limited (IANA 1390) \n123-Reg Limited (IANA 1515) \nGoDaddy Online Services Cayman Islands Ltd (IANA 1659) \nGoDaddy Corporate Domains, LLC (IANA 3786)\n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":13,"questionText":"AGB Q13. Is the applying entity a back-end registry service provider (RSP), an ICANN-approved data escrow agent, an emergency back-end registry operator, a Uniform Rapid Suspension (URS) service provider, an ICANN dispute resolution service provider, a Privacy or Proxy Service Provider, or a Reseller?","instructions":"Choose Yes or No.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":14,"questionText":"AGB Q14. If the applying entity is an Affiliate of any of the entities listed in Question 13, explain.","instructions":"1. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement).\n2. Provide the type of the provider and the name of the applicable entity of which the applying entity is an Affiliate.","responseText":"Yes, Affiliate of resellers: \nDomains Priced Right \nHeart Internet \nHost Europe \nMad Dog Domains \nMedia Temple \nMr. Site \nTSO Host \n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":17,"questionText":"AGB Q17. Phone Country Code","instructions":"","responseText":"1","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":18,"questionText":"AGB Q18. Primary Business Phone","instructions":"Provide the primary business phone number without including the country code.","responseText":"4805058800","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":19,"questionText":"AGB Q19. Primary Business Email Address","instructions":"Provide the primary business email address of the applying entity.","responseText":"rsllc-primary@registry.godaddy","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":20,"questionText":"AGB Q20. Address Line 1","instructions":"Enter the street address (no PO Box).","responseText":"100 S Mill Avenue","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":21,"questionText":"AGB Q21. Address Line 2","instructions":"","responseText":"Suite 1600","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":22,"questionText":"AGB Q22. Locality","instructions":"Enter the city, village, municipality, etc.","responseText":"Tempe","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":23,"questionText":"AGB Q23. State/Province/Region","instructions":"Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.","responseText":"Arizona","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":24,"questionText":"AGB Q24. Postal Code","instructions":"1. Enter the postal code, if applicable.\n2. If a postal code does not exist, type “Not Applicable”. ","responseText":"85281","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":25,"questionText":"AGB Q25. Country Code of Location","instructions":"","responseText":"US","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":26,"questionText":"AGB Q26. Full Legal Name","instructions":"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. ","responseText":"Desert Newco, LLC","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":28,"questionText":"AGB Q28. Legal Entity Form/Business Structure","instructions":"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.","responseText":"Limited liability company","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":29,"questionText":"AGB Q29. Jurisdiction","instructions":"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.","responseText":"Delaware","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":36,"questionText":"AGB Q36. Full Legal Name","instructions":"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.","responseText":"GoDaddy Inc.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":38,"questionText":"AGB Q38. Legal Entity Form/Business Structure","instructions":"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.","responseText":"Corporation","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":39,"questionText":"AGB Q39. Jurisdiction","instructions":"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.","responseText":"Delaware  ","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":2,"sectionId":"1","sectionTitle":"Applying Entity Background and Organization","sectionInstructions":"This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.","questions":[{"displayOrder":2,"questionText":"AGB 105. List all officers & partners of the applying entity.","instructions":"","responseText":"Phontip Palitwanon, Jared Sine, Jessica Habicht, Neepa Ranavat","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB 106. List all Material Shareholders","instructions":"","responseText":"Desert Newco LLC","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB 107. List Individuals with Executive Responsibility","instructions":"","responseText":"Phontip Palitwanon, Jared Sine, Jessica Habicht, Neepa Ranavat","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB 108. Disclose Ultimate Control of applying entity","instructions":"","responseText":"GoDaddy Inc.","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":4,"sectionId":"6","sectionTitle":"Self-Certification","sectionInstructions":"Provide a single document for Self-Certification question Q2.2-1.\r\nThe document must include only the SC2.2-1.1, SC2.2-1.2, or SC2.2-1.3 statements.\r\nDo not modify any of the Self-Certification statements.","questions":[{"displayOrder":1,"questionText":"AGB Q199. Q2.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO, and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE) of the applying entity, the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant:\nSC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). \nSC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings.\nSC2.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.","instructions":"1. Provide a single document for Self-Certification question Q2.2-1.\n2. The document must include only the SC2.2-1.1 through SC2.2-1.3 statements.\n3. Do not modify any of the Self-Certification statements.\n4. 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.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":5,"sectionId":"7","sectionTitle":"Operational/Planning","sectionInstructions":"The document for Q2.3.1 must be a PDF.\r\nThe document for Q2.3-2 must be an Excel (.xlsx) file.","questions":[{"displayOrder":1,"questionText":"AGB Q200. Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).","instructions":"The document for Q2.3-1 must be a PDF.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":6,"sectionId":"8","sectionTitle":"Security Policy and Planning","sectionInstructions":"Provide a single document for Self-Certification question AGB Q220, Q5.1-1.\r\nThe document must include only the SC5.1-1.1 through SC5.1-1.3 statements.\r\nDo not modify any of the Self-Certification statements.\r\nIf 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.","questions":[{"displayOrder":1,"questionText":"AGB Q220. Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant:\nSC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services.\nSC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent).  The security program must be in place prior to delegation, and exist through at least the period of the registry agreement.\nSC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.","instructions":"1. Provide a single document for Self-Certification question Q5.1-1.\n2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements.\n3. Do not modify any of the Self-Certification statements.\n4. 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.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":7,"sectionId":"9","sectionTitle":"DNS Abuse","sectionInstructions":"Provide a single document for Self-Certification question AGB Q221, Q5.2-1.\r\nThe document must include only the SC5.2-1.1 through SC5.2-1.7 statements.\r\nDo not modify any of the Self-Certification statements.\r\nIf 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.","questions":[{"displayOrder":1,"questionText":"AGB Q221. Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant:\nSC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD.\nSC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies.\nSC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6).\nSC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate.\nSC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone.\nSC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse.\nSC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.","instructions":"1. Provide a single document for Self-Certification question Q5.2-1.\n2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements.\n3. Do not modify any of the Self-Certification statements.\n4. 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.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":8,"sectionId":"16","sectionTitle":"Primary String","sectionInstructions":"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.","questions":[{"displayOrder":4,"questionText":"AGB Q118. What is the meaning/definition of the applied-for gTLD string?","instructions":"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\"","responseText":"DNA is the abbreviation for deoxyribonucleic acid, the molecule carrying the genetic instructions used in the growth, functioning, and reproduction of living organisms.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q120.  Phonetic Representation","instructions":"Provide a representation of the string according to the International Phonetic Alphabet.","responseText":"/ˌdiː.ɛnˈeɪ/","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q121. As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.","instructions":"Confirm the statement using a checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":8,"questionText":"AGB Q133. What is the mission and purpose of the applied-for gTLD?","instructions":"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.\n\n1a. 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.\n\n2. Explain how this purpose is sustainable over time.","responseText":"1. Describe the mission and purpose of the applied-for gTLD.\n.DNA helps genomics companies, personalized health providers, and wellness brands create a clear and memorable online presence for what makes people and their health unique, making it easier to be discovered and trusted by the audiences seeking genetic and preventive health insight. It turns a category-defining scientific term into an instantly recognizable digital identity. For brands built around individuality, it signals their focus in a single, universally understood word.\n\nIntended Registrants: Genetic testing and genomics companies, biotechnology firms, personalized health and wellness providers, ancestry and heritage services, research institutions, laboratories, and health-focused consumer brands seeking a clear, biology-anchored web address. \n\nIntended Users: Individuals exploring their genetic health, ancestry, and wellness; clinicians and researchers; and consumers evaluating personalized nutrition, fitness, and preventive health services. \n\nRelated Activities Supporting the Purpose:\n•\tAwareness-building among genomics, biotech, and personalized wellness sectors\n•\tRegistrar distribution to reach health, science, and consumer brands\n•\tRegistrant education on how a category-specific address supports discoverability\n•\tCommunity outreach across research and health-innovation networks\n•\tResponsible registry operations consistent with standard practices\n\n.DNA gives the fast-growing world of genetics, genomics, and personalized wellness a naming space that instantly communicates what an organization is about. As health increasingly moves toward individualized, data-informed care, a domain ending in .DNA lets a company signal its focus on the biological blueprint at the center of its work. A genetic testing service, a precision nutrition brand, or an ancestry platform can turn a name into something immediately recognizable and relevant to the audience it serves. \nThe purpose of .DNA is to help these organizations establish a clear online identity in a field where credibility and clarity matter deeply. A memorable, on-topic address helps a lab, clinic, or wellness brand be discovered and understood by the people searching for genetic insight, personalized health guidance, or research collaboration. Rather than competing for crowded generic names, registrants can claim an address that describes their category directly. \n\n2. Explain how this purpose is sustainable over time.\nThe durability of .DNA rests on knowledge creation: the continuous scientific advancement built on understanding the genome. DNA is not a trend or a product category that can be replaced; it is a foundational unit of biology that anchors entire fields of research, medicine, and wellness. Every discovery in genetics opens new questions, and each answered question generates fresh avenues for study, from disease prevention to nutrition to longevity. This self-reinforcing cycle of inquiry keeps the concept perpetually relevant. \nGenomic sequencing has moved from specialized laboratories into consumer health, agriculture, diagnostics, and preventive care. As sequencing becomes more accessible and analysis grows more sophisticated, more organizations require language that clearly situates them within this domain. The relevance of .DNA grows alongside the research ecosystem it reflects, rather than depending on any single company, platform, or technology remaining dominant. \nBecause the concept is embedded in education, medicine, and public understanding of biology, its meaning does not erode as tools and businesses change. New discoveries deepen rather than dilute the significance of the term. That combination of continual knowledge creation and durable cultural recognition is what makes .DNA a naming space likely to remain purposeful well into the future.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":1,"questionText":"AGB Q116. Applied-for Primary String (ASCII Label)","instructions":"","responseText":"dna","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":13,"sectionId":"2","sectionTitle":"Safeguard Identification","sectionInstructions":"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.","questions":[{"displayOrder":1,"questionText":"AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD?\r\nThink about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"Yes","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused?\r\nThink about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business?\r\nThink about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB Q167. Would most people think that (domains in) the TLD(s) in the application are used for activities that require regular government reporting, inspections, and oversight in various countries?\r\nThink about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment?\r\nThink about how the TLD string(s) in the application will be understood globally, including different languages and cultures.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\nI-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q169. Would most people think that the TLD is used for something usually done by governments?\r\nThink about how the TLD string(s) in the application will be understood globally, including different languages and cultures.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\na. Literally as described in the application\nb. Literally in any other language in which the string is a recognized word or phrase.\nc. Informally in any language or regional variant, where alternative meanings exist.\nI-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q170. Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Registry Agreement (RA) voluntarily regardless of ICANN’s Safeguard Assessment outcomes?","instructions":"Select Yes or No.\n\nNotes:\n1. 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).\n2. 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.\n3. 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).","responseText":"Yes","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":8,"questionText":"AGB Q171. If Yes, which Safeguard PIC(s) are you proposing to include in the RA?","instructions":"Choose the applicable Safeguard PICs from the provided list (more than one option can be selected).","responseText":" • Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring registrants to comply with all applicable laws, including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct), fair lending, debt collection, organic farming, disclosure of data, and financial disclosures.\n • Registry Operators will include a provision in their Registry-Registrar Agreements that requires registrars at the time of registration to notify registrants of the requirement to comply with all applicable laws.\n • Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring that registrants who collect and maintain sensitive health and financial data implement reasonable and appropriate security measures commensurate with the offering of those services, as defined by applicable law.","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":14,"sectionId":"12","sectionTitle":"Registry Voluntary Commitments (RVCs)","sectionInstructions":"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.","questions":[{"displayOrder":1,"questionText":"AGB Q172. Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Registry Agreement (RA) that are unique to your applied-for string?","instructions":"1. Select Yes or No.\n2. 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).\n3. 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.\n4. 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).\n\nNotes:\nIf 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.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":16,"sectionId":"11","sectionTitle":"Brand & Code of Conduct Exemptions","sectionInstructions":"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).","questions":[{"displayOrder":1,"questionText":"AGB Q179. Are you applying for a Brand TLD?","instructions":"Select Yes or No","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q185. Does the applying entity request a Code of Conduct Exemption?","instructions":"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.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":17,"sectionId":"13","sectionTitle":"Additional Information and Supporting Materials","sectionInstructions":"This question set collects any additional information that the applying entity would like to provide, including any supporting materials.","questions":[]},{"displayOrder":18,"sectionId":"14","sectionTitle":"Bona Fide Intent and Prohibited Communications","sectionInstructions":"This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.","questions":[{"displayOrder":1,"questionText":"AGB Q223. By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.","instructions":"Confirm the statement using the checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q224. By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1  Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.","instructions":"Confirm the statement using the checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]}]}}