Anonymous IRC Server VPS Reachable Over Tor

Modern ircd software supports binding to localhost and exposing the IRC port only through Tor as a hidden service. We deploy InspIRCd, UnrealIRCd, and ergo with hardened defaults: TLS only, SASL required, no plaintext fallback. The Tor hidden service is configured separately and never exposed on clearnet. Onion v3 keys are generated on first boot and can be persisted across reinstalls if the operator backs them up.

Services packages, including Anope and Atheme, are deployed alongside the ircd so channels, nicks, and bans persist across restarts. Web clients like Gamja can be reached over a separate onion if operators want browser based access for less technical users.

Many IRC users run a bouncer to maintain a persistent presence. We support ZNC and Soju bouncers on the same VPS as the ircd or on a dedicated bouncer VPS for higher assurance deployments. Bouncers are accessed only over Tor through a separate onion v3, with TLS termination inside the bouncer process itself for end to end protection from any networks the user transits.

The bouncer identity is independent of the AnubizHost account and rotates on user command. Operators of public bouncer services for a community keep operator details opaque to the community while still providing reliable always on presence.

Operating a Tor IRC network for an anonymous community inherits the community's threat model. AnubizHost provides anonymous signup, crypto only billing, and no KYC. The operator's identity is decoupled from the IRC infrastructure on our side. We do not aggregate operator data, we do not share customer identifiers with third parties, and we retain no traffic logs that could be used to correlate IRC sessions with operator activity.

Bitcoin and Monero are accepted on every plan. Romania and Iceland remain the recommended jurisdictions for long term anonymous IRC networks. Operators run networks for years on the same anonymous account.