The .onion, much more than the "dark web"

When we talk about .onion sites, we immediately think of illegal marketplaces and clandestine forums. However, many legitimate organizations — BBC, New York Times, ProPublica, Facebook, Deutsche Welle — have deployed their own onion services. The goal is not to hide but to offer their users guarantees of privacy and security that the traditional web cannot provide.

Here are the main reasons why a site operator may legitimately wish to make their service accessible via Tor.


1. Free end-to-end encryption

One of the major advantages of onion services is the full encryption of traffic, from the client to the host. As the Tor Project explains in its official documentation:

"Onion service traffic is encrypted from the client to the onion host. This is like getting strong SSL/HTTPS for free."

Unlike traditional HTTPS, where an intermediate node can theoretically intercept or redirect traffic (man-in-the-middle attacks, DNS poisoning), the onion protocol ensures that traffic remains encrypted throughout the chain, without break points.

2. Native cryptographic key authentication

The .onion address itself is derived from the service's public key. This means that when a user connects to an onion address, they have the cryptographic guarantee that the server at the end of the connection is indeed the one that possesses the corresponding private key.

"When a user visits a particular onion, they know that the content they are seeing can only come from that particular onion. No impersonation is possible." — Tor Project

Gone are the days of DNS spoofing attacks, fraudulent SSL certificates, or malicious redirections: the identity of the service is embedded in its address.

3. Masking the server's IP address

An onion service does not have a publicly accessible IP address. The protocol works as an overlay network above TCP/IP, and IP addresses are simply not used in the protocol. The server only connects outbound (outgoing connections only), making it invisible from the outside.

This property is valuable for:

  • Investigative journalism organizations (via SecureDrop) that gather anonymous leaks;
  • Victim support platforms;
  • Internal business services accessible remotely without exposing infrastructure.

4. Bypassing censorship

This is the reason that prompted the BBC to launch its Tor mirror in October 2019. In countries like China, Iran, or Vietnam, access to the BBC site is regularly blocked. The .onion mirror allows internet users in these countries to bypass national filtering.

"The BBC World Service's news content is now available on the Tor network to audiences who live in countries where BBC News is being blocked or restricted." — BBC News

Access via Tor not only masks the user's identity but also the nature of the site visited, making blocking much more difficult for a state.

5. NAT traversal without port opening

Onion services do not need open ports on the firewall. They only establish outbound connections, allowing them to "traverse" NAT (Network Address Translation). This is a major technical advantage for servers hosted in restricted environments: university campuses, corporate networks, airports, etc.

6. Offloading Tor exit nodes

When a Tor user visits a regular HTTP site, their traffic exits through an exit node, which has limited bandwidth. By offering a .onion service, the traffic remains entirely within the Tor network, without passing through an exit node. As Professor Steven Murdoch (University College London) noted during the launch of the BBC mirror:

"Onion services take load off scarce exit nodes, preserve end-to-end encryption [and] the self-authenticating domain name resists spoofing."

This improves performance for Tor users and reduces the load on the network's volunteer infrastructure.


Who should consider a .onion service?

Use case Main benefit
Media (BBC, NYT, DW) Bypassing censorship, access for surveilled populations
Reporting platforms (SecureDrop) Source anonymity, protection for whistleblowers
Support services (hotlines, NGOs) Protection for vulnerable users
Businesses (remote access, internal dashboards) IP masking, no open port, native authentication
Messaging/email sites Traffic privacy, resistance to interception

Limitations and precautions

Deploying an onion service does not exempt one from good security practices:

  • Key management: the service's private key is its identity. If it is compromised, the service must be recreated with a new address.
  • Server hardening: the underlying server must remain secure (updates, isolation, segmentation).
  • OpSec: a misconfigured onion service can leak information about the infrastructure (logs, headers, errors).
  • Reputation: association with Tor may raise questions, hence the importance of clearly communicating the reasons for deployment.

Conclusion

Far from being reserved for criminal dark web activities, the .onion protocol offers a set of security properties — end-to-end encryption, cryptographic authentication, IP masking, resistance to censorship — that increasingly interest legitimate organizations. With players like the BBC and the New York Times leading the way, the deployment of onion mirrors is part of a commitment to protecting users and defending access to information.