.crew

The mission of .CREW is to provide a namespace associated with the concept of crew as a group of people working or acting together for a common purpose The .CREW gTLD is intended to serve a broad range of registrants and users, including individuals, businesses, organizations, communities, projects, and other entities that identify with, relate to, or wish to be associated with the concept represented by the applied-for string. The purpose of .CREW is to enable registrants to establish online identities using domain names that correspond to this concept. To achieve this purpose, Acid Medal, LLC will make .CREW available for registration through registrars and other appropriate distribution channels; maintain a secure, stable, and reliable registry infrastructure; implement registration and operational policies that support the availability, security, and integrity of the namespace; and provide ongoing administration of the gTLD to enable registrants to register and use domain names within the namespace. The purpose of .CREW is sustainable over time because groups of people working or acting together for a common purpose will continue to play a fundamental and enduring role across society. As society, technology, and methods of collaboration evolve, organizations and individuals will continue to establish online identities associated with the applied-for string.

Mission, Purpose and Sustainability of .crew The mission of .crew is to provide a clear and meaningful digital space for people who work, create, travel or build together. The word “crew” conveys belonging, shared responsibility and collective purpose. The .crew gTLD is therefore intended for teams, communities, organizations, projects, clubs, companies, creators, operators and other groups wishing to identify themselves online through a name that reflects cooperation and human connection. Intended registrants include individuals, businesses, associations, professional groups, sports teams, maritime or aviation crews, gaming and esports organizations, cultural and creative collectives, project teams, online communities, and individuals using .crew for personal or family identity, including surname-based registrations. Intended users include their members, customers, supporters, partners, employees and the broader Internet public seeking information, services, platforms, campaigns or community resources. The purpose of .crew is to offer an open and accessible namespace for many types of groups while preserving the positive meaning of the string. Registrations are expected to be available through participating ICANN-accredited registrars. Although .crew is not intended as a restricted community TLD, the registry will maintain appropriate policies, monitoring and abuse-mitigation measures to protect users, support trust and discourage uses that could undermine the namespace. To achieve this purpose, the registry will support registrar onboarding, registrar communication, publication and enforcement of registration and acceptable-use policies, rights-protection and abuse-response procedures, responsible use, and technical operation in line with ICANN requirements. It also intends to support DNSSEC, strong access controls, safeguards for high-value names, privacy and data-protection practices consistent with applicable law, and Universal Acceptance. The purpose of .crew is sustainable because the need to organize, recognize and connect groups of people is enduring. Human activity increasingly relies on distributed teams, shared projects, online communities and trusted digital identities. A namespace dedicated to collective action can therefore remain relevant across sectors and generations, from local groups to global organizations. .crew is designed to remain sustainable through transparent governance, broad registrar access, reasonable pricing, continuous compliance monitoring, scalable technical operations, responsive abuse handling and the ability to update policies as technologies, security risks, user expectations and ICANN requirements evolve. No variant of an existing gTLD is being applied for. Accordingly, no separate mission or purpose statement for an existing gTLD is required.