.god

Q2.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) of the applying entity, 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: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.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.

Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).

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

Explain the rationale for any limitations to the commitment proposed by the applying entity in Question 173.

See corresponding documentation to this question for a more comprehensive analysis of the limitation and rationale of each RVC proposed.

Why are the commitment(s) being proposed?

See corresponding documentation to this question for a more comprehensive analysis of the purpose, necessity, and compatibility of each RVC proposed

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

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.

LFG intends to implement Registrant verification as part of the TLD’s Terms of Service to ensure a secure, trusted and responsible namespace. LFG anticipates a risk-based, technology-neutral approach capable of accommodating reliable verification methods available in different jurisdictions. Methods may include government-issued identification or authoritative records, qualified third-party identity verification services, and digitally signed or cryptographically verifiable identity credentials.

As part of its due diligence, LFG reviewed ICANN Registry Services Evaluation Policy (RSEP) requests involving registrant authentication and verification. fTLD Registry Services’ approved Dynamic Registration Verification request for .BANK and .INSURANCE provides an example incorporating pre-verification, ongoing re-verification and registry audit capabilities. LFG also reviewed Amazon Registry Services’ approved Registration Authentication and Customer Discovery Tool. These precedents demonstrate approaches for integrating registrant verification into registry operations while preserving the Registrar channel. As a European-based Registry Operator, LFG also recognizes the continuing development of trusted digital identity frameworks. Regulation (EU) 2024/1183, commonly referred to as eIDAS 2.0, establishes the European Digital Identity framework and European Digital Identity Wallet ecosystem, through which individuals and organizations can identify themselves and present trusted identity attributes to public and private relying parties. Interoperable digital identity wallets and verifiable electronic attestations may become useful mechanisms for future domain-name registrant verification. Based on this precedent LFG believes that a RSEP is the more optimal path forward towards implementing Registrant Verification as opposed to a PICs or RVC.

Similarly, ISO/IEC 18013-5 establishes specifications for mobile driving licences (mDLs), including mechanisms enabling a verifier to obtain credential data, bind the credential to its holder, authenticate its origin and verify its integrity. Standards-based credentials may provide privacy-preserving alternatives to collecting and retaining copies of physical identity documents. LFG therefore intends to design its Registrant verification program to remain adaptable as trusted digital identity ecosystems mature. The objective is not to mandate a single technology or credential worldwide, but to establish a robust framework capable of accepting reliable, interoperable and appropriately secure methods of establishing registrant identity. Implementation will take account of applicable privacy and data-protection requirements, including data minimization and security, and will seek where practicable to verify necessary attributes without retaining unnecessary identity documentation.

Final procedures and accepted credential types will be developed prior to launch. Registry Operator will engage its selected service providers and follow any applicable ICANN or RSP evaluation and approval processes required for implementation.

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