.okta
Is .okta a real TLD? Who’s applying to run it?
.okta is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Okta, Inc..
A single-company brand domain: handy for Okta's own login and product addresses, but nothing anyone else can buy or resell.
okta, inc. itself — its product, sign-in, developer and documentation endpoints; no third-party registrations or resale
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 coined, meaning-free corporate name owned by an enterprise security-software vendor, where the string's only job is to be the company's own identity for IT buyers rather than to capture any generic demand.
Same bet: an invented portmanteau belonging to a B2B trust-and-identity infrastructure company, betting that a vendor whose product is verification can make its own brand string the credential it signs things with.
Same bet structurally — a short coined corporate name with zero consumer recognition, applied for purely as the primary identity of a business-to-business supplier — though the buyer is industrial procurement rather than enterprise IT.
What a .okta domain is
.okta 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 .okta domain extension real yet?
.okta 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 .okta domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .okta name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .okta was .symantec, delegated on 3 December 2015.
Is .okta a real TLD?
Not yet. .okta is not in the DNS root, so nothing resolves under it. It’s here because .okta is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Okta, Inc. · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The record shows a single application by Okta, Inc. with ICANN application type 'brand', so this is a closed dot-brand: the only realistic buyer is the applicant, there is no open registration market and no aftermarket by design. It is not in the 30-49 band because registrations at volume and any resale value are absent, not merely weak. It is above the 1-9 band because, uniquely among most dot-brands, an identity provider has a credible primary-identity use case: hosting sign-in, admin and API endpoints under a namespace only the brand can control is a plausible anti-phishing and trust signal, which is end-use utility a serious project (the brand itself) might actually adopt. By analogy (flagged as analogy), prior-round dot-brands split between a minority that moved real traffic onto the TLD and a majority that stayed idle or were later retired; the outcome depends entirely on operator commitment, which is unknown here. Main market uncertainty: whether Okta migrates customer-facing authentication traffic onto the TLD (which would make it a working trust surface) or holds it defensively, in which case it is effectively inert.