.sdk
Is .sdk a real TLD? Who’s applying to run it?
.sdk is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Identity Digital.
A developer-tools label most companies will use for an SDK landing page, not as their main web address.
software and AI companies that publish developer kits and want a short pointer for their SDK docs, plus developer-tool startups and hobbyist projects
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: an insider technical term that nobody makes a consumer brand out of, sold to platform and tooling vendors as a developer-facing namespace, so it only works if engineers accept a jargon TLD as a legitimate place for their tools and resources.
Also a generic resource-type word rather than an identity word — the buyer is a software vendor standing up a side namespace for material developers consume, not a company putting its primary name on it.
Same category of software-industry common noun open to the whole trade rather than one owner, but it is a word the general public uses and will carry primary identities, where .sdk stays confined to a developer audience.
What a .sdk domain is
.sdk is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. One application for it is on ICANN’s Reveal Day list.
Is the .sdk domain extension real yet?
.sdk 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 .sdk domain?
You can’t yet. A .sdk name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .sdk was .dev, delegated on 18 December 2014.
Is .sdk a real TLD?
Not yet. .sdk is not in the DNS root, so nothing resolves under it. It’s here because .sdk is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Identity Digital · first recordedICANN
- Band chosen: 10-29 (vanity/narrow), at the top of it. 'SDK' is a precise, widely understood term among developers, so the string is memorable and self-explaining to its audience, but that audience uses it as a product label, not as an identity: an SDK lives under the vendor's own brand, typically on a docs or developer subdomain, so a serious company is unlikely to adopt brand.sdk as its primary web address over the next 5 years. By analogy, developer-oriented strings such as .dev and .app achieved broad primary-identity use because they describe who the registrant is (a developer, an app) rather than one artifact they ship; narrower tooling strings from the 2012 round such as .software, .systems and .codes settled into modest, price-sensitive niches (analogy, no figures asserted). .sdk is narrower still than those, which is why it does not reach the 30-49 band: demand would be mostly defensive or redirect registrations by vendors that already ship an SDK, not volume registrations or a real aftermarket. It sits above the 1-9 band because the term has a stable and currently growing meaning (AI and agent frameworks are marketed heavily as SDKs) and there is a plausible trickle of redirect, developer-portal and side-project use. The single application on the record is from Identity Digital under a standard (not brand) application, which suggests the string would be sold through ordinary registrar channels and be generally available, supporting adoption breadth but not the brand signal. Main market uncertainty: whether developer-tool vendors treat a short .sdk pointer as worth maintaining alongside their existing docs subdomains, or whether it stays a one-time defensive registration.