.echostar
Is .echostar a real TLD? Who’s applying to run it?
Nobody has applied for .echostar in its own right, as of 7 October 2026. EchoStar named .echostar as the replacement string of its .echo application.
A single-company brand name as a web ending: useful only to that one brand, with no open market for anyone else.
the one corporate brand the string names, for its own product, service and campaign addresses; not open to outside registrants in any realistic scenario
No applications recorded for this TLD yet.
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 exactly: a proper-noun corporate house name of a satellite-communications firm, applied as a closed brand TLD whose value is corporate identity and defensive control rather than registrations, with no generic meaning anyone else could claim.
The primary consumer-facing identity of a satellite pay-TV operator putting its single corporate brand on a TLD, differing only in that the string doubles as a common noun, which raises the bar for proving the name is the company's rather than the category's.
Also a satellite-operator's own short-form brand mark staked as a closed company TLD, but it is an initialism rather than a distinctive coined house name, so it carries the extra burden of defending a three-letter string that reads as a generic abbreviation.
What a .echostar domain is
.echostar is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. Nobody has applied for .echostar in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .echostar domain extension real yet?
.echostar is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .echostar domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .echostar name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .echostar was .hughes, delegated on 10 August 2016.
Is .echostar a real TLD?
Not yet. .echostar is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .echostar as part of an application for another string. Every entry on this page links to its source.
- EchoStar · first recordedICANN
“EDCL2689T-T81667 · ECHO Domain Co L.L.C. · replacement string of .echo”ICANN
“EDCL2689T-T94739 · ECHO Domain Co L.L.C. · replacement string of .agent · Deactivated XI2694T-T39173 · XRegistry Incorporated · replacement string of .xn--6oqv20b1zgzxr · Deactivated XI2694T-T41185 · XRegistry Incorporated · replacement string of .get · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow). The string is a compound brand name rather than a dictionary word, and the record shows it filed as a replacement string for a primary .echo application by ECHO Domain Co L.L.C., which reads as a brand-protection or brand-identity filing rather than an open registry play. By analogy (flagged as analogy) with the dot-brand cohort from the earlier new-gTLD round, such strings tend to see either no public use or a handful of corporate redirects and campaign addresses, with zero aftermarket because no third party can register. It is not in the 30-49 band because there are no volume or price-driven registrations possible and no brand signal for anyone but the owner; it is above the 1-9 band because a real operator can and sometimes does use a brand TLD as a genuine primary identity for its own properties, which is a realistic if narrow use. Main market uncertainty: whether the owner actually migrates customer-facing properties onto the string or leaves it dormant as a defensive asset; usage figures for the string are unknown.