Applications / .kord / CL2660T-T64559 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.kord

Brand TLD · Spec 13Active

§ 1 — Meaning of the string Q118·Q120

kord

kord

§ 2 — Mission and purpose Q133

The .kord gTLD will operate as a Specification 13 (.Brand) top-level domain and serve as a trusted digital namespace exclusively controlled by Checkboard Limited (Checkboard). The mission of .kord is to promote trust, transparency, security, and accountability in digital interactions involving identity verification, compliance processes, and the collection or management of personal information.
As a .Brand TLD, all registrations within the .kord namespace will remain under the control of Checkboard, its affiliates, and authorized trademark licensees. No domain names will be available for public registration. The namespace will be used solely to support Checkboard-operated services, products, platforms, customer experiences, business functions, and other activities consistent with the Kord brand and its trademark rights.
The .kord namespace will provide a clear and recognizable indicator that a website, application, service, or digital resource is an authentic Checkboard-controlled destination. By maintaining exclusive control over registrations and DNS operations, Checkboard can reduce the risk of impersonation, phishing, and other forms of online fraud that rely on confusing or misleading domain names.
Checkboard may use .kord domains to support identity verification services, customer onboarding, compliance workflows, consent management, document exchange, secure communications, data governance functions, and related trust-based digital interactions. The namespace may also be used for internal operations, partner integrations, research and development, security initiatives, and future digital services developed by Checkboard and its affiliated entities.
A core objective of the .kord gTLD is to reinforce confidence in online interactions by ensuring that every active .kord domain represents a resource that is operated, controlled, or authorized by Checkboard. This closed operating model enables consistent governance, security standards, technical controls, and compliance requirements across the entire namespace.
The long-term sustainability of .kord is supported by its direct integration with the Kord brand, business operations, and intellectual property assets. Because the namespace is not dependent on third-party registrations, its ongoing viability is driven by Checkboard's continuing use of the domain ecosystem to support its commercial activities, customer engagement, innovation initiatives, and digital trust services.
The .kord gTLD will also provide public interest benefits by creating a highly trusted environment in which Internet users can readily identify authentic Checkboard-operated digital services. Through centralized governance and exclusive registration policies, Checkboard can maintain consistent security practices, protect users from fraudulent imitations, and support transparency regarding digital interactions conducted within the namespace.
By operating .kord as a closed .Brand TLD, Kord will maintain direct accountability for all registrations and services within the namespace while providing a secure, trustworthy, and sustainable platform for present and future digital initiatives.

§ 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
Brand TLD criteria confirmed, trademark certificate attached Q180·Q181	Yes · certificate not published
Confirms the string is not a “generic string” Q183	Yes
Spec 11 §3(d) statement Q184	The proposed .kord gTLD does not create any conflicts with ICANN Specification 11 because it is intended to operate as a Specification 13 .Brand TLD, under the exclusive control of Checkboard Limited as the Registry Operator. Specification 13 expressly requires that only the Registry Operator, its affiliates, and authorized trademark licensees may register domain names within the TLD, and that the TLD string correspond to a registered trademark. Unlike a generic, community, or open-registration gTLD, .kord will not offer domain names to the general public, independent third parties, or unaffiliated organizations. All domain names within the namespace will remain under the ownership, control, and accountability framework of Kord and entities authorized by Kord. As a result, the registry will not function as a public registration platform or as a generic industry namespace. Furthermore, the string .kord corresponds to the Kord brand and is intended to serve as a branded namespace supporting Kord-operated services, products, platforms, business functions, and digital trust initiatives. The TLD is therefore not proposed for use as a generic term describing a class of goods, services, or market participants. Accordingly, .kord does not raise the concerns addressed by Specification 11 provisions relating to generic strings and the operation of generic terms in an exclusive manner. The operation of .kord will be governed through centralized policies, technical controls, and registration practices established by Kord. Because all registrations will remain within the Kord corporate ecosystem, the Registry Operator will maintain direct oversight of DNS operations, security requirements, acceptable use policies, and compliance obligations across the namespace. This closed and highly controlled operating model significantly reduces the risk of consumer confusion and supports the objectives of stability, accountability, and transparency that underlie ICANN's registry framework. Accordingly, .kord does not present a conflict with Specification 11. The TLD will operate as a closed .Brand registry consistent with Specification 13 requirements, will not function as a generic or open-use namespace, and will remain under the exclusive control of the Registry Operator and its authorized affiliates and trademark licensees.

§ 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.

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

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