.sands
Is .sands a real TLD? Who’s applying to run it?
.sands is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Las Vegas Sands Corp..
A company-owned namespace for one hospitality brand; useful to that business, but not something outsiders can buy or trade.
the applicant company and its affiliated resort, casino and hospitality properties, for owned-channel addresses rather than public registration
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 single integrated casino-resort operator putting its own corporate name on a dot-brand, where the string's value depends entirely on one gaming company's identity rather than on any category of registrants.
Same bet structurally — one hospitality corporation owning its brand as a namespace for properties and loyalty assets — but a pure hotel operator, without the regulated-gaming dimension that shapes who can even use the string.
Same awkward structure as the target: an ordinary English dictionary noun claimed as a single company's exclusive brand, so the applicant has to hold a generic word against everyone's plain-language reading of it.
What a .sands domain is
.sands 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 .sands domain extension real yet?
.sands 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 .sands domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .sands name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .sands was .genting, delegated on 20 June 2015.
Is .sands a real TLD?
Not yet. .sands is not in the DNS root, so nothing resolves under it. It’s here because .sands is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Las Vegas Sands Corp. · first recordedICANN
- Band chosen: 10-29 (vanity/narrow), scored 15. The record shows a single confirmed application by Las Vegas Sands Corp. of ICANN application type 'brand', with a .lvs application recorded as its replacement string, so .sands is being pursued as a corporate namespace rather than an open generic. By analogy with brand TLDs from the earlier round, the realistic pattern is that the operator registers names for its own properties, campaigns and services, sometimes as the primary identity of a site and sometimes only as redirects; third parties cannot register, so there is no aftermarket and the TLD adds no credibility to anyone outside the company. It is not in the 1-9 band because a large hospitality group has a genuine, plausible primary-identity use for a short memorable word that matches its trading name, and some earlier brand TLDs did become real customer-facing addresses (inference from analogy). It is not in the 30-49 band because an address on it is not purchasable by the general market, so there is no volume registration, no price-driven demand and no resale value at all; the value is captured entirely by one buyer. The word 'sands' also has generic meanings (beaches, landscapes), but under a brand-type application that generic demand is unserved and does not raise the score. Main market uncertainty: whether the operator uses the namespace substantively as its primary web identity (which would push it toward the top of this band) or leaves it as a defensive or redirect-only holding (which would push it toward the bottom), and whether any affiliated partners are ever allowed addresses on it. Counts, dates and figures beyond the verified-facts block are unknown.