.echo
Is .echo a real TLD? Who’s applying to run it?
.echo is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are EchoStar and Amazon.
A short, memorable word, but mostly a brand-shaped string; open demand would be thin and rarely a serious primary identity.
audio, voice and podcast projects, plus developers who like the shell-command pun, if the TLD is sold openly; otherwise the two corporate applicants' own brand use
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.
Both are short, ordinary dictionary nouns with no trade, industry, or community that would claim them as its own name, so the bet is identical: a plain evocative word bought as a brandable naming canvas whose meaning has to be supplied by whoever registers under it.
Same bet as a corporation claiming a common noun it has already attached to a consumer product line, where the string's value rests on the owner's product identity rather than on any generic meaning registrants would come looking for.
Another concrete everyday noun whose appeal is metaphorical (groups, reach, reverberation) rather than categorical, so like the target it has no natural registrant class and must be sold on suggestion alone.
What a .echo domain is
.echo is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Brand category. 2 applications for it are on ICANN’s Reveal Day list.
Is the .echo domain extension real yet?
.echo 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 .echo domain?
You can’t yet. A .echo 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 .echo was .song, delegated on 24 February 2016.
Is .echo a real TLD?
Not yet. .echo is not in the DNS root, so nothing resolves under it. It’s here because .echo is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“ARSI2666T-T58152 · Amazon Registry Services, Inc. · primary · contention set 2026-73 EDCL2689T-T81667 · ECHO Domain Co L.L.C. · primary · contention set 2026-73”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows two confirmed applications in one contention set, one from Amazon Registry Services, Inc. and one from ECHO Domain Co L.L.C., the latter also holding a replacement application for .echostar; both read as brand-intent filings, so the most likely post-delegation shape is a brand-controlled namespace with little or no third-party availability. Scoring as if generally available, .echo is a short dictionary word with associations to sound, voice, audio, repetition and the shell 'echo' command, which gives it a sliver of hack appeal (by analogy with single-word TLDs like .fm, .audio or .voice, which have found niche but modest open-market use). It is not in the 30-49 band because nothing about the string suggests volume registrations or a price-driven market: it is neither a geographic, category nor commercial keyword that a broad set of businesses would need, and the brand-shaped applicant pool makes open promotion unlikely. It is not in the 1-9 band because the word is clean, memorable and pronounceable in many languages and would attract some audio/voice and developer vanity registrations. Main market uncertainty: whether a generally available .echo would be positioned as an open audio/voice namespace with registrar distribution, or simply sit as a dormant word TLD with no category story. Applicant details are stated neutrally from the record and used only to gauge adoption likelihood.