.beach
Is .beach a real TLD? Who’s applying to run it?
.beach is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are XYZ and Phoenix Domain Partners. Vant Nexus named .beach as a backup string for its .truck application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
Reads nicely for coastal tourism and rentals, but most serious businesses will treat it as a fun extra, not their main address.
coastal hotels, vacation-rental operators, beach-town tourism boards, and surf/lifestyle brands wanting a descriptive place-flavored address
One of 13 strings Phoenix Domain Partners published as applied-and-paid in the ICANN 2026 round, reported by Domain Name Wire on 2026-08-17.
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .truck application, shown as deactivated: another applicant applied for the same string or named it as a backup
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 short, common leisure-destination word whose primary identity buyers are resorts, local operators and place-name holders in a specific geography, so value depends on a finite set of destinations adopting it rather than on broad registrant demand.
Same bet on a coastal lifestyle noun/verb that doubles as a category and a culture, sold to the identical buyer pool (shops, schools, apparel and hospitality brands trading on the same seaside identity) with the same weakness that most of them already have a fine .com.
Also a generic leisure-amenity place word that venues and hospitality operators would put their name in front of, though it names a business type people transact with rather than a public natural feature anyone can claim.
What a .beach domain is
.beach is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Places. 2 applications for it are on ICANN’s Reveal Day list.
Is the .beach domain extension real yet?
.beach 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 .beach domain?
You can’t yet. A .beach name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .beach was .ski, delegated on 30 May 2015.
Is .beach a real TLD?
Not yet. .beach is not in the DNS root, so nothing resolves under it. It’s here because .beach is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Vant Nexus · first recordedICANN
- XYZ · first recordedICANN
- Phoenix Domain Partners · now confirmedICANN
- Phoenix Domain Partners · first recordedDomain Name Wire
“MLG2688T-T61684 · 101130013 Saskatchewan Ltd. · primary · contention set 2026-22 VNTL2649T-T76006 · VANT NEXUS TECHNOLOGIES LLC · replacement string of .truck · Deactivated XL2625T-T54390 · XYZ.COM LLC · primary · contention set 2026-22”ICANN
“MLG2688T-T61684 · 101130013 Saskatchewan Ltd. · primary · contention set 2026-22 XL2625T-T54390 · XYZ.COM LLC · primary · contention set 2026-22”ICANN
“Phoenix Domain Partners published 13 strings for which it says it has applied and paid the application fees.”Domain Name Wire
- The string has genuine semantic pull: place-plus-beach combinations (a town, resort, or rental name to the left of the dot) read naturally, which is more than many lifestyle strings can claim. But by analogy with comparable leisure/lifestyle TLDs such as .surf, .vacations, .holiday and .cruises — which saw thin registration bases, price-driven demand, and little primary-identity use — .beach is likely to be registered defensively or as a campaign/redirect address rather than as a serious main identity, keeping the aftermarket shallow. That puts it in the 30-49 'usable but limited' band: it clears the vanity band below because coastal hospitality is a large, real commercial vertical with a plausible descriptive fit, but it misses the 50-69 niche band above because there is no evidence, and no strong analogy, of sustained primary-identity adoption in that vertical for extension-based branding. The main market uncertainty is whether tourism-heavy destinations and rental platforms adopt geo.beach names as canonical identities over the next 5 years, or continue defaulting to .com and country-code names with 'beach' inside the second-level string.