.lake
Is .lake a real TLD? Who’s applying to run it?
.lake is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is XYZ.
A pleasant nature word for lakeside resorts, realtors and lake communities, but few would pick it as their main web address.
lakefront property firms, lake resorts, marinas and lake associations wanting a place-flavoured address, plus a small data-engineering crowd playing on "data lake"
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 undisputed physical-place common noun whose registrants would be thousands of scattered, small, owner-operated businesses naming the property they sit on, with no gatekeeper and no corporate claimant.
Same shape of bet - a short terrain-and-recreation word sold to destination resorts, outfitters and enthusiasts clustered around one landscape feature - but it names the activity rather than the feature, so the buyer is a leisure operator more than a resident or landowner.
Same class of word (a bare geographic common noun open to all comers with no defining registrant) and the same thin, diffuse demand, but broad enough to sell as a wordplay suffix rather than as a literal claim to a place.
What a .lake domain is
.lake is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Places. One application for it is on ICANN’s Reveal Day list.
Is the .lake domain extension real yet?
.lake 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 .lake domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .lake name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .lake was .farm, delegated on 28 December 2013.
Is .lake a real TLD?
Not yet. .lake is not in the DNS root, so nothing resolves under it. It’s here because .lake is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- XYZ · first recordedICANN
- Band chosen: 30-49, usable but limited. Verified facts: one confirmed standard application from XYZ.COM LLC (ICANN ID XL2625T-T47346), listed as the primary for a .dentistry application marked replacement; no category tag recorded. The string is a common English nature noun that maps to a real but fragmented set of buyers: lakefront real estate agents, resorts and rental operators, marinas and fishing outfitters, homeowner and conservation associations, and named lakes themselves (a lake-name-dot-lake pattern reads naturally). By analogy to earlier nature and place-flavoured generic words such as .farm, .fish and .garden (analogy, no figures asserted), demand over the next 5 years is likely to be steady at the low end, driven by registrar promotion and price rather than organic pull, with most buyers keeping a .com as the primary identity and using .lake as a themed or redirect address. The data-lake and lakehouse vocabulary in data engineering gives a minor tech hook that could produce a few clever startup names, but analogous wordplay TLDs have tended to produce memorable one-offs rather than a category standard (analogy). Not the band above (50-69) because there is no single category where a serious project would default to .lake as its primary identity without explanation, and an aftermarket for lake-themed names on a new extension would likely be thin outside a handful of famous lake names. Not the band below (10-29) because the word is a real place-and-industry descriptor with recurring commercial use (tourism, property, recreation), not a joke or event-driven string, so registrations should happen at modest volume. Main market uncertainty: whether lake-tourism and lakefront-property businesses, which are mostly small and local, treat a themed extension as worth a primary identity or only as a cheap add-on; retail pricing and registrar placement are unknown.