.codex

Mission and Purpose - OpenAI OpCo, LLC is applying for the .codex top-level domain as a dotBrand TLD under Specification 13 of the Registry Agreement. The mission of .codex is to provide a controlled namespace for authorized information, products, services, and operations associated with the Codex brand. The dotBrand TLD will allow OpenAI and its affiliates to organize the online presence of Codex under a distinctive, brand-controlled namespace and will help Internet users identify digital properties authorized by OpenAI. The intended registrants of .codex are consistent with Specification 13's requirement. OpenAI's internal policies will govern use of .codex and will remain tightly controlled to protect the integrity and trust associated with the Codex brand. OpenAI intends to use .codex for sites and services supporting Codex and related offerings. Uses may include product information, developer resources, customer support, product or service access points, and other authorized purposes associated with the Codex brand. A controlled .codex namespace will provide a consistent framework for the Codex digital presence, help users distinguish authorized Codex properties, and reduce opportunities for impersonation and namespace confusion. Sustainability OpenAI intends to maintain the .codex TLD as long-term brand infrastructure. OpenAI is a well-established company with global operations and significant technical and financial resources. The ongoing operational costs of maintaining a dotBrand TLD are well within OpenAI's organizational capacity, and OpenAI has the technical infrastructure and vendor relationships necessary to support registry operations in compliance with ICANN's requirements. Because .codex will function as a closed, single-registrant TLD under Specification 13, it does not depend on third-party registration revenue for sustainability. The TLD's value is derived from its role within OpenAI's broader business, not from commercial registration activity. OpenAI views .codex as a living asset whose specific use cases may evolve, while remaining anchored to the Codex brand and subject to Specification 13's requirements throughout the term of the Registry Agreement.