.株式会社
Is .株式会社 a real TLD? Who’s applying to run it?
.株式会社 is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is XServer.
A Japanese "Inc." ending that reads as corporate, but most companies will keep .co.jp or .com and buy this, if at all, as a side name.
Japanese joint-stock companies (kabushiki kaisha) wanting a native-script corporate address, mostly as a defensive or marketing alias beside their existing .co.jp or .com
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.
公司 is the same bet in the adjacent market: the everyday local-language word a company appends to its own name, sold in native script to any incorporated business that wants its legal identity on the right of the dot.
Both are a single-jurisdiction statutory corporate form (GmbH / 株式会社) rather than a descriptive noun, so the registry's whole thesis is the same — every firm legally entitled to the suffix already prints it, and the TLD just moves it into the address bar.
Same incorporation-suffix bet and same buyer (the registered company putting its primary identity on it), but it is the language-neutral, globally recognized form rather than one tied to a single legal system and script, so the addressable pool and defensive dynamics differ.
What a .株式会社 domain is
.株式会社 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 .株式会社 domain extension real yet?
.株式会社 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 .株式会社 domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .株式会社 name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .株式会社 was .xn--55qx5d, delegated on 18 January 2014.
Is .株式会社 a real TLD?
Not yet. .株式会社 is not in the DNS root, so nothing resolves under it. It’s here because .株式会社 is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- XServer · first recordedICANN
“ASL2693T-T37161 · Agador Slip, LLC · primary · contention set 2026-247 ISL2626T-T66950 · Innovation Service Limited · primary · contention set 2026-247 XI2694T-T10138 · XRegistry Incorporated · replacement string of .geek · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow). The string is the legal-entity suffix carried by Japanese joint-stock companies, so it has a clear, real buyer group and a credible corporate meaning in Japanese; that is why it sits above the 1-9 band: a defensive or marketing registration by an established company is a plausible, serious use, and the applicant on the record is a Japanese operator (XServer / XRegistry Incorporated, status confirmed, IDN application), which suggests distribution through Japanese hosting channels. It stays below the 30-49 band because, by analogy (flagged as analogy), Japanese-script and Chinese-script IDN gTLDs from the earlier round such as .コム, .みんな and .公司 have generally seen thin uptake relative to ASCII equivalents, and Japanese companies already have a strong, entity-verified corporate namespace in .co.jp plus .com for international identity; a full-width IDN also carries input and email friction that discourages primary-identity use. By analogy with .inc (flagged as analogy), a corporate-suffix TLD tends to attract brand-protection buys at a premium rather than volume registration, which caps aftermarket depth. Registration counts, pricing and launch terms for this string are unknown. Note on the record: a separate .recruit application by the same applicant names this string as its primary and is deactivated, which does not change the market read. Main market uncertainty: whether Japanese corporations would treat a native-script corporate ending as a credible primary address at all, or purely as an alias; I lean strongly toward alias, which is what holds the score in the low 20s over the next 5 years.