tld.report · The 2026 Round

Snapshot of 8 October 2026 · ICANN APS, public fields

Applications / .chromebook / CRRI2564-T75498 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.chromebook

Brand TLD · Spec 13Active

Charleston Road Registry Inc., US Q1·Q25

Ultimately controlled by Alphabet Inc. Q108 · ICANN record ↗

Existing registry operator, registrar or affiliate, as declared: Q12

Applying entity is an existing registry operator

§ 1 — Meaning of the string Q118·Q120

The applied-for string, 'chromebook', is a brand name referring to the line of laptop and tablet computers running the Linux-based ChromeOS operating system designed by Google.

/ˈkrəʊm.bʊk/

§ 2 — Mission and purpose Q133

Mission and Purpose: Charleston Road Registry Inc. dba Google Registry (Charleston Road Registry), an American company wholly owned by Google, provides registry services to the public. Google is a global technology leader focused on improving how millions of users connect with information. In line with Google’s mission, Charleston Road Registry aims to make information universally accessible by extending the utility of the Domain Name System while enhancing the performance, security, and stability of the Internet. We aspire to create unique web spaces where users learn about products and services in a targeted manner. The primary purpose of the applied-for gTLD is to provide a dedicated, recognizable, and trusted Internet space where Google can consolidate and innovate its educational and computing hardware offerings. This applied-for gTLD provides Google ability to categorize its online locations, securely manage its brand presence, and offer a highly recognized web space to the general Internet population.

Intended Registrants and Users: Charleston Road Registry intends to operate the applied-for gTLD as a closed registry and Google or its subsidiary acting as the registrant. The ultimate goal is to allow Google to comprehensively manage the domain space for its educational hardware offerings. Members of the general public will not be able to register domains in this applied-for gTLD. Registration will be tightly managed, and only designated internal personnel will be authorized to register domains. If multiple internal parties seek the same domain name, designated personnel will make the final decision on which registration represents a higher business priority. The intended users of the applied-for gTLD are the general Internet public, students, educators, and enterprise workers who will navigate to these domains to securely access Google's educational and computing hardware technologies and services.

Related Activities: The applied-for gTLD will provide Google with the ability to customize its domain names to signal to Internet users that its websites are secure and managed directly by Google. The specialization goal of the applied-for gTLD is to extend Google’s Chromebook brand to each dedicated second-level domain space. This provides a centralized mechanism for Google to link its diverse initiatives, allowing it to actively manage its brand presence and coordinate the introduction, testing, and phase-out of web spaces for educational hardware services. Launching the applied-for gTLD will generate increased competition in the online marketplace by adding incremental availability to the domain pool. The applied-for gTLD provides an authoritative environment for the exclusive provision of Google’s Chromebook content. The applied-for gTLD will spur further innovation by providing an accelerated platform for the seamless introduction of new offerings and a mechanism for enhanced global branding.

Sustainability Over Time: Charleston Road Registry will strive to provide the highest level of user experience through operational stability, security, and performance for the applied-for gTLD. This purpose is highly sustainable over time due to Google's long-term corporate standing, continuous investment, and robust technical infrastructure. We are uniquely positioned to provide this experience given our relationship with Google; Google invests heavily in IT infrastructure and maintains operational excellence. Google runs one of the largest DNS system in the world, has industry-leading uptime on its services, and offers enterprise services on which governments depend. Google keeps speed, reliability and scale in mind with each new service, ensuring ongoing stability for the registry's lifetime. Google is well-financed and committed to maintaining Charleston Road Registry, ensuring operation of the TLD remains viable, relevant, and fully funded.

§ 3 — Commitments and safeguards Q164–Q188

More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169No to each
Voluntary Safeguard PICs Q170·Q171

• Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring registrants to comply with all applicable laws, including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct), fair lending, debt collection, organic farming, disclosure of data, and financial disclosures. • Registry Operators will include a provision in their Registry-Registrar Agreements that requires registrars at the time of registration to notify registrants of the requirement to comply with all applicable laws. • Registry Operators will include a provision in their Registry-Registrar Agreements that requires Registrars to include in their Registration Agreements a provision requiring that registrants who collect and maintain sensitive health and financial data implement reasonable and appropriate security measures commensurate with the offering of those services, as defined by applicable law.

Registry Voluntary Commitments Q172·Q173None · 5 do
Brand TLD criteria confirmed, trademark certificate attached Q180·Q181Yes · certificate not published
Confirms the string is not a “generic string” Q183Yes
Spec 11 §3(d) statement Q184

This response is submitted by Charleston Road Registry Inc. ("Registry Operator"), a wholly-owned subsidiary of Google LLC, whose ultimate parent company is Alphabet Inc. Registry Operator confirms that there is no conflict with Section 3(d) of Specification 11 of the Base Registry Agreement, as the applied-for string .chromebook is not a "generic string" and will be operated strictly as a closed, proprietary .Brand TLD (or under a Code of Conduct exemption) in full compliance with ICANN policies.

1. Definition of Generic String vs. Brand Trademark Section 3(d) of Specification 11 defines a "generic string" as a word or term that "denominates or describes a general class of goods, services, groups, organisations or things, as opposed to distinguishing a specific brand of goods, services, groups, organisations or things from those of others." The applied-for string .chromebook does not denominate or describe a general class of goods, services, or things. Rather, it represents a highly distinctive, proprietary trademark owned by Alphabet Inc. or its affiliates, which is registered globally and recorded in the Trademark Clearinghouse (TMCH). The primary and exclusive purpose of the TLD is to distinguish Alphabet's brand, products, services, and proprietary ecosystem from those of other market actors, ensuring absolute clarity regarding source, sponsorship, and affiliation for Internet users.

2. Application of Specification 13 (.Brand TLD Status) Registry Operator has self-designated this application as a .Brand TLD under Specification 13 of the Base Registry Agreement. In accordance with the criteria set forth in Section 9.3 of Specification 13: - Registry Operator shall be the sole registrant and user of second-level domain names within the TLD. - Registry Operator shall maintain absolute, exclusive control over the DNS records associated with all domain names at any level within the .chromebook namespace. - Registrations will not be made available to the general public or unaffiliated third parties. Because Specification 13 explicitly permits and formalises the exclusive operation of TLDs that are brand-specific and trademark-backed, there is zero risk of an exclusive-use conflict under Specification 11.

3. Mitigation for Potential Dictionary Meanings To the extent that .chromebook may be associated with a common dictionary term in certain contexts, Registry Operator clarifies that its intended and actual operation of the TLD is strictly restricted to its brand-specific, trademarked meaning. By restricting all domain registrations exclusively to Alphabet Inc. and its affiliates, the TLD will function solely to host Alphabet's proprietary offerings, services, and technologies. The TLD will not operate as an open or generic registry for the corresponding dictionary term, thereby ensuring that third-party access to the generic namespace on the wider Internet is completely unaffected.

Therefore, because the TLD is backed by a verified registered brand trademark, qualifies for .Brand TLD status, and is operated on a strictly single-registrant basis to represent the trademark owner's proprietary offerings, its exclusive operation does not constitute a "closed generic" and remains in perfect alignment with Section 3(d) of Specification 11.

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

Q199Q2.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) of the applying entity, 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: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.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.

Q2.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) of the applying entity, 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: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.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.

Q200Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).

Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).

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

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