Facebook and the Tor Project get the IETF to fomally recognize .onion domains as special use, which prevents ICANN from selling off the gTLD
Facebook helps Tor's hidden sites get official recognition — Today the Tor Project and Facebook announced that .onion web addresses …
Context & Ripple Effects
The move caps a rapid institutionalization of .onion: weeks earlier, ICANN parent IANA had officially recognized the .onion TLD, giving Tor domains basic security features like TLS certificates. What changed with the IETF designation is ownership — a special-use reservation takes .onion out of ICANN's auction pipeline entirely.
It also reflects Facebook's growing stake in Tor access: within months the company would report a million users reaching it over Tor in 30 days and ship an Android path through Orbot, making .onion infrastructure something a major platform depends on rather than an anonymity niche.
First-order effects
- ICANN is barred from ever selling .onion as a gTLD, removing the risk that a private buyer could control the root of every hidden service address.
- Operators of Tor hidden services gain durable legitimacy for their namespace, building on the certificate support that followed the IANA recognition.
Second-order effects
- Big-platform adoption becomes the proof case: Facebook's million-user Tor traffic and later Twitter's launch of its own onion service show mainstream sites treating .onion as production infrastructure, not an experiment.
Third-order effects
- The special-use designation sets a governance template — namespaces serving security purposes can be reserved at the IETF rather than contested in ICANN's commercial process — though sustaining them depends on operator commitment, as Twitter's lapsed certificate killing its onion service later demonstrated.
The trend: Internet namespace governance is splitting between ICANN's market-based allocation and IETF special-use reservations for security-critical domains like .onion.