Last published on: 7 October 2026 at 15:22 UTC
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.
Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.
17161573 Canada Inc.
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.
17161573 Canada Inc.
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.
Private Indigenous Business
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.
Canada
Provide the website URL of the applying entity, if available.
http://17161573.ca
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
Choose Yes or No.
false
1
Provide the primary business phone number without including the country code.
8673339960
Provide the primary business email address of the applying entity.
amanda.buffalo@proton.me
Enter the street address (no PO Box).
#5 Pelly Banks, Robert Campbell Highway
Enter the city, village, municipality, etc.
Pelly Banks (Ross River)
Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.
YT
1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.
Y0B 1S0
CA
This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.
Erika Gilson
Amanda Buffalo, Erika Gilson, Amanda Buffalo
Provide a single document for Self-Certification question Q4.2-1. The document must include only the SC4.2-1.1, SC4.2-1.2, or SC4.2-1.3 statements. Do not modify any of the Self-Certification statements.
1. Provide a single document for Self-Certification question Q4.2-1. 2. The document must include only the SC4.2-1.1 through SC4.2-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC4.2-1.1 through SC4.2-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC4.2-1.1 through SC4.2-1.3 statements.
Provide a single document for Self-Certification question AGB Q220, Q5.1-1. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements.
1. Provide a single document for Self-Certification question Q5.1-1. 2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1.1-3 statements.
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.
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.
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.
indigenous
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"
"Indigenous" refers to peoples and nations who are the original inhabitants of a particular land or territory and maintain distinct cultural, political, and social identities from the societies that subsequently colonized or settled those territories.
Provide a representation of the string according to the International Phonetic Alphabet.
/ɪnˈdɪdʒənəs/
Confirm the statement using a checkbox.
true
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.
Mission: establish .indigenous as a dedicated, Indigenous-owned and governed namespace within the Domain Name System that serves the global Indigenous community by providing digital infrastructure that generates own-source revenue for Indigenous peoples, advances Indigenous digital sovereignty, and ensures that Indigenous nations, governments, organizations, and businesses can establish authentic and verifiable online identities. The purpose of the .indigenous TLD is fourfold: 1. Digital Sovereignty and Self-Determination - Indigenous peoples have historically been excluded from the governance and infrastructure of the internet. The .indigenous TLD creates a namespace that is owned, operated, and governed by Indigenous peoples, ensuring that decisions regarding eligibility, policy, administration, and revenue distribution remain within Indigenous control. This aligns with the United Nations Declaration on the Rights of Indigenous Peoples (UNDRIP), particularly Articles 3, 4, and 31, which affirm the right of Indigenous peoples to self-determination and to control developments affecting them and their resources. 2. Economic Development and Own-Source Revenue - The .indigenous TLD is structured as a revenue-generating registry operated by 17161573 Canada Inc., a wholly Indigenous-owned entity. Domain registration fees generate ongoing own-source revenue that is directed toward Indigenous community development, rather than extracted by external entities. The tiered pricing model ensures accessibility for Indigenous governments and organizations while capturing fair market value from Indigenous commercial enterprises. 3. Authenticity and Verification - The .indigenous TLD provides a trusted and verifiable namespace where Indigenous nations, governments, organizations, and businesses can establish their digital presence with authenticity. In an era of online misrepresentation, cultural appropriation, and identity fraud, .indigenous domains serve as a signal of verified Indigenous identity and legitimacy. Eligibility criteria require registrants to demonstrate their status as Indigenous nations, governments, organizations, or businesses, creating a namespace that the public can trust as genuinely Indigenous. 4. Cultural Continuity and Global Connection - The TLD creates a shared digital namespace that connects Indigenous peoples across borders — from First Nations in Canada to Native American tribes, Alaska Native corporations, Native Hawaiian organizations, Māori iwi, Aboriginal and Torres Strait Islander entities, Sámi communities, and Indigenous peoples worldwide. This fosters cross-cultural connection, knowledge sharing, and solidarity among Indigenous nations while preserving each community's distinct identity through their domain presence. Intended Users: Members of the public seeking authentic Indigenous goods, services, governance information, cultural resources, and community connections. The TLD serves as a navigational trust signal — a .indigenous domain tells a visitor that the entity behind it has been verified as Indigenous. Intended Registrants: Indigenous nations, governments, and tribal councils (e.g., First Nations in Canada, federally recognized tribes in the US, Alaska Native corporations, Native Hawaiian organizations, Māori iwi, Aboriginal and Torres Strait Islander entities). First Nation development corporations, tribal enterprises, and Indigenous commercial businesses. Indigenous small businesses, cultural organizations, language revitalization programs, and educational institutions. Individual registrations are deferred until Year 3 to anchor the namespace with institutional registrants first. Related Activities: The applying entity secured ASP qualification as the sole Indigenous applicant, employing a back-end registry provider, develop tiered pricing balancing accessibility with revenue generation, and engaged Indigenous community organizations to inform registry policies.
This question set collects information specific to Community gTLDs. However, question 133 (Mission & Purpose) must be answered by all applying entities.
Yes
1. Provide the name of the community that the applying entity is committing to serve. 2. Describe the distinct aspects of the community.
Pelly Banks Dena is the founding community, with the .indigenous TLD serving the broader global Indigenous community—First Nations, tribes, Māori iwi, Sámi, Aboriginal peoples, and Indigenous nations across 70+ countries worldwide.
Enter a category that best describes your community. Some examples of community categories could include, but are not limited to: activity-based and volunteer groups, online or social media groups, religious or political groups, diasporic communities, linguistic communities, celebrity or sports team supporters.
Indigenous peoples and nations worldwide — a global community of distinct peoples who are the original inhabitants of their respective territories, maintaining historical continuity with pre-colonial societies, and possessing inherent rights to self-determination, lands, and cultural preservation as affirmed by the United Nations Declaration on the Rights of Indigenous Peoples (UNDRIP). This community encompasses over 370 million people across more than 70 countries, including First Nations, Inuit, and Métis in Canada; federally and state-recognized Native American tribes, Alaska Native corporations, and Native Hawaiian organizations in the United States; Aboriginal and Torres Strait Islander peoples in Australia; Māori iwi and hapū in Aotearoa New Zealand; Sámi peoples across Sápmi (Norway, Sweden, Finland, and Russia); and countless other Indigenous nations across Latin America, the Pacific, Africa, Asia, and the Arctic. Despite extraordinary cultural, linguistic, and political diversity, this global community is united by shared experiences of colonization, dispossession, and resilience, and by a collective commitment to maintaining distinct identities, governing their own affairs, and transmitting cultural knowledge across generations. The founding community served by the applying entity is Pelly Banks Dena, a distinct Kaska Dena community located at the confluence of the Pelly and Ross Rivers in the Yukon Territory, Canada. Pelly Banks Dena members are Dena people who speak the Pelly Banks dialect of the Kaska language — one of at least six recognized Kaska dialects, distinguished by unique grammatical features, phonology, and vocabulary. In 1956, the federal government forcibly amalgamated Pelly Banks band members into neighbouring Kaska First Nations without their consent. Despite this, Pelly Banks Dena members and descendants have continuously maintained their distinct identity, governance structures, and relationship to their ancestral territory. The community remains unrecognized as a separate First Nation by the Yukon and federal governments — a status that Pelly Banks Dena continues to challenge through governance resurgence, advocacy, and the re-establishment of its own governance body, the Pelly Banks (Nahonni Dena) Government. The sole shareholder and Director of the applying entity serves as a Director on the Board of the Pelly Banks (Nahonni Dena) Government and has acted as Special Advisor to Nahonni Dena leadership on inherent rights, title, and jurisdiction over Dena territory. The applying entity's commitment to serve this community is grounded in direct, lived relationship and accountability. The .indigenous TLD is designed to extend the principles of Indigenous self-determination into the digital realm — principles that Pelly Banks Dena embodies through its ongoing struggle for recognition, language preservation, and governance resurgence. The registry's community-based eligibility criteria, tiered pricing structure, and revenue-reinvestment model are all designed to serve Indigenous communities like Pelly Banks Dena: communities that have been historically excluded from infrastructure ownership, whose identities have been subject to external categorization and control, and whose economic self-sufficiency depends on developing new, self-governed revenue streams. By naming Pelly Banks Dena as the founding community and serving the broader global Indigenous community, the applying entity demonstrates that the .indigenous TLD is not an abstract commercial venture but a community-rooted initiative grounded in real relationships, real accountability, and a real commitment to Indigenous digital sovereignty.
Describe and provide evidence of the relationship between the applying entity and the identified community.
The applying entity, 17161573 Canada Inc., is a recently incorporated entity (2025) whose sole purpose is to acquire and operate the .indigenous TLD on behalf of the Indigenous communities it is committed to serving. The corporation itself is new, but its sole shareholder and Director brings nearly two decades of direct, sustained relationships with the identified community — relationships that predate the corporation and that form the foundation of the corporation's mandate to serve. Pelly Banks Dena — Founding Community The applying entity's leadership holds a governance role with the Pelly Banks (Nahonni Dena) Government, the governance body re-established by the community to advocate for its recognition, rights, and jurisdiction. This work has included advising Nahonni Dena leadership on inherent rights, title, and jurisdiction over Dena territory, and leading community consultations on the implementation of the UN Declaration on the Rights of Indigenous Peoples (UNDRIP) in Kaska Dena territory. Additional support to Pelly Banks governance resurgence includes initiatives funded through the Growing Change, Groundswell Community Justice Trust Fund and mapping work funded by Polar Knowledge Canada. The applying entity draws its commitment to serve Pelly Banks Dena directly from these relationships. Kaska Dena — Broader Community The applying entity's leadership has worked extensively with the broader Kaska Dena nation, including the collaborative development of a from-the-land Dena education framework developed with Kaska Dena Elders for the Liard Aboriginal Women's Society's Dena Gédḗní Kǫ́ā (Centre for Indigenous Women in Leadership) and the Tu Cho Centre for Dena Arts and Culture. This work has included advisory services to the Liard Aboriginal Women's Society, land-based curriculum development, and participation in steering committees for youth and advocacy initiatives within Kaska Dena communities. Yukon First Nations and National Indigenous Community The applying entity's leadership has worked with Indigenous communities across the Yukon and Canada for nearly two decades in professional and community-based capacities. This work includes collaborating with the Government of Yukon on culturally grounded programming for Indigenous women, girls, and 2S+ people; supporting research protocols and health surveys with the Council of Yukon First Nations; advancing cultural preservation and educational programming with the Kwanlin Dün Cultural Centre; and developing language plans and training-to-employment programming with the Champagne and Aishihik First Nations. On a national level, this work extends to governance roles with the Native Women's Association of Canada, and advocacy before the National Inquiry into Missing and Murdered Indigenous Women and Girls and the United Nations Special Rapporteur. The applying entity draws its mandate from these sustained relationships — it was established to carry this work forward into the digital infrastructure space, ensuring that the .indigenous TLD remains accountable to the communities it is committed to serving. The corporation was established to carry this work forward into the digital infrastructure space — the .indigenous TLD is an extension of these existing relationships and accountabilities, not a venture seeking community endorsement after the fact.
Describe and provide evidence related to the community organization, any relevant organizing bodies, and any relevant leaders within the community.
Community Organization The global Indigenous community is not organized under a single governing body. Indigenous peoples are diverse, sovereign nations and communities with distinct governance structures, legal traditions, and political systems that predate colonial state formations. No single organization represents or administers all Indigenous peoples worldwide, and the .indigenous TLD is not predicated on such a structure existing. Rather, the community is organized through layered and interconnected governance systems — from local community governments to regional and national Indigenous organizations to international bodies — each with distinct mandates, jurisdictions, and accountabilities. Pelly Banks Dena — Founding Community Organization Pelly Banks Dena is organized through the Pelly Banks (Nahonni Dena) Government, a governance body re-established by the community to advocate for its recognition, rights, and jurisdiction following its forcible amalgamation into neighbouring Kaska First Nations in 1956. The Nahonni Dena Government operates with a Board of Directors and maintains governance structures aligned with Kaska Dena legal orders and traditions. The applying entity's leadership holds a governance role within this body, providing a direct line of accountability between the corporation and the founding community. Yukon First Nations — Territorial Organization Yukon First Nations are organized through self-governing First Nation governments established under modern treaties (Umbrella Final Agreement), as well as through the Council of Yukon First Nations, which serves as a coordinating body for Yukon First Nations on matters of shared concern. There are 14 self-governing First Nations in the Yukon, each with distinct constitutions, citizenship codes, and jurisdictions. National and International Organization At the national level in Canada, Indigenous peoples are represented by organizations including the Assembly of First Nations, the Inuit Tapiriit Kanatami, the Métis National Council, and the Native Women's Association of Canada. In the United States, the National Congress of American Indians, the National Indian Gaming Commission, and regional inter-tribal organizations serve coordinating functions. In Australia, organizations such as the National Aboriginal and Torres Strait Islander Commission and land councils represent Aboriginal and Torres Strait Islander peoples. In Aotearoa New Zealand, iwi and hapū exercise tino rangatiratanga (self-determination) through both traditional and contemporary governance structures. At the international level, the UN Permanent Forum on Indigenous Issues, the Expert Mechanism on the Rights of Indigenous Peoples, and the Special Rapporteur on the Rights of Indigenous Peoples provide international advocacy and monitoring functions. None of these bodies represent all Indigenous peoples, and the .indigenous TLD does not claim endorsement from any single body. Rather, the TLD is designed to serve the community as it actually exists — diverse, self-organizing, and accountable to its own governance structures.
1. Describe any formal membership process, if there is one. 2. If there is no formal membership process, provide evidence related to how an individual can join the identified community (i.e., “self-identify” as a community member).
1. Formal Membership Process The global Indigenous community does not have a single, unified membership process. Membership and citizenship in Indigenous nations is determined by each nation according to its own laws, traditions, and governance structures. This is a fundamental aspect of Indigenous self-determination: the right to determine one's own citizens is an inherent right of Indigenous nations, not a function of external registration or centralized licensing. Indigenous membership and citizenship take many forms: Citizenship Codes and Enrollment Laws Many Indigenous nations maintain formal citizenship or enrollment processes governed by their own laws. In Canada, First Nations citizenship may be determined through community-specific membership codes established under the Indian Act or through self-government agreements that return citizenship determination to First Nation control. Modern treaty First Nations in the Yukon maintain their own constitutions and citizenship codes. In the United States, federally recognized tribes establish their own enrollment criteria, which may include blood quantum requirements, lineal descent, or community-based eligibility standards. Alaska Native corporations maintain shareholder enrollment records tied to ANCSA. In Australia, Aboriginal and Torres Strait Islander peoples may be recognized through three-part tests (descent, self-identification, and community acceptance) established in Australian law. In New Zealand, Māori affiliation is determined through whakapapa (genealogical connection) and iwi registration. Customary Law and Traditional Recognition Beyond formal state-recognized enrollment systems, Indigenous nations also determine membership through customary law, kinship systems, clan affiliations, and oral histories. These systems predate colonial governance structures and remain authoritative within many communities. For example, Kaska Dena society is traditionally matriarchal, organized into Wolf and Crow moieties, with clan and kinship relationships determining roles, responsibilities, and belonging. These customary systems are not "informal" — they are legal orders with their own rules, processes, and authorities. Non-Recognition and Contested Status Importantly, not all Indigenous communities have been permitted by colonial states to maintain or administer their own membership. Pelly Banks Dena, the founding community for this application, was forcibly amalgamated into neighbouring Kaska First Nations by the federal government in 1956, and remains unrecognized as a separate First Nation by the Yukon and federal governments. Despite this legal non-recognition, Pelly Banks Dena members and descendants maintain their distinct identity through self-identification, kinship networks, cultural practice, and governance resurgence through the Pelly Banks (Nahonni Dena) Government. This case illustrates that Indigenous membership and belonging cannot be reduced to state-administered enrollment — it persists through community relationships, shared territory, language, and governance, even where the state refuses to recognize it. 2. How Individuals Join or Self-Identify Because the global Indigenous community is not a single organization with a membership roster, there is no universal joining process. An individual's membership in the Indigenous community is determined through their relationship to a specific Indigenous nation, community, or people. The pathways are multiple and nation-specific. These include, but may not be limited to: 1. Birth and Descent, 2. Community Acceptance, 3. Enrollment or Registration, and 4. Self-Identification.
Provide the primary location of the community.
Pelly Banks Dena are located throughout Kaska territory in the Yukon (Pelly Banks, Ross River, Watson Lake, Upper Liard, Tu Cho) and Northern BC (Lower Post, etc.)
1. Provide the estimated size of the community. The size should be in number format (e.g., “1,000,000 members”). 2. If the community is divided by group, region, sector, etc., this should include estimated size for each group.
There are approximately 3,000 Kaska Dena (of which Pelly Banks forms part), and the global estimated Indigenous population is over 370 million across 70+ countries.
Provide the estimated size of the community that is administered or represented by each relevant organizing body in the identified community.
No single body represents all 370+ million Indigenous peoples worldwide. Multiple local, regional, national, and international organizations each represent specific nations, communities, or regions — none administer more than a fraction of the total.
1. Provide evidence of any documented practices of community efforts to date 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Offering support; b) Sharing information; c) Responding to specific community needs; d) Fostering and strengthening relationships within the community.
The founding community, Pelly Banks (Nahonni Dena) Government, demonstrates active engagement alongside other Indigenous community bodies serving the broader Indigenous community: (a) Offering Support: The Pelly Banks (Nahonni Dena) Government provides governance support through territorial mapping initiatives, UNDRIP implementation consultations, and governance resurgence work. Community partners operate land-based education centers and cultural programming initiatives, supported by infrastructure funding secured through Indigenous Services Canada's Indigenous Community Infrastructure Fund (2023–2025). (b) Sharing Information: Engagement efforts include participation in public forums such as the Canadian Political Science Association Conference (2022, 2025), NAISA (2022), Yukon MMIWG2S+ Annual Accountability Forum (annually), testimony before the House of Commons Standing Committee on the Status of Women (Nov 2024), and community-based teaching roles, partnering with various academic institutions (e.g. Dechinta, University of Toronto, etc.). (c) Responding to Needs: Food sovereignty grants supporting land-based education centers (2025); Data sovereignty initiative for MMIWG2S+ database, receiving innovation funding from Grand Challenges Canada (2024); Language revitalization programming for Kaska Dena communities; Safety and justice consultations with families and survivors for Yukon's MMIWG2S+ Strategy. (d) Fostering Relationships: Collaboration between Pelly Banks Dena and community organizations strengthens intergenerational and cross-community bonds across Kaska Dena territory. Governance and advisory networks sustain relationships across the Yukon. Academic partnerships foster relationships between Indigenous communities and institutions through land-based education programming.
1. Describe whether the applying entity has a role in any of the activities listed in Question 141. 2. If the applying entity does play a role, provide evidence of the applying entity’s role. If the applying entity does not play a role, describe why this is the case.
Role Description: The applying entity plays a central role in the engagement efforts listed above. While 17161573 Canada Inc. was incorporated in 2025, the entity was established specifically to institutionalize and carry forward community-rooted work into the digital infrastructure space. The entity acts as the legal vehicle through which community engagement is organized, resourced, and directed toward establishing and operating the .indigenous TLD. 2. Evidence of Role: Relationship Stewardship: The applying entity's leadership holds formal governance roles within the Pelly Banks (Nahonni Dena) Government and maintains advisory and collaborative relationships with community organizations. These pre-existing relationships form the basis of the entity's mandate and ensure registry operations remain accountable to communities served. Resource Mobilization: The applying entity has played a direct role in securing funding to support community-identified priorities, including infrastructure funding for land-based education centers, innovation funding for MMIWG2S+ data projects, and mapping funding from Polar Knowledge Canada. These grants demonstrate the entity's capacity to convert community needs into resourced action. Policy Development: The applying entity translates community engagement into registry policy. The .indigenous TLD's eligibility criteria, tiered pricing model, and revenue-reinvestment framework were developed in response to community priorities identified through UNDRIP consultations, language revitalization work, and governance resurgence efforts with Pelly Banks Dena and partner organizations. Operational Continuity: By incorporating this work into 17161573 Canada Inc., the applying entity transforms relationship-based advocacy into sustainable infrastructure. The .indigenous TLD itself becomes the mechanism for continued community engagement—each registration and renewal generates revenue that supports the mission, and the registry's governance model incorporates ongoing community consultation. In summary, the applying entity serves as the operational arm converting community relationships into digital infrastructure. Evidence lies in the governance roles held by its leadership, funding secured under its direction, and policy frameworks developed to align TLD operations with community priorities.
1. Provide evidence that demonstrates that community members are aware of the identified community and the different member groups or segments within the identified community. 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Surveys conducted; b) Records of activities involving a diversity of community groups, segments, or members.
Yes, community members are aware of the identified community and each other. The global Indigenous community maintains interconnected networks through shared governance structures, language families, kinship systems, and collaborative advocacy initiatives. Members of distinct nations—such as Pelly Banks Dena, Ross River Dena, Liard First Nation, and other Kaska Dena groups—are aware of one another through traditional territory overlaps, intermarriage, and modern political organizations. Beyond the founding community, awareness extends globally through international Indigenous rights frameworks, digital communication, and cross-border solidarity movements. Awareness is demonstrated through the active participation of community members in shared governance, cultural, and advocacy processes. Indigenous nations in the Yukon and British Columbia, including Kaska Dena communities, regularly convene for treaty negotiations, land claims, and resource management discussions where delegates from different groups interact. The existence of regional coordinating bodies, such as the Kaska Dena Council, facilitates ongoing communication among member bands regarding shared priorities. Furthermore, the widespread adoption of the UN Declaration on the Rights of Indigenous Peoples (UNDRIP) has created a common language of rights and self-determination that connects distinct communities across jurisdictions. In the digital space, awareness is reinforced through existing Indigenous-owned and operated websites, social media channels, and communication platforms that link communities. For example, initiatives addressing Missing and Murdered Indigenous Women, Girls, and 2S+ People (MMIWG2S+) have necessitated cross-jurisdictional cooperation, ensuring that families and advocates in Yukon, British Columbia, and beyond are aware of parallel struggles and support mechanisms. This visibility fosters a sense of shared identity despite geographic and political fragmentation caused by colonial borders. 2. Documentation of Practices (Aug 2024–Aug 2026) a) Surveys/Consultations: UNDRIP implementation consultations with Pelly Banks (Nahonni Dena) Government and Kaska Dena stakeholders (2024–2026); MMIWG2S+ data sovereignty surveys conducted through The RedString Project connecting families across regions (2024); Kaska Dena language revitalization assessments engaging speakers across dialect groups (2024–2025). b) Activities Involving Diverse Community Groups: MMIWG2S+ family gatherings uniting survivors and families from across Yukon and British Columbia (2023–2024); land-based education programming at the Tu Cho Centre bringing together Elders, youth, and knowledge keepers from multiple communities (2024–2026); governance and strategic planning sessions with Pelly Banks (Nahonni Dena) Government involving women's organizations, youth councils, and Elder circles (2024–2026).
1. Provide evidence of community members’ awareness of the applying entity and its intent to apply for a community gTLD. 2. If there is no such evidence, explain why not.
1. Evidence of Community Awareness Key leaders of the Pelly Banks (Nahonni Dena) Government — the founding community — are aware of the applying entity and its intention to apply for the .indigenous gTLD. The sole shareholder and Director of 17161573 Canada Inc. communicated the intent to pursue the TLD application directly with Pelly Banks leadership, who provided instruction to proceed with the application. This awareness exists at the governance level of the founding community, where the decision to support the application was made through existing accountability structures between the applying entity's leadership and the Nahonni Dena Government Board of Directors. 2. Explanation of Limited Dissemination Awareness has not been widely disseminated across the broader Indigenous community at this stage, for the following reasons: Novelty of the Endeavour: This is the first application for a wholly Indigenous-owned gTLD in the history of the Internet Corporation for Assigned Names and Numbers (ICANN). The concept of a top-level domain as community infrastructure — and the technical, financial, and governance implications of operating a registry — is not widely understood outside of specialized Internet governance circles. Premature dissemination before the application was structurally sound and financially feasible (confirmed through ASP qualification on August 7, 2026) risked creating confusion or unrealistic expectations within communities that have no precedent for this type of initiative. ASP Qualification Timeline: The Applicant Support Program (ASP) qualification was a prerequisite for the application's viability. Until ASP approval was confirmed, the application's feasibility was uncertain. Widely communicating an application that might not proceed due to financial constraints would have been irresponsible. The August 7, 2026 ASP notification left five days before the August 12, 2026 application deadline — insufficient time for broad community consultation. Strategic Sequencing: The applying entity determined that community engagement should follow, not precede, the application's structural foundations. The entity prioritized securing the technical infrastructure (CIRA as back-end registry provider), financial feasibility (ASP qualification and capitalization plan), and governance framework (the entity's incorporation and founding community mandate) before initiating broader consultation. This sequencing ensures that when wider community engagement occurs, the applying entity can present a concrete, actionable proposal rather than an aspirational concept. Confidentiality During Competitive Window: The 2026 gTLD application round is competitive. Until the application submission deadline (August 12, 2026), disclosing the string and application details broadly could have enabled competing applications or strategic objections. Maintaining confidentiality within the founding community's leadership protected the application's integrity during the submission period. Plan for Broader Engagement: Following application submission and ICANN's Reveal Day (approximately October 2026), when applied-for strings become public, the applying entity will initiate structured community engagement with Indigenous organizations, First Nations governments, and tribal councils across the target market. This engagement will include presentations at Indigenous governance conferences, direct outreach to First Nations and tribal leadership, and consultations with Indigenous business and development organizations to inform registry policies, eligibility criteria, and pricing structures prior to the Sunrise and General Availability launch phases.
Provide evidence of the established presence of the community prior to the opening of the application submission period.
1. Provide evidence that demonstrates that individuals and groups outside of the community show an awareness of the identified community. 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Media or other public information regarding the community and its activities or members; b) Discussion of the community in various fora, whether online or in person; c) Evidence of partnerships or collaborations with groups outside of the identified community; d) Evidence of the chartering or organization of the community prior to the opening of the application submission window; e) Evidence of contributions (for example, cultural or scientific) to a larger society or population;
Yes, individuals and groups outside of the identified community are aware of the existence of the community. Indigenous peoples are recognized in international law, national legislation, academic discourse, and public consciousness globally. Evidence of this awareness is substantial and multidimensional. External Awareness Indigenous peoples are recognized as distinct communities by the United Nations and its member states through UNDRIP (2007), the Permanent Forum on Indigenous Issues, and the Expert Mechanism on the Rights of Indigenous Peoples. National governments maintain formal recognition frameworks — Canada's Constitution Act, 1982 (Section 35), the United States' federal recognition of tribes, Australia's Native Title Act, and New Zealand's Treaty of Waitangi—all of which acknowledge Indigenous peoples as distinct communities with inherent rights. Academic institutions worldwide maintain Indigenous Studies programs, and major media outlets routinely report on Indigenous issues, land rights, and cultural contributions. Pelly Banks Dena specifically has gained public awareness through media coverage of its fight for recognition following the 1956 forced amalgamation, including coverage by APTN (Aboriginal Peoples Television Network), Canada's national Indigenous broadcaster. Documentation of Practices (Aug/24–Aug/26) a) Media or Other Public Information: Pelly Banks Dena's advocacy has been documented in APTN's investigative reporting on forced amalgamation and its impacts. Broader Indigenous community activities have received extensive media coverage including MMIWG2S+ advocacy, land-based education initiatives, and UNDRIP implementation efforts across the Yukon and Canada. Indigenous representation in film, literature, fashion, and art continues to generate public awareness of Indigenous communities and cultures. b) Discussion of the Community in Various Fora: Indigenous issues have been discussed at the Canadian Political Science Association Conference, NAISA, the House of Commons Standing Committee on the Status of Women (2024), and the Yukon MMIWG2S+ Annual Accountability Forum. UNDRIP implementation discussions have occurred in Yukon legislative contexts and community fora throughout the application period. c) Partnerships or Collaborations with Outside Groups: Indigenous communities collaborated with non-Indigenous institutions including the University of Toronto (OISE), Dechinta University, Google.org (Impact Award for the Centre for Indigenous Women in Leadership), and Wal-Mart Canada (Indigenous People's Resiliency Fund). These partnerships demonstrate that external organizations recognize and engage with Indigenous communities as distinct entities. d) Chartering or Organization Prior to Application Window: The Pelly Banks Government was organized and chartered prior to the 2026 application window. Kaska Dena First Nations have operated since the early 1940s (as recognized by Canada) but have existed since time immemorial. Other Indigenous community organizations (e.g., the Liard Aboriginal Women's Society) maintain formal incorporation and governance structures predating the application period. The applying entity, 17161573 Canada Inc., was incorporated in 2025 specifically for this application, building on these existing community organizations. e) Contributions to Larger Society: Indigenous communities contribute to broader society through land stewardship, climate leadership, language revitalization, cultural production, and governance innovation. The Dene K'éh Kusān conservation initiative—protecting 24 million hectares of ancestral territory—contributes directly to global biodiversity and climate goals. Indigenous MMIWG2S+ advocacy has shaped national policy and legislation in Canada. Indigenous land-based education models have influenced pedagogical approaches internationally. These contributions ensure that Indigenous communities are visible and recognized well beyond their own membership.
1. Provide evidence of the longevity of the community. 2. The applying entity should provide documentation of the following practices which should have occurred within the two years leading up to application submission: a) Evidence of recurring or scheduled activities that demonstrate continuity over time; b) Documented records of past activities that demonstrate a long-standing tradition or practice; c) Records of discussions emphasizing the community’s enduring presence or its cultural significance.
1. Evidence of Longevity Indigenous peoples have occupied and governed their territories since time immemorial. Archaeological evidence within Kaska Dena ancestral territory confirms continuous occupation for at least 7,500 years. Kaska Dena society has maintained its matriarchal clan system, language, kinship networks, and legal orders despite colonial displacement, forced amalgamation, and residential schools. Pelly Banks Dena demonstrates enduring identity despite state-imposed non-recognition. Following the federal government's forced amalgamation into neighbouring Kaska First Nations in 1956, members and descendants have maintained distinct identity through kinship, oral histories, cultural practice, and territorial relationships. The re-establishment of the Pelly Banks (Nahonni Dena) Government represents the continuation of governance traditions never extinguished — only disrupted. Globally, Indigenous peoples have maintained distinct identities, languages, and governance systems over centuries despite colonization. The community's pursuits — sovereignty, self-determination, language revitalization, land stewardship — are intergenerational obligations, not transient projects. 2. Documentation of Practices (Aug 2024–Aug 2026) a) Recurring Activities Demonstrating Continuity: Pelly Banks (Nahonni Dena) Government governance sessions held regularly throughout the application period; annual Yukon MMIWG2S+ Accountability Forum gathering families, survivors, and advocates (ongoing); recurring land-based education programming at the Tu Cho Centre for Dena Arts and Culture connecting Elders and youth; phased UNDRIP implementation consultations across Kaska Dena territory (2024–2026). b) Documented Records of Long-Standing Tradition: The Kaska Dena Council has operated as a society since 1981, advancing treaty negotiations for over four decades. Kaska Dena oral histories and archaeological records document continuous occupation and cultural practice spanning millennia, validated through Polar Knowledge Canada-funded mapping work (2025). The Liard Aboriginal Women's Society has delivered advocacy and cultural programming for Kaska Dena women over multiple decades, maintaining continuous organizational records. c) Discussions Emphasizing Enduring Presence: House of Commons Standing Committee on the Status of Women testimony (November 2024) emphasized ongoing violence against Indigenous women and the enduring strength of advocacy networks. The Canadian Political Science Association Conference (June 2025) engaged with the persistence of Indigenous governance despite colonial disruption. UNDRIP implementation consultations (2024–2026) framed governance resurgence as the continuation of pre-existing authority. The Dene K'éh Kusān ("Always Will Be There") conservation initiative — protecting 24 million hectares of ancestral territory — asserts enduring Kaska Dena stewardship while contributing to global biodiversity goals.
Explain how the applied-for string matches the name of the community or is a well-known alternative name (whether long or short form) of the community.
The applied-for string ".indigenous" directly matches the name of the identified community. The community is identified as "Indigenous peoples" — a term universally recognized in international law, national legislation, academic discourse, and popular usage to describe the global community of First Nations, Inuit, Métis, Aboriginal, Torres Strait Islander, Māori, Native American, and other distinct peoples who maintain historical continuity with pre-colonial societies. The term "Indigenous" is the most broadly recognized and inclusive descriptor for this community. It appears in the United Nations Declaration on the Rights of Indigenous Peoples (UNDRIP), the UN Permanent Forum on Indigenous Issues, the Expert Mechanism on the Rights of Indigenous Peoples, and the International Labour Organization's Convention 169. It is the term adopted by the community itself in international advocacy, scholarly publishing, and intergovernmental representation. "Indigenous" is not a colloquial abbreviation or a branding choice. It is the formal, legal, and self-referential name of the community. The string is the lowercase, singular adjectival form of "Indigenous," which is the standard convention for top-level domains (e.g., .org, .edu, .gov). The string functions simultaneously as a community identifier and a categorical namespace — any eligible Indigenous organization, government, business, or individual would register under a domain that plainly names their community.
1. Explain how the applied-for string clearly relates to or represents the community 2. Explain whether the applied-for string has any other significant meaning beyond identifying the community or community members described in the application. The applying entity may wish to provide pertinent information regarding any particular geography, region, or themes that may be alluded to by the string, of which the community may or may not be a part.
1. How the String Relates to the Community The general public will instinctively associate ".indigenous" with the Indigenous community. "Indigenous" is the primary term used in global public discourse to refer to the world's Indigenous peoples. It is the term used by the United Nations, national governments, media organizations, academic institutions, and Indigenous peoples themselves. No other community, industry, or interest group is associated with the word. When a member of the public encounters a web address ending in ".indigenous," they will immediately understand that the website belongs to or relates to an Indigenous person, organization, government, or business. This instant recognizability is precisely what makes the string valuable as a community TLD — it provides trust, visibility, and authenticity in a digital landscape where Indigenous identity is frequently misrepresented or appropriated. 2. Other Significant Meanings The string ".indigenous" does not have any other significant meaning beyond identifying the Indigenous community. Unlike strings such as ".apple" (brand vs. fruit) or ".bank" (financial institution vs. river bank), "Indigenous" carries no ambiguity in common usage. Its primary and overwhelming association is with Indigenous peoples. The word "indigenous" technically describes anything native or originating from a particular place — for example, Indigenous plants, Indigenous microorganisms, or Indigenous technologies. However, this generic usage is overwhelmingly contextual (typically scientific) and is not associated with any discrete community, movement, or interest group that would seek a TLD. No botanists, biologists, or technologists identify as a "community" around the word "Indigenous." The word's dominant cultural, legal, and political meaning — recognized in international law and enshrined in UNDRIP — refers unambiguously to Indigenous peoples. No particular geography, region, or theme outside of the Indigenous community is alluded to by the string. The term transcends national borders by design, reflecting the reality that Indigenous peoples exist across more than 70 countries worldwide.
Select from Radio Buttons - Yes/No. Notes: 1. Community Registration Policies are conditions that community gTLD registry operators impose upon registrants within their gTLDs. 2. If you select “Yes” to this question, the applying entity is required to pay the conditional Registry Commitments Evaluation fee, and Community Registration Policies that are approved by ICANN will be scored in the CPE (if the applying entity elects to participate) and included in Specification 12 of the applicable Base RA. 3. If you select “No,” then the application cannot proceed as a community application.
Yes
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy with respect to registrant eligibility in each response field. Up to 10 Community Registration Policies can be submitted. 3. Follow this format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars ,: a) "Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) "Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) "Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring ___"; and/or b) "Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___". 6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a registration eligibility policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the registration policy described in (a) at least once per year, and publish the results of such review (including any updates to the registration policy) on its website within thirty (30) days following the anniversary of the Effective Date. 7. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a registrant eligibility restriction is time-limited, the applying entity must state if the restriction will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 8. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
Registry Governance Model The .indigenous registry will be operated under a community-accountable governance model. While 17161573 Canada Inc. is the legal contracting entity with ICANN, the registry's policies, eligibility criteria, and revenue allocation are designed to be informed by ongoing engagement with Indigenous communities. The applying entity recognizes that community accountability is not a one-time endorsement but a continuous practice, and the registry's governance will reflect this through community consultation mechanisms, transparent policy development, and revenue reinvestment directed toward community priorities. This approach mirrors the governance resurgence work the applying entity's leadership has supported through Pelly Banks Dena and other Indigenous communities — work grounded in the principle that Indigenous peoples must control the institutions that affect them. The .indigenous TLD's eligibility framework reflects the complexity of Indigenous membership. The registry will not impose a single definition of "Indigenous" or create a centralized membership process that supersedes Indigenous nations' own citizenship determinations. Instead, registry eligibility will be based on verification that a registrant is an Indigenous nation, government, organization, or business — verified through appropriate documentation such as: Recognition under applicable Indigenous governance frameworks (e.g., tribal enrollment, First Nation citizenship, iwi registration, ANCSA shareholder status) Self-identification corroborated by community connection (for organizations and businesses) Formal incorporation or governance documents demonstrating Indigenous ownership or control Community letters of support or endorsement from recognized Indigenous organizations This approach respects Indigenous self-determination by deferring to each nation's own membership processes while maintaining the integrity of the .indigenous namespace as a verified Indigenous space. The registry's role is not to determine who is Indigenous — that authority rests with Indigenous nations themselves — but to verify that registrants can demonstrate their connection to a recognized Indigenous community or nation. See attached Community Registration Policy for details.
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Base Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy with respect to name selection criteria or rules for the applied-for string in each response field. Up to 10 Community Registration Policies can be submitted. 3. These criteria or rules should align with the community objectives of the applied-for gTLD string. 4. Follow this format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars: a) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 6. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring___""; and/or b) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___"". 7. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a name selection rule and publish it on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the name selection rule described in (a) at least once per year, and publish the results of such review (including any updates to the rule) on its website within thirty (30) days following the anniversary of the Effective Date. 8. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a name selection rule is time-limited, the applying entity must state if the rule will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 9. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
1. Permitted Uses. Registry Operator shall register domain names in the .indigenous TLD only where the proposed domain name is reasonably connected to the registrant's Indigenous identity, community affiliation, cultural purpose, governance function, or legitimate organizational or business activity. This includes names reflecting: (a) an Indigenous nation, community, or government name; (b) an Indigenous language word, phrase, or place name; (c) an Indigenous organization, program, or initiative name; (d) an Indigenous-owned business or brand name; or (e) an Indigenous individual's personal or professional identity. 2. Prohibited Names. Registry Operator shall not register any domain name in the .indigenous TLD that: (a) disparages or misrepresents Indigenous peoples, cultures, languages, ceremonies, or spiritual practices; (b) appropriates, exploits, or commercializes Indigenous cultural heritage without community authorization; (c) contains racial slurs or derogatory references to Indigenous peoples; (d) impersonates an Indigenous nation, government, or organization without authorization; or (e) is otherwise inconsistent with the community objectives of the .indigenous gTLD as stated in the application. 3. Reserved Names. Registry Operator shall reserve, at no cost, the names of Indigenous nations, governments, and recognized Indigenous organizations that have not yet registered, where such names can be objectively identified through publicly available records. Registry Operator shall release a reserved name only to the corresponding Indigenous nation, government, or organization upon verification of eligibility. 4. Registrar Obligations. Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall review each proposed domain name against the criteria in Sections 1 and 2 prior to submitting a registration request. Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not submit a registration request for any domain name that violates Section 2. 5. Registration Agreement Provisions. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring registrants to confirm that the requested domain name does not violate Sections 1 or 2. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting registrants from registering domain names that disparage, appropriate, or misrepresent Indigenous peoples, cultures, or spiritual practices. 6. Complaint Process. Registry Operator shall implement a name selection complaint process allowing any person or organization to submit a complaint regarding a domain name alleged to violate Sections 1 or 2. Registry Operator shall investigate such complaints within thirty (30) days and shall suspend or cancel any domain name found in violation. 7. Publication and Review. Registry Operator shall develop and implement the name selection rule and publish it on its website no later than the date on which the TLD is delegated in the DNS. Registry Operator shall review the rule at least once per year, and publish the results (including any updates) on its website within thirty (30) days following the anniversary of the Effective Date. 8. Duration. The name selection criteria in this Community Registration Policy shall apply for the lifetime of the .indigenous gTLD.
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy in each response field. Up to 10 Community Registration Policies can be submitted. 3. Follow the format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars: a) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring___""; and/or b) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting___"". 6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a Community Registration policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the Community Registration Policy described in (a) at least once per year, and publish the results of such review (including any updates to the registration policy) on its website within thirty (30) days following the anniversary of the Effective Date. 7. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a commitment is time-limited, the applying entity must state if the rule will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 8. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
Community Registration Policy — Revenue Reinvestment 1. Revenue Reinvestment. Registry Operator shall allocate a minimum of fifty percent (50%) of net registry revenue annually to a Community Benefit Fund. Of this amount, Registry Operator shall designate ten percent (10%) as a Founding Community Allocation to the Pelly Banks (Nahonni Dena) Government. The remainder shall be distributed to Indigenous communities and organizations through the process in Section 2. Registry Operator shall not distribute allocations to any entity that is not an Indigenous nation, government, organization, or community-rooted initiative serving Indigenous peoples. 2. Community Advisory Body. Registry Operator shall establish a Community Advisory Body of Indigenous community representatives selected through an open nomination process to advise on allocations, excluding the Founding Community Allocation. The Pelly Banks (Nahonni Dena) Government shall designate one permanent representative. Registry Operator shall publish composition, terms of reference, and selection criteria on its website no later than TLD delegation. Registry Operator shall convene the Body at least twice annually and shall not allocate revenues without its recommendation, except the Founding Community Allocation, which shall be disbursed directly upon the annual report described in Section 3. 3. Transparency and Reporting. Registry Operator shall publish an annual report on its website within twelve (12) months of the Effective Date and thereafter within thirty (30) days following each anniversary, detailing: (a) total net revenue; (b) Community Benefit Fund allocation; (c) Founding Community Allocation to Pelly Banks (Nahonni Dena) Government and purposes applied; (d) all other recipients and purposes; and (e) outcomes achieved. 4. Tiered Pricing. Registry Operator shall implement tiered pricing with discounted or no-cost registrations for qualifying Indigenous nations, governments, and non-profit organizations. Registry Operator shall not charge standard commercial rates to qualifying entities. Registry Operator shall publish the pricing structure and eligibility criteria on its website no later than TLD delegation. 5. Registrar Obligations. Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall apply the tiered pricing structure in Section 4 and shall not charge qualifying entities more than the applicable discounted rate. Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not offer .indigenous registrations at prices inconsistent with the published structure. 6. Registration Agreement Provisions. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring registrants to acknowledge that registration fees support the Community Benefit Fund. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting registrants from misrepresenting eligibility for discounted pricing. 7. Review and Duration. Registry Operator shall review this policy at least once per year and publish results (including updates) on its website within thirty (30) days following the anniversary of the Effective Date. This policy shall apply for the lifetime of the .indigenous gTLD.
1. If you are proposing any limitation to a proposed Community Registration Policy in Questions 151-153, please provide a rationale in this response field. Please see Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria. 2. If you are not proposing any limitation to a proposed Community Registration Policy in Questions 151-153, please type ""Not Applicable"" in this response field.
Not applicable.
1. Provide an explanation of how the proposed Community Registration Policies meet the Registry Commitments Evaluation criteria 4 and 5 using the considerations in the Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria. 2. Consider whether the proposed Community Registration Policy could be argued to be duplicative of a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. There may be circumstances in which a Community Registration Policy that would duplicate requirements under applicable consensus policy or law could be approved at ICANN’s sole discretion. If not duplicative, please explain why you believe the Community Registration Policy is not duplicative. If yes, please specify such a requirement and explain why you believe duplication in the Base RA is necessary. 3. Consider whether the proposed Community Registration Policy could be argued to be contrary to a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. ICANN will not approve any Community Registration Policies that are found to be contrary to applicable laws, ICANN agreements and policies. Please share your views on this issue in the answer to this question. 4. Consider whether the proposed Community Registration Policy could be argued to be incompatible with ICANN’s Bylaws. ICANN will not approve any Community Registration Policies that are found to be incompatible with the ICANN Bylaws. See background at the ICANN Board resolution 2024.06.08.08-2024.06.08.10. Please share your views on this issue in the answer to this question. 5. Consider whether the proposed Community Registration Policy requires the operation of an additional Registry Service. The applying entity shall engage its selected RSP to discuss the implementation of such an additional Registry Service, which must be evaluated through the RSP Program and approved by ICANN.
The three Community Registration Policies proposed (Registrant Eligibility, Name Selection Criteria, and Revenue Reinvestment) satisfy Registry Commitments Evaluation (RCE) Criteria 4 and 5 as follows: Criterion 4 (Specificity and Enforceability): Each policy uses mandatory "shall/shall not" language creating clear, verifiable obligations. Registrant eligibility defines four discrete categories with specific verification documentation. Name selection criteria enumerate five permitted uses and five explicit prohibitions. Revenue reinvestment specifies exact percentages (50% total, 10% Founding Community Allocation) and reporting timelines. These commitments can be objectively measured through ICANN Contractual Compliance audits, website reviews, annual reports, and complaint investigations. Criterion 5 (Measurable Obligations): Each policy includes objective compliance measures: publication deadlines (TLD delegation date), review cycles (annual within 30 days of anniversary), response timelines (30-day complaint investigation), disbursement triggers (upon annual report), and tiered pricing availability. The Community Advisory Body convening frequency (twice annually) and permanent Pelly Banks representation create quantifiable benchmarks for enforcement. Non-Duplicative Nature: These policies exceed ICANN consensus policy requirements. Standard gTLD obligations under the Base Registry Agreement do not mandate eligibility restrictions, name selection prohibitions beyond unlawful content, revenue allocation to community benefit, or tiered pricing structures. While ICANN Consensus Policy prohibits certain unlawful uses (child sexual abuse material, counterfeiting), our name selection criteria protect cultural heritage and prevent appropriation—distinct from legal prohibitions. Revenue reinvestment and tiered pricing are voluntary commitments beyond any ICANN requirement. Not Contrary to Existing Requirements: The policies do not conflict with applicable law or ICANN agreements. Eligibility verification respects Indigenous nations' self-determination rights enshrined in UNDRIP and Canadian Charter Section 35. Name selection criteria prohibit harmful speech without violating free expression protections, focusing on cultural appropriation rather than viewpoint. Revenue allocation is contractual between Registry Operator and registrants. Tiered pricing complies with competition law as discriminatory pricing is permitted when objectively justified (community sustainability). No ICANN Consensus Policy requires open registration that would conflict with our restrictions. Compatible with ICANN Bylaws: The policies align with ICANN's Bylaw commitments to public interest and community protection (Bylaw 2.1, 3.3). They support ICANN's mission to coordinate the DNS while respecting regional and national diversity. The Community Advisory Body structure ensures stakeholder input consistent with ICANN's multistakeholder model. No Bylaw provisions prohibit community-focused registry commitments or revenue redistribution mechanisms. No Additional Registry Services Required: These policies operate within standard registry technical infrastructure. Eligibility verification uses existing WHOIS/RDDS systems with registrar-submitted documentation. Name selection criteria apply during registration requests using existing EPP commands. Revenue allocation is financial accounting, not technical registry function. Tiered pricing uses standard registry pricing APIs. No new Registry Service Provider (RSP) services, sunrise mechanisms, or specialized registries beyond current operational capacity are required. All obligations are administrative or financial commitments implementable through existing registry-registrar relationships and ICANN contract enforcement mechanisms.
Please provide evidence of support for the applying entity’s application by attaching written endorsements from the organizing bodies relevant to the identified community (related to Question 136).
The applying entity derives its mandate to operate the .indigenous TLD from the Pelly Banks Government, the founding community identified in this application. The sole shareholder and Director of 17161573 Canada Inc. communicated the intent to pursue the .indigenous gTLD directly with Pelly Banks leadership, who provided instruction to proceed with the application. This instruction constitutes the founding community's endorsement of the applying entity as the vehicle through which the TLD application is pursued. A written letter of support from the Pelly Banks Government is attached as Corresponding Documentation, confirming: (a) the governance relationship between the applying entity's leadership and the Pelly Banks Government; (b) the community's awareness of and support for the .indigenous TLD application; and (c) the community's endorsement of the applying entity as the appropriate entity to carry forward this application on behalf of the community it serves. As documented in the response to Question 144, broader endorsement from other Indigenous organizations has not yet been sought. This reflects the novelty of the endeavour, the ASP qualification timeline (confirmed August 7, 2026 — five days before the submission deadline), and the competitive confidentiality considerations that governed the pre-submission period. Premature solicitation of endorsements before the application's structural and financial viability was confirmed would have been irresponsible and potentially damaging to community relationships. Following ICANN's Reveal Day (approximately October 2026), the applying entity will initiate structured engagement with Indigenous organizations, First Nations governments, and tribal councils to solicit formal endorsements, inform registry policy development, and establish the Community Advisory Body described in the Revenue Reinvestment Community Registration Policy. The applying entity is confident that the community-accountable governance model, revenue reinvestment commitment, and tiered pricing structure will attract broad community support once the application is public and the entity can engage openly. The applying entity respectfully submits that the endorsement of the founding community — Pelly Banks Government — combined with the documented two-decade history of community-rooted work that forms the basis of the entity's mandate, constitutes sufficient evidence of community support at the application stage. The applying entity commits to expanding this support base substantially during the post-submission evaluation period.
Provide an explanation of why opposition may or may not be relevant or how the applying entity intends to address or resolve the opposition, if applicable.
The applying entity is not aware of any formal opposition to the application or the applied-for string at the time of submission. No objections, challenges, or expressions of concern have been received from any party. However, the applying entity acknowledges that the following factors may give rise to questions or potential opposition during the evaluation period and addresses each proactively: 1. Single-Entity Representation of a Global Community The applying entity is a single corporation applying to serve a global community of over 370 million Indigenous peoples across more than 70 countries. Some may question whether one entity — particularly one whose founding community is a specific Kaska Dena community in the Yukon — can legitimately represent a community of this scale. The applying entity addresses this by: (a) grounding its mandate in the direct governance relationship with Pelly Banks (Nahonni Dena) Government as founding community; (b) committing to a Community Advisory Body with representation from diverse Indigenous communities; (c) committing to structured post-Reveal Day engagement with Indigenous organizations worldwide; and (d) designing eligibility criteria that defer to each Indigenous nation's own citizenship processes rather than imposing a centralized definition. 2. Potential Competing Applications The 2026 gTLD round is competitive. It is possible that another entity may apply for .indigenous or a variant string. The applying entity is prepared to defend its application on the basis of its community connection, community-accountable governance model, and the depth of documented community-rooted work described throughout this application. 3. Concerns About Appropriation Risk Some Indigenous community members may raise concerns that a gTLD could itself constitute a form of appropriation — that the string "indigenous" should not be owned by any single entity, even an Indigenous-owned one. The applying entity takes this concern seriously and addresses it through: (a) the Revenue Reinvestment Policy committing 50% of net revenue to community benefit; (b) the Community Advisory Body structure ensuring community direction of fund allocations; (c) tiered pricing ensuring affordability; (d) eligibility restrictions limiting registration to verified Indigenous entities; and (e) name selection criteria prohibiting cultural appropriation within the namespace. The applying entity views the TLD not as ownership of the word "indigenous" but as stewardship of a digital space on behalf of the community, analogous to how Indigenous nations steward territorial resources for collective benefit. 4. Non-Recognition of Pelly Banks Dena Pelly Banks Dena remains unrecognized as a separate First Nation by the Yukon and federal governments following the 1956 forced amalgamation. Some may question the legitimacy of an unrecognized community as the founding community for this application. The applying entity addresses this by noting that: (a) Pelly Banks Dena's non-recognition is itself a product of colonial governance decisions that the community continues to challenge; (b) the Pelly Banks Government operates with community authority regardless of state recognition; (c) Indigenous self-determination includes the right to organize and govern without state permission, as affirmed in UNDRIP; and (d) the applying entity's mandate extends well beyond Pelly Banks Dena to the broader global Indigenous community through the governance model, eligibility framework, and Community Advisory Body.
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.
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.
Yes
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.
No
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.
No
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.
No
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.
No
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.
No
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).
No
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.
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.
Yes
1. Draft the Registry Voluntary Commitment (RVC) as proposed contract language. Policies that are approved by ICANN will be included in Specification 11 of the applicable Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 11, Section 2 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed RVC in each response field. Up to 10 RVCs can be submitted. 3. Follow this format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 3. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars: a) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring___""; and/or b) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting___"". 5. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Registry Voluntary Commitment. For example: a) Registry Operator shall develop and implement a Registry Voluntary Commitment and publish this commitment on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the commitment described in (a) at least once per year, and publish the results of such review (including any updates to the registration policy) on its website within thirty (30) days following the anniversary of the Effective Date. 6. If the Registry Voluntary Commitment is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a commitment is time-limited, the applying entity must state if the commitment will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 7. See Section 7.8.3.3 Registry Commitments Evaluation Criteria for evaluation criteria that ICANN will apply for evaluating each proposed RVC.
Yes. The applying entity is proposing three Registry Voluntary Commitments unique to the .indigenous gTLD: Registrant Eligibility — restricting registration to verified Indigenous nations, governments, organizations, businesses, and individuals, with mandatory documentation, continuous eligibility requirements, and registrar verification obligations. Name Selection Criteria — permitting domain names connected to Indigenous identity, culture, or legitimate activity, while prohibiting names that disparage, appropriate, or misrepresent Indigenous peoples, with a complaint-driven enforcement mechanism. Revenue Reinvestment — allocating a minimum of 50% of net registry revenue to a Community Benefit Fund, with a 10% Founding Community Allocation to the Pelly Banks (Nahonni Dena) Government, a Community Advisory Body governing allocations, tiered pricing for affordability, and annual transparency reporting. All three RVCs are drafted as Specification 12 contract language, apply for the lifetime of the gTLD, and include objective compliance measures, registrar obligations, and registration agreement provisions.
1. If you are proposing any limitation to a proposed RVC in Question 173, please provide a rationale in this response field. See Section 7.8.3.3 Registry Commitments Evaluation Criteria. 2. If you are not proposing any limitation to a proposed RVC in Question 173, please type ""Not Applicable"" in this response field.
Not Applicable. All three Registry Voluntary Commitments proposed in Question 173 (Registrant Eligibility, Name Selection Criteria, and Revenue Reinvestment) apply for the lifetime of the .indigenous gTLD with no time limitations, scope restrictions, sunset provisions, or conditional applicability.
1. Provide background information to explain why the commitment is relevant, important, and necessary in support of the gTLD application. See Section 7.8.3.2.1 Applicants Must Identify Purposes for Proposed RVC. 2. Consider whether the proposed commitment could be argued to be duplicative of a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. There may be circumstances in which an RVC that would duplicate requirements under applicable consensus policy or law could be approved at ICANN’s sole discretion, for example, if this type of RVC is necessary to address GAC Consensus Advice. If not duplicative, please explain why you believe the commitment is not duplicative. If yes, please specify such a requirement and explain why you believe duplication in the Base RA is necessary. 3. Consider whether the proposed commitment could be argued to be contrary to a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. ICANN will not approve any commitments that are found to be contrary to applicable laws, ICANN agreements and policies. Please share your views on this issue in the answer to this question. 4. Consider whether the proposed commitment could be argued to be incompatible with ICANN’s Bylaws. ICANN will not approve any commitments that are found to be incompatible with the ICANN Bylaws. See background at the ICANN Board resolution 2024.06.08.08-2024.06.08.10. Please share your views on this issue in the answer to this question. 5. Consider whether the proposed commitment requires the operation of an additional Registry Service. The applying entity shall engage its selected RSP to discuss the implementation of such an additional Registry Service, which must be evaluated through the RSP Program and approved by ICANN. 6. For further guidance on the aforementioned considerations, please see Section 7.8.3.3 Registry Commitments Evaluation Criteria 7. [If the commitment is being proposed as an Application Change Request]: If the commitment is being proposed in response to an objection, GAC Member Early Warning, GAC Advice, or application comment, please provide a reference to the item to which the commitment responds
The commitments are proposed for four core rationales: 1. Protecting Community Integrity and Preventing Harm Without eligibility restrictions, non-Indigenous entities could register domains that appropriate, misrepresent, or disparage Indigenous peoples and cultures. The name selection criteria explicitly prohibit cultural appropriation, racial slurs, and impersonation. These protections are essential because the digital space has historically been used to misrepresent, exploit, or erase Indigenous identities. The TLD must be a verified Indigenous space, not an open namespace where anyone can claim Indigenous identity. 2. Honoring Indigenous Self-Determination The eligibility framework defers to each Indigenous nation's own citizenship and membership processes rather than imposing a centralized definition. This respects the inherent right of Indigenous peoples to determine their own citizens (UNDRIP Article 33) and avoids repeating colonial patterns of external categorization. The registry's role is verification, not determination—authority rests with Indigenous nations themselves. 3. Ensuring Economic Benefit Flows Back to Community Historically, Indigenous peoples have been excluded from infrastructure ownership and the economic benefits it generates. The 50% revenue reinvestment commitment ensures that the TLD generates tangible community benefit, not private profit. The Founding Community Allocation to Pelly Banks (Nahonni Dena) Government recognizes the specific community that anchors this initiative, while the Community Advisory Body ensures broader distribution aligns with community priorities like language revitalization, MMIWG2S+ support, and digital capacity-building. 4. Building Trust Through Transparency and Accountability The tiered pricing structure, annual reporting requirements, and Community Advisory Body create measurable accountability mechanisms. Without these commitments, there would be no enforceable guarantee that the TLD serves its stated mission rather than commercial interests. ICANN Contractual Compliance can monitor publication deadlines, disbursement amounts, and advisory body convening frequency—objective benchmarks that distinguish a genuine community commitment from aspirational language. These commitments collectively ensure the .indigenous gTLD fulfills its purpose as digital infrastructure for Indigenous self-determination, not merely as a commercial asset. They operationalize the community-accountable governance model described throughout this application and distinguish this TLD from unrestricted gTLDs where no such obligations exist.
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).
Select Yes or No
No
This serves as an indication of intent to apply for an exemption to Specification 9 and that the applying entity is NOT requesting to be designated a .Brand TLD, pursuant to Specification 13.
No
This question set collects any additional information that the applying entity would like to provide, including any supporting materials.
1. An applying entity may use this response field to submit any additional, optional information or documentation that the applying entity believes enhances understanding of its application or may be of interest to the general public. This could include, but is not limited to, the applying entity’s: a) Individual registry policies; b) Separate agreement with a third-party to fulfill certain commitments; c) Terms of use; d) Additional Community Registration Policies not intended for RA inclusion; e) Other materials that clarify the applying entity’s mission, values, or intended use of the gTLD. Notes: 1. This question is optional and for informational purposes only. 2. The information provided here will not be evaluated as part of the application, or be contractually binding on the applying entity. 3. All submissions to this question will be posted for the public to review and comment.
Historical Significance This application represents one of the earliest attempts in ICANN's history to secure a gTLD dedicated to and operated by Indigenous peoples. While a .maori application was submitted in the 2012 round, it was withdrawn before delegation. If delegated, .indigenous would be the first community gTLD in the DNS root whose purpose, governance, and revenue model are explicitly designed to serve Indigenous self-determination across multiple nations and peoples. Pelly Banks Soverignty This is not merely a technical application — it is an act of digital sovereignty by a community that has been historically excluded from infrastructure ownership and whose identity has been subject to external categorization, control, and erasure. This application is an assertion of the sovereignty and continuous presence of the Pelly Banks Dena. Alignment with ICANN's Mission and Public Interest The .indigenous TLD advances ICANN's commitment to a multilingual, inclusive, and globally representative DNS. It expands namespace choice for over 370 million Indigenous peoples across 70+ countries, supports Internationalized Domain Names in Indigenous languages and scripts, and brings a fundamentally underrepresented community into registry operations. The application aligns with ICANN's Bylaw commitments to preserve DNS stability while promoting competition, consumer choice, and geographic and cultural diversity in the DNS. Commitment to Good Faith Engagement The applying entity acknowledges that its community engagement to date has been necessarily limited to the founding community — Pelly Banks Government — due to the novelty of the endeavour, ASP qualification timelines, and competitive confidentiality requirements. The applying entity commits in good faith to expanding community engagement substantially following ICANN's Reveal Day, including outreach to Indigenous organizations globally, consultations on registry policy, and establishment of the Community Advisory Body. The applying entity views ICANN's evaluation period as an opportunity to demonstrate that the governance structures, registration policies, and revenue model proposed in this application warrant the trust of the broader Indigenous community. Applicant Support Program The applying entity expresses gratitude to ICANN's Applicant Support Program (ASP) for qualifying this application for reduced fees. Without ASP support, this application would not have been financially feasible. The ASP program's role in enabling participation from underrepresented communities is directly relevant to the .indigenous TLD's mission of democratizing access to digital infrastructure. Contact The applying entity welcomes inquiries from ICANN evaluation staff, community members, and interested parties. Correspondence may be directed to the applying entity through its registered contact information.
This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.
Confirm the statement using the checkbox.
true
Confirm the statement using the checkbox.
true