$ whois rans0m.net

A public XMPP/Jabber server run for the hacker community. No logs, no bullshit.

$ connect

JID format: yourname@rans0m.net

$ clients --recommended

• Gajim Linux / Windows gajim.org
• Dino Linux dino.im
• Conversations Android conversations.im
• Monal iOS / macOS monal-im.org
• Profanity Terminal profanity-im.github.io

$ why --not-otr

OTR is considered legacy. Here's why:

• ✗ No multi-device support. OTR is tied to a single session — if you're logged in on two devices, messages only arrive on one of them.
• ✗ No offline messages. The recipient must be online, otherwise the message is lost. No buffering, no retry.
• ✗ Forward secrecy breaks on reconnect. After every disconnect a new handshake is required — in practice this is often silently skipped or broken.
• ✗ No group chat encryption. OTR only works in 1-to-1 conversations. MUC rooms stay unencrypted.
• ✗ Poor client support. Most modern clients don't ship OTR or only offer it as an unmaintained plugin.

→ Use OMEMO. Double Ratchet, multi-device, offline-capable, actively maintained.

$ services --all

• XMPP Jabber / OMEMO rans0m.net
• Mumble Voice Chat mumble.rans0m.net
• Privatebin Encrypted Pastebin paste.rans0m.net
• Gitea Self-hosted Git git.rans0m.net
• CryptPad Encrypted Docs pad.rans0m.net
• Vaultwarden Password Manager vault.rans0m.net

$ features --list

• ✓ OMEMO End-to-End Encryption
• ✓ OTR Support (legacy)
• ✓ TLS (mandatory)
• ✓ MAM — Message Archive Management
• ✓ MUC — Multi-User Chat
• ✓ In-Band Registration
• ✓ vCard / Avatars
• ✓ HTTP Upload (file transfer)

$ policy

• No message logging on the server.
• No real name or email required.
• Everything is allowed. The only hard line is CSAM — instant ban, no discussion.
• You are responsible for your own actions. Act accordingly.
• Server is operated on a best-effort basis.

$ tor --onion

Full addresses in faq. Requires Tor Browser or Tor-aware client.

$ contact

Questions, abuse reports: admin@rans0m.net