.human

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.

ADDITIONAL INFORMATION AND SUPPORTING MATERIALS.

Submitted exhibits are listed in the Attachment Link column.

COMMUNITY ALIGNMENT NARRATIVE. Although Human Centered Holdings LLC (HCH) is applying for .human as a Standard gTLD rather than a Community gTLD, the applying entity is substantively aligned with the human-centered community and has designed the registry to serve it. Because every human advance in history has begun as a creative act, creative practitioners and creators are expressly included as a first-class constituent sector. This alignment is operationalized in the published Registry Policies described below.

FORMATION PURPOSE. HCH was organized as a Delaware LLC for the specific purpose of applying for, securing, and operating the .human top-level domain. The Operating Agreement, Subscription Agreement, and Backer Joinder bind the entity to this purpose.

FOUNDER CONNECTION. Founder & Manager Justin O'Mara Henning holds prior leadership experience in the human-centered nonprofit sector, including leadership of 'Being Human' (a nonprofit dedicated to human dignity initiatives), and has spent his career building infrastructure for civil-society organizations, mental-health and wellness practitioners, and creative practitioners.

BACKER COMPOSITION. Backers admitted under the Subscription Joinder and Terms of Commitment were selected for alignment with the human-centered community; each signed a Terms of Commitment supporting HCH's stewardship role.

CONSTITUENT SECTORS. The applying entity identifies six constituent sectors: (1) civil-society and nonprofit organizations; (2) mental-health and wellness practitioners; (3) human-rights advocates; (4) ethical-AI signatories; (5) dignity-focused initiatives; and (6) creative practitioners and creators. Each sector holds a dedicated seat on the Community Advisory Council established under the Registry Policies.

REGISTRY DESIGN. The published Registry Policies (voluntary eligibility verification with a creative-practitioner path, name selection safeguards, DNS abuse policy, six-seat Community Advisory Council, and an annual Community Impact Report) operationalize the community-aligned design as public, transparent registry policy; a community reinvestment target of no less than 5% of audited annual net surplus (Registry Policy Section 8) is likewise maintained as published registry policy and reported annually. The Registry Policies document is filed as an exhibit to this response.

ADDRESSABLE COMMUNITY. The community served by .human is large, global, and growing: ~1.8M registered U.S. 501(c)(3)s plus international equivalents, 700K+ licensed mental-health practitioners, tens of millions of creative practitioners, and the signatory communities of major ethical-AI frameworks (Asilomar, Montreal Declaration, IEEE, Partnership on AI, OECD, UNESCO).

PRE-EXISTING PRESENCE. The community's institutional presence pre-dates this application by decades: the Universal Declaration of Human Rights (1948), the Authors Guild (1912), AIGA (1914), PEN America (1922), the Recording Academy (1957), Creative Commons (2001), and recurring international convenings (RightsCon, AI for Good, World Mental Health Day, Sundance Film Festival).

CONTENTION POSTURE. This is a Standard gTLD application; the applying entity makes no claim to Community Priority Evaluation. If .human enters a string contention set, HCH will participate in ICANN's contention resolution mechanisms as prescribed for the 2026 round (noting private resolution among contention-set applicants is not permitted). The published Registry Policies will remain in place regardless of how contention is resolved.

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

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