Applications / .safari / KNIC2550-T86937 · published by ICANN 7 October 2026 · snapshot 2026-10-08
§ 1 — Meaning of the string Q118·Q120
In Swahili, safari means a journey or trip; in English, it is also commonly understood as an expedition or journey, especially one involving travel and exploration.
N/A
§ 2 — Mission and purpose Q133
The mission of the applied-for gTLD is to establish a trusted, globally recognised digital namespace for tourism, adventure travel, wildlife conservation, cultural heritage, education, research, and related industries. The gTLD will support organisations, communities, businesses and individuals connected to the global travel ecosystem by enabling authentic, meaningful and discoverable online identities.
Its purpose is to provide a distinctive and globally accessible platform for entities involved in travel experiences, tourism, hospitality, destination promotion, wildlife and environmental conservation, cultural heritage, education, storytelling, digital commerce and related activities. The gTLD is intended to help registrants establish trusted digital presences that reflect their connection to travel, exploration, nature, culture and responsible tourism.
The Registry Operator intends to steward the namespace responsibly and to promote sustainable tourism practices, environmental stewardship, cultural appreciation, innovation and economic participation. The gTLD will support tourism boards, destination marketing organisations, tour operators, travel agencies, hospitality providers, protected areas, conservancies, conservation organisations, educational and research institutions, government agencies, community-based organisations, small and medium-sized enterprises, technology providers, content creators and individual professionals.
The gTLD will also support public-interest objectives by encouraging responsible representation of travel destinations, wildlife, cultural heritage and local communities; improving the visibility of tourism and conservation initiatives; facilitating knowledge sharing and environmental education; and enabling digital transformation and entrepreneurship across tourism-related sectors.
Through these activities, the applied-for gTLD seeks to become a trusted online identity for tourism, conservation, cultural heritage and adventure-related experiences, while supporting registrant trust, user confidence, responsible innovation and global discoverability.
§ 3 — Commitments and safeguards Q164–Q188
| More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169 | Yes to: more trustworthy (Q164), consumer risk if abused (Q165), licensing or accreditation (Q166) |
|---|---|
| Voluntary Safeguard PICs Q170·Q171 | None · 90 applications in the round offer some |
| Registry Voluntary Commitments Q172·Q173 | None · 5 do |
| Code of Conduct exemption requested Q185·Q188 | No |
§ 4 — All other published answers
Every other answer ICANN published for this application, in the order of the form. Contact details (Q17–Q24) are left to the ICANN record.
Q212Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Answered with a document. Attachments are not published by ICANN.
Q220Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Answered with a document. Attachments are not published by ICANN.
Q221Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Answered with a document. Attachments are not published by ICANN.
Q119Script of String
Script of String
Latin
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
Q222If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.
If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.
KeNIC submits two endorsement letters demonstrating complementary public-sector and private-sector support for its participation in the ICANN 2026 New gTLD Program.
The public-sector endorsement, dated 30 July 2026 and issued by the Ministry of Information, Communications and the Digital Economy through the Communications Authority of Kenya (CA), conveys the Ministry’s full support for KeNIC’s application. The letter recognises KeNIC as the designated registry operator for Kenya’s .ke country-code top-level domain and acknowledges its role in administering, managing and developing Kenya’s Internet namespace. It states that the proposed application is consistent with the Kenya National Digital Master Plan and the Government’s broader digital-transformation agenda. The Ministry identifies anticipated public-interest benefits including strengthened digital sovereignty, greater security and resilience of the national Internet ecosystem, trusted digital identities for businesses and institutions, and mitigation of cyber-enabled fraud. It also considers KeNIC to have the technical expertise, operational experience and institutional capacity required to steward the proposed gTLD and supports KeNIC’s proposed role as registry operator.
The private-sector endorsement, also dated 30 July 2026, was issued by the Kenya Private Sector Alliance (KEPSA). KEPSA describes itself as Kenya’s apex private-sector body, with a reach of more than two million businesses, from start-ups and SMEs to large local enterprises and multinational corporations. It is also the focal point for the East African Business Council in Kenya and hosts ICC Kenya. KEPSA supports KeNIC’s participation and recognises the importance of a secure, trusted and well-governed digital ecosystem to economic growth, innovation, digital trade, competitiveness and sustainable private-sector development. It also acknowledges KeNIC’s role in Kenya’s domain-name ecosystem and its efforts to enhance Kenya’s digital presence and create an inclusive environment for businesses, entrepreneurs, institutions and other stakeholders.
Together, the endorsements support KeNIC’s proposed multistakeholder approach. KeNIC intends to maintain collaboration throughout the application process and, if the application is successful, during implementation, involving government institutions, the regulator, the private sector, the technical community, civil society and other relevant stakeholders globally. This approach is intended to promote transparency, inclusion, technical resilience and broad-based value to Kenya’s digital economy, while supporting a secure, stable, resilient and innovative namespace globally.
The endorsements are presented as evidence of institutional support and policy alignment; they do not replace or predetermine ICANN’s independent evaluation. The Ministry’s endorsement remains expressly subject to ICANN policies, evaluation procedures, contractual requirements, Kenyan law and other applicable legal and regulatory obligations. KEPSA states that its endorsement is based on information provided to it and is not an independent technical, legal, financial, operational or regulatory assessment, confirmation that ICANN requirements have been satisfied, or a guarantee, warranty, certification or representation regarding the application’s outcome or future operation. KeNIC remains solely responsible for satisfying all applicable ICANN, contractual, legal and regulatory requirements.
Answered with a document. Attachments are not published by ICANN.
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