.catalog
Is .catalog a real TLD? Who’s applying to run it?
Nobody has applied for .catalog in its own right, as of 7 October 2026. Intercap named .catalog as the replacement string of its .look application.
A descriptive word that fits product listings and data catalogs, but it names a section of a site, not a brand, so demand stays modest.
retailers, marketplaces and wholesalers publishing product lines, plus library, archive and data-catalog projects wanting a self-describing address
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: an everyday English noun for the document a merchant publishes to list what it sells, wagering that the artifact word becomes the namespace every seller puts that listing on, with no community or company behind the string to anchor it.
Same bet on a format noun rather than a venue noun — the string names the compiled list itself, so its value depends on publishers of listings adopting it as the home for an index, exactly the demand .catalog has to manufacture.
Same buyer and same generic-commerce-noun bet, but one level off: it names the place that sells rather than the listing of goods, so it can carry a seller's whole primary identity in a way a listing artifact struggles to.
What a .catalog domain is
.catalog 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 .catalog in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .catalog domain extension real yet?
.catalog 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 .catalog domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .catalog name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .catalog was .menu, delegated on 30 November 2013.
Is .catalog a real TLD?
Not yet. .catalog is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .catalog as part of an application for another string. Every entry on this page links to its source.
- Intercap · first recordedICANN
“IRI2679T-T92731 · Intercap Registry Inc. · replacement string of .look”ICANN
“EDI2665T-T28371 · Endpoint Domains, Inc. · primary IRI2679T-T96997 · Intercap Registry Inc. · replacement string of .wiz · Deactivated NA2626T-T63059 · ShortDot (Ireland) Limited · replacement string of .ask · Deactivated XL2625T-T48604 · XYZ.COM LLC · replacement string of .con · Deactivated”ICANN
- Band chosen: 30-49 (usable but limited). The string is a plain English dictionary word with live meaning in e-commerce (product catalogs), libraries and archives, and increasingly in data engineering (data catalogs), so a steady trickle of descriptive and defensive registrations is plausible over the next 5 years. It is not in the 50-69 band because 'catalog' describes a part of a site or a function, not an entity: a serious retailer or software project is unlikely to make brand.catalog its primary identity rather than a secondary or redirect address, and by analogy with descriptive-function strings such as .directory, .guide, .menu and .gallery, that pattern tends to produce low-volume, price-driven registrations with a thin aftermarket. It is not in the 10-29 band because the word is neither a joke nor event-driven; it maps to real, recurring commercial activity (product feeds, supplier catalogs, catalog retail) and to a growing data-infrastructure concept, so some genuine end-use is likely rather than pure vanity. The record shows a single application by Intercap Registry Inc. listed as a replacement string for a primary .look application; that is stated neutrally and only suggests the string is a secondary choice for the applicant, which weakly lowers the chance of heavy launch marketing. Registration counts, pricing and comparable-TLD volumes are unknown from the facts block; all comparisons above are by analogy. Main market uncertainty: whether any e-commerce or data platform adopts a brand.catalog pattern as a default showcase or feed address (which would lift it toward niche-standard status), versus catalog use remaining a subdomain or path on an existing site; the catalog/catalogue spelling split is a secondary drag on global demand.