History of the TLD

.press is a generic top-level domain (gTLD) introduced through ICANN’s New gTLD Program and delegated to the DNS root zone in 2014. The registry operator is Radix Technologies Inc. The extension was created to provide a distinct namespace for press and media‑oriented content worldwide.

Main Use and Industry Position

.press is primarily used by journalists, media organisations, bloggers, publishers, news outlets, and content creators who wish to signal media credibility and focus on press‑related content. It serves as a branding tool for newsworthy or informative content. The TLD is open for public registration without sector restrictions and is recognised globally within the domain market as a media‑centric extension.

Comparison to Other TLDs

Compared with general-purpose TLDs like .com and .net, .press is niche‑oriented towards media and publishing. Compared with other niche gTLDs like .media or .news, .press emphasises editorial and press identity. It differs from generic extensions such as .info by explicitly aligning with journalistic and media positioning.

Pros and Cons of the TLD

Pros

• Strong association with media, journalism, and press themes

• Open registration without eligibility restrictions

• Supported by multiple registrars globally

Cons

• Potentially higher cost compared to generic extensions like .com or .net

• Less universal brand recognition outside media niches

• Market perception varies by audience and industry

Registration Criteria

Any individual or organisation may register a .press domain on a first‑come, first‑served basis. There are no specific eligibility requirements beyond standard ICANN registration rules.

Summary

.press is a targeted gTLD designed to serve media and press entities. It is operated by Radix Technologies Inc., widely supported by registrars, and used by journalists, content creators, and publishers. Registration is unrestricted and simple, making it suitable for media branding. Its media‑centric focus offers a clear identity, though it may not be as broadly recognised as legacy TLDs.