.akamai
Is .akamai a real TLD? Who’s applying to run it?
.akamai is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Akamai Technologies, Inc..
A company-owned brand TLD: useful inside Akamai's own services, but no outside buyer can register or resell an address on it.
the applicant itself, Akamai Technologies, Inc., for its own corporate, product and infrastructure hostnames; no third-party registrants are expected
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 B2B internet-infrastructure vendor putting its non-descriptive corporate name on a string that has zero generic value to anyone else, sold to enterprise buyers who already know the brand from contracts rather than consumer advertising.
Same bet: a coined, meaningless-to-the-public company word owned by a plumbing-layer network services provider whose primary identity audience is enterprise and carrier customers, not retail consumers.
Same bet in kind — a coined corporate word for a networking-infrastructure vendor claiming its own namespace — but the brand carries far more consumer and channel recognition, so the string works as a household mark as well as an enterprise one.
What a .akamai domain is
.akamai 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 .akamai domain extension real yet?
.akamai 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 .akamai domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .akamai name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .akamai was .verisign, delegated on 25 November 2015.
Is .akamai a real TLD?
Not yet. .akamai is not in the DNS root, so nothing resolves under it. It’s here because .akamai is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Akamai Technologies, Inc. · first recordedICANN
“AKAM2694T-T35782 · Akamai Technologies, Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified-facts block shows a single confirmed application from Akamai Technologies, Inc. with no contention, and the string is a company name, so this is a closed dot-brand: addresses on it are not for sale to the public, there is no aftermarket, and the only 'buyer' is the operator. It is not in the 30-49 band because that band presumes registrations happen at volume or on price, and a brand TLD has no open registration market at all. It is not in the 1-9 band because the string has genuine end-use utility for its owner: by analogy with 2012-round brand TLDs that were put to real use (inference from analogy, no figures asserted), a content-delivery and edge-services company can plausibly use its own namespace for product, documentation, customer-portal and infrastructure hostnames where the TLD itself signals authenticity, which is a modest but real identity value over the next 5 years. Many 2012-round brand TLDs were left dormant or voluntarily retired (analogy, qualitative), so actual usage depth is uncertain. Main market uncertainty: whether the operator moves primary customer-facing or infrastructure identities onto the TLD rather than keeping it as a defensive, lightly used namespace; a dot-brand that is only defensively held sits near the bottom of this band, while one that becomes the operator's primary identity for products could justify the top of it.