tld.report · La ronde 2026

Instantané du 8 octobre 2026 · ICANN APS, champs publics

Candidatures / .meinl / JMCG2659T-T65563 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.meinl

TLD de marque · Spec 13Active

JULIUS MEINL Central GmbH, AT Q1·Q25

Contrôle ultime déclaré : Thomas H. Meinl Q108 · Fiche ICANN ↗

§ 1 — Sens de la chaîne Q118·Q120

MEINL is the Applicant’s registered trademark, trade name and established brand. Originating from the founding family, it has identified the Applicant’s business since 1862 and corresponds directly to its corporate identity and trademark portfolio.

/ˈmaɪnl̩/

§ 2 — Mission et objet Q133

The mission and purpose of the applied-for .MEINL gTLD is to serve as a trusted, secure, and centrally governed digital namespace for JULIUS MEINL Central GmbH (the “Applicant” or "Julius Meinl") and its authorised users.

The .MEINL gTLD will support the Applicant's online presence and established digital activities by providing a secure and clearly identifiable space for official corporate, product, service, marketing, hospitality, and customer-facing communications associated with the MEINL name and related commercial activities.

The Julius Meinl business has a heritage dating back to 1862 and longstanding international activities centred on premium coffee, tea, and related products and services. Within the wider company structure associated with these activities, the Applicant has historically performed central functions relating to domain name management and key Internet infrastructure. The coffee business provides livelihoods to over 100'000 people and has subsidiaries or distribution partners in most of the key markets around the world.

The registry will be operated for the benefit of the Applicant and authorised entities within this wider company structure. Registrations may support official websites, product and service information, marketing campaigns, customer engagement, corporate communications, hospitality-related activities, and other legitimate activities associated with the MEINL name.

Since 1994, the Applicant has managed the MEINL online namespace and related Internet assets, beginning with meinl.com and encompassing MEINL-related domain names across multiple TLDs, including meinl.net, meinl.org, meinl.at, meinl.it, meinl.coffee, and meinl.eu. An overview of this domain name portfolio is provided as supporting documentation.

The Applicant's responsibilities also include the management of PI IPv4 and IPv6 address space and related RIPE accounts used within the wider company structure, SSL certificates and associated Internet infrastructure, as well as significant network connectivity infrastructure in Vienna. These longstanding responsibilities demonstrate the Applicant's central role in managing domain names and Internet infrastructure within the wider company structure.

The Applicant is the registered proprietor of a MEINL word mark corresponding to the applied-for .MEINL string. The .MEINL gTLD represents a natural extension of these trademark rights and of the Applicant's longstanding responsibility for MEINL-related domain names and Internet infrastructure.

The .MEINL gTLD will support the consistent presentation and protection of the MEINL name in the digital environment by enabling official and authorised MEINL-related resources to operate within a trusted namespace controlled by the Applicant. It will also support trademark governance, intellectual property protection and digital identity objectives by allowing authorised MEINL-related domain names to remain under centralised strategic, legal, and operational control.

The Applicant already owns 6x 255 PI ipv4 addresses, 5x /48 PI ipv6 address spaces and 200+ MEINL related domains. The Applicant's established management of MEINL-related domain names, IP resources and Internet infrastructure demonstrates that the .MEINL gTLD is a natural extension of existing activities rather than a new or speculative undertaking. The Applicant intends to maintain the namespace as a controlled registry for official and authorised MEINL-related use, ensuring trusted and consistent online communications over time.

§ 3 — Engagements et sauvegardes Q164–Q188

Confiance accrue, risque pour le consommateur, secteur réglementé, déclarations à l'État, préjudice, fonction régalienne Q164–Q169Non à chacune
PIC de sauvegarde volontaires Q170·Q171Aucun · 90 candidatures de la ronde en proposent
Registry Voluntary Commitments Q172·Q173Aucun · 5 en proposent
Critères de TLD de marque confirmés, certificat de marque joint Q180·Q181Oui · certificat non publié
Confirme que la chaîne n'est pas une « generic string » Q183Oui
Déclaration Spec 11 §3(d) Q184

The applied-for .MEINL gTLD is intended to operate as a Specification 13 dotBrand registry associated with the Applicant's registered MEINL trademark.

The Applicant intends to operate the .MEINL gTLD as a closed .BRAND registry in accordance with the Registry Agreement and the commitments applicable to Specification 13 dotBrand registries. Registrations will be limited to the Applicant and, where appropriate, authorised affiliated entities under the Applicant’s direct control. The .MEINL gTLD will not operate as an open or unrestricted namespace, and domain names will not be made available for registration by unaffiliated third parties.

The primary purpose of the .MEINL gTLD is to provide a trusted, secure and authentic namespace supporting the Applicant’s digital strategy and online presence. The Applicant intends to use the TLD to strengthen and protect its brand identity across digital channels while providing a consistent and reliable online identity for its legitimate business activities. The Applicant also regards the .MEINL gTLD as part of its broader trademark management, brand governance, intellectual property protection, and digital identity strategy, supporting consistent and controlled use of the MEINL trademarks across digital channels.

Depending on operational and business requirements, domain names within the .MEINL gTLD may be used by the Applicant and, where appropriate, its authorised affiliated entities for purposes including corporate websites, product and brand information, customer-facing services, digital communications, marketing and promotional campaigns, authenticated online services, internal platforms, and other legitimate business purposes consistent with the Applicant’s internal policies, trademark strategy, and brand governance requirements. As the Applicant’s digital strategy evolves, additional business uses may be developed, provided they remain consistent with the Registry Agreement and the operating model of a Specification 13 dotBrand registry.

All registrations within the .MEINL gTLD will be centrally controlled and managed by the Applicant. All registrations and authorised use within the .MEINL gTLD will remain subject to the Applicant’s continuing strategic, legal, and operational control. Appropriate internal governance procedures will be maintained to review, approve and administer domain name registrations throughout their lifecycle. The Applicant will retain full oversight of the namespace and will ensure that domain names are registered, maintained and used only for legitimate business purposes consistent with the Applicant’s internal policies, the Registry Agreement, and applicable laws and regulations. Where necessary, domain names may be modified, suspended or retired if they are no longer required or no longer comply with those policies.

This operating model enables the Applicant to maintain continuous oversight of all registrations and their use while ensuring that the namespace remains dedicated to the Applicant and, where appropriate, its authorised affiliated entities. As registrations are centrally controlled, restricted to authorised entities and not made available to independent third parties, the Applicant does not anticipate any circumstance in which the operation of the .MEINL gTLD would create a conflict with Section 3(d) of Specification 11. The Applicant will maintain appropriate policies and oversight mechanisms to ensure that domain names registered within the .MEINL gTLD are used in a manner consistent with the Registry Agreement and applicable laws and regulations.

The registry will therefore be operated in a manner intended to preserve the integrity, distinctiveness, reputation, and goodwill associated with the MEINL trademarks, while ensuring the consistent and controlled use of the namespace across digital channels.

§ 4 — Toutes les autres réponses publiées

Toutes les autres réponses que l'ICANN a publiées pour cette candidature, dans l'ordre du formulaire. Les coordonnées (Q17–Q24) sont laissées à la fiche ICANN.

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.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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