dev Domain vs io Domain

HSTS Preload: the Technical Reality

An open-source maintainer publishing documentation for a Rust framework weighs the two extensions side by side. On the surface, developer communities treat them interchangeably. Beneath the surface, .dev carries a technical guarantee that .io does not: Google Registry, which operates the .dev TLD, enrolled the entire extension in the browser HSTS preload list. Every browser that supports preloading — which covers all modern browsers — will refuse to load a .dev domain over plain HTTP. The connection upgrades to HTTPS automatically, before the first byte arrives.

For most projects in 2026, this is academic. Let’s Encrypt and similar services have made HTTPS effectively free and universal. But for developers who care about security posture as a signal — or who need to demonstrate compliance to enterprise buyers — .dev’s enforced HTTPS removes one variable from the conversation. On .io, HTTPS is equally available but not structurally enforced. The difference is philosophical more than practical, yet it surfaces in forum threads as a tie-breaker when all else is equal.

Cost Trajectory and Governance

Where the two extensions diverge more sharply is in their economic and political structures. The .dev TLD is a generic extension operated by Google Registry. Its pricing, while higher than .com, follows predictable commercial patterns with no geopolitical exposure. The .io extension, by contrast, is a country-code TLD tied to the British Indian Ocean Territory, and its pricing has moved upward — Cloudflare community members and Domain Name Wire have reported notable increases since 2024.

Developers on Hacker News have noted that .dev domains typically cost two to three times what a .com does, but that the price has been relatively stable since launch. The .io trajectory is less certain, with the Chagos sovereignty question adding a layer of governance uncertainty that .dev simply does not carry.

If you are choosing between the two for a long-running project, feed your registrar’s actual prices into the chooser tool on this page. It factors in renewal cost direction, audience type, and extension stability — because the right answer depends on numbers specific to your situation, not on which TLD the last blog post you read happened to favour.

HSTS preload is a documented technical fact (Google Registry). Price comparisons use directional language only. Scenario: open-source Rust framework maintainer.