.finder
Is .finder a real TLD? Who’s applying to run it?
Nobody has applied for .finder in its own right, as of 7 October 2026. XYZ named .finder as the replacement string of its .wellness application.
A natural suffix for search and directory sites (job.finder, home.finder), but a volume-and-price name, not a brand standard.
builders of directory, comparison, lead-generation and search-style sites that want a "noun.finder" compound, plus app makers with "finder" already in their product name
No applications recorded for this TLD yet.
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 as .finder: a bare discovery-function word nobody can own, whose worth sits entirely in second-level verticals (car.search / job.search) rather than in any applicant putting its own identity on the string.
The same generic find-things utility noun aimed at the listings and lead-gen buyer, working only if thousands of verticals each want {category}.directory as a signpost rather than a brand.
Also an intent word for shopping-discovery whose registrants would be comparison and referral operators monetizing traffic, though it names the user's action rather than, as .finder does, the agent doing the finding.
What a .finder domain is
.finder is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody has applied for .finder in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .finder domain extension real yet?
.finder is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .finder domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .finder name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .finder was .search, delegated on 29 June 2017.
Is .finder a real TLD?
Not yet. .finder is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .finder as part of an application for another string. Every entry on this page links to its source.
- XYZ · first recordedICANN
- Band chosen: usable but limited (30-49). The string works as a readable compound after almost any noun (car.finder, job.finder, flat.finder), which gives it real registration appeal across directory, comparison and lead-gen use cases, and the applicant on the record, XYZ.COM LLC, operates a portfolio of generic-word TLDs, which by analogy suggests broad registrar distribution and promotional pricing rather than a restricted or premium launch. It is not in the strong-niche band (50-69) because, by analogy with descriptive-suffix TLDs such as .directory, .guide, .tips and .help, demand for this kind of string has tended to be price-driven and speculative, with few serious projects adopting it as a primary identity and a thin aftermarket; a buyer choosing noun.finder still has to explain the choice. It is not in the vanity band (10-29) because the word is a genuine functional category term with repeatable commercial use, not an event or joke string, and it reads naturally in a URL. A further qualitative drag is that 'Finder' coincides with a widely known desktop software product name, which may complicate brand positioning for some registrants; that is an inference, not a recorded fact. The record shows this is a replacement string for a .wellness application rather than a first-choice filing, which I treat only as a signal about applicant priority, not about the string's merit. Main market uncertainty: whether 'noun.finder' compounds attract sustained primary-identity use by directory and lead-gen operators over the next 5 years, or only defensive and speculative registrations at launch pricing.