{"applicationHumanReadableId":"ECB2684T-T54124","applicationDetails":{"applicationHumanReadableId":"ECB2684T-T54124","applicationType":"New gTLD","primaryString":{"aLabel":"euro","uLabel":""},"tldVariants":[],"originalTldVariants":[],"tldTypes":[],"priorityNumber":-1,"applicationStatus":"Active","processingStage":"Pre-Evaluation Processing","hasClarifyingQuestions":false,"hasChangeRequests":false,"hasObjections":false,"lastPublishedAt":"2026-10-07T15:38:00.915Z"},"questionAndResponses":{"applicationHumanReadableId":"ECB2684T-T54124","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":"European Central Bank ","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q2. Doing Business As ","instructions":"Provide the name under which the applying entity is doing business, if different from the full legal name answered in Question 1. Such a name must be registered with appropriate local jurisdiction or public authority.","responseText":"Not Applicable ","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":"Institution of the European Union","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":"Germany","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://www.ecb.europa.eu/","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":"false","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":"false","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":17,"questionText":"AGB Q17. Phone Country Code","instructions":"","responseText":"49","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":"69 13 44 0","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":"info@ecb.europa.eu","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":20,"questionText":"AGB Q20. Address Line 1","instructions":"Enter the street address (no PO Box).","responseText":"Sonnemannstrasse 20 ","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":22,"questionText":"AGB Q22. Locality","instructions":"Enter the city, village, municipality, etc.","responseText":"Frankfurt am Main  ","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":"Frankfurt am Main  ","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":"60314","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":25,"questionText":"AGB Q25. Country Code of Location","instructions":"","responseText":"DE","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":1,"questionText":"AGB 104. List all directors of the applying entity.","instructions":"","responseText":"Alain Jean-Jacques Busac, Thierry Roger Julia  Bracke,  Evelien Francisca Joanna Nagelkerke","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":3,"sectionId":"1","sectionTitle":"Self-Certification","sectionInstructions":"Provide a single document for Self-Certification question Q1.1-1.0\r\nThe document must include only the SC1.1-1.1 and SC1.1-1.2 statements.0\r\nDo not modify any of the Self-Certification statements.","questions":[{"displayOrder":1,"questionText":"AGB Q192. Q1.1-1 - Provide the applying entity's self-certification document that commits government support on official letterhead from a proper authority that the application for the gTLD(s) and its operation by the applying entity is permitted and that represents and warrants:\nSC1.1-1.1 - That the applying entity is the recognized government of its jurisdiction and that the government has authorized the application(s) for applied-for gTLD string(s) or is a recognized intergovernmental organization with relevant authorization for its application(s) for applied-for gTLD string(s). \nSC1.1-1.2 - That the applying entity and/or an affiliate commits to the long-term funding required to operate all of the existing gTLDs (if applicable) and newly applied-for gTLD string(s) of the applying entity.","instructions":"1. Provide a single document for Self-Certification question Q1.1-1.\n2. The document must include only the SC1.1-1.1 and SC1.1-1.2 statements.\n3. Do not modify any of the Self-Certification statements.\n4. If the applying entity cannot Self-Certify the SC1.1-1.1 and SC1.1.1-2 statements, provide a document that explains why the applying entity cannot Self-Certify the SC1.1-1.1 and SC1.1.1-2 statements.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":4,"sectionId":"2","sectionTitle":"Operational/Planning","sectionInstructions":"The document for Q1.2-1 must be a PDF.\r\nThe document for Q1.2-2 must be an Excel (.xlsx) file.","questions":[{"displayOrder":1,"questionText":"AGB Q193. Q1.2-1 - Provide a document with a list of the applying entity’s current gTLDs (if applicable) and a list of all gTLDs for entities affiliated with the applying entity (if applicable). If the applying entity and affiliates have no current gTLDs, submit a document that confirms this.","instructions":"1. The document for Q1.2-1 must be a PDF.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":5,"sectionId":"3","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":6,"sectionId":"4","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":"The term “EURO” refers to the common currency used by many countries within the European Union. It denotes the official monetary unit (€) adopted by the Eurozone member states for economic and financial transactions.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q119. Script of String","instructions":"If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)","responseText":"Latin","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":"/ˈjʊə.rəʊ/ (UK) or /ˈjʊr.oʊ/ (US)","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":"The mission of the .euro TLD (Top Level Domain) is to create a highly trusted and secure ecosystem online that is defined by its pre-approved Registrants (the European Central Bank and euro area National Central Banks and their partners) to communicate everything about the euro and central bank related topics.\n\nThe .euro TLD provides support online to the European Central Bank’s (ECB) objective of ensuring the continued trust, stability, and accessibility of the euro currency in an increasingly digital environment by enabling a reliable and recognisable online presence.\nEuropean Central Bank and 21 euro area National Central Banks currently include:\n1.\tBanque nationale de Belgique (Belgium) \n2.\tБългарска народна банка (Bulgaria) \n3.\tDeutsche Bundesbank (Germany) \n4.\tEesti Pank (Estonia) \n5.\tCentral Bank of Ireland\n6.\tBank of Greece\n7.\tBanco de España (Spain) \n8.\tBanque de France\n9.\tHrvatska narodna banka (Croatia) \n10.\tBanca d'Italia (Italy) \n11.\tCentral Bank of Cyprus\n12.\tLatvijas Banka (Latvia) \n13.\tLietuvos bankas (Lithuania) \n14.\tBanque centrale du Luxembourg\n15.\tCentral Bank of Malta\n16.\tDe Nederlandsche Bank (Netherlands) \n17.\tOesterreichische Nationalbank (Austria) \n18.\tBanco de Portugal\n19.\tBanka Slovenije (Slovenia) \n20.\tNárodná banka Slovenska (Slovakia) \n21.\tFinlands Bank (Finland) \n\nPurpose\nThe purpose of the .euro TLD (Top Level Domain) is to operate a trusted and clearly identifiable namespace that enables pre-approved Registrants (ECB and euro area National Central Banks) to register and use domain names associated with euro-related activities, information, and services, within a framework designed to support user confidence and trust.\nThe .euro TLD will:\n\n•\tProvide a clearly defined, trusted and recognisable space online for euro-related digital content, services, and communications.\n•\tCreate a unified, secure and recognisable namespace for euro-related services, outreach, education and innovation.\n•\tSupport the ECB’s and the Eurosystem’s long-term digital communication, trust and stakeholder engagement strategies.\n•\tImplement policies and operational practices that enhance trust, security, and accountability within the namespace\n•\tFacilitate the effective representation of the euro in the digital economy.\n•\tReinforce the ECB’s digital identity, authority and credibility in an increasingly complex online environment.\n\nThe .euro TLD is intended to operate as a trusted, secure and policy-governed namespace where the European System of Central Banks can communicate about the euro to its audiences. \n\nThe .euro TLD would provide a restricted, trusted and authoritative digital namespace for the ECB, euro area National Central Banks and their partner Banks to communicate clearly and securely about the euro and other central bank related initiatives.\n\nAs the institution responsible for the euro and for maintaining public trust in the currency, the ECB is uniquely positioned to establish .euro as an official online environment for euro-related information, services, outreach and innovation. The TLD would support communications concerning euro banknotes, the digital euro, public education, stakeholder engagement, and other euro-related activities led or coordinated by the ECB and the Eurosystem.\n\nThe .euro TLD would therefore serve the public interest by creating a clear, secure and institutionally governed online space for authoritative euro-related content. It would enhance public confidence, reduce opportunities for online abuse, and ensure that information concerning the euro currency is accessible through a domain environment that is trusted, recognisable and controlled by the appropriate public authority.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":1,"questionText":"AGB Q116. Applied-for Primary String (ASCII Label)","instructions":"","responseText":"euro","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":"Yes","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":"Yes","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":"Yes","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":"Yes","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.\n • Registry Operators will proactively create a clear pathway for the creation of a working relationship with the relevant regulatory or industry self-regulatory bodies by publicizing a point of contact and inviting such bodies to establish a channel of communication, including for the purpose of facilitating the development of a strategy to mitigate the risks of fraudulent and other illegal activities.\n • 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 provide administrative contact information, which must be kept up-to-date, for the notification of complaints or reports of registration abuse, as well as the contact details of the relevant regulatory, or industry self-regulatory, bodies in their main place of business.\n • Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring a representation that the Registrant possesses any necessary authorizations, charters, licenses and/or other related credentials for participation in the sector associated with the Registry TLD string.\n • If a Registry Operator receives a complaint expressing doubt with regard to the authenticity of licenses or credentials, Registry Operators should consult with relevant national supervisory authorities, or their equivalents regarding the authenticity.\n • 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 report any material changes to the validity of the Registrants' authorizations, charters, licenses and/or other related credentials for participation in the sector associated with the Registry TLD string in order to ensure they continue to conform to appropriate regulations and licensing requirements and generally conduct their activities in the interests of the consumers they serve.\n • Registry Operators will develop and publish registration policies to minimize the risk of cyber bullying and/or harassment.\n • Registry Operators will include a provision in its Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring a representation that the Registrant will take reasonable steps to avoid misrepresenting or falsely implying that the Registrant or its business is affiliated with, sponsored or endorsed by one or more country's or government's military forces if such affiliation, sponsorship or endorsement does not exist.","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":"Yes","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":8,"questionText":"AGB Q186. The applying entity confirms all domain name registrations in the TLD will be registered to, and maintained by, registry operator for the exclusive use of the registry operator or its affiliate (as defined in the Base RA);","instructions":"Confirm statement with a checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":9,"questionText":"AGB Q187. Confirm the registry operator will not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an affiliate of registry operator.","instructions":"Confirm statement with a checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":10,"questionText":"AGB Q188. Confirm and specify why the Application of the Code of Conduct to the applied-for string is not necessary to protect the public interest.","instructions":"Provide justification for why the Code of Conduct is not necessary to protect the public interest. This may include an explanation of how the TLD's operation under the exemption would serve the best interests of the registry operator, its stakeholders, and the broader Internet community, without adversely affecting the domain name ecosystem.","responseText":"The European Central Bank (\"ECB\") confirms that it is applying for an exemption from the Code of Conduct pursuant to Specification 9 of the Registry Agreement. \n\nThe .euro TLD will operate under a restricted registration model. Registrations will not be available to the general public and will be limited to the ECB and National Central Banks participating in the Eurosystem. \n\nThis model reflects the unique institutional and public-interest nature of the euro. Article 1 of the Statute of the European System of Central Banks (\"ESCB\") provides that the ECB and the national central banks constitute the ESCB and that the ECB and the national central banks of Member States whose currency is the euro constitute the Eurosystem. Article 3 provides that the ESCB's basic tasks include defining and implementing the monetary policy of the Union, conducting foreign-exchange operations, holding and managing official foreign reserves, and promoting the smooth operation of payment systems. Article 8 further provides that the ESCB shall be governed by the decision-making bodies of the ECB. \n\nThe governance relationship between the ECB and the National Central Banks is established by the Statute of the ESCB. Article 12.1 provides that the Governing Council shall adopt the guidelines and decisions necessary to ensure performance of the tasks entrusted to the ESCB and that the Executive Board shall give the necessary instructions to national central banks. Article 14.3 further provides that national central banks are an integral part of the ESCB and shall act in accordance with the guidelines and instructions of the ECB. \n\nThe ECB understands that the purpose of the Code of Conduct is to ensure non-discriminatory access to registry services and prevent anti-competitive conduct where domain names are offered in a competitive public market. Those concerns do not arise in relation to the proposed .euro operating model. \n\nThe .euro TLD will not operate as a general-purpose public namespace. Rather, it will operate under objective eligibility criteria linked to the institutional framework of the Eurosystem. Registrant eligibility will be strictly controlled and registrar participation will be subject to accreditation requirements established by the Registry Operator. \n\nThe relationship between the ECB and the National Central Banks should be assessed in light of the Treaty-based governance framework described above. Under the ICANN Base Registry Agreement, the definition of Affiliate is based on concepts of control rather than solely on corporate ownership. \n\nGranting the requested exemption will: \n\n1- Protect the integrity of the .euro namespace by limiting registrations to authorised Eurosystem institutions. \n\n2 - Reduce the risk of fraud, abuse, phishing and misleading use associated with the euro. \n\n3 - Ensure clear accountability through the governance framework established under the Treaties and the Statute of the ESCB. \n\n4 - Cause no competitive harm, as .euro will not operate as a public retail domain-name market. \n\n5 - Allow the Registry operator to select registrars already showing a high level of security and service demonstrated by the existing relationship with local national banks \n\nIn light of the restricted registration model, the ESCB governance framework, and the absence of the competition concerns that the Code of Conduct is intended to address, the ECB respectfully submits that application of the Code of Conduct is not necessary to protect the public interest and that granting the requested exemption is appropriate and consistent with ICANN's objectives","hasResponseDocuments":true,"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":1,"questionText":"AGB Q222. If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.","instructions":"1. An applying entity may use this response field to submit any additional, optional information or documentation that the applying entity believes enhances understanding of its application or may be of interest to the general public. This could include, but is not limited to, the applying entity’s: \r\na) Individual registry policies;\r\nb) Separate agreement with a third-party to fulfill certain commitments; \r\nc) Terms of use; \r\nd) Additional Community Registration Policies not intended for RA inclusion; \r\ne) Other materials that clarify the applying entity’s mission, values, or intended use of the gTLD. \r\n\r\nNotes:\r\n1. This question is optional and for informational purposes only. \r\n2. The information provided here will not be evaluated as part of the application, or be contractually binding on the applying entity. \r\n3. All submissions to this question will be posted for the public to review and comment. ","responseText":"The European Central Bank (ECB) wishes to highlight the support expressed by national central banks through 17 formal letters of endorsement from the following countries:\n\nAustria\nCyprus\nGermany\nGreece\nEstonia\nSpain\nFrance\nCroatia\nIreland\nItaly\nLuxembourg\nLithuania\nMalta\nThe Netherlands\nPortugal\nSlovenia\nSlovakia\nThe .euro project aims to establish a dedicated online space for the Eurozone market, representing approximately 350 million people across 21 countries and a combined GDP of €15 trillion.\n\nThe support of the national central banks is therefore of significant importance, as it reflects a shared vision and a coordinated strategic approach to the Eurozone’s digital representation.\n\nNote : the 17 letters have been merged into two file for facility of use. \n","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"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}]}]}}