The J3di network limits each IP address to 5 concurrent connections (or "sessions").
This is quite a high limit; most networks limit clients to 2 or 3 connections per IP.
If the limit is abused, the limit for that IP (or ISP) will be reduced.
There are several measures in place to ensure the security of the network as a whole, its individual servers and all the connected users.
- We check all connecting clients against various DNS RBLs (DNS Realtime Block Lists). If found, the client is forcefully disconnected and their IP address is banned.
- On connection, users hostnames (or IP addresses) are "cloaked".
- For example, 12-34-56-78.some.isp.com becomes j3di-a7b8c9d0.some.isp.com.
- An IP address without a PTR record (reverse DNS), such as 18.104.22.168 would become j3di-a6q.wmr.22.11.IP
- All passwords are encrypted using a secure, non-reversible cryptographic hashing method (SHA1)
- SSL is supported by each server. The servers use a common "wildcard" certificate, signed by CACert.
- All servers are linked to each other using encrypted connections.