.beam
Is .beam a real TLD? Who’s applying to run it?
.beam is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A short, upbeat English word with no clear buyer group: fine for a few tech and lifestyle brands, unlikely to become a standard.
small tech, lighting, communications and lifestyle brands that already use "beam" in their name or want a short, energetic suffix for a product or campaign site
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, everyday English word that names no industry and so has no ready-made registrant pool, meaning its value comes entirely from one owner pouring brand meaning into an otherwise ownerless word.
Same bet in the trademark dimension: a plain dictionary word that is simultaneously a company's name, so the application rests on a single firm putting its primary identity on a string any English speaker could claim a generic use for.
Same bet: an abstract, tonal one-word namespace chosen for brevity and connotation rather than for any profession, category or community that would naturally register under it.
What a .beam domain is
.beam is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One application for it is on ICANN’s Reveal Day list.
Is the .beam domain extension real yet?
.beam 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 .beam domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .beam name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .beam was .spot, delegated on 19 February 2016.
Is .beam a real TLD?
Not yet. .beam is not in the DNS root, so nothing resolves under it. It’s here because .beam is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T22202 · Charleston Road Registry Inc. · primary”ICANN
- Band chosen: usable but limited (30-49). The record shows a single confirmed application from Charleston Road Registry Inc. (ICANN ID CRRI2564-T22202) on the Reveal Day list of 7 October 2026, with no category tag recorded; the string itself is a common, positive English word (a beam of light, a structural beam, to beam a signal, a beaming smile) that appears in tech, physics, lighting, telecom and software product naming. Assuming delegation and general availability, .beam has genuine but shallow appeal: it is short, pronounceable and brand-friendly, so some startups and product lines will take name.beam as a primary identity, but it names no category of business or community and therefore gives a visitor no clue what sits behind it. It is not in the strong-niche band (50-69) because there is no sustained, self-explaining demand pool the way a vertical or geo string has: adoption will be opportunistic and name-driven rather than a group of buyers who need it. It is above the vanity band (10-29) because the word has multiple serious commercial meanings and reads as a brand suffix rather than a joke, so primary-identity use by real projects is plausible rather than rare. By analogy (flagged as analogy), short evocative generics such as .live, .space, .zone and .fun have found registrations largely on price and promotions, with weak aftermarket pricing and few category-defining uses; .beam is narrower than .live or .space, which pulls it toward the lower half of the band. Main market uncertainty: whether a coherent buyer community forms around one meaning of the word (for example a tech or telecom cluster) or whether demand stays scattered across unrelated uses, which would keep aftermarket value near registration price.