Application Details

Last published on: 7 October 2026 at 15:21 UTC

Application Type: New gTLD

Primary String: base

Application ID: CTI2649T-T85441

Application Priority Number: --

Application Status: Active

Processing Stage: Pre-Evaluation Processing

Comment Period: --

View:

Summary Responses Clarifying Questions Change Requests Documents Objections

Application Responses

Section: Applying Entity Information

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.

AGB Q1. Full Legal Name

Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.

Coinbase Technologies, Inc.

AGB Q3. Legal Entity Form/Business Structure

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.

Corporation

AGB Q4. Jurisdiction

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.

Delaware USA

AGB Q10. Website URL

Provide the website URL of the applying entity, if available.

https://www.base.org/

AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?

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

AGB Q13. Is the applying entity a back-end registry service provider (RSP), an ICANN-approved data escrow agent, an emergency back-end registry operator, a Uniform Rapid Suspension (URS) service provider, an ICANN dispute resolution service provider, a Privacy or Proxy Service Provider, or a Reseller?

Choose Yes or No.

false

AGB Q17. Phone Country Code

AGB Q18. Primary Business Phone

Provide the primary business phone number without including the country code.

4152095329

AGB Q19. Primary Business Email Address

Provide the primary business email address of the applying entity.

legalnotices@coinbase.org

AGB Q20. Address Line 1

Enter the street address (no PO Box).

248 3rd Street

AGB Q21. Address Line 2

#434

AGB Q22. Locality

Enter the city, village, municipality, etc.

Oakland

AGB Q23. State/Province/Region

Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.

California

AGB Q24. Postal Code

1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.

94607

AGB Q25. Country Code of Location

AGB Q26. Full Legal Name

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.

Coinbase Global, Inc.

AGB Q28. Legal Entity Form/Business Structure

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.

Corporation

AGB Q29. Jurisdiction

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.

Texas

AGB Q36. Full Legal Name

If applicable, provide the full legal name as it appears on the official registration documents of the Ultimate Parent Company of the applying entity. Do not use abbreviations. "Ultimate Parent Company" means, with respect to an Applicant (and, if applicable, a Direct Parent Company), the top-level entity that directly or indirectly possesses the power to direct the management and policies of such Applicant (and, if applicable, a Direct Parent Company) through the ownership of voting securities, as a general partner, as a managing member, by contract, or otherwise. An Ultimate Parent Company is not controlled by any other entity. If there are no intermediary entities between the Applicant and the Ultimate Parent Company, the Ultimate Parent Company would be the same entity as the Direct Parent Company.

Coinbase Global, Inc.

AGB Q38. Legal Entity Form/Business Structure

Provide the long form (no acronyms) of the legal entity form/business structure of the Ultimate 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.

Corproation

AGB Q39. Jurisdiction

The jurisdiction indicates the location in which the business of the Ultimate 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.

Texas

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

Section: DNS Abuse

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.

AGB Q221. 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.

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.

Has Documents

Section: Primary String

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.

AGB Q116. Applied-for Primary String (ASCII Label)

base

AGB Q118. What is the meaning/definition of the applied-for gTLD string?

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"

“BASE” is a Coinbase trademark identifying the Base protocol, an open-source Ethereum Layer 2 network incubated by Coinbase, and its ecosystem. In English, “base” may mean a foundation or starting point, distinct from its specific use here.

AGB Q120. Phonetic Representation

Provide a representation of the string according to the International Phonetic Alphabet.

/beɪs/

AGB Q121. 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.

Confirm the statement using a checkbox.

true

AGB Q133. What is the mission and purpose of the applied-for gTLD?

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.

Coinbase Technologies, Inc. is applying for and, if successful, will operate the .base gTLD as a stable, secure, and authoritative DNS namespace associated with the Base protocol, network, and ecosystem. Base is an open-source optimistic rollup and Ethereum Layer 2 network incubated by Coinbase and used for onchain applications, payments, digital-asset services, wallets, developer tools, and other Internet-based activity. “Base” is used in this application as the distinctive name of that specific protocol, network, and ecosystem, not as a term describing a general class of goods, services, groups, organizations, or things. Coinbase owns the BASE trademark registrations identified in this application, and its Affiliates use the mark under license. The mission and purpose of .base is to provide trusted and memorable Internet identities for official websites, applications, developer resources, products, services, communications, and other lawful online activities of Coinbase Technologies, Inc. and its Affiliates. The namespace will help Internet users identify and navigate to authoritative Base-related resources through the globally coordinated Domain Name System. All domain-name registrations in .base will be registered to and maintained by Coinbase Technologies, Inc. for the exclusive use of Coinbase Technologies, Inc. or its Affiliates. Registrations will not be sold, distributed, or transferred for the control or use of unaffiliated third parties. Intended users are members of the Internet public seeking to identify, discover, navigate to, or interact with authoritative Base-related resources, including developers, businesses, institutions, creators, consumers, and ecosystem participants. They may access and use resources in .base but will not be eligible registrants. This allocation model serves a substantive purpose. Digital-asset and payment services are frequent targets of impersonation and phishing, and deception involving those services can cause direct financial loss. Restricting every .base registration and usage to Coinbase Technologies, Inc. or its Affiliates prevents unaffiliated parties from registering names in the TLD and materially reduces the risk of registrant-based impersonation, rather than relying solely on detection and takedown after harm occurs. To achieve this mission and purpose, Coinbase Technologies, Inc. intends to work with its registry service provider and other service providers to support reliable registry operations, controlled domain-name allocation, DNS security, rights protection, data escrow, continuity, and DNS-abuse prevention and response. The applicant will establish internal registration, security, acceptable-use, and domain-management procedures appropriate for an authoritative corporate and technology namespace. This purpose is sustainable because .base supports an established protocol, network, and active technology ecosystem and is intended to form part of Coinbase’s long-term Internet, product, developer, and security infrastructure. Its operation will be supported by Coinbase Technologies, Inc. and its corporate group and will not depend on third-party registration volume, public domain sales, or short-term market demand.

Section: Safeguard Identification

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.

AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

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.

AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q167. Would most people think that (domains in) the TLD(s) in the application are used for activities that require regular government reporting, inspections, and oversight in various countries? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

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.

AGB Q169. Would most people think that the TLD is used for something usually done by governments? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

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.

AGB Q170. Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Registry Agreement (RA) voluntarily regardless of ICANN’s Safeguard Assessment outcomes?

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

Section: Registry Voluntary Commitments (RVCs)

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.

AGB Q172. Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Registry Agreement (RA) that are unique to your applied-for string?

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.

Section: Brand & Code of Conduct Exemptions

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

AGB Q179. Are you applying for a Brand TLD?

Select Yes or No

AGB Q185. Does the applying entity request a Code of Conduct Exemption?

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.

Yes

AGB Q186. The applying entity confirms all domain name registrations in the TLD will be registered to, and maintained by, registry operator for the exclusive use of the registry operator or its affiliate (as defined in the Base RA);

Confirm statement with a checkbox.

true

AGB Q187. Confirm the registry operator will not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an affiliate of registry operator.

Confirm statement with a checkbox.

true

AGB Q188. Confirm and specify why the Application of the Code of Conduct to the applied-for string is not necessary to protect the public interest.

Provide justification for why the Code of Conduct is not necessary to protect the public interest. This may include an explanation of how the TLD's operation under the exemption would serve the best interests of the registry operator, its stakeholders, and the broader Internet community, without adversely affecting the domain name ecosystem.

Application of the Registry Operator Code of Conduct to .base is not necessary to protect the public interest because the TLD will not have unaffiliated registrants requiring the protections that Specification 9 is intended to provide. Coinbase Technologies, Inc., as Registry Operator, will be the registrant of record for all domain-name registrations in .base and will maintain those registrations exclusively for its own use or the use of its Affiliates, as defined in the Base Registry Agreement. It will not sell, distribute, transfer, or otherwise provide control or use of any .base registration to a person or entity that is not an Affiliate. Base ecosystem developers, partners, customers, users, and other participants will not be eligible to control or use registrations merely because they participate in or maintain a relationship with the Base ecosystem. There will therefore be no public registration market, unaffiliated registrant class, or third-party registrant whose interests could be affected by preferential registrar access, registry self-allocation, use of registration data, or other differential treatment addressed by Specification 9. Domain names will be allocated and managed internally for the official websites, applications, developer resources, products, services, communications, and other lawful activities of Coinbase Technologies, Inc. and its Affiliates. Internet users may visit and interact with resources using .base names, but they will not become registrants or obtain control or use of registrations. The exemption will serve the public interest by allowing .base to operate as a controlled and authoritative namespace for the Base protocol, network, and ecosystem. Digital-asset, wallet, payment, and financial-technology services are frequent targets of impersonation, phishing, and fraudulent domain use. Restricting every .base registration to a single, identifiable corporate group will prevent unaffiliated parties from registering names within the TLD and materially reduce the risk that Internet users will mistake an unauthorized .base registration for an official Base or Coinbase resource. Centralized allocation will also support consistent security controls, domain-management practices, lifecycle management, and prompt response to abuse or compromise. The requested exemption is limited to Specification 9. Coinbase Technologies, Inc. will remain subject to all other applicable provisions of the Registry Agreement, ICANN Consensus Policies, technical and operational requirements, rights-protection mechanisms, DNS security and stability obligations, registration-data requirements, data escrow, continuity requirements, and DNS-abuse mitigation and response obligations. If Coinbase Technologies, Inc. later proposes to make .base registrations available for the control or use of unaffiliated third parties, it will first notify ICANN, relinquish the exemption as required, and comply with Specification 9 and all applicable launch and rights-protection requirements before implementing that change. Accordingly, Specification 9 would provide no material additional protection to registrants because the only registrants will be the Registry Operator and its Affiliates, while the exemption will facilitate the secure, accountable, and authoritative operation of .base without adversely affecting registrants, competition, or the broader domain-name ecosystem.

Application Details

Application Responses

Section: Applying Entity Information

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

Section: DNS Abuse

Section: Primary String

Section: Safeguard Identification

Section: Registry Voluntary Commitments (RVCs)

Section: Brand & Code of Conduct Exemptions

Section: Additional Information and Supporting Materials

Section: Bona Fide Intent and Prohibited Communications