.veo
Is .veo a real TLD? Who’s applying to run it?
.veo is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A closed Google brand string: no outside buyer can register here, so it has no open market or resale value.
the applicant itself (Google, via Charleston Road Registry) for its own product and campaign addresses; no third-party buyer group exists
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 four-letter, vowel-ended Romance-language verb form ('I live' / 'I see') carrying no English dictionary meaning, claimed by a single company as the whole of its own identity rather than as a category anyone else could occupy.
Same bet in a different market: a short, phonetic, invented-looking consumer-tech brand with zero generic pull, where the string only works if the company's own name recognition does the work — no category traffic will ever arrive on its own.
Same bet structurally: a coined four-letter vowel-heavy brand string registered to one operator for a consumer-facing product line, betting on marketing spend to give the word meaning rather than inheriting any.
What a .veo domain is
.veo 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 .veo domain extension real yet?
.veo 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 .veo domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .veo name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .veo was .vivo, delegated on 15 July 2016.
Is .veo a real TLD?
Not yet. .veo is not in the DNS root, so nothing resolves under it. It’s here because .veo is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T52620 · Charleston Road Registry Inc. · primary”ICANN
- Band chosen: 1-9 (no realistic market). The record shows a single application, filed by Google (Charleston Road Registry Inc.), typed "brand" on the ICANN record. A brand-type TLD is operated for the applicant's own use, so there is no public registration channel, no third-party primary-identity use and no aftermarket; the value of an address here accrues only to the applicant. From my own knowledge (not in the facts block), the string matches the name Google uses for a video-generation model, which places the likely use in the AI/product-marketing lane. By analogy to earlier brand TLDs run by the same operator (.google, .youtube and others), such strings tend to be used for a handful of redirects and campaign hosts rather than as a widely adopted namespace; that is an inference from analogy. It is not in the 10-29 band because even vanity or joke strings in that band are open to outside registrants and can carry shallow event-driven demand, whereas a closed brand string has zero addressable buyers beyond the operator. It is not below the band floor because the applicant may genuinely use it as a short product identity, which gives it some end-use utility. Main market uncertainty: whether Google deploys the string as a visible primary identity for the product (which would raise brand-signal utility toward the top of this band) or leaves it dormant, as many brand TLDs are, over the five-year window.