tld.report · The 2026 Round

Snapshot of 8 October 2026 · ICANN APS, public fields

Applications / .antel / ANDT2658T-T33133 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.antel

Brand TLD · Spec 13Active

Administración Nacional de Telecomunicaciones, UY Q1·Q25

ICANN record ↗

§ 1 — Meaning of the string Q118·Q120

"ANTEL" is the official name and registered trademark of Administración Nacional de Telecomunicaciones, a decentralized public service of the Oriental Republic of Uruguay providing telecommunications services.

/ˈæn.tɛl/

§ 2 — Mission and purpose Q133

The mission and purpose of the .ANTEL gTLD are to provide a secure and dedicated online namespace for Administración Nacional de Telecomunicaciones (ANTEL), supporting ANTEL's digital identity and strengthening the recognition and protection of the ANTEL brand. The intended registrants are ANTEL, its Affiliates, and authorized Trademark Licensees, in accordance with Specification 13 of the Registry Agreement. The intended users include ANTEL's customers, employees, business partners, suppliers, and other stakeholders accessing official ANTEL online resources and services. The .ANTEL gTLD will support ANTEL's official websites, digital platforms, customer-facing services, corporate communications, and other online resources associated with the ANTEL brand. Its implementation will contribute to strengthening user confidence, reducing the risk of fraud and phishing, improving brand recognition, and supporting ANTEL's digital transformation strategy. ANTEL will progressively implement the .ANTEL namespace across its official online presence and digital services, in accordance with its digital strategy and operational requirements. The .ANTEL namespace will be used to support existing and future online initiatives while ensuring that official ANTEL services and communications are clearly identifiable and associated with the ANTEL brand. The mission and purpose of the .ANTEL gTLD are sustainable over time because they are directly linked to ANTEL's long-term institutional mission, established brand identity, and its continued provision of telecommunications services in Uruguay. As ANTEL continues to expand and modernize its digital services, the .ANTEL namespace will remain an integral component of its digital strategy, providing a secure and trusted environment for its online presence and future digital services and initiatives.

§ 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 .ANTEL gTLD will be operated exclusively as a .Brand TLD in accordance with Specification 13 of the Registry Agreement. Domain names will be registered solely for ANTEL, its Affiliates, and authorized Trademark Licensees, and will be used exclusively to support ANTEL's official operations, digital services, corporate communications, internal functions, customer-facing services, and other legitimate business activities associated with the ANTEL brand.

ANTEL does not intend to operate .ANTEL as an open or commercial registry, nor will it register domain names for the primary purpose of selling, reselling, warehousing, or otherwise engaging in speculative domain name activities. Domain names will be assigned only where they serve a legitimate operational, administrative or business purpose consistent with ANTEL's corporate objectives and brand strategy.

Accordingly, the operation of the .ANTEL gTLD will not create any conflict with Section 3(d) of Specification 11. The restricted registration model established by Specification 13, together with ANTEL's intended use of the namespace exclusively for its own benefit and that of its Affiliates and authorized Trademark Licensees, ensures that the .ANTEL gTLD will not be used for speculative registration practices or the commercialization of domain names.

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

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