.kuiper
Is .kuiper a real TLD? Who’s applying to run it?
.kuiper is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Amazon.
A closed Amazon brand space for its satellite internet project; nobody outside Amazon can register, so no market value.
Amazon itself, for first-party addresses tied to its satellite-broadband project; no outside 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 exactly: a single corporation claiming an ordinary evocative noun that the public knows as a word but not as its product, so the string's whole value is defensive control of a house-brand namespace with no third-party registrant ever intended.
A borrowed common word elevated into one company's platform/service brand, where the TLD works only if that firm succeeds in making the word mean its infrastructure rather than its dictionary sense.
Also a repurposed everyday word owned as a single firm's product line, but it arrived with mass consumer recognition already attached, whereas this kind of string is a pre-launch service brand still borrowing meaning rather than lending it.
What a .kuiper domain is
.kuiper 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 .kuiper domain extension real yet?
.kuiper 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 .kuiper domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .kuiper name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .kuiper was .silk, delegated on 7 June 2016.
Is .kuiper a real TLD?
Not yet. .kuiper is not in the DNS root, so nothing resolves under it. It’s here because .kuiper is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Amazon · first recordedICANN
“ARSI2666T-T89828 · Amazon Registry Services, Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows a single confirmed application from Amazon Registry Services, Inc., filed as a brand type, which in the ICANN framework generally means registrations are restricted to the applicant and its affiliates. The string corresponds to Amazon's satellite-broadband project name, so its plausible end use is first-party addresses for customer portals, device setup, or service status rather than a namespace anyone else can adopt. It is not in the 30-49 band because there are no third-party registrations at any volume or price and no aftermarket at all; it is not in the 1-9 band because a large operator with a consumer-facing service has a real, if narrow, end-use case for a short, recognizable brand suffix in its own communications and on devices. By analogy (flagged as analogy), most dot-brands from the earlier round saw little or no public use and some were later retired, while a minority became a visible part of their owner's web identity; whether .kuiper lands in the visible minority depends on how central the Kuiper name stays in Amazon's consumer branding. Main market uncertainty: whether the service is marketed to consumers under the Kuiper name over the next 5 years or under a different Amazon brand, which would leave this TLD as an internal or redirect-only space.