.lvs
Is .lvs a real TLD? Who’s applying to run it?
Nobody has applied for .lvs in its own right, as of 7 October 2026. Las Vegas Sands Corp. named .lvs as the replacement string of its .sands application.
A company-only web address for Las Vegas Sands; useful to that one firm, but nobody else can buy or trade names on it.
the applicant company itself, for corporate sites, resort and property microsites, campaigns and internal services; not open to the public or to resellers
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 exactly: a single corporation fencing off its three-letter stock-ticker abbreviation as a closed brand string that means nothing to the public, with the spelled-out company name pursued as a separate application.
A ticker-style initialism filed by one company as a registry of one, where the acronym carries no independent dictionary or category meaning and only the filer could ever put its identity on it.
A holding-company initialism whose consumer-facing brands live under entirely different names, so the string works only as corporate-identity real estate rather than as anything a customer would type.
What a .lvs domain is
.lvs is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. Nobody has applied for .lvs in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .lvs domain extension real yet?
.lvs 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 .lvs domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .lvs name can only be registered after that, once the string is delegated and its registry opens.
Is .lvs a real TLD?
Not yet. .lvs is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .lvs as part of an application for another string. Every entry on this page links to its source.
- Las Vegas Sands Corp. · first recordedICANN
“LVS2668T-T72361 · Las Vegas Sands Corp. · replacement string of .sands”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows .lvs applied for by Las Vegas Sands Corp. as a brand-type application and as the replacement string for .sands, so the realistic market is a single operator using it for its own properties, with no third-party registrations and no aftermarket. By analogy with earlier-round dot-brands (flagged as analogy), a share of such strings have seen real but modest use as corporate redirects or campaign hosts, while many have sat unused or been retired, so end-use utility to the one buyer is plausible but not certain. The string is a three-letter abbreviation of the company name rather than a public-facing word, which in my judgment makes it weaker as a consumer identity than the primary .sands string; the applicant's hospitality footprint gives it a commerce and destination flavour, which is why those categories trail brand. Not in 30-49 because no volume or price-driven registrations are possible on a closed brand string and there is no aftermarket at all; not in 1-9 because a large, well-known operator has a credible internal use for a short memorable namespace over the next 5 years. Main market uncertainty: whether the company will actually move primary identities (resort sites, loyalty, bookings) onto the string or keep it as a defensive, lightly used fallback to .sands.