.indigenous
Is .indigenous a real TLD? Who’s applying to run it?
.indigenous is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is 17161573 Canada Inc..
A meaningful identity badge for Indigenous nations and organisations, but a small, dispersed buyer pool and little resale value.
Indigenous nations, tribal and First Nations governments, Indigenous-led organisations, cultural institutions and Indigenous-owned businesses that want their identity visible in the address itself
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: a pan-ethnic umbrella self-name covering many distinct peoples, where the registry's value rests on being accepted as the legitimate home of a collective identity rather than on selling a commercial category.
Same bet: a community's own informal word for itself that no company or government owns, registered by people and organizations wanting to flag membership in a peoples-level identity.
Same identity-affirmation bet for a dispersed population whose registrations are declarations of belonging and advocacy, though it is a coalition acronym rather than a peoples' ancestral self-name.
What a .indigenous domain is
.indigenous is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. One application for it is on ICANN’s Reveal Day list.
Is the .indigenous domain extension real yet?
.indigenous is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .indigenous domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .indigenous name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .indigenous was .latino, delegated on 4 August 2016.
Is .indigenous a real TLD?
Not yet. .indigenous is not in the DNS root, so nothing resolves under it. It’s here because .indigenous is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- 17161573 Canada Inc. · first recordedICANN
- Band chosen: 30-49 (usable but limited), low end. The string is a long English common noun describing a global, multilingual community rather than a product or place, and the record shows one applicant, 17161573 Canada Inc., filing as a community application with Applicant Support Program status; by analogy with community-type TLDs, that likely implies eligibility rules, which tend to keep registration counts small and suppress any aftermarket (inference from analogy). It is not in the 10-29 band because demand here would be identity-driven and durable rather than joke or event-driven: cultural-community TLDs such as .cat, .eus, .scot and .bzh have shown sustained, if modest, primary-identity use by organisations that want the affiliation visible (analogy; no figures asserted). It is not in the 50-69 band because the eligible pool is small, geographically dispersed and already well served by existing namespaces (tribal governments and First Nations commonly sit on government, country-code or .org addresses), the string is English-only for communities that often prioritise their own languages, and a verified-community TLD rarely develops a real aftermarket, so 'real sustained demand with a genuine aftermarket' is unlikely within 5 years. Main market uncertainty: whether Indigenous organisations adopt .indigenous as a primary identity or treat it as a secondary redirect alongside an established .org/.ca/.gov address, which depends heavily on how broad and how friction-free eligibility turns out to be.