.slack
Is .slack a real TLD? Who’s applying to run it?
.slack is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Salesforce.
A company-owned namespace for one messaging product; no one else can register here, so it has no resale market.
the applicant itself, as a single-owner namespace for its workplace-messaging product and related services; no outside buyers
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 ordinary English word repurposed as the brand of a team-communication service, applied for by the company whose product identity rests on it, betting that its own users recognize the word as the product rather than its dictionary sense.
Same bet: the single-product brand of a messaging/communication platform putting its primary identity on its own string, where the TLD's value depends entirely on the product's installed base rather than on any category meaning.
Same bet in string shape: a plain common noun owned as a software brand by its maker, so the application has to defend a generic word as a corporate identity and accept that outsiders read the dictionary meaning first.
What a .slack domain is
.slack is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .slack domain extension real yet?
.slack 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 .slack domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .slack name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .slack was .hangout, delegated on 24 January 2015.
Is .slack a real TLD?
Not yet. .slack is not in the DNS root, so nothing resolves under it. It’s here because .slack is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Salesforce · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The record shows one applicant, Salesforce, Inc., with an application typed as brand, so the string is best read as a closed, single-owner namespace rather than an open registry. On this scale the only best-fit buyer is the operator, and the value is pure end-use utility: a widely used team-messaging product whose addresses are naturally organised by workspace could plausibly move or mirror those addresses under a short, memorable string (inference from analogy with other product-named brand namespaces, not from any record fact). It is not in the 30-49 band because there are no third-party registrations, no price-driven volume and no aftermarket at all; resale/brand strength for outside buyers is zero by design. It is not in the 1-9 band because the string names a product that is itself in daily use by many organisations, so a real operator use case exists even if it is never exercised. By analogy, many closed brand strings in the earlier round stayed dormant or were used only for redirects and a few marketing pages, while a minority became live primary addresses for the owner's products; that split is the main market uncertainty here. Whether the generic English meaning of "slack" would ever matter is moot while the string is closed. Counts, usage levels and any launch timing are unknown beyond the single application on the record.