The mission of .SERVER is to provide a namespace associated with the concept of server as a computer or system that provides resources, applications, or services to other computers or users. The .SERVER 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 .SERVER is to enable registrants to establish online identities using domain names that correspond to this concept. To achieve this purpose, Pirin Tablet, LLC will make .SERVER 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 .SERVER is sustainable over time because computers and systems that provide resources, applications, or services to other computers or users will continue to play a fundamental and enduring role in technology. As technology evolves, organizations and individuals will continue to establish online identities associated with the applied-for string.
The mission of .server is to give the hosting and network infrastructure sector a namespace that names its own object. The string is the ordinary English noun ""server"" - the program or machine that provides a service to other computers over a network. It is applied for and will be operated in that plain descriptive sense, as an open namespace.
Registrants are the organisations and people who operate infrastructure: hosting and cloud providers, data centre and colocation operators, managed service providers, network operators, system integrators, software vendors distributing self-hosted products, IT departments, developers and open source projects, and individuals running personal infrastructure.
Users are the people who reach those addresses: customers checking a status page, administrators opening a control panel, client software calling an API endpoint, and developers following documentation.
Why the namespace is needed: Naming machines and services is a continuous, everyday operation, but it is currently done inside a domain chosen for commercial reasons. Infrastructure ends up addressed as a subdomain of a marketing site, which ties operational naming to a brand that may change and gives the reader no indication of what the address is for.
A top-level namespace whose word is precisely ""server"" resolves that mismatch. name.server is short, self-describing, and readable by the audience that matters - an address that announces itself as infrastructure rather than as a page. It serves equally for a provider's public offering, a product's documentation and download host, or a region-specific service endpoint.
The TLD will launch with the rights protection mechanisms required by Specification 7, including a Sunrise period and a Trademark Claims period. General Availability will then be open, with no eligibility restrictions and no reservation of the namespace to the applying entity or its affiliates. Distribution will be through ICANN-accredited registrars on published, non-discriminatory terms consistent with Specification 9; in particular, availability and pricing will not be conditioned on a registrant being a customer of any company affiliated with the applying entity. Technical operation is contracted to a pre-evaluated Registry Service Provider. Abuse mitigation follows the Mandatory Public Interest Commitments and the DNS abuse obligations of the Base Registry Agreement, with a published abuse point of contact and particular attention to the abuse patterns that affect infrastructure-oriented namespaces.
The purpose is sustainable because the underlying activity is attached to no product cycle: for as long as networks exist, machines and services must be named, and that naming happens continuously as infrastructure is provisioned, migrated and retired. A domain used as an operational endpoint also behaves differently from one used as a website, being written into configuration files, DNS records, monitoring systems, client software and customer contracts, so letting it lapse breaks running systems rather than merely taking a page offline, and the registrant renews it as a matter of operational necessity. That gives the TLD a retention profile closer to a hosting subscription than to a speculative registration. The applying entity belongs to an established hosting and infrastructure group whose customer base is precisely the population of intended registrants, so awareness does not rest on paid distribution alone, while the technical sense of the word is understood identically across language markets, keeping the addressable market global rather than regional. Registry operations are contracted to a pre-evaluated Registry Service Provider under a signed agreement, so the obligations of the Registry Agreement are met throughout ramp-up without depending on registration revenue alone.