Application Details

Last published on: 7 October 2026 at 15:35 UTC

Application Type: New gTLD

Primary String: juliusmeinl

TLD Types: Brand

Application ID: JMA2639T-T95985

Application Priority Number: --

Application Status: Active

Processing Stage: Pre-Evaluation Processing

Comment Period: --

View:

Summary Responses Clarifying Questions Change Requests Documents Objections

Application Responses

Section: Applying Entity Information

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.

AGB Q1. Full Legal Name

Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.

JULIUS MEINL AG

AGB Q2. Doing Business As

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.

JULIUS MEINL

AGB Q3. Legal Entity Form/Business Structure

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.

Public Limited Company

AGB Q4. Jurisdiction

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.

Switzerland

AGB Q10. Website URL

Provide the website URL of the applying entity, if available.

https://juliusmeinl.ch

AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?

1. Choose Yes or No. 2. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement).

false

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?

Choose Yes or No.

false

AGB Q17. Phone Country Code

AGB Q18. Primary Business Phone

Provide the primary business phone number without including the country code.

0815115411

AGB Q19. Primary Business Email Address

Provide the primary business email address of the applying entity.

juliusmeinl.net.ops.global.icann@juliusmeinl.ch

AGB Q20. Address Line 1

Enter the street address (no PO Box).

Gäuggelistrasse 1

AGB Q22. Locality

Enter the city, village, municipality, etc.

Chur

AGB Q23. State/Province/Region

Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.

Graubünden

AGB Q24. Postal Code

1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.

7001

AGB Q25. Country Code of Location

AGB Q26. Full Legal Name

If applicable, provide the full legal name as it appears on the official registration documents of the Direct Parent Company of the applying entity. Do not use abbreviations.

GELGIA AG

AGB Q28. Legal Entity Form/Business Structure

Provide the long form (no acronyms) of the legal entity form/business structure of the Direct Parent Company 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.

Private Limited Company

AGB Q29. Jurisdiction

The jurisdiction indicates the location in which the business of the Direct Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include "Delaware", "Germany", etc.

Switzerland

AGB Q36. Full Legal Name

If applicable, provide the full legal name as it appears on the official registration documents of the Ultimate Parent Company of the applying entity. Do not use abbreviations. "Ultimate Parent Company" means, with respect to an Applicant (and, if applicable, a Direct Parent Company), the top-level entity that directly or indirectly possesses the power to direct the management and policies of such Applicant (and, if applicable, a Direct Parent Company) through the ownership of voting securities, as a general partner, as a managing member, by contract, or otherwise. An Ultimate Parent Company is not controlled by any other entity. If there are no intermediary entities between the Applicant and the Ultimate Parent Company, the Ultimate Parent Company would be the same entity as the Direct Parent Company.

GELGIA AG

AGB Q37. Doing Business As

Provide the name under which the Ultimate Parent Company is doing business, if different from the full legal name answered in Question 36. Such a name must be registered with appropriate local jurisdiction or public authority.

GELGIA

AGB Q38. Legal Entity Form/Business Structure

Provide the long form (no acronyms) of the legal entity form/business structure of the Ultimate Parent Company 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.

Private Limited Company

AGB Q39. Jurisdiction

The jurisdiction indicates the location in which the business of the Ultimate Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include "Delaware", "Germany", etc.

Switzerland

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

Section: DNS Abuse

Provide a single document for Self-Certification question AGB Q221, Q5.2-1. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. Do not modify any of the Self-Certification statements. If 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.

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

1. Provide a single document for Self-Certification question Q5.2-1. 2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. 3. Do not modify any of the Self-Certification statements. 4. 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.

Has Documents

Section: Primary String

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.

AGB Q116. Applied-for Primary String (ASCII Label)

juliusmeinl

AGB Q118. What is the meaning/definition of the applied-for gTLD string?

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"

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

AGB Q119. Script of String

If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)

Latin

AGB Q120. Phonetic Representation

Provide a representation of the string according to the International Phonetic Alphabet.

/ˈjuːli̯ʊs ˈmaɪnl/

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.

Confirm the statement using a checkbox.

true

AGB Q133. What is the mission and purpose of the applied-for gTLD?

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. 1a. 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. 2. Explain how this purpose is sustainable over time.

The mission and purpose of the applied-for .JULIUSMEINL gTLD is to serve as a trusted, secure, and centrally governed digital namespace for JULIUS MEINL AG (the “Applicant” or "Julius Meinl") and its authorised users. The .JULIUSMEINL 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 JULIUS MEINL name and related commercial activities. The Julius Meinl business and its subsidiaries have 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 JULIUS MEINL name. Since 1994, the Applicant has managed the JULIUSMEINL online namespace and related Internet assets, beginning with juliusmeinl.com and encompassing JULIUSMEINL-related domain names across multiple TLDs, including juliusmeinl.org, juliusmeinl.at, juliusmeinl.it, juliusmeinl.shop, juliusmeinl.ch, and juliusmeinl.eu. An overview of this domain name portfolio is provided as supporting documentation. The Applicant's responsibilities also include the management of related RIPE accounts used within the wider company structure, SSL certificates and associated Internet infrastructure. 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 JULIUSMEINL word mark corresponding to the applied-for .JULIUSMEINL string. The .JULIUSMEINL gTLD represents a natural extension of these trademark rights and of the Applicant's longstanding responsibility for JULIUSMEINL-related domain names and Internet infrastructure. The .JULIUSMEINL gTLD will support the consistent presentation and protection of the JULIUS MEINL name in the digital environment by enabling official and authorised JULIUSMEINL-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 JULIUSMEINL-related domain names to remain under centralised strategic, legal, and operational control. The Applicant already owns 50+ JULIUSMEINL related domains. The Applicant's established management of JULIUSMEINL-related domain names, IP resources and Internet infrastructure demonstrates that the .JULIUSMEINL 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 JULIUSMEINL-related use, ensuring trusted and consistent online communications over time.

Has Documents

Section: Safeguard Identification

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.

AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD? Think 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.

1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.

AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused? Think 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.

AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business? Think 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.

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? Think 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.

AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.

AGB Q169. Would most people think that the TLD is used for something usually done by governments? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.

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?

Select Yes or No. Notes: 1. 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). 2. 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. 3. 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).

Section: Registry Voluntary Commitments (RVCs)

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.

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?

1. Select Yes or No. 2. 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). 3. 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. 4. 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). Notes: If 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.

Section: Brand & Code of Conduct Exemptions

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

AGB Q179. Are you applying for a Brand TLD?

Select Yes or No

Yes

AGB Q180. The applying entity confirms that the applied-for gTLD string meets the Brand TLD criteria as described in Section 9.3 of Specification 13. The applying entity also confirms their understanding of contractual obligation to maintain Brand TLD status and communicate changes in registration policies that could potentially disqualify the TLD as a Brand TLD.

Select Yes or No. Notes: If the applying entity selects “no,” it will be required to provide additional documentation describing which criteria is not met as well as a justification for the TLD to nonetheless qualify as a .Brand TLD.

Yes

Has Documents

AGB Q181. Submit Trademark Certificate

Attach an accurate and complete copy of the applicable trademark registration that forms the basis of the request for .Brand TLD qualification.

Has Documents

AGB Q183. The applying entity confirms that this applied-for string is not a “generic string” as defined in Section 3(d) of Specification 11 of the Base RA, which prohibits generic TLDs from being operated on an exclusive basis.

Confirm statement with a checkbox.

true

AGB Q184. No Specification 11 Conflicts

Explain how the applying entity intends to operate the TLD such that there would not exist any such conflict with Section 3(d) of Specification 11.

The applied-for .JULIUSMEINL gTLD is intended to operate as a Specification 13 dotBrand registry associated with the Applicant's registered JULIUSMEINL trademark. The Applicant intends to operate the .JULIUSMEINL 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 .JULIUSMEINL 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 .JULIUSMEINL 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 .JULIUSMEINL gTLD as part of its broader trademark management, brand governance, intellectual property protection, and digital identity strategy, supporting consistent and controlled use of the JULIUS MEINL trademarks across digital channels. Depending on operational and business requirements, domain names within the .JULIUSMEINL 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 .JULIUSMEINL gTLD will be centrally controlled and managed by the Applicant. All registrations and authorised use within the .JULIUSMEINL 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 .JULIUSMEINL 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 .JULIUSMEINL 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 JULIUS MEINL trademarks, while ensuring the consistent and controlled use of the namespace across digital channels.

Application Details

Application Responses

Section: Applying Entity Information

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

Section: DNS Abuse

Section: Primary String

Section: Safeguard Identification

Section: Registry Voluntary Commitments (RVCs)

Section: Brand & Code of Conduct Exemptions

Section: Additional Information and Supporting Materials

Section: Bona Fide Intent and Prohibited Communications