Examples of the Dark Web

Discover specific examples of dark web sites, such as illicit marketplaces and privacy-focused forums, and understand their functions.

First published: | Revised: 2026-11-02 | Written by: Eliot Mercer

News Outlets and Whistleblower Platforms

Several major news organizations and whistleblower platforms utilize .onion services to enhance privacy and circumvent censorship. These platforms allow users to access information and submit tips anonymously.

ProPublica was the first significant mainstream news outlet to launch a Tor hidden service in January 2016. This initiative aimed to protect user metadata and reading privacy, making it easier for whistleblowers to share sensitive information without fear of surveillance (1). ProPublica uses SecureDrop, a secure platform for anonymous communication, allowing sources to send documents and messages directly to journalists. SecureDrop employs end-to-end encryption, ensuring that both the source and the journalist remain anonymous (4).

The BBC also launched its .onion site in October 2019, providing access to news in regions with stringent state controls, such as China and Iran. This site helps users bypass censorship and access reliable information without revealing their identity (2).

Both ProPublica and the BBC take advantage of the unique architecture of Tor. Unlike conventional web services, .onion connections do not depend on exit nodes. The entire data transfer occurs within the Tor network, which enhances security and anonymity (5).

For those interested in exploring these platforms, here are some notable features:

  • ProPublica: Offers a Tor hidden service for secure news access and anonymous tips.

  • BBC: Provides a .onion site for accessing international news in censored regions.

  • SecureDrop: Enables anonymous file transmission between sources and journalists.

These platforms exemplify how journalists and whistleblowers leverage Tor to protect their identities and ensure the flow of information in restrictive environments.

Search Engines and Directory Services

Finding .onion services requires specialized search engines and directory services designed for the Tor network. These tools index hidden services, making them accessible to users. Here are some notable options:

  • Ahmia: A search engine that indexes .onion sites while filtering out illegal content. It provides a user-friendly interface and is accessible via both Tor and clearnet.

  • Torch: One of the oldest search engines for .onion sites, Torch allows users to search for content on the hidden web. It has a simple search functionality and indexes a wide range of services.

  • Not Evil: A search engine that emphasizes user privacy. It indexes .onion sites and does not track user activity while searching.

Indexing on the hidden network differs from traditional web indexing. Tor-specific crawlers like Torch and Ahmia navigate the network through a process that respects user anonymity. They do not rely on exit nodes, ensuring that the entire indexing process occurs within the Tor network (5). This method helps to maintain the privacy of both the users and the indexed services.

The architecture of Tor uses a unique address structure for onion services. The current v3 onion addresses consist of a 56-character string, derived from the service's Ed25519 identity public key (6). This cryptographic approach enhances security and makes it difficult for malicious actors to identify or target these services.

Directory authorities play a critical role in the Tor network. They maintain a list of active onion services, helping users connect to these services without exposing their identities. The connection circuit for an onion service consists of six relays, ensuring mutual location privacy during data transfer (6).

Using these search engines and understanding the indexing process can help users navigate the hidden web more effectively. For additional resources, consider exploring the List of Dark Web Sites for verified .onion services.

Privacy-Focused Communication and Mail Services

Encrypted messaging and email services play a crucial role in maintaining user privacy on the dark web. These services utilize the Tor network to protect metadata and ensure secure communication. Here are some notable examples:

ProtonMail

ProtonMail provides a secure email service with an onion endpoint. Users can access it via the Tor network, which enhances anonymity. ProtonMail employs end-to-end encryption, meaning only the sender and recipient can read the messages. The service does not store IP addresses, further protecting user identities. The onion site allows users in regions with strict surveillance to communicate without fear of interception.

Riseup

Riseup offers email and communication services that prioritize privacy and security. Their onion service provides users with an alternative way to access their accounts anonymously. Riseup is particularly popular among activists and journalists, as it allows for secure communication without compromising user data. They also emphasize the importance of protecting metadata, which is often overlooked in traditional email services.

SecureDrop

While primarily a whistleblower platform, SecureDrop also facilitates encrypted communications. It allows sources to submit documents and messages anonymously to journalists. SecureDrop operates on .onion services, ensuring that both parties remain hidden from surveillance. This tool is essential for those looking to share sensitive information securely.

Key Features of Privacy-Focused Services

  • End-to-end encryption: Protects the content of messages from unauthorized access.

  • Onion endpoints: Provide access via the Tor network, enhancing anonymity.

  • No IP logging: Services like ProtonMail do not store user IP addresses, further protecting identities.

  • Metadata protection: Focus on minimizing metadata exposure, which can reveal user behavior and identities.

These privacy-focused communication services demonstrate how users can maintain their anonymity while exchanging sensitive information. Utilizing these tools can significantly enhance security for those operating in environments where privacy is paramount.

Public Metric Dashboards and Network Health Nodes

Monitoring tools are essential for understanding the health and performance of the Tor network. One notable resource is Tor Metrics, an official public analytics platform that aggregates various network health data, user estimates, relay status, and onion service traffic statistics. This platform does not compromise user anonymity and provides valuable insights into the functioning of the Tor network (3).

Key Features of Tor Metrics

  • Network Health Data: Provides real-time statistics on the number of active relays, bridges, and users.

  • User Estimates: Offers insights into the estimated number of users accessing the Tor network at any given time.

  • Relay Status: Displays the status of relays, including whether they are operational or down.

  • Onion Service Traffic Statistics: Tracks traffic patterns to onion services, helping administrators optimize performance.

Node Visualization and Relay Telemetry

Tor Metrics includes visualizations that represent the network's structure. Users can explore the geographical distribution of relays and the number of connections each relay handles. This data helps network engineers identify potential bottlenecks and optimize relay performance.

Relay telemetry data is crucial for understanding how well each relay contributes to the overall network. It can show metrics such as bandwidth usage and latency, allowing administrators to make informed decisions about their relay configurations.

Network Consensus Data

The Tor network relies on a consensus mechanism involving directory authorities that maintain lists of active relays. Each relay communicates its status to these authorities, which then disseminate this information to clients. Understanding this consensus data is vital for network engineers who want to ensure reliable connections.

To enhance reliability and protect against attacks, Tor has introduced features such as a built-in proof-of-work mechanism. This mechanism prioritizes client connection requests during network congestion, which is particularly useful during high-traffic periods (7).

For those interested in exploring the metrics available, accessing Tor Metrics can provide a comprehensive overview of network performance and health. Understanding these metrics can significantly improve the management of onion services and ensure optimal user experiences.

Institutional Archives and Open-Access Repositories

Various institutional archives and open-access repositories utilize .onion services to provide access to academic research and data. These resources allow users to bypass regional blocks and censorship, especially in countries with strict information control.

Notable Examples

  • Sci-Hub: A popular repository that provides free access to millions of research papers. It operates through hidden services, enabling users to access academic content without facing regional restrictions.

  • Library Genesis (LibGen): Similar to Sci-Hub, LibGen offers a wide range of academic papers, books, and articles. Its .onion address allows users to circumvent censorship and access materials that may be blocked in their regions.

These platforms leverage the anonymity of Tor to facilitate access to knowledge that might otherwise be restricted.

How It Works

Onion services use a v3 address structure, enhancing security through cryptographic measures. Each service has a unique 56-character string derived from its identity public key (6). This structure ensures that accessing these repositories remains anonymous and secure.

Using these services typically involves navigating to their .onion addresses via the Tor browser. Once connected, users can search for and download academic papers directly. The browsing experience is similar to traditional academic databases, but with added privacy protections.

Benefits of Using .onion Services for Research

  1. Censorship Bypass: Users in restrictive environments can access valuable academic resources without fear of surveillance.

  2. Anonymity: The Tor network ensures user identities are protected during access, which is particularly valuable for researchers in sensitive fields.

  3. Access to Unavailable Content: Many academic papers and books are behind paywalls. .onion services provide alternative access points to this content.

Considerations

While these services provide significant benefits, users should be aware of potential legal implications. Accessing certain materials may violate copyright laws in some jurisdictions. Always ensure compliance with local regulations when using such platforms.

For further exploration of hidden services, consider checking the List of Dark Web Sites for verified academic resources available through .onion addresses.

Technical Architecture of .Onion Hidden Services

Onion services leverage a unique technical architecture to establish secure connections while maintaining user anonymity. This architecture primarily utilizes distributed hash tables (DHT) and introduction points. Here’s how it works.

Connection Establishment

  1. Introduction Points: Each onion service selects one or more introduction points within the Tor network. These are regular Tor relays that act as intermediaries for incoming connections. The service shares its introduction points with clients through a directory authority without revealing its actual IP address.

  2. Client Connection: When a client wants to connect to an onion service, it creates a hidden service descriptor. This descriptor includes the introduction point information and is published to the directory authority. The client retrieves this descriptor and establishes a connection to the introduction point.

  3. Rendezvous Point: The connection process involves a rendezvous point, which is another relay in the Tor network. The client and the onion service both create circuits to this rendezvous point, ensuring that neither party knows the other's IP address. This layer of abstraction protects both users and services from network reconnaissance.

Circuit Configuration

The complete connection circuit for an onion service comprises six relays: three selected by the client and three by the service. This configuration meets at the rendezvous point, ensuring mutual location privacy during data transfer (6). The entire communication remains within the Tor network, eliminating reliance on exit nodes, which enhances security (5).

Security Features

  • v3 Onion Addresses: The latest onion services utilize a v3 address structure, consisting of a 56-character string derived from the service's Ed25519 identity public key. This cryptographic design enhances security and mitigates risks associated with previous v2 addresses, which had known vulnerabilities (6).

  • DDoS Protection: To safeguard against volumetric Distributed Denial of Service (DDoS) attacks, Tor 0.4.8 introduced a built-in proof-of-work mechanism. This prioritizes legitimate client requests during periods of network congestion (7).

  • Backend Communication: Security engineering guidelines recommend using UNIX sockets instead of TCP connections for backend communication. This practice reduces local attack surfaces and enhances overall security (8).

Understanding these technical aspects of .onion hidden services is crucial for system administrators and network engineers who manage or utilize onion services. The architecture not only provides anonymity but also ensures robust security measures are in place for both users and service providers.

Protocol-Level Risks in Network Reconnaissance

Onion services, while providing anonymity, can expose several technical vulnerabilities and configuration errors during deployment. Understanding these risks is essential for maintaining the integrity and security of your onion services.

Clock Skew

Clock skew refers to discrepancies in time settings between servers and clients. This misalignment can lead to issues in cryptographic protocols that rely on timestamps. For example, if a server's clock is ahead or behind by several minutes, it may reject legitimate connections, causing service outages. Regularly synchronize server clocks using Network Time Protocol (NTP) to mitigate this issue.

Weak RSA/Ed25519 Keys

Using weak cryptographic keys can compromise the security of onion services. For instance, RSA keys that are less than 2048 bits or poorly generated Ed25519 keys can be vulnerable to brute-force attacks. Ensure that your keys are generated using strong cryptographic libraries and adhere to recommended key lengths for maximum security. Regular audits of key strength can help identify and replace weak keys before they are exploited.

Server-Side Script Leaks

Server-side scripts can inadvertently expose sensitive information if not properly configured. For example, misconfigured web servers may allow access to files containing database credentials or debugging information. Use strict access controls and regularly review server configurations. Implementing security best practices, such as disabling directory listings and using environment variables for sensitive information, will help prevent these leaks.

Recommendations for Secure Deployment

  1. Regular Security Audits: Conduct periodic audits of your onion service configurations and code to identify vulnerabilities.

  2. Use Strong Cryptography: Always employ robust cryptographic practices, including strong key generation and secure protocols.

  3. Monitor Logs: Regularly check server logs for unusual access patterns that may indicate reconnaissance activities.

  4. Implement Best Practices: Follow security engineering guidelines, such as using UNIX sockets for backend communications, to reduce the attack surface (8).

By addressing these protocol-level risks, you can enhance the security of your onion services and protect against potential threats during network reconnaissance.

Technical Comparison of v2 vs v3 Onion Services

Featurev2 Onion Servicesv3 Onion ServicesExample Services
Address StructureLegacy 16-character56-character from Ed25519 keyBBC, ProPublica
SecurityKnown vulnerabilitiesEnhanced cryptographic measuresSci-Hub, LibGen
Connection MethodRelies on exit nodesNo exit nodes; internal networkOnion Balance
DDoS ProtectionNoneBuilt-in proof-of-workN/A
Backend CommunicationTCP connectionsUNIX sockets recommendedN/A
Circuit ConfigurationLess secureSix relays for privacyN/A

Conclusions

  • Implement v3 onion addresses with 56-character strings to secure your infrastructure against legacy vulnerabilities.

  • Configure UNIX sockets for backend communications to reduce local attack surfaces.

  • Synchronize server clocks regularly using Network Time Protocol to prevent cryptographic timestamp mismatches.

  • Audit your cryptographic keys and enforce strict server-side access controls to block script leaks.

Review the Topic Links 3.0 Onion guide to deepen your understanding of modern hidden service architectures.

Explore More Dark Web Resources

Discover additional insights and examples on our site.

View More Articles