ahmia-site VS onionscan

go to ahmia.fi and search something up but don't click a honeypot website ;)

If you want to play around with a Dark Web search engine, I suggest ahmia.fi which I used as an OSINT analyst.

ahmia.fi on tor

Step 1: Go to https://torproject.org Step 2: Install Tor Browser on your operating system Step 3: Launch Tor Browser and connect into the network Step 4: Access a site like Facebook to click on it's hidden service which redirects you to the site as a .onion or simply use a search engine dedicated to darknet sites like https://ahmia.fi or https://vormweb.de/en and search with common and harmless terms.

For hidden services it's nearly the same. To find some, start with search engines like Ahmia (https://ahmia.fi) or VormWeb (https://vormweb.de/en)

Ahmia is available on the surface web and supports searches on the i2p network as well. You can visit Ahmia’s .Onion domain here.

Download tor browser, go to ahmia.fi and search from there. has all the results.

As for a proper nginx configuration, that's at least a day or four's research to get exactly right. The basic idea is disable everything you don't need, and only ever accept connections from the localhost, but the specifics are grand, especially with fancy servers like nginx. Read everything you can find about how nginx servers are configured. Then, when you think you're done, go read about https://github.com/s-rah/onionscan, use it, and clean up any issues you missed.

You have unfortunately mis-interpreted the "Use SSL to connect to target" option. It's an easy mistake to make, what it's referring to is the connection from the client at the end of the tunnel to the "target" i.e. the HTTPS server. It's used for situations which have a site with a clearnet presence where you want to offer an I2P gateway, but don't want to put that gateway on the same server as the I2P router. So the proxy is doing the SSL connection, and not necessarily the browser. To see an example of how it can be used in this fashion, have a look at: https://mirror-github-pages-to-i2p.github.io In order to be able do HTTPS on your I2P site it's a little more complicated, I don't know that we have native support for it with the default i2ptunnel. sam-forwarder(the Go i2ptunnel) has it, and I can do a tutorial/writeup of how to use it soon. Most importantly have a look at https://github.com/s-rah/onionscan and related work before deploying http/2 and http/3, there is probably a safe way to do it but there is a reason our defaults in the Jetty server are very cautious.

See OnionScan for more details of common mistakes: https://github.com/s-rah/onionscan/blob/da42865bb5b1a77df6d7a6fa212a86eeff814b61/doc/what-is-scanned-for.md