Page Secure But Empty

When Google launched the .page top-level domain in late 2018, it arrived with a promise of modernity, professionalism, and built-in security. Marketed as a sleek, flexible namespace for individuals, businesses, and content creators, .page was part of Google Registry’s expanding catalog of new generic top-level domains under the broader ICANN new gTLD program. It stood out for two reasons: its universal, content-neutral name—ideal for nearly any kind of website—and its strict HTTPS requirement, which mandated that all .page domains be served over secure connections with SSL certificates. In an age of growing concerns over digital privacy and phishing, this was not just a feature but a core selling point. Yet despite its technical merit and the strength of its backing, .page has largely failed to gain traction. Today, it stands as a paradox in the domain world: secure by design, but eerily underused—a digital ghost town with clean streets and no residents.

From the outset, .page seemed like a slam dunk. The name itself was as generic and versatile as it gets, making it an attractive option for everything from personal websites and portfolios to product landing pages, marketing campaigns, and online documentation. The word “page” already held deep connotations with the web itself, evoking everything from blog posts to landing sites and sales funnels. For content creators frustrated with overcrowded .com real estate or turned off by the spammy reputation of other new TLDs like .biz or .info, .page offered a clean slate—memorable, uncluttered, and Google-endorsed.

Google’s approach to .page was both disciplined and innovative. By requiring HTTPS across all domains, Google aimed to make .page a standard-bearer for secure web practices. Domain registrants were required to obtain valid SSL certificates—something Google made easy through integrations with services like Let’s Encrypt and its own Certificate Authority. This mandatory security layer set .page apart from legacy domains, where HTTPS was optional and, even in 2018, not universally adopted. It aligned perfectly with Google’s broader mission to encrypt the web and improve user safety across search and browser ecosystems.

The pricing model also seemed calibrated for accessibility. At launch, .page domains were offered at relatively modest prices compared to premium gTLDs, especially for non-premium names. This encouraged early adoption by independent developers, freelancers, and small businesses. Google tied .page into its suite of services, making it easily purchasable via Google Domains and integrable with tools like Firebase Hosting and Blogger. The infrastructure, the branding, and the technical design were all in place. The runway was clear.

And yet, adoption of .page never materialized at scale. While initial registration numbers were respectable, they plateaued quickly. The domain failed to develop a vibrant aftermarket. Few major brands adopted it. Even among Google’s own products and initiatives, .page saw little internal use. Instead, most .page domains remained parked, redirected, or minimally developed. A significant percentage of registrations were speculative—short generic words or trendy phrases snapped up by domain investors hoping for future demand that never came. As a result, browsing through .page websites today often leads to dead ends: template pages, basic redirects, or domain-for-sale notices. The promise of a clean, secure content space was realized only in architecture—not in actual habitation.

Several factors contributed to this curious failure. Chief among them was the persistent dominance of .com in public and commercial consciousness. Despite decades of alternatives, .com remains the de facto home of the web, deeply ingrained in user behavior and brand strategy. New TLDs like .page, no matter how elegant or secure, struggle to overcome this inertia. Businesses, when choosing a domain, still prioritize familiarity and credibility—and .com continues to deliver both. .page, while technically superior in some respects, couldn’t match the reflexive trust of .com or even the niche identity strength of extensions like .tech, .dev, or .design.

Another limiting factor was perception. Unlike industry-specific or purpose-built TLDs, .page suffered from its own neutrality. It didn’t speak to any one community or vertical. It was universal, but in the process, it became vague. While a photographer might be drawn to .photo or a startup to .io, .page lacked that same sense of identity or affiliation. It was meant for everyone, but ended up attracting no one in particular. The open-endedness that once seemed like a strength proved to be a branding weakness.

The mandatory HTTPS, while a technically sound and forward-thinking move, may also have created hidden friction. For users unfamiliar with SSL setup or DNS management, the requirement added a layer of complexity compared to more permissive domains. Despite Google’s efforts to simplify the process, the average small site builder or casual blogger might have been dissuaded by the extra steps, particularly if they didn’t fully understand the benefits. Ironically, in trying to build a safer internet, .page may have alienated the very audience most in need of that protection.

Even in Google’s own ecosystem, .page failed to become a flagship. Unlike .dev, which gained a solid following among developers and projects on GitHub, or .app, which Google positioned as a dedicated namespace for mobile apps and progressive web apps, .page had no defined role. It became the overlooked sibling in Google’s domain family—well-resourced but underpromoted. With no clear focus or community to anchor it, .page drifted into digital obscurity.

As of 2025, .page remains an active and technically robust domain, still available through Google Domains and other registrars, still compliant with modern security standards, and still under the stewardship of one of the most powerful tech companies in the world. Yet its presence on the web is sparse. It hasn’t been widely adopted for mainstream content, nor has it become a cult favorite in any subculture or tech niche. It is not plagued by spam or misuse, but it also lacks vitality. Secure by design, but deserted in practice, .page stands as a quietly haunting example of a domain extension that did everything right—except find its audience.

The fate of .page underscores a larger truth in the domain space: technical merit is not enough. A domain extension, no matter how well constructed, must resonate emotionally, culturally, or commercially with its users. It must solve a problem, signal membership in a community, or offer a distinct advantage. .page, for all its minimal elegance, did none of these convincingly. Its streets may be clean and well lit, but they remain, for the most part, empty.

When Google launched the .page top-level domain in late 2018, it arrived with a promise of modernity, professionalism, and built-in security. Marketed as a sleek, flexible namespace for individuals, businesses, and content creators, .page was part of Google Registry’s expanding catalog of new generic top-level domains under the broader ICANN new gTLD program. It stood…