.alexa
Is .alexa a real TLD? Who’s applying to run it?
.alexa is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Amazon.
A single-company brand namespace for Amazon's Alexa products; nobody else can expect to register on it, so there is no open market.
the applicant itself (Amazon Registry Services) and its Alexa product, developer and device teams; no third-party registrant group
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 technology company putting a consumer product-brand name (a repurposed everyday word, not the corporate name) on its own TLD to anchor a device-plus-content ecosystem, with the same defensive-portfolio logic behind it.
A tech giant's consumer platform brand rather than its company name, where the TLD's value depends on the brand hosting a third-party developer and content ecosystem under the owner's control.
Also a coined consumer-platform brand owned by one company and aimed at a developer ecosystem, but it is a licensed platform spanning other manufacturers' identities rather than a brand the owner alone would put its primary identity on.
What a .alexa domain is
.alexa 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 .alexa domain extension real yet?
.alexa 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 .alexa domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .alexa name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .alexa was .kindle, delegated on 7 June 2016.
Is .alexa a real TLD?
Not yet. .alexa is not in the DNS root, so nothing resolves under it. It’s here because .alexa is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Amazon · first recordedICANN
“ARSI2666T-T50233 · Amazon Registry Services, Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified-facts block shows one confirmed application from Amazon Registry Services with no contention, which is the profile of a closed .brand TLD: addresses on it are expected to be used only by the brand owner, and by analogy with existing brand TLDs such as .google, .apple and .amazon (analogy), the typical pattern is light operator use for redirects, campaigns or product endpoints rather than a public namespace. It is not in the 30-49 band because registrations do not happen at volume or on price at all; there is no retail channel, no third-party primary identity and no aftermarket, so the usual 'usable but limited' dynamics do not apply. It is not in the 1-9 band because the best-fit buyer, the operator, has a genuine end-use: a voice-assistant and smart-home product line whose device, skill and developer surfaces could plausibly sit on a short, self-descriptive namespace, and by analogy a minority of brand TLDs have moved real primary traffic onto their string (analogy, flagged). Main market uncertainty: whether the operator will actually adopt the string as a primary product identity or hold it defensively, which within this band is the difference between the low teens and the mid twenties; the public-market question is settled either way by the closed model.