Last published on: 7 October 2026 at 15:31 UTC
This question set collects information regarding the legal entity that would enter into a Registry Agreement with ICANN upon successful completion of all relevant application processes. The information collected is intended to be used for background screening.
Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.
Chess Domains Limited
Provide the long form (no acronyms) of the legal entity form/business structure of the applying entity as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation. No additional information should be provided as this will be used for the automatic population of the Registry Agreement.
Private limited company
The jurisdiction indicates the location in which the business of the applying entity is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the applying entity is registered. No additional information should be provided as this will be used for the automatic population of the Base Registry Agreement. Examples include "Delaware", "Germany", etc.
United Kingdom
Provide the website URL of the applying entity, if available.
https://worldchess.com/domains
1. Choose Yes or No. 2. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement).
false
Choose Yes or No.
false
49
Provide the primary business phone number without including the country code.
17687526206
Provide the primary business email address of the applying entity.
ms@worldchess.com
Enter the street address (no PO Box).
Eastcastle House
27/28 Eastcastle Street
Enter the city, village, municipality, etc.
London
Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.
N/A
1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.
W1W 8DH
GB
If applicable, provide the full legal name as it appears on the official registration documents of the Direct Parent Company of the applying entity. Do not use abbreviations.
World Chess PLC
Provide the long form (no acronyms) of the legal entity form/business structure of the Direct Parent Company as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation.
Public limited company
The jurisdiction indicates the location in which the business of the Direct Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include "Delaware", "Germany", etc.
United Kingdom
This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.
Matvey SHEKHOVTSOV
Richard Collett, Matvey SHEKHOVTSOV
World Chess Plc
Provide a single document for Self-Certification question Q3.2-1. The document must include only the SC3.2-1.1, SC3.2-1.2, SC3.2-1.3 and SC3.2-1.4 statements. Do not modify any of the Self-Certification statements.
1. Provide a single document for Self-Certification question Q3.2-1. 2. The document must include only the SC3.2-1.1 through SC3.2-1.4 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC3.2-1.1 through SC3.2-1.4 statements, provide a document that explains why the applying entity cannot Self-Certify the SC3.2-1.1 through SC3.2-1.4 statements.
Provide a single document for Self-Certification question AGB Q220, Q5.1-1. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements.
1. Provide a single document for Self-Certification question Q5.1-1. 2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1.1-3 statements.
Provide a single document for Self-Certification question AGB Q221, Q5.2-1. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.
1. Provide a single document for Self-Certification question Q5.2-1. 2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.
This question set collects basic information regarding the string that is being applied for (for example, a-label, meaning, script). If the applying entity opts to designate a replacement string, it must answer the same set of questions for the replacement string from the AGB Question Set 5 on.
chess
Provide the meaning, or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applying entity. If there is no literal meaning in English (for example, a brand name or a proper noun without a translation) simply state "No English Translation"
The applied-for string "CHESS" is the English word for the internationally recognized strategic board game played on a 64-square board. It is governed internationally by FIDE and played competitively and recreationally worldwide.
If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)
Latin
Provide a representation of the string according to the International Phonetic Alphabet.
/tʃes/
Confirm the statement using a checkbox.
true
1. Describe the mission and purpose of the applied-for gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 1a. If applying for a variant of an existing gTLD, please also describe the mission and purpose of the existing gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 2. Explain how this purpose is sustainable over time.
The .chess gTLD will provide a secure, trusted, community-governed Internet namespace dedicated to the global chess community and operated for its benefit under FIDE's continuing institutional stewardship. Please see the separately uploaded response to Question 133 for the complete description of the mission and purpose of .chess, its intended registrants and users, activities supporting that mission, governance framework, and long-term sustainability.
This question set collects information specific to Community gTLDs. However, question 133 (Mission & Purpose) must be answered by all applying entities.
Yes
1. Provide the name of the community that the applying entity is committing to serve. 2. Describe the distinct aspects of the community.
The global chess community: individuals and organizations that play, administer, organize, teach, support, compete in, or otherwise contribute to chess worldwide, anchored by FIDE (the International Chess Federation) and its Member Federations.
Enter a category that best describes your community. Some examples of community categories could include, but are not limited to: activity-based and volunteer groups, online or social media groups, religious or political groups, diasporic communities, linguistic communities, celebrity or sports team supporters.
The global chess community is an international, organized, activity-based community composed of individuals and organizations that participate in, administer, organize, teach, support, promote, develop, report on, or provide goods or services to chess. The community includes a formal institutional structure anchored by the International Chess Federation ("FIDE"), its Continents, Zones, Member Federations, and Affiliated Organisations, together with the broader professional and non-professional chess ecosystem. That broader ecosystem includes players, clubs, tournament organizers, arbiters and other officials, trainers and educators, educational institutions, media and content contributors, technology providers and developers, chess-related businesses, sponsors, volunteers, and other persons and organizations having a bona fide connection to chess. The community is therefore neither limited to formal membership in FIDE nor defined merely by a shared interest in chess. It is characterized by sustained participation in a common activity; longstanding institutions and organizational structures; shared rules, competition, rating and title systems; recurring international, national, regional, and local activities; and continuing interaction among participants throughout the world. The community has both institutional and participatory dimensions. Its institutional dimension provides governance, representation, rules, competition structures, and continuity through FIDE and its constituent bodies. Its participatory dimension encompasses the broader network of individuals and organizations whose activities sustain, develop, promote, teach, organize, report on, and provide services to chess. Accordingly, the Applicant categorizes the identified community as an established, organized, international chess community with a federated institutional core and a broader activity-based ecosystem of participants and contributors.
Describe and provide evidence of the relationship between the applying entity and the identified community.
Chess Domains Limited has a formal and documented relationship with the identified global chess community through its authorization by the International Chess Federation ("FIDE") to apply for and, if approved, operate the .chess gTLD for the benefit of that community. FIDE serves as the international governing body for chess and provides the principal institutional framework for organized chess worldwide through its Continents, Zones, Member Federations, Affiliated Organisations, and related structures. Chess Domains Limited was established as a dedicated entity to serve as the Registry Operator for .chess. Under the governance framework established for the TLD, the Applicant will be responsible for registry operations and implementation of the Community Registration Policies, while FIDE will maintain a continuing institutional role in stewardship and oversight of the community purpose and policies of the namespace. This structure connects the Applicant directly to the established organizing body of the identified community while preserving a clear distinction between FIDE's community-governance role and the Applicant's registry-operational role. The Applicant's connection to the community is further supported through its parent, World Chess Plc, an established participant in the international chess ecosystem and FIDE's official commercial partner. World Chess has longstanding experience organizing, promoting, and developing international chess events and digital chess services and therefore provides the Applicant with relevant experience and familiarity with FIDE, organized chess, and the broader chess ecosystem. The Applicant's relationship with the community is therefore not based merely upon an asserted interest in the applied-for string. It arises from FIDE's express authorization of the Applicant to pursue and operate .chess for the benefit of the global chess community, the continuing governance role established for FIDE, and the Applicant and its parent's existing connection to the international chess ecosystem. The FIDE authorization letter and other supporting materials submitted with the application document this relationship.
Describe and provide evidence related to the community organization, any relevant organizing bodies, and any relevant leaders within the community.
The global chess community is organized through an established international structure anchored by FIDE, with continental, zonal, national, and affiliated organizing bodies that represent and administer organized chess worldwide. FIDE's 204 Member Federations provide national representation, while FIDE Continents, Zones, and Affiliated Organisations provide additional regional and specialized organization. The identified community also extends beyond these formal bodies to the broader ecosystem of individuals and organizations that participate in, contribute to, support, teach, promote, develop, report on, organize, or provide goods or services to chess. Please see the separately uploaded response to Question 136 for the complete description of the community's organizational structure, supporting evidence and citations, and an illustrative organizational graphic.
1. Describe any formal membership process, if there is one. 2. If there is no formal membership process, provide evidence related to how an individual can join the identified community (i.e., “self-identify” as a community member).
Yes. The global chess community includes both formally defined and participation-based forms of community membership, depending upon the participant's role. Certain categories have formal, objective membership, admission, registration, or identification requirements established through the International Chess Federation (FIDE) and its constituent bodies. FIDE Continents, Member Federations, and FIDE Affiliated Organisations are constituted or admitted pursuant to the FIDE Charter. Member Federation status is conferred through admission by the FIDE General Assembly pursuant to Articles 9 and 12, while Affiliated Organisation status is conferred pursuant to Article 14. Many players also possess a FIDE ID associated with FIDE's international rating, title, and competition structures. These categories therefore participate through established institutional, registration, or identification mechanisms. Other categories do not participate through a single centralized membership registry. They may self-identify through their activities and relationship with chess, but their community nexus is objectively verifiable through participation, contribution, professional activity, organization, education, support, or other bona fide involvement in chess. These categories include clubs and organizers; arbiters and other officials; trainers and coaches; authors, journalists, media and technology contributors; educational institutions; chess-related businesses and service providers; and other bona fide participants and contributors. The absence of a centralized registry for these categories does not make membership dependent upon subjective assertion. Their connection may be demonstrated through objectively identifiable activities and relationships, such as participation in or organization of chess activities, professional or educational roles, creation of chess-related content or technology, provision of goods or services to the community, or other sustained participation in or contribution to chess. The Registry Operator's Community Registration Policy reflects this mixed structure for purposes of the .chess namespace. Applicants may identify their applicable eligibility category, but self-identification alone does not establish eligibility for activation. Where centralized records exist, eligibility may be validated against those records; for other categories, reasonable documentary or other objective evidence may be required. Accordingly, the global chess community incorporates both formal and participation-based models of membership. Some categories are defined through formal admission, registration, identification, or institutional status, while others participate through sustained and objectively verifiable involvement in chess. In all cases, the Community Registration Policy requires an objective and bona fide nexus to the identified community. The .chess Community Registration Policy, attached to this response to Question 137, provides the complete framework governing community eligibility, name selection, verification, allocation, compliance, and governance and supports the Applicant's responses concerning the Community Registration Policies in Questions 151–156.
Provide the primary location of the community.
Global across all six eligible categories: governing bodies, clubs, players, officials, contributors, and community partners are present in essentially every country with an organized chess federation
1. Provide the estimated size of the community. The size should be in number format (e.g., “1,000,000 members”). 2. If the community is divided by group, region, sector, etc., this should include estimated size for each group.
204 Member Federations globally. Over 1,000,000 registered users on the FIDE-recognized online gaming platform, plus millions more competitive and casual players worldwide via the FIDE ID and rating system.
Provide the estimated size of the community that is administered or represented by each relevant organizing body in the identified community.
FIDE and its Member Federations are the sole internationally recognized governing structure for organized chess, representing essentially the entire organized global chess community.
1. Provide evidence of any documented practices of community efforts to date 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Offering support; b) Sharing information; c) Responding to specific community needs; d) Fostering and strengthening relationships within the community.
Yes. FIDE and the other organizing bodies demonstrate active, consistent, and sustained engagement with the identified global chess community through representative governance, development funding, tournament support, education and training, social initiatives, consultation, information sharing, and recurring international competition. Please see the separately uploaded response to Question 141 for the complete response, supporting evidence, sources, and illustrative materials.
1. Describe whether the applying entity has a role in any of the activities listed in Question 141. 2. If the applying entity does play a role, provide evidence of the applying entity’s role. If the applying entity does not play a role, describe why this is the case.
Chess Domains Limited is a dedicated entity established to apply for and, if approved, operate the .chess TLD pursuant to FIDE's authorization. Its role is distinct from, but complementary to, the community-engagement role performed by FIDE, its Continents, Member Federations, Affiliated Organisations, and other organizing bodies described in Question 141. The Applicant does not purport to replace those longstanding organizing bodies or independently reproduce the governance, development, education, tournament, consultation, and community-building activities through which FIDE and its constituent bodies engage the global chess community. Instead, the Applicant's role is to translate that existing community structure and engagement into the administration of the .chess namespace. This includes implementing the Community Registration Policies, operating the eligibility and name-selection verification processes, administering community-priority launch procedures, maintaining compliance and dispute-resolution mechanisms, supporting community outreach concerning adoption and use of .chess, and carrying out the periodic consultation and review processes established for the TLD. Chess Domains Limited will perform these functions under FIDE's authorization and within a governance framework that preserves FIDE's continuing institutional role in stewardship of the namespace. FIDE's engagement with its Member Federations and the broader chess community therefore provides the community foundation for the TLD, while the Applicant provides the dedicated registry structure through which the resulting community policies and objectives will be implemented. The Applicant is also supported by its parent, World Chess Plc, an established participant in the international chess ecosystem. World Chess Plc is listed on the Main Market of the London Stock Exchange and is FIDE's official commercial partner. Its activities include operation of worldchess.com, FIDE's official online chess platform, organization and commercial presentation of major international chess events, and development of chess-related digital, media, and commercial services. This experience provides the Applicant with relevant operational knowledge of the chess ecosystem, FIDE's institutional environment, and the ways in which players, organizers, commercial participants, media, and other community members interact with chess services. Accordingly, the Applicant's role in the engagement efforts described in Question 141 is not to substitute itself for FIDE or the existing organizing bodies. Its role is to work within and support that established community framework by providing the dedicated registry infrastructure, policy implementation, outreach, compliance, and accountability mechanisms necessary to operate .chess for the benefit of the identified global chess community.
1. Provide evidence that demonstrates that community members are aware of the identified community and the different member groups or segments within the identified community. 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Surveys conducted; b) Records of activities involving a diversity of community groups, segments, or members.
Yes. Members of the identified global chess community demonstrate awareness both of the community as a whole and of its distinct groups and segments through recurring governance, international competitions, surveys, educational and social programs, and cross-segment events. Please see the separately uploaded response to Question 143 for the complete response and supporting evidence.
1. Provide evidence of community members’ awareness of the applying entity and its intent to apply for a community gTLD. 2. If there is no such evidence, explain why not.
Yes. FIDE has expressly authorized Chess Domains Limited to apply for .chess as a Community gTLD, and additional community organizations have provided pre-filing endorsements. Broader community outreach and endorsement efforts will follow submission. Please see the separately uploaded response to Question 144 for the complete response and supporting evidence.
Provide evidence of the established presence of the community prior to the opening of the application submission period.
1. Provide evidence that demonstrates that individuals and groups outside of the community show an awareness of the identified community. 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Media or other public information regarding the community and its activities or members; b) Discussion of the community in various fora, whether online or in person; c) Evidence of partnerships or collaborations with groups outside of the identified community; d) Evidence of the chartering or organization of the community prior to the opening of the application submission window; e) Evidence of contributions (for example, cultural or scientific) to a larger society or population;
Yes. The identified global chess community is widely recognized outside the community, as demonstrated by recognition from international sporting and intergovernmental organizations, extensive mainstream media coverage, government and public-sector engagement, major public events, and collaborations with organizations outside chess. Please see the separately uploaded response to Question 146 for the complete response and supporting evidence.
1. Provide evidence of the longevity of the community. 2. The applying entity should provide documentation of the following practices which should have occurred within the two years leading up to application submission: a) Evidence of recurring or scheduled activities that demonstrate continuity over time; b) Documented records of past activities that demonstrate a long-standing tradition or practice; c) Records of discussions emphasizing the community’s enduring presence or its cultural significance.
Yes. The pursuits of the identified global chess community are enduring and sustainable, supported by centuries of cultural significance, more than a century of international organization, recurring competitions and governance activities, expanding education and development programs, and demonstrated adaptability to technological and social change. Independent recognition by the United Nations further identifies chess as an inclusive global activity that contributes to education, social inclusion, international cooperation, and sustainable development. Please see the separately uploaded response to Question 147 for the complete response and supporting evidence.
Explain how the applied-for string matches the name of the community or is a well-known alternative name (whether long or short form) of the community.
Yes. The applied-for string, “chess,” directly matches the name of the activity around which the identified global chess community is organized and the name by which that community is commonly recognized. The community is not defined by an artificial label created for this application. It is the global chess community: the worldwide body of individuals and organizations that play, organize, administer, teach, support, promote, develop, report on, or provide goods and services to chess. The relationship between the string and the community is therefore direct rather than associative. “Chess” is not merely a product, characteristic, location, or interest tangentially connected to the identified community. It is the common term that identifies the shared activity from which the community derives its identity, institutions, rules, competitions, professions, organizations, culture, and ongoing activities. The scope of the identified community is also consistent with the scope of the string. The Applicant has not defined a narrower subset, such as professional chess players, online chess users, tournament organizers, or members of a particular federation, and then sought the broader string “chess.” Instead, the identified community encompasses the institutional, professional, and non-professional ecosystem associated with chess worldwide, subject to the objective nexus requirements described in the Community Registration Policy. Thus, the thematic breadth of the string corresponds to the breadth of the community identified in the application. The use of “chess” to identify this broader community is independently recognizable outside the community itself. The United Nations describes chess as a global activity that transcends borders, cultures, and generations and recognizes its worldwide cultural, educational, and social significance. See https://www.un.org/en/observances/world-chess-day/stories. International sporting institutions likewise use “chess” as the ordinary name for the organized activity represented internationally through FIDE and national federations. Accordingly, .chess constitutes a direct match to the identified community: the string is the ordinary and established name of the shared activity defining the identified community, the scope of the community is commensurate with the scope of the string, and the term is widely recognized by persons both within and outside the community as identifying the global chess ecosystem.
1. Explain how the applied-for string clearly relates to or represents the community 2. Explain whether the applied-for string has any other significant meaning beyond identifying the community or community members described in the application. The applying entity may wish to provide pertinent information regarding any particular geography, region, or themes that may be alluded to by the string, of which the community may or may not be a part.
Yes. The general public will instinctively associate “chess” with the game of chess and the worldwide community organized around it. The ordinary dictionary meaning, international institutional usage, and public recognition of the term all support this direct association. Please see the separately uploaded response to Question 149 for the complete analysis and supporting evidence.
Select from Radio Buttons - Yes/No. Notes: 1. Community Registration Policies are conditions that community gTLD registry operators impose upon registrants within their gTLDs. 2. If you select “Yes” to this question, the applying entity is required to pay the conditional Registry Commitments Evaluation fee, and Community Registration Policies that are approved by ICANN will be scored in the CPE (if the applying entity elects to participate) and included in Specification 12 of the applicable Base RA. 3. If you select “No,” then the application cannot proceed as a community application.
Yes
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy with respect to registrant eligibility in each response field. Up to 10 Community Registration Policies can be submitted. 3. Follow this format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars ,: a) "Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) "Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) "Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring ___"; and/or b) "Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___". 6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a registration eligibility policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the registration policy described in (a) at least once per year, and publish the results of such review (including any updates to the registration policy) on its website within thirty (30) days following the anniversary of the Effective Date. 7. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a registrant eligibility restriction is time-limited, the applying entity must state if the restriction will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 8. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
This Community Registration Policy implements the registrant eligibility requirements described in Part B of the separately uploaded .chess Community Registration Policy (attached to the response to Question 137) and includes an additional platform-neutrality commitment proposed by the Applicant in this application. Capitalized terms used below have the meanings assigned to them in the .chess Community Registration Policy unless otherwise defined in the Registry Agreement. The additional platform-neutrality commitment supplements, and does not amend, the .chess Community Registration Policy.
Please see full instructions in AGB Q151.1.
1. Registrant Eligibility Registry Operator shall restrict activation and continued active use of domain names in the TLD to Registrants that have a bona fide nexus to the chess community and that fall within one or more of the following eligible registrant categories: (a) FIDE; FIDE Continents; FIDE Zones; Member Federations and their regional, state or local subdivisions; and FIDE Affiliated Organisations; (b) chess clubs, leagues, academies, schools, educational institutions, scholastic and collegiate chess programs, tournament and event organizers, and similar organizations affiliated with, authorized by, recognized by, or actively participating within the organized chess community; (c) players participating in organized chess, including holders of a FIDE ID, registered users of the official FIDE gaming platform, members of national federations, participants in recognized over-the-board or online chess competitions, titled players, scholastic and collegiate competitors, and other individuals who actively participate in organized chess; (d) arbiters, trainers, coaches, instructors, tournament directors, organizers, officials, volunteers, and other persons serving the organized chess community; (e) authors, journalists, commentators, broadcasters, publishers, researchers, historians, streamers, podcasters, content creators, software developers, engine developers, database providers, and other persons contributing to the development or promotion of chess; and (f) businesses, nonprofit organizations, educational institutions, media organizations, sponsors, publishers, retailers, manufacturers, software companies, online platforms, technology providers, event service providers, and other organizations whose activities actively support, promote, develop, or provide goods or services to the chess community. Registry Operator shall require each Registrant, as a condition of activation and continued use of a .chess domain name, to have and maintain a genuine nexus to the chess community. Registry Operator shall not treat a Registrant's desire to register, activate, or maintain an active .chess domain name, without additional objective evidence of eligibility, as sufficient to establish the required nexus to the chess community. Registry Operator shall apply the registrant eligibility requirements on a platform-neutral basis. Registry Operator shall not condition eligibility for activation or continued active use of a .chess domain name upon a Registrant's use of, affiliation with, or commercial relationship with any particular online chess platform, the Registry Operator, or an Affiliate of the Registry Operator, except where such relationship independently constitutes the basis for eligibility under an otherwise applicable eligibility category.
Please see full instructions in AGB Q151.1.
2. Eligibility Verification Registry Operator shall administer the eligibility verification process through a Registry-operated website or other Registry-operated verification mechanism. Registry Operator shall require each Registrant to identify the basis of its eligibility, including, where applicable, Member Federation affiliation, FIDE ID, membership in the official FIDE gaming platform, participation through another established online chess platform where such participation provides objective evidence of eligibility, participation in organized chess activities, operation of a chess-related business or organization, provision of chess-related goods or services, or another objective connection to the chess community. Registry Operator shall determine eligibility by objective reference to the applicable eligible registrant category and relevant documentation, affiliations, records, or other verifiable evidence. Registry Operator shall not determine eligibility solely on the basis of a Registrant's unverified self-assertion. Registry Operator shall apply verification proportionate to the Registrant, eligibility category, and domain name concerned, which may include automated verification, documentary verification, statistically targeted post-registration review, and complaint-driven review, consistent with Part B of the .chess Community Registration Policy. Section B.3 of the .chess Community Registration Policy, attached to the response to Question 137, provides for these forms of verification.
Please see full instructions in AGB Q151.1.
3. Activation and Continuing Eligibility Registry Operator shall not activate a domain name in the TLD unless the Registrant has identified the basis of its eligibility and completed the applicable eligibility verification process. Registry Operator shall conduct ongoing eligibility compliance activities, including statistically targeted and complaint-driven post-registration review. Registry Operator shall notify a Registrant if Registry Operator determines that the Registrant does not meet or no longer meets the applicable eligibility requirements and shall provide the Registrant any applicable opportunity to correct the deficiency provided under the .chess Community Registration Policy. Registry Operator shall deactivate, place on hold, suspend, or cancel a domain name if the Registrant does not meet or ceases to meet the applicable eligibility requirements and fails to correct the deficiency within the applicable period established under the .chess Community Registration Policy. This is also consistent with Part E.1 of the .chess Community Registration Policy (attached to Question 137), which provides for verification at activation and post-registration review and permits deactivation, hold, suspension, or cancellation for uncured noncompliance.
Please see full instructions in AGB Q151.1.
4. Registry-Registrar Agreement Requirements Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall clearly inform each prospective Registrant, prior to registration, that registration and continued maintenance of a .chess domain name are restricted by the .chess Community Registration Policy and subject to Registry Operator's eligibility verification process. Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall provide each Registrant with the information reasonably necessary to access and complete Registry Operator's eligibility verification process. Registry Operator shall conduct the substantive eligibility determination and shall not require Registrar to independently determine a Registrant's eligibility under the Community Registration Policy
Please see full instructions in AGB Q151.1.
5. Registration Agreement Requirements Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Registrant to meet and continue to meet the registrant eligibility requirements of the .chess Community Registration Policy for as long as the Registrant holds the registration. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Registrant to identify the basis of its eligibility and provide information reasonably required for Registry Operator to conduct its eligibility verification process. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Registrant to acknowledge that a .chess domain name will not be activated unless the applicable eligibility verification process has been completed and may subsequently be deactivated, placed on hold, suspended, or cancelled if the Registrant ceases to satisfy the eligibility requirements.
Please see full instructions in AGB Q151.1.
6. Objective Measures of Compliance Registry Operator shall develop and implement registration eligibility procedures consistent with Part B of the .chess Community Registration Policy (attached to the response to Question 137) and the additional platform-neutrality commitment set forth in this Community Registration Policy and publish the eligibility requirements and information concerning the Registry-operated eligibility verification process on its website no later than the date on which the TLD is delegated in the DNS. Registry Operator shall publish on its website that eligibility for activation and continued active use of a .chess domain name does not depend upon use of, affiliation with, or a commercial relationship with any particular online chess platform, the Registry Operator, or an Affiliate of the Registry Operator, except as provided in the platform-neutrality commitment above. Registry Operator shall maintain records reasonably sufficient to demonstrate implementation of its eligibility verification procedures and application of the registrant eligibility requirements. Registry Operator shall conduct a review of the Community Registration Policies at least once every five (5) years to determine whether those policies continue to serve the interests of the identified community and remain consistent with the mission and purpose of the .chess TLD. Registry Operator shall as part of each such review invite comments from Member Federations, FIDE Affiliated Organisations, Registrants, and other members of the identified community and publish a summary of the issues raised and any resulting policy proposals in accordance with the policy development procedures applicable to the TLD.
Please see full instructions in AGB Q151.1.
7. Limitations Registry Operator shall apply the registrant eligibility requirements and platform-neutrality commitment set forth in the .chess Community Registration Policy for the lifetime of the TLD.
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Base Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy with respect to name selection criteria or rules for the applied-for string in each response field. Up to 10 Community Registration Policies can be submitted. 3. These criteria or rules should align with the community objectives of the applied-for gTLD string. 4. Follow this format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars: a) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 6. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring___""; and/or b) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___"". 7. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a name selection rule and publish it on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the name selection rule described in (a) at least once per year, and publish the results of such review (including any updates to the rule) on its website within thirty (30) days following the anniversary of the Effective Date. 8. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a name selection rule is time-limited, the applying entity must state if the rule will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 9. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
This Community Registration Policy implements the name selection requirements described in Part C of the .chess Community Registration Policy (attached to the response to Question 137) and includes an additional platform-neutrality commitment proposed by the Applicant in this application. Capitalized terms used below have the meanings assigned to them in the .chess Community Registration Policy unless otherwise defined in the Registry Agreement. The additional platform-neutrality commitment supplements, and does not amend, the separately uploaded .chess Community Registration Policy.
Please see full instructions in AGB Q152.1.
1. General Name Selection Requirement Registry Operator shall require each domain name, as a condition of activation and continued active use in the .chess TLD, to have a bona fide connection to the Registrant's own name, identity, role, activities, or contribution to the chess community, or to a trademark, service mark, trade name, business name, or pseudonym in which the Registrant holds rights or under which the Registrant is publicly known or lawfully operates within the chess community. Registry Operator shall not activate or permit the continued active use of a domain name that does not satisfy the applicable name selection requirements set forth in this Community Registration Policy. Registry Operator shall apply the following name selection classifications in determining whether a requested domain name satisfies the required connection between the domain name and the Registrant.
Please see full instructions in AGB Q152.1.
2. Name Selection Classifications Registry Operator shall allocate the names and recognized acronyms of FIDE, FIDE Continents, FIDE Zones, Member Federations, and FIDE Affiliated Organisations only to the corresponding community body. Where two recognized bodies have a legitimate claim to the same name, Registry Operator shall resolve allocation in accordance with the allocation procedures applicable to the .chess TLD. Registry Operator shall allocate names corresponding to recognized chess disciplines, formats, and well-established terms of the game only to Registrants that demonstrate a documented nexus between their activities and the applicable discipline, format, or term, consistent with its established meaning in the chess community. Registry Operator shall allocate the names of chess clubs, leagues, academies, events, and other recognized community organizations only to the corresponding organization or an authorized registrant acting on its behalf. Registry Operator shall permit activation of a domain name consisting of the legal or commonly known name of a player, official, or other recognized individual within the chess community only where the Registrant is that individual or an authorized representative of that individual. Registry Operator shall permit activation of a domain name consisting of a trademark, service mark, trade name, business name, or pseudonym only where the Registrant holds rights in that name or mark, is an authorized user thereof, or is publicly known or lawfully operates under that name within the chess community. Registry Operator shall reserve names of FIDE bodies, Member Federations, recognized chess disciplines, and other names designated for allocation to appropriate members or bodies of the chess community, consistent with the Registry Agreement and the .chess Community Registration Policy. Registry Operator shall not allocate or permit activation of a reserved name contrary to the conditions applicable to that reserved name. Registry Operator shall permit activation of other names not falling within one of the classifications above only where the Registrant satisfies the registrant eligibility requirements applicable to the .chess TLD and the requested name satisfies the general name selection requirement in Section 1 above. Registry Operator shall not give a Registrant preferential access to or permit activation of a domain name based solely upon the Registrant's use of, affiliation with, or commercial relationship with any particular online chess platform, the Registry Operator, or an Affiliate of the Registry Operator, except where such relationship independently establishes the Registrant's rights in or bona fide connection to the requested name under an otherwise applicable name selection classification.
Please see full instructions in AGB Q152.1.
3. Verification and Continuing Compliance Registry Operator shall verify compliance with the applicable name selection requirements when a Registrant seeks to activate a .chess domain name. Registry Operator shall determine compliance with the name selection requirements by objective reference to the applicable name classification and relevant documentation, rights, affiliations, records, activities, or other verifiable evidence demonstrating the required connection between the domain name and the Registrant. Registry Operator shall apply verification proportionate to the Registrant, domain name, and applicable name classification and may request reasonable documentation or other objective evidence necessary to establish compliance. Registry Operator shall not determine that a domain name satisfies the name selection requirements solely on the basis of a Registrant's unverified assertion. Registry Operator shall conduct ongoing name selection compliance activities after launch, including statistically targeted and complaint-driven post-registration review. Registry Operator shall notify a Registrant if Registry Operator determines that a domain name does not satisfy or no longer satisfies the applicable name selection requirements and shall provide the Registrant any applicable opportunity to correct the deficiency provided under the .chess Community Registration Policy. Registry Operator shall deactivate, place on hold, suspend, or cancel a domain name if the domain name does not satisfy the applicable name selection requirements and the deficiency is not corrected within the applicable period established in accordance with the .chess Community Registration Policy.
Please see full instructions in AGB Q152.1.
4. Registry-Registrar Agreement Requirements Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall clearly inform each prospective Registrant, prior to registration, that registration and continued maintenance of a .chess domain name are subject to the name selection requirements of the .chess Community Registration Policy. Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall provide each Registrant with the information reasonably necessary to access and complete any Registry Operator process applicable to verification of the name selection requirements. Registry Operator shall perform the substantive verification of compliance with the name selection requirements and shall not require Registrar to independently determine such compliance.
Please see full instructions in AGB Q152.1.
5. Registration Agreement Requirements Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Registrant to select and maintain a .chess domain name that satisfies the name selection requirements of the .chess Community Registration Policy. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Registrant to provide information reasonably required by Registry Operator to establish the required connection between the domain name and the Registrant. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Registrant to acknowledge that a .chess domain name will not be activated unless the applicable name selection requirements have been satisfied and may subsequently be deactivated, placed on hold, suspended, or cancelled if the domain name fails or ceases to satisfy those requirements. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting the Registrant from registering or maintaining a reserved or protected .chess domain name unless the Registrant satisfies the conditions applicable to allocation of that name.
Please see full instructions in AGB Q152.1.
6. Objective Measures of Compliance Registry Operator shall develop and implement name selection procedures consistent with Part C of the .chess Community Registration Policy and the additional platform-neutrality commitment set forth in this Community Registration Policy and publish the applicable name selection requirements on its website no later than the date on which the TLD is delegated in the DNS. Registry Operator shall maintain records reasonably sufficient to demonstrate implementation of its name selection verification procedures and application of the name selection requirements. Registry Operator shall maintain procedures for statistically targeted and complaint-driven post-registration review of compliance with the name selection requirements. Registry Operator shall conduct a review of the Community Registration Policies, including the name selection requirements, at least once every five (5) years to determine whether those policies continue to serve the interests of the identified community and remain consistent with the mission and purpose of the .chess TLD. Registry Operator shall as part of each such review invite comments from Member Federations, FIDE Affiliated Organisations, Registrants, and other members of the identified community and shall publish a summary of the issues raised and any resulting policy proposals in accordance with the policy development procedures applicable to the TLD.
Please see full instructions in AGB Q152.1.
7. Limitations Registry Operator shall apply the name selection requirements and platform-neutrality commitment set forth in this Community Registration Policy for the lifetime of the .chess TLD.
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy in each response field. Up to 10 Community Registration Policies can be submitted. 3. Follow the format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars: a) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring___""; and/or b) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting___"". 6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a Community Registration policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the Community Registration Policy described in (a) at least once per year, and publish the results of such review (including any updates to the registration policy) on its website within thirty (30) days following the anniversary of the Effective Date. 7. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a commitment is time-limited, the applying entity must state if the rule will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 8. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
1. Community Registration Policy: Registration Eligibility Dispute Resolution Policy This Community Registration Policy implements the dispute resolution commitment described in Section E.4 of the .chess Community Registration Policy (attached to the Response to Question 137) and includes an additional platform-neutrality commitment proposed by the Applicant in this application. The additional platform-neutrality commitment supplements, and does not amend, the separately uploaded .chess Community Registration Policy. Capitalized terms used below have the meanings assigned to them in the .chess Community Registration Policy unless otherwise defined in the Registry Agreement. Registry Operator shall develop, publish, and implement a Registration Eligibility Dispute Resolution Policy (“REDRP”) providing an administrative challenge mechanism for: (a) an Applicant that believes its request to activate a .chess domain name was improperly denied based upon the registrant eligibility or name selection requirements; and (b) a third party that believes an existing Registrant or an active domain name does not satisfy the registrant eligibility or name selection requirements applicable to the .chess TLD. Registry Operator shall establish and publish procedures governing REDRP proceedings, including standing requirements, filing procedures, applicable fees, response procedures, timelines, standards for decision, available remedies, and procedures for implementing determinations. Registry Operator shall provide an appropriate opportunity for the affected Applicant or Registrant to respond to a challenge before a final determination is issued, except where immediate action is otherwise permitted or required under the Registry Agreement or applicable ICANN policy. Registry Operator shall comply with and implement final determinations issued under the REDRP, including any determination requiring activation, deactivation, placement on hold, suspension, cancellation, or other appropriate action concerning a domain name consistent with the Registry Agreement and applicable ICANN policies. a) Registry-Registrar Agreement Requirements Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall reasonably cooperate with Registry Operator in implementing final REDRP determinations concerning domain names sponsored by that Registrar, including by giving effect to any required activation, deactivation, placement on hold, suspension, cancellation, or other action within the Registrar's control. b) Registration Agreement Requirements Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Registrant to submit to proceedings brought pursuant to the REDRP concerning the Registrant's .chess domain name and to be bound by final determinations issued pursuant to the REDRP, subject to any review or appeal rights provided under that policy. c) Objective Measures of Compliance Registry Operator shall publish the REDRP, including its procedures, applicable timelines, fees, and available remedies, on its website no later than the commencement of the first launch phase in which the REDRP may be invoked by an Applicant or third party under its terms. Registry Operator shall maintain records reasonably sufficient to demonstrate administration of REDRP proceedings and implementation of final REDRP determinations. Registry Operator shall review the REDRP as part of the periodic review of the Community Registration Policies conducted at least once every five (5) years pursuant to Section G.7 of the .chess Community Registration Policy. Any amendment resulting from such review shall be made in accordance with the applicable policy development process. d) Limitations Registry Operator shall maintain and apply the REDRP for the lifetime of the .chess TLD.
Please see full instructions in AGB Q153.1.
2. Community-Priority Launch and Allocation This Community Registration Policy implements the community-priority launch and allocation framework described in Part D of the .chess Community Registration Policy, attached to the Response to Question 137. Registry Operator shall implement a sequenced launch process providing registration opportunities to governing and representative bodies of the chess community before registrations are generally available to other eligible community members. Registry Operator shall conduct an initial phase for FIDE to register their names, recognized acronyms, programs and/or activities. Registry Operator shall conduct a subsequent phase for FIDE Continents, FIDE Affiliated Organisations and Member Federations to register their names, recognized acronyms, and community names within their authority. Registry Operator shall not activate a domain name registered during any applicable Trademark Clearinghouse Sunrise unless the Registrant satisfies the registrant eligibility and name selection requirements applicable to the .chess TLD. Registry Operator shall thereafter conduct a limited-registration phase for other eligible community members, including clubs, organizers, players, officials, contributors, and community partners, before General Availability. Registry Operator shall not provide launch priority based solely on an Applicant's use of, affiliation with, or commercial relationship with any particular online chess platform, the Registry Operator, or an Affiliate of the Registry Operator, except where that relationship independently establishes eligibility for the applicable launch phase. Upon General Availability, Registry Operator shall make registrations available on a first-come, first-served basis, provided that no domain name shall be activated unless the Registrant and domain name satisfy all applicable eligibility, name selection, reserved-name, and verification requirements. Registry Operator shall not treat payment of a registration fee as establishing eligibility for activation. a) Registry-Registrar Agreement Requirements Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall comply with the eligibility, phase, and allocation requirements for each launch phase and shall not knowingly submit a registration request during a restricted phase for an Applicant ineligible for that phase. b) Registration Agreement Requirements Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring the Applicant or Registrant to provide information reasonably required to establish eligibility for any restricted community launch phase. c) Objective Measures of Compliance Registry Operator shall publish the eligibility requirements, dates, and allocation procedures for each community launch phase on its website before that phase begins. Registry Operator shall maintain records reasonably sufficient to demonstrate implementation of the community-priority launch sequence and applicable eligibility requirements. Registry Operator shall review this Community Registration Policy as part of the periodic review of the Community Registration Policies conducted at least once every five (5) years pursuant to Section G.7 of the .chess Community Registration Policy. d) Limitations Registry Operator shall apply these launch-phase requirements only during the applicable launch phases of the .chess TLD. Following General Availability, all continuing registrant eligibility, name selection, reserved-name, verification, and other Community Registration Policies shall apply for the periods specified in those policies.
1. If you are proposing any limitation to a proposed Community Registration Policy in Questions 151-153, please provide a rationale in this response field. Please see Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria. 2. If you are not proposing any limitation to a proposed Community Registration Policy in Questions 151-153, please type ""Not Applicable"" in this response field.
The Community Registration Policies proposed in Questions 151–153 are intended to preserve the community-based nature of the .chess TLD and, except as described below, apply for the lifetime of the TLD. The registrant eligibility requirements proposed in Question 151 are not limited in duration. Continued restriction of registration to persons and organizations having a bona fide nexus to the global chess community is fundamental to the mission and purpose of the .chess TLD. Accordingly, Registrants must satisfy the applicable eligibility requirements at registration and throughout the period in which they maintain a .chess domain name. The name selection requirements proposed in Question 152 likewise are not limited in duration. Requiring a bona fide connection between a registered domain name and the Registrant's identity, role, activities, contribution, rights, or other recognized connection to the chess community is intended to preserve the integrity and community orientation of the namespace throughout its operation. The platform-neutrality requirements proposed in Questions 151 and 152 likewise are not limited in duration. They are intended to ensure that eligibility for activation and continued active use of a .chess domain name, and application of the name selection requirements, remain based upon an objective nexus to the global chess community rather than a Registrant's use of, affiliation with, or commercial relationship with any particular online chess platform, the Registry Operator, or an Affiliate of the Registry Operator. The Registration Eligibility Dispute Resolution Policy proposed in Question 153 is also intended to apply for the lifetime of the TLD. An ongoing challenge mechanism is necessary to provide Applicants, Registrants, and other members of the community with a means to address alleged violations of the registrant eligibility and name selection requirements. The Community-Priority Launch and Allocation Policy proposed in Question 153 is necessarily limited in duration to the launch of the .chess TLD. Its purpose is to provide FIDE and other governing and representative bodies of the chess community with sequenced community-based registration opportunities before the namespace is opened more broadly to other eligible community members. Once the applicable launch phases have concluded and General Availability begins, those phase-specific priorities no longer serve an operational purpose. However, all continuing registrant eligibility, name selection, verification, reserved-name, and compliance requirements remain applicable following General Availability for the periods specified in the applicable Community Registration Policies. The five-year review provisions applicable to the Community Registration Policies are not limitations on the duration or enforceability of those policies. Rather, they provide a periodic mechanism to evaluate whether the policies continue to serve the interests of the identified community and remain consistent with the mission and purpose of the .chess TLD. Any resulting amendment remains subject to the community governance and policy development procedures described in the separately uploaded .chess Community Registration Policy, attached to the response to Question 137. Section G.7 provides for review at least once every five years, while Parts G.2-G.6 establish the broader consultation and governance framework for amendments.
1. Provide an explanation of how the proposed Community Registration Policies meet the Registry Commitments Evaluation criteria 4 and 5 using the considerations in the Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria. 2. Consider whether the proposed Community Registration Policy could be argued to be duplicative of a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. There may be circumstances in which a Community Registration Policy that would duplicate requirements under applicable consensus policy or law could be approved at ICANN’s sole discretion. If not duplicative, please explain why you believe the Community Registration Policy is not duplicative. If yes, please specify such a requirement and explain why you believe duplication in the Base RA is necessary. 3. Consider whether the proposed Community Registration Policy could be argued to be contrary to a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. ICANN will not approve any Community Registration Policies that are found to be contrary to applicable laws, ICANN agreements and policies. Please share your views on this issue in the answer to this question. 4. Consider whether the proposed Community Registration Policy could be argued to be incompatible with ICANN’s Bylaws. ICANN will not approve any Community Registration Policies that are found to be incompatible with the ICANN Bylaws. See background at the ICANN Board resolution 2024.06.08.08-2024.06.08.10. Please share your views on this issue in the answer to this question. 5. Consider whether the proposed Community Registration Policy requires the operation of an additional Registry Service. The applying entity shall engage its selected RSP to discuss the implementation of such an additional Registry Service, which must be evaluated through the RSP Program and approved by ICANN.
See separately uploaded “Q155 – .chess Community Policies Meet Registry Commitments Evaluation Criteria 4 and 5” for the complete response addressing non-duplication, consistency with applicable law and ICANN requirements, compatibility with the ICANN Bylaws, additional Registry Services, and the relationship of the commitments to the .chess community.
Please provide evidence of support for the applying entity’s application by attaching written endorsements from the organizing bodies relevant to the identified community (related to Question 136).
Yes. Chess Domains Limited has express authorization from FIDE to apply for and, if approved, operate .chess for the benefit of the global chess community, together with written endorsements from multiple FIDE Member Federations representing diverse national and regional portions of that community. Broader endorsement outreach will commence following submission of the application. Please see the separately uploaded response to Question 156 and supporting endorsement letters for the complete response and evidence.
Provide an explanation of why opposition may or may not be relevant or how the applying entity intends to address or resolve the opposition, if applicable.
See separately uploaded “Question 157.” for the complete response addressing known and reasonably foreseeable potential opposition, including concerns of online chess platforms and other commercial participants, FIDE’s role, community eligibility, name allocation, Registry neutrality, and community accountability.
This question set collects information related to determining whether certain Safeguard Public Interest Commitments (Safeguard PICs) are required for the applied-for gTLD string. See Section 7.8.2.3 Safeguard PICs. Answers to these questions will inform assessment by ICANN on whether and which Safeguard PICs must be incorporated in the applicable Registry Agreement (RA) if the string proceeds to delegation. The answers themselves will not automatically make such a determination.
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
Select Yes or No. Notes: 1. ICANN will evaluate whether an applied-for gTLD string requires one or more Safeguard Public Interest Commitments (Safeguard PICs) to be included in the Base RA). 2. In addition to the Mandatory Public Interest Commitments (PICs) that must be included in each Base RA, a subset of Base RAs must include Safeguard PICs based on ICANN’s Safeguard Assessment. See Section 7.8.2.3 Safeguard PICs. 3. Applying entities for TLDs that are not found to require Safeguard PICs can elect to add them to the applicable Base RAs voluntarily to, for example, further their business objectives, help address issues or concerns that are raised or could be raised with respect to their applications, or avoid the need for the evaluation and implementation of customized Registry Voluntary Commitment (RVC). See Section 7.8.3 Registry Voluntary Commitments (RVCs).
No
This question set collects information related to any Registry Voluntary Commitments (RVCs) that the applying entity is submitting. The decision to submit an RVC is typically voluntary, except for those recognized by ICANN to resolve an objection or to address GAC Consensus Advice. See Section 7.8.3 Registry Voluntary Commitments for more information.
1. Select Yes or No. 2. In addition to Safeguard Public Interest Commitments (PICs), an applying entity will be permitted to propose one or more Registry Voluntary Commitments (RVCs) to provide additional safeguards with regard to the registry operator’s operation of an applied-for gTLD string. See Section 7.8.3 Registry Voluntary Commitments (RVCs). 3. RVCs are separate from Community Registration Policies. See Section 7.8.3 Registry Voluntary Commitments (RVCs) and Section 7.8.4 Community Registration Policies for more information. If you are applying for a Community gTLD, please submit the Community Registration Policies by answering Questions 150-155. However, if you propose to include additional Registry Voluntary Commitments in the RA beyond the Community Registration Policies, you may answer "yes" and proceed to answer the following questions. 4. You are encouraged to consider whether there are other means, separate from including commitment(s) in the Base RA, that could be used to further your business objectives or help resolve any anticipated or actual issue(s) raised regarding the applied-for gTLD string or application. See Section 7.8.3 Registry Voluntary Commitments (RVCs). Notes: If you select “yes” to this question, you are required to pay the conditional Registry Commitments Evaluation fee, and commitments that are approved by ICANN will be included in Specification 11 of the applicable Base RA as specific voluntary public interest commitments as contractual obligations.
No
This question set collects information related to whether the applied-for gTLD string is a .Brand (see Section 7.3) or if the applying entity is seeking a Code of Conduct exemption (see Section 7.4).
Select Yes or No
No
This serves as an indication of intent to apply for an exemption to Specification 9 and that the applying entity is NOT requesting to be designated a .Brand TLD, pursuant to Specification 13.
No
This question set collects any additional information that the applying entity would like to provide, including any supporting materials.
This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.
Confirm the statement using the checkbox.
true
Confirm the statement using the checkbox.
true