Applications / .株式会社 / XI2694T-T39173 · published by ICANN 7 October 2026 · snapshot 2026-10-08
.株式会社
IDNActiveA-label xn--6oqv20b1zgzxr Q116
XRegistry Incorporated, JP Q1·Q25
Affiliate of XServer Inc. registrar with IANA ID 1557
§ 1 — Meaning of the string Q118·Q120
“Kabushiki kaisha”: the Japanese term for a stock company (joint-stock corporation) incorporated under Japan’s Companies Act. It forms part of the official registered name of every such company; closest English equivalents: Co. Ltd. Inc.
/kabɯɕiki ɡaiɕa/
§ 2 — Mission and purpose Q133
The mission and purpose of the .株式会社 gTLD is to provide a trusted, native-language namespace built around the official Japanese corporate designation 株式会社 ("kabushiki kaisha," "KK"), which forms an integral part of the legal name of every stock company incorporated under Japan's Companies Act. A domain of the form [name].株式会社 lets a business use a fully Japanese-script identifier that mirrors its corporate name in commercial life, rather than relying on transliteration or a generic Latin-script TLD.
The namespace is oriented primarily toward Japanese stock companies and founders and businesses forming, rebranding, or preparing to incorporate. Registration is open, first-come first-served, on equivalent published terms through all ICANN-accredited registrars, consistent with the Registry Operator Code of Conduct (Specification 9). The Registry deliberately imposes no upstream eligibility screening and no one-domain-per-company cap. This reflects genuine market needs: a founder can secure a name before formal incorporation — a legitimate step, since a trade name is often reserved before the entity legally exists — and a group can hold several names covering its trade names, brands and subsidiaries. This mirrors the established model of comparable corporate-designation gTLDs such as .inc, .gmbh, .sarl and .ltd, which operate as open namespaces rather than gated registries, and avoids the adoption friction of restricted Japanese second-level spaces.
The users are Japanese businesses together with the consumers, partners and institutions that interact with them online. The namespace's value lies in coherence and memorability: a Japanese-script domain matching the corporate designation audiences already recognize. Rather than guaranteeing status through registration-time gatekeeping, the Registry relies on ICANN's established rights-protection framework to address abusive or infringing registrations — the forum in which trademark and impersonation concerns are properly adjudicated. Consistent with this, the Registry also maintains a standard anti-abuse policy that operates purely reactively — acting on well-founded notifications of abuse or infringement and complying with applicable ICANN Consensus Policies — without any pre-registration restriction.
Planned activities include: (i) a standard launch compliant with Specification 7, comprising a Sunrise period and Trademark Claims service via the Trademark Clearinghouse (TMCH); (ii) availability of the UDRP and Uniform Rapid Suspension (URS), giving clear, uniform recourse to resolve trademark conflicts after registration rather than through upstream filters; (iii) distribution through ICANN-accredited registrars with strong Japanese-market coverage; (iv) outreach to Japanese businesses and newly forming companies through incorporation-adjacent channels; and (v) premium positioning appropriate to a corporate-identity product.
The purpose is sustainable because it rests on a renewal-driven, business-oriented model: businesses that adopt their corporate name as a domain exhibit high retention, and the addressable base — millions of existing Japanese companies plus a continuous flow of new incorporations and pre-incorporation reservations — is large, stable and continuously replenished. The applying entity is part of the Xserver group, a leading Japanese hosting provider whose infrastructure, distribution relationships and financial resources support long-term operation. All Critical Functions (DNS, DNSSEC, EPP, RDDS, Data Escrow) are provided by Identity Digital, an established, ICANN pre-evaluated Registry Service Provider. Second-level registrations support Japanese-script labels under the applicable IDN tables, ensuring the namespace is fully usable in the language of its users.
§ 3 — Commitments and safeguards Q164–Q188
| More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169 | No to each |
|---|---|
| Voluntary Safeguard PICs Q170·Q171 | None · 90 applications in the round offer some |
| Registry Voluntary Commitments Q172·Q173 | None · 5 do |
| Code of Conduct exemption requested Q185·Q188 | No |
§ 4 — All other published answers
Every other answer ICANN published for this application, in the order of the form. Contact details (Q17–Q24) are left to the ICANN record.
Q212Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Answered with a document. Attachments are not published by ICANN.
Q220Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Answered with a document. Attachments are not published by ICANN.
Q221Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Answered with a document. Attachments are not published by ICANN.
Q119Script of String
Script of String
Japanese (Hiragana, Katakana, and Kanji [Han])
Q121As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.
As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.
true
Q117.1Applied-for Primary String (U-Label)
Applied-for Primary String (U-Label)
株式会社
Q117.2Applied-for Primary String (Code Points)
Applied-for Primary String (Code Points)
U+682A U+5F0F U+4F1A U+793E
Q222If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.
If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.
The Registry operates .株式会社 as an open namespace and does not impose eligibility screening before registration. Conflicts are addressed after registration through ICANN's established rights-protection framework, whose rules for trademark and corporate-name disputes — Sunrise and Trademark Claims via the TMCH, the UDRP and URS — are clear and well tested. On that basis the Registry does not anticipate significant disputes.
The Registry will nonetheless make claims a specific, standing point of attention. It will establish a dedicated claims-and-abuse channel at registry level: a single, published point of contact through which any party may raise a trademark, impersonation or abuse concern. Every substantiated claim will be reviewed promptly and met with proportionate action — including suspension where warranted — in accordance with ICANN policy.
The Registry also sees a genuine educational role for the Japanese market. Trademark registration remains relatively uncommon among Japanese small and medium-sized enterprises, so a legitimate business may hold no registered mark even where the trade name is unquestionably its own. To ensure this does not translate into unfair outcomes, the Registry will provide targeted support and guidance to registrants and complainants who encounter difficulties — helping them understand their options, the applicable ICANN procedures, and the evidence relevant to a fair resolution. In this way an open, low-friction registration experience is paired with active, responsible stewardship of the namespace after registration.
Q223By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
true
Q224By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
true