tld.report · The 2026 Round

Snapshot of 8 October 2026 · ICANN APS, public fields

Applications / .ygeia / PBCA2619T-T89086 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.ygeia

Brand TLD · Spec 13Active

BAILA CON AGUA, ID Q1·Q25

Ultimately controlled by Marie Laure Annick Henriette Becquelin ep Bitar Q108 · ICANN record ↗

§ 1 — Meaning of the string Q118·Q120

The string is a transliteration of υγεία, the Goddess of health in the Greek mythology. The string as applied for is not a word in English or in any other Latin-script language. It is the applicant's registered trademark, and not a descriptive term.

/iˈʝi.a/

§ 2 — Mission and purpose Q133

The mission of the .YGEIA gTLD is to establish a trusted, secure and distinctive digital infrastructure for the YGEIA brand and its international ecosystem of knowledge, research, education, certification, regenerative wellness, professional care and technological innovation.

.YGEIA is conceived not merely as a commercial brand extension or conventional domain-name registration service, but as the controlled digital environment and governance layer of the YGEIA ecosystem. It will provide a recognizable namespace through which Internet users can identify resources operated by, affiliated with or formally authorized through YGEIA.

The intended registrants will be limited to the Applicant and, where applicable, its Affiliates and Trademark Licensees, in accordance with Specification 13 of the Registry Agreement and ICANN requirements. The namespace will not be open to unrestricted public registration.

Intended users include clients, practitioners, therapists, educators, researchers, institutional and professional partners, certified operators, licensees, members of the YGEIA network and the public seeking reliable information about YGEIA’s activities, services, technologies and initiatives.

The principal purposes of .YGEIA are to:

• provide a trusted digital home for YGEIA’s institutes, educational and certification programs, research, professional networks, technologies, products, services and public-interest initiatives; • organize knowledge and digital resources through clear and memorable domain names; • authenticate YGEIA-authorized websites, platforms, professional services and communications; • support education, professional training, certification and the responsible dissemination of information; • facilitate collaboration among practitioners, researchers, educators, institutions and technology partners; • support quality standards and, where appropriate, product and service authentication and traceability; • provide dedicated environments for YGEIA institutes, geographic markets, customer and professional services, applications and future initiatives; and • reduce impersonation, phishing, cybersquatting and other online abuse associated with the YGEIA brand.

Activities undertaken to achieve this purpose will include official YGEIA websites and platforms; educational and certification portals; authenticated pages for authorized institutes, practitioners and partners; knowledge and research resources; secure communications; customer and professional services; product-information and authentication systems; and digital tools supporting the YGEIA ecosystem.

Registrations will be centrally approved and managed under policies preserving the integrity of the YGEIA brand and the connection between each domain name and an authorized YGEIA activity. Appropriate technical, operational and security measures will protect the namespace.

The purpose of .YGEIA is sustainable over time because the namespace forms part of YGEIA’s long-term institutional, operational and digital strategy. Its use will develop alongside YGEIA’s enduring activities in education, certification, research, institutes, professional services, technologies and products. Its controlled registration model, ecosystem-wide integration and continued operational and financial support from the Applicant and its affiliated structure are intended to ensure that .YGEIA remains actively used, securely operated and relevant as technologies and user needs evolve.

The ultimate purpose of .YGEIA is to create the trusted digital infrastructure of a global domain of knowledge and care—not simply a commercial showcase—uniting authenticity, education, professional standards, security and innovation within one controlled namespace.

§ 3 — Commitments and safeguards Q164–Q188

More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169No to each
Voluntary Safeguard PICs Q170·Q171None · 90 applications in the round offer some
Registry Voluntary Commitments Q172·Q173None · 5 do
Brand TLD criteria confirmed, trademark certificate attached Q180·Q181Yes · certificate not published
Confirms the string is not a “generic string” Q183Yes
Spec 11 §3(d) statement Q184

The applicant will operate the TLD exclusively as a .Brand TLD under Specification 13. Registrations will be limited to the applicant, its Affiliates as defined in Section 2.9(c), and Trademark Licensees, and the applicant will control the DNS records for all names at every level in the TLD. No domain names will be offered, sold, or licensed to the general public, and the applicant will not operate a secondary market in names within the TLD.

The applied-for string corresponds to the applicant's registered trademark and to the name under which it has traded since 2019. Within the TLD it will be used to identify properties and services originating from the applicant and its licensees — the same source-identifying function the mark performs offline. The TLD will not be presented, marketed, or held out as a namespace for the health sector, for health information generally, or for any class of goods or services beyond those the applicant itself supplies.

Because the string operates as a source identifier rather than as a term denominating a general class, its delegation removes nothing from the competitive field. Providers of health-related goods and services retain the Greek-script term υγεία, the English term "health," and every existing and future generic namespace addressing that sector. No competitor requires the applied-for string in Latin script to describe its own offering, and none is disadvantaged by the applicant's use of its own mark at the top level.

The applicant will certify its continued Specification 13 eligibility to ICANN annually and will notify ICANN if the conditions supporting that eligibility cease to be met.

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

Q212Q4.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), 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: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.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.

Q4.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), 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: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.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.

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

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