.salesforce
Is .salesforce a real TLD? Who’s applying to run it?
.salesforce is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Salesforce.
A single-company brand domain: useful only to Salesforce itself, with no open registrations and no resale market.
the applicant company itself, for product, developer, and campaign addresses under its own name; no outside buyer can register here
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 exactly: a single enterprise-software vendor's own corporate brand as a dot-brand, where the value is a controlled, trust-signalling namespace for a cloud platform's products, docs and partner ecosystem rather than any open registration demand.
Also a B2B enterprise-software company putting its primary corporate identity on its own string, with the same requirement — that customers and a large partner/ISV ecosystem come to read the TLD as the vendor's authoritative space — though it is an acronym rather than a readable word.
A software-company brand making the same vendor-identity bet, but aimed at small-business and consumer subscribers rather than enterprise IT, so the namespace works as marketing for a product family instead of as an enterprise platform's trusted root.
What a .salesforce domain is
.salesforce 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 .salesforce domain extension real yet?
.salesforce 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 .salesforce domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .salesforce name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .salesforce was .oracle, delegated on 3 March 2015.
Is .salesforce a real TLD?
Not yet. .salesforce is not in the DNS root, so nothing resolves under it. It’s here because .salesforce 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/joke/narrow). The verified facts show one confirmed application from Salesforce, Inc. with an ICANN application type of brand, so this is a closed, single-registrant namespace. By analogy (flagged as analogy) with brand TLDs from the earlier round, outcomes have ranged from active use as a primary web identity for some properties to near-dormancy, with the typical pattern being redirects and secondary campaign addresses rather than replacing the .com identity; specific usage figures for those analogues are unknown under the rules here. It is not in the band above (30-49) because that band assumes registrations happening at volume or on price with a thin aftermarket, and a brand TLD has neither open registrations nor any aftermarket over the next 5 years. It is not in the band below (1-9) because a large enterprise software company has a real, if optional, use case: trusted addresses for products, developer portals, trust and security pages, and phishing-resistant communications under its own name, which gives the address genuine end-use utility to its one best-fit buyer. The main market uncertainty is whether the company shifts any primary properties onto the string or keeps it as a defensive and redirect asset; the former would lift utility within the band, the latter leaves it near the bottom.