vpn_lock I2P Setup Guide

The Invisible Internet Project — a different kind of anonymous network. Harder to set up than Tor, but worth understanding.

warning The Wild West Disclaimer

I2P is a smaller, more technical network than Tor. The community is tight-knit but the network is essentially unmoderated. Here's what you should know:

It's a peer-to-peer network. Your computer becomes a relay for other people's traffic (encrypted — you can't see it). This is how the network works. If that makes you uncomfortable, I2P may not be for you.
Sites come and go. I2P eepsites are far less stable than Tor hidden services. Expect broken links, slow loads, and sites that worked yesterday but don't today.
The content is uncurated. There is no central authority deciding what's allowed. You will find forums, blogs, file sharing, and communication tools. Some of it is valuable. Some of it isn't. Exercise judgement.
Setup requires patience. Unlike Tor (download, click, browse), I2P needs configuration. Give yourself 15-20 minutes the first time, and expect the network to be slow for the first hour while your router builds tunnels and learns peers.

HyveHeim indexes I2P sites for OSINT and research purposes. We only index known, legitimate sources. But if you venture beyond our indexed content, you're on your own.

What is I2P?

I2P (Invisible Internet Project) is an anonymous overlay network. Unlike Tor, which is designed primarily to access the regular internet anonymously, I2P is built for network-internal communication — services hosted within I2P for I2P users.

Think of it as a parallel internet. Websites on I2P are called eepsites and use .i2p addresses. Traffic is encrypted in multiple layers and routed through a distributed network of volunteer nodes. Every user's computer is both a client and a router.

compare_arrows Tor vs I2P — Quick Comparison

	Tor	I2P
Primary use	Access clearnet anonymously + .onion sites	Network-internal services (.i2p eepsites)
Setup difficulty	Easy (download & click)	Moderate (needs proxy config)
Speed	Slow but usable	Slower initially, improves over time
Network size	~6,000+ relays	~30,000+ routers
Routing	Circuit-based (3 hops)	Packet-based (garlic routing)
Your role	Client only (by default)	Client + relay (always)

Option A: i2pd (Recommended)

i2pd is a lightweight C++ implementation of I2P. Smaller, faster, fewer dependencies than the Java version. This is what we recommend.

1 Install i2pd

Windows: Download the installer from i2pd.website. Run it. Done.

macOS: brew install i2pd

Linux (Debian/Ubuntu):

sudo apt install i2pd

Linux (Arch): sudo pacman -S i2pd

Linux (Fedora): sudo dnf install i2pd

2 Start i2pd

Windows: It starts automatically as a service after installation.

Linux: sudo systemctl start i2pd && sudo systemctl enable i2pd

macOS: brew services start i2pd

Give it 5-10 minutes to bootstrap. It needs to discover peers and build tunnels. The first launch is always the slowest.

You can check the web console at http://127.0.0.1:7070 to see tunnel status and peer count.

3 Configure Your Browser

i2pd runs an HTTP proxy on 127.0.0.1:4444. You need to tell your browser to use it only for .i2p addresses.

Firefox (easiest):

Go to Settings → Network Settings → Settings
Select "Manual proxy configuration"
HTTP Proxy: 127.0.0.1, Port: 4444
Check "Also use this proxy for HTTPS"
No Proxy for: leave your regular domains here if you want split routing

Better option — use a separate browser profile:

Run firefox -P to create a new profile called "I2P"
Set the proxy only in that profile
Use your normal browser for clearnet, the I2P profile for eepsites

Even better — FoxyProxy extension:

Install FoxyProxy in Firefox
Add a proxy rule: pattern *.i2p → HTTP proxy 127.0.0.1:4444
This automatically routes only .i2p traffic through I2P, everything else goes direct

4 Test It

Once i2pd is running and your browser is configured, try these eepsites:

stats.i2p — I2P network statistics
zzz.i2p — I2P developer forum
notbob.i2p — Directory of I2P eepsites
legwork.i2p — I2P search engine

If they load (even slowly), you're connected. If not, wait longer — I2P needs time to build tunnels. Check http://127.0.0.1:7070 and look for "Active tunnels" > 0.

Option B: Java I2P (Original)

The original I2P implementation in Java. More features (built-in BitTorrent, email, IRC), but heavier. Requires Java runtime.

download Java I2P geti2p.net/en/download package_2 Easy Install Bundle Includes Java + browser profile

Java I2P includes a web console at http://127.0.0.1:7657 with a built-in address book, tunnel manager, and more. It's the full experience, but we recommend i2pd for most users.

shield Staying Safe on I2P

Use a separate browser profile. Don't mix I2P browsing with your regular browsing. Cookies, history, and fingerprints can link your identities.
Disable JavaScript for untrusted sites. Use NoScript or set browser security to strict. JS can leak your real IP through WebRTC or other APIs.
Don't share personal information. The network is anonymous. Keep it that way. No real names, no personal emails, no social media links.
Expect slow speeds. I2P prioritises anonymity over speed. Large downloads will be slow. Streaming is generally not practical.
Keep i2pd/I2P updated. Security patches matter. Run the latest version.
Be aware you're relaying. Your node routes other people's traffic (encrypted). This is normal and by design. You can't see or control what's in the encrypted packets.
Don't run exit tunnels unless you know what you're doing. Exit tunnels let I2P users access the clearnet through your IP. Most users should not enable this.
Verify .i2p addresses carefully. There's no certificate authority on I2P. Phishing eepsites exist. Bookmark trusted addresses.

Troubleshooting

Nothing loads after installing?

I2P takes 5-15 minutes to bootstrap on first launch. Check the web console (127.0.0.1:7070 for i2pd, 127.0.0.1:7657 for Java I2P). Look for active tunnels and known peers > 0. If still nothing after 20 minutes, check your firewall isn't blocking UDP traffic.

Pages load but very slowly?

Normal for the first hour. I2P gets faster as your router integrates into the network and builds more tunnels. Leave it running — it improves over time. After a few hours, speeds should be reasonable for text-based content.

"Host not found" errors?

The eepsite might be down (common on I2P) or your address book doesn't have the entry. For i2pd, try accessing via the full base32 address instead of the human-readable .i2p name. For Java I2P, check the Susidns address book at 127.0.0.1:7657/susidns/.

Can't access I2P from behind a strict firewall?

I2P uses UDP by default. If UDP is blocked, enable NTCP2 (TCP) in your router settings. For i2pd, add ntcp2.enabled = true to the config. Corporate firewalls may still block it — in that case, consider using Tor with bridges instead.

Back to HyveHeim Search · Tor Browser Guide