Net Neutrality Debates Reignited by ISP-Driven gTLDs

The expansion of the DNS root through future rounds of new generic top-level domains (gTLDs) has the potential to rekindle long-simmering net neutrality debates, particularly as internet service providers (ISPs) increasingly explore vertical integration into domain name infrastructure. While the first wave of gTLD expansion in 2012 was dominated by brand owners, city governments, and niche domain entrepreneurs, a new trend is emerging: large telecommunications providers are positioning themselves to acquire and operate their own gTLDs—not only to reinforce brand identity, but to anchor content delivery strategies, user portals, and potentially even preferential data pathways. This convergence of access provision and namespace control raises fundamental questions about the neutrality of the open internet and the structural incentives that shape how content is delivered, prioritized, or potentially discriminated against.

Net neutrality, in its foundational definition, refers to the principle that all internet traffic should be treated equally, without discrimination based on source, destination, content, or application. It aims to ensure that ISPs cannot throttle, block, or prioritize traffic in a manner that undermines competition, free expression, or user choice. While legislative and regulatory battles over net neutrality have unfolded at national levels for more than two decades—most visibly in the United States through FCC reversals and judicial challenges—the domain name system has historically remained tangential to this debate. However, as ISPs begin to explore domain ownership and gTLD operation, the potential for subtle, systemic favoritism in traffic patterns and user experience becomes much more pronounced.

Consider a scenario in which a major broadband provider successfully operates a gTLD such as .fastnet or .fiberhome, and begins to offer exclusive or performance-enhanced content experiences through second-level domains like streaming.fastnet or news.fiberhome. While such services may not explicitly block access to competing content hosted on other TLDs, the integration of DNS resolution, CDN edge optimization, and preferential peering arrangements could result in perceptibly faster or more reliable experiences for content hosted within the ISP’s own namespace. Users might gravitate toward those domains not because they prefer the content, but because it loads faster, buffers less, or incurs fewer data cap penalties—circumventing the spirit, if not always the letter, of net neutrality.

The ability of an ISP to shape these experiences through a gTLD also opens the door to commercial gatekeeping. An ISP-controlled registry could offer domains under .fastnet to affiliates, content partners, or advertisers willing to pay for inclusion in a high-performance namespace. Smaller publishers, independent creators, or civic groups unable to afford such access would be disadvantaged, even if their content is equally valuable. If these economic relationships are bundled with DNS-level tools—such as prioritized A records in zero-rated apps or custom resolver behavior embedded in carrier-grade DNS infrastructure—the effects could be invisible to most users, yet structurally distortionary at scale.

This concern becomes more acute in jurisdictions without robust net neutrality protections. In countries where regulatory frameworks permit differentiated pricing or where oversight bodies lack enforcement capacity, an ISP-operated gTLD could effectively function as a walled garden. Users might find that content within the .fiberhome namespace loads instantly, incurs no mobile data charges, and is promoted through pre-installed browser homepages, while content outside the domain is throttled, metered, or absent from default search results. While such arrangements may be justified under marketing or technical rationales, the long-term consequence is a tiered internet where domain ownership correlates with visibility, speed, and audience reach.

Additionally, ISP-driven gTLDs could reshape DNS behavior in ways that undermine universal accessibility. DNS resolvers provided by ISPs might be configured to preferentially resolve queries for domains within their own gTLDs with shorter time-to-live (TTL) values, faster recursion, or local caching nodes. Conversely, they may introduce artificial delays or more frequent timeouts for domains that fall outside their preferred network pathways. Such practices, though difficult to detect or prove without specialized measurement tools, would have profound effects on digital competition and the neutrality of the DNS as a foundational layer of the internet.

The implications extend beyond performance to censorship and content control. In politically sensitive environments, an ISP-owned gTLD could be leveraged as a mechanism for state-aligned content dissemination. By controlling which organizations are allowed to register under a given gTLD, and by embedding national narratives into registrar agreements, governments and their allied ISPs could curate an “official internet” while relegating dissenting voices to less performant or more heavily scrutinized domains. The gTLD thus becomes not only a technical resource but a geopolitical instrument—one that may outpace traditional content regulation in both subtlety and effectiveness.

These developments place a renewed burden on ICANN and global internet governance stakeholders to clarify the limits of acceptable conduct for registry operators, particularly those with significant upstream control over access and infrastructure. While ICANN’s Registry Agreements prohibit certain types of discriminatory practices, enforcement has historically focused on operational compliance rather than competitive neutrality. If ISP-driven gTLDs gain traction, new policy mechanisms may be required to address vertical integration, resolve conflicts of interest, and ensure that DNS governance remains aligned with the broader public interest in an open and equal internet.

Furthermore, civil society, digital rights organizations, and net neutrality advocates must expand their monitoring frameworks to include not just access-level throttling or content blocking, but also DNS-layer favoritism and gTLD-driven market distortions. Technical transparency tools—such as DNS measurement probes, resolver benchmarking, and content delivery monitoring—should be developed with these scenarios in mind. Transparency reports from ISPs and gTLD operators could be mandated or incentivized, providing insight into traffic routing policies, registration practices, and DNS behavior at the namespace level.

In parallel, user education must evolve. The average internet user remains largely unaware of the role that domain names play in shaping access and performance. If the domain someone clicks becomes a proxy for how quickly or reliably they receive content—not due to internet topology, but due to deliberate namespace segregation by ISPs—the concept of a level playing field online erodes. Browser vendors and device manufacturers may need to consider UI cues or built-in tools that help users detect when their experience is being optimized or constrained based on domain-level affiliations.

In conclusion, the emergence of ISP-driven gTLDs introduces a new vector in the long-running net neutrality debate—one that operates not at the transport layer, but within the naming and resolution fabric of the internet itself. As the next wave of gTLDs is considered and delegated, it is imperative that the internet governance community address the risks of domain-level favoritism and ensure that the DNS remains a neutral, interoperable space. Otherwise, the future of the web may not be shaped solely by what content exists, but by who controls the domain it resides under and the network it flows through.

The expansion of the DNS root through future rounds of new generic top-level domains (gTLDs) has the potential to rekindle long-simmering net neutrality debates, particularly as internet service providers (ISPs) increasingly explore vertical integration into domain name infrastructure. While the first wave of gTLD expansion in 2012 was dominated by brand owners, city governments, and…