History

Changelog

Changes to the node, its configuration and this documentation, newest first. Corrections are logged here rather than quietly edited — if we told you something wrong, you should be able to find out that we did.

2026-08-17 — Documentation corrected and expanded

Correction. Earlier versions of this site described anonymity as a Tox feature and stated that "privacy is the default". That was wrong. Tox is peer-to-peer, and your contacts can see your IP address — the protocol was never designed to hide it. The claim has been removed, and there is now a page explaining precisely what Tox protects and what it does not, including how to route Tox over Tor if you need location privacy.

Anyone who chose Tox on the basis of that claim should re-read the privacy page and reconsider whether it fits what they are protecting against.

Also changed:

• Added a bootstrap setup guide covering qTox, Toxic, Android clients, tox-bootstrapd and the toxcore API.
• Added a technical explanation of how the DHT, bootstrapping and TCP relays work.
• Added this changelog and a status page documenting specifications, uptime expectations and logging policy.
• Documented what this node can observe about visitors, on the homepage and in the policy.
• Corrected a labelling error: the field previously marked "IPv4 Address" contained a hostname. Both values are now listed separately, and IPv6 is honestly marked as unavailable rather than shown as a dash.
• Explained why ports 443 and 3389 are in use, and warned that traffic on 3389 may be flagged by monitoring on managed networks.
• Softened the claim that Tox is "impossible to censor". The DHT is resistant to takedown, but Tox traffic is detectable by deep packet inspection and is actively blocked in several countries.