Distributed web experimental server of the WebCookies.org project

WebCookies.org is a popular web privacy and security provider, and we're very much into the innovation of decentralised web, blockchain and other privacy-protecting technologies.

This server offers a number of privacy-friendly protocols for Web 3.0, which is all about decentralization, both in terms of hosting and controls. If you're interested in decentralized social media check The Federation. If you're a webmaster, check So you want to decentralize your website.

SSB (Secure Scuttlebutt)

The SSB (Secure ScuttleButt) is a secure decentralized message exchange protocol that allows both public posting as well as private messaging. The biggest application built on top of SSB is currently PatchWork.

  1. Install PatchWork
  2. Use the following "invitation" code to join the network through this server, or use any other public pub.

SSB is fully peer-to-peer protocol and does not use central servers, but it needs an existing node to bootstrap and discover other nodes in network. Pubs are long-running, stable SSB nodes whose only purpose is to facilitate this initial contact.

DAT protocol

The dat:// protocol allows secure, decentralized file storage with the biggest application being web publishing without a central server. DAT ecosystem can be accessed using a Chrome-based Beaker Browser on most systems and Bunsen for Android. You can access these URLs if using one of them:

Actually, this website runs from dat:// — I'm writing this text in Beaker Browser built-in HTML editor on my laptop and when I save, all P2P nodes in the DAT network will pick the changes almost instantly. If you view this website in Beaker Browser as dat://ssb.webcookies.pub/, your browser will too.

Behind the traditional HTTP-accessible https://ssb.webcookies.pub/ website sits a little DAT-to-HTTP gateway (homebase) which publishes the code as a regular HTTP website.

As a file storage and distribution protocol, DAT cannot publish fully dynamic websites, but it can perfectly well store HTML, CSS and JavaScript files, which allows creation of pretty sophisticated web applications as long as they can be self-contained.

Using the DAT hostname addresses is part of the protocol: the browser first attempts to fetch hint file https://ssb.webcookies.pub/.well-known/dat which simply points it to the actual DAT address.


IPFS (InterPlanetary File System) is a decentralized file storage protocol and network, very much like DAT. IPFS offers more services than just file storage (which DAT does very well), including name services and integration with blockchain-based ENS (Ethereum Name Service) which makes is popular for Web3 blockchain-based web applications.

While IPFS is primarily file storage, it can be also used to host static websites (pretty much as DAT). Brave Browser comes with built-in support for IPFS and ENS (see below).

Because we use IPFS technique called DNSLink, you can actually use the shortest possible address of /ipns/webcookies.pub (try). Behind the scenes, this is implemented by a simple _dnslink.webcookies.pub TXT DNS record which points to the full "bafy..." address above.


ENS (Ethereum Name Service) is a DNS-like but fully decentralized and blockchain-based name service, especially popular among Web3 blockchain-based web applications. ENS offers an unique .eth top-level domain that is resolved entirely in decentralized manner using Ethereum smart contracts (registration costs pennies). ENS names can be resolved using popular MetaMask extension for popular browsers and comes built into Brave Browser.

As you can see, internally the webcookies.eth domain resolves to the same IPFS address as listed above, so the whole path is decentralized.


This server is also available on the Yggdrasil, a decentralised and self-organising, encrypted overlay network. Yggdrasil provides a VPN-like worldwide flat network subnet with its own unique IPv6-based addressing. If you're on Yggdrasil, you can connect to services on this node using the y.webcookies.pub hostname which resolves to Yggdrasil address. For example:

  • HTTP http://y.webcookies.pub/
  • IPFS /ip6/204:6a75:ab97:544f:4a03:7a9:ac33:93d5/tcp/4001/ipfs/QmdevXZDDRizS1SgCw73rHXMR55jxNECqCQBiVZHNh16KL

All other services on this node (SSB, IPFS, HTTP, DAT) are in principle available over Yggdrasil too, you just need to use y.webcookies.pub as target. Connections to SSB however do not work until bug #49 in SSB is resolved.


If you access this website in Tor Browser, your requests never goes onto the public Internet either — we run a Tor hidden service here too. Not to hide our server, but to hide your traffic.Our "regular" Internet server uses Alt-Svc header to hint Tor Browser how to find this website on Tor automatically.

You can also use the onion3 address directly in Tor Browser:


I'm an application and infrastructure security consultant living in the UK. I'm on Mastodon kravietz, SSB (@kravietz) and Twitter kravietz2.

To contact me privately: