Applications / .euro / ECB2684T-T54124 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.euro

StandardActive

§ 1 — Meaning of the string Q118·Q120

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.

/ˈjʊə.rəʊ/ (UK) or /ˈjʊr.oʊ/ (US)

§ 2 — Mission and purpose Q133

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.
The .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. European Central Bank and 21 euro area National Central Banks currently include: 1. Banque nationale de Belgique (Belgium) 2. Българска народна банка (Bulgaria) 3. Deutsche Bundesbank (Germany) 4. Eesti Pank (Estonia) 5. Central Bank of Ireland 6. Bank of Greece 7. Banco de España (Spain) 8. Banque de France 9. Hrvatska narodna banka (Croatia) 10. Banca d'Italia (Italy) 11. Central Bank of Cyprus 12. Latvijas Banka (Latvia) 13. Lietuvos bankas (Lithuania) 14. Banque centrale du Luxembourg 15. Central Bank of Malta 16. De Nederlandsche Bank (Netherlands) 17. Oesterreichische Nationalbank (Austria) 18. Banco de Portugal 19. Banka Slovenije (Slovenia) 20. Národná banka Slovenska (Slovakia) 21. Finlands Bank (Finland)
Purpose The 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. The .euro TLD will:
• Provide a clearly defined, trusted and recognisable space online for euro-related digital content, services, and communications. • Create a unified, secure and recognisable namespace for euro-related services, outreach, education and innovation. • Support the ECB’s and the Eurosystem’s long-term digital communication, trust and stakeholder engagement strategies. • Implement policies and operational practices that enhance trust, security, and accountability within the namespace • Facilitate the effective representation of the euro in the digital economy. • Reinforce the ECB’s digital identity, authority and credibility in an increasingly complex online environment.
The .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.
The .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.
As 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.
The .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.

§ 3 — Commitments and safeguards Q164–Q188

More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169	Yes to: more trustworthy (Q164), consumer risk if abused (Q165), licensing or accreditation (Q166), government reporting (Q167), government function (Q169)
Voluntary Safeguard PICs Q170·Q171	• 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. • 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. • 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. • 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. • 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. • 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. • 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. • 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. • Registry Operators will develop and publish registration policies to minimize the risk of cyber bullying and/or harassment. • 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.
Registry Voluntary Commitments Q172·Q173	None · 5 do
Code of Conduct exemption requested Q185·Q188	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. The .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. This 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. The 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. The 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. The .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. The 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. Granting the requested exemption will: 1- Protect the integrity of the .euro namespace by limiting registrations to authorised Eurosystem institutions. 2 - Reduce the risk of fraud, abuse, phishing and misleading use associated with the euro. 3 - Ensure clear accountability through the governance framework established under the Treaties and the Statute of the ESCB. 4 - Cause no competitive harm, as .euro will not operate as a public retail domain-name market. 5 - 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 In 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

§ 4 — All other published answers

Every other answer ICANN published for this application, in the order of the form. Contact details (Q17–Q24) are left to the ICANN record.

Q192Q1.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: SC1.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). SC1.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.

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: SC1.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). SC1.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.

Answered with a document. Attachments are not published by ICANN.

Q193Q1.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.

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.

Answered with a document. Attachments are not published by ICANN.

Q220Q5.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: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.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. SC5.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.

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: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.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. SC5.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.

Answered with a document. Attachments are not published by ICANN.

Q221Q5.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: SC5.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. SC5.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. SC5.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). SC5.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. SC5.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. SC5.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. SC5.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.

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: SC5.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. SC5.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. SC5.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). SC5.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. SC5.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. SC5.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. SC5.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.

Answered with a document. Attachments are not published by ICANN.

Q119Script of String

Script of String

Latin

Q121As 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.

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.

true

Q186The 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);

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);

true

Q187Confirm 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.

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.

true

Q222If 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.

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.

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:
Austria Cyprus Germany Greece Estonia Spain France Croatia Ireland Italy Luxembourg Lithuania Malta The Netherlands Portugal Slovenia Slovakia The .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.
The 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.
Note : the 17 letters have been merged into two file for facility of use.

Answered with a document. Attachments are not published by ICANN.

Q223By 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.

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.

true

Q224By 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.

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.

true