Several GitHub repositories collect and curate onion site addresses with different verification approaches. For mainstream services with proof, check pred2k/onion-sites at https://github.com/pred2k/onion-sites/blob/master/README.md, which includes verification links from official clearnet sources like bbc.com and torproject.org (1). For PGP-verified contributions, oniontree-org/oniontree at https://github.com/oniontree-org/oniontree requires all submissions to be signed with contributor's PGP key (2). If you need substantial commercial or social-good sites with 10,000+ users, visit alecmuffett/real-world-onion-sites at https://github.com/alecmuffett/real-world-onion-sites/ (3). For categorized lists including search engines, see praveenjalasutram/Darkweb-Onion-Links at https://github.com/praveenjalasutram/Darkweb-Onion-Links (4). Manual verification by users remains the standard approach for checking onion addresses (5).
GitHub Repositories for Onion Site Collections
oniontree-org/oniontree (69 stars, 14 forks) requires all contributions to be verified for authenticity and signed with contributor's PGP key (2). This cryptographic requirement means each address includes a signature linking it to a specific contributor. You can verify signatures yourself if you have the contributor's public key.
pred2k/onion-sites includes proof links from official clearnet sources (1). BBC News onion address references bbc.com and torproject, while The New York Times onion address cites open.nytimes.com and blog.torproject.org (1). Follow these proof links to confirm organizations published addresses on official websites.
alecmuffett/real-world-onion-sites focuses on substantial commercial or social-good mainstream websites with 10,000+ users, excluding onion-only sites and smaller services (3). Licensed under cc-by-sa, this repository prioritizes established organizations over experimental services (3). You'll find major news outlets, social platforms, and privacy tools rather than niche communities.
matronator/awesome-darknet provides a curated list with PGP verification (6). The repository includes a disclaimer that PGP verification doesn't mean sites are 100% safe and the author did not test most sites or make purchases (6). This transparency shows what the repository guarantees and what it doesn't.
praveenjalasutram/Darkweb-Onion-Links organizes addresses by categories including Search Engines with entries for Ahmia, Deep Search, and Torch (4). Category organization helps when you need specific service types rather than browsing all addresses.
Star count indicates how many users bookmarked a repository. Higher stars suggest community interest but don't verify address accuracy or safety. Fork count shows how many users copied the repository to their own account, often to contribute changes or maintain personal versions.
Verification Methods in GitHub Onion Collections
oniontree-org/oniontree requires all contributions to be verified for authenticity and signed with contributor's PGP key (2). Each address addition includes a cryptographic signature proving a specific contributor approved it. This doesn't verify the onion address itself is legitimate, only that a contributor vouched for it.
pred2k/onion-sites includes proof links from official clearnet sources like bbc.com, torproject.org, open.nytimes.com, and blog.torproject.org (1). You can follow these links to confirm organizations published onion addresses on their official websites. This cross-referencing approach lets you verify against known sources.
matronator/awesome-darknet uses PGP verification with a disclaimer that verification doesn't guarantee 100% safety (6). The author states they did not test most sites or make purchases (6). This verifies cryptographic signatures but doesn't confirm current operational status or content safety.
Manual verification by users is the standard approach for checking whether an onion address is correct for a given service, except when Onion Discovery protocol is used (5). You're responsible for confirming addresses match official sources, even in curated repositories.
The Tor Project's onionprobe tool can check both onion service descriptor reachability and onion service reachability (7). Descriptor reachability confirms the service published information to the Tor network. Service reachability tests whether you can connect. These checks don't verify legitimacy, only that the service responds.
Step-by-step verification workflow:
Find the onion address in a GitHub repository
Check if the repository documents verification method (PGP signatures, proof links, or other)
If proof links exist, visit the official clearnet website to confirm the organization published that address
If PGP signatures exist, verify the signature against the contributor's public key
Search for the same address in multiple repositories to see if others list it
Use onionprobe to test descriptor and service reachability (7)
Visit the address in Tor Browser and check the onion icon for security indicators
Understanding Onion Service Security Indicators
Tor Browser displays different onion icons in the address bar to indicate security levels (8). A plain onion icon shows either HTTPS with Extended Validation certificate, Domain Validated certificate, or HTTP service (8). This icon means the connection follows expected patterns.
An onion icon with a caution sign indicates HTTPS with a self-signed certificate, an expired certificate, or other security warnings (8). Self-signed certificates are common for onion services because obtaining standard certificates involves cost and complexity. The caution sign alerts you to verify the certificate fingerprint against official sources if the service publishes one.
HTTP connections to onion services are not a security issue because Tor's onion service protocol provides end-to-end encryption by default (8). This differs from regular web browsing where HTTP exposes traffic. The onion protocol encrypts all data between your browser and the service, regardless of whether the service uses HTTPS.
TLS certificates for onion services require manual management with no ACME support as of August 2024, and involve an annual cost for purchasing and renewing certificates (9). When onion services use TLS certificates published on Certificate Transparency Logs, the .onion address becomes publicly known (9). This is acceptable for public sites but removes address obscurity for services that prefer it.
The plain onion icon for HTTP service means you're getting the protocol's built-in encryption (8). The caution sign for self-signed HTTPS means the service added an extra layer but you can't verify the certificate through standard certificate authorities (8). Both scenarios provide encrypted connections; the difference is certificate validation method.
Repository evaluation checklist:
Commit frequency: Active repositories show commits within the last 3 months; dormant repositories may contain outdated addresses
Star/fork ratio: Ratios above 5:1 suggest more users bookmark than contribute; ratios below 3:1 indicate active community participation
Issue resolution: Check closed issues for how maintainers handle reported problems; unresolved issues older than 6 months suggest inactive maintenance
Verification documentation: Repositories should explain their verification method in README; absence suggests no systematic checking
Last address update: Check commit history for when addresses were last added or verified; gaps longer than 6 months increase staleness risk
Contributor diversity: Multiple contributors reduce single-point-of-failure risk; single-contributor repositories depend entirely on one person's diligence
For more community-curated collections, see Onion Links Reddit: Where to Find Trusted Collections.
References
[1] pred2k/onion-sites README.md
[3] alecmuffett/real-world-onion-sites
[4] praveenjalasutram/Darkweb-Onion-Links
[5] Certificates - The Onion Services Ecosystem
[6] matronator/awesome-darknet
[7] Troubleshooting - The Onion Services Ecosystem
Q&A
- What GitHub repositories collect onion site addresses
Several repositories collect onion addresses: oniontree-org/oniontree requires PGP-signed contributions (2), pred2k/onion-sites includes proof links from official clearnet sources like bbc.com and torproject.org (1), alecmuffett/real-world-onion-sites focuses on mainstream sites with 10,000+ users (3), and praveenjalasutram/Darkweb-Onion-Links organizes addresses by categories including search engines (4).
- How do GitHub onion repositories verify link authenticity
Verification methods vary by repository: oniontree-org/oniontree requires all contributions to be signed with contributor's PGP key (2), pred2k/onion-sites provides proof links from official sources like bbc.com and open.nytimes.com (1), and matronator/awesome-darknet uses PGP verification with a disclaimer that it doesn't guarantee 100% safety (6). Manual verification by users remains the standard approach for checking onion addresses (5).
Where to look next
These services are useful starting points for further research. Tools & services.