.prompt

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.

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.

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.

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

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.

.Prompt Inc. provides the following additional information to assist the public in understanding the background, intended operation, and development of the .PROMPT application.

.Prompt Inc. is not approaching .PROMPT solely as a new or speculative namespace. The company currently operates a “.prompt” identifier within a Web3/alternative namespace and has an existing base of registrations and associated revenue. The application for .PROMPT represents an effort to extend that existing identity and experience into the ICANN-administered Domain Name System while recognizing that operation of an ICANN gTLD involves materially different technical, contractual, rights-protection, and compliance requirements.

.Prompt Inc. has also made sustained efforts to protect the PROMPT identity through trademark registration. The company holds a registered United Kingdom trademark for PROMPT and has pending trademark applications before the European Union Intellectual Property Office (EUIPO), the Swiss Federal Institute of Intellectual Property, and the United States Patent and Trademark Office (USPTO). These filings reflect .Prompt Inc.’s ongoing use of, and good-faith commitment to, the PROMPT identity independently of this gTLD application.

.Prompt Inc. intends to operate .PROMPT as an open generic TLD. Registration will not require proof of affiliation with the artificial intelligence industry. While the mission and market positioning of .PROMPT are centered on artificial intelligence, prompt-driven interaction, AI tools, agents, digital identities, and related technologies, individuals and organizations may register available .PROMPT domains for any lawful purpose consistent with applicable registry policies.

.Prompt Inc. also intends to provide a limited customer-continuity opportunity for eligible holders of its pre-existing Web3 “.prompt” identifiers. Any such migration program will be implemented only in a manner consistent with applicable ICANN Rights Protection Mechanisms, including the priority afforded to eligible trademark holders through Sunrise and applicable Trademark Claims requirements. The program is intended to recognize .Prompt Inc.’s own existing customers and is not intended to displace or circumvent trademark protections.

The planned commercial strategy for .PROMPT combines distribution through ICANN-accredited registrars, outreach to the AI, developer, creator, agency, and technology communities, and awareness generated from .Prompt Inc.’s existing user base. The company expects .PROMPT to serve organizations and individuals using AI models, tools, conversational interfaces, digital twins, agents, chatbots, and other emerging forms of human-to-AI and system-to-AI interaction.

.Prompt Inc. recognizes that an AI-oriented namespace may attract heightened attention regarding fraud, impersonation, DNS Abuse, and other misuse. The company intends to maintain registry policies and operational practices addressing abuse consistent with its obligations under the Base Registry Agreement and applicable Consensus Policies, while keeping those measures appropriately scoped to the role and technical capabilities of a registry operator.

.Prompt Inc. intends to develop .PROMPT as a durable, broadly accessible namespace that can evolve with artificial intelligence technologies rather than depend on any single model, platform, company, or technical architecture.

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

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