Voidly Community Probe — Help measure internet censorship worldwide
Project description
Voidly Community Probe
Help measure internet censorship worldwide. Run a lightweight probe node from anywhere.
What it does
Tests connectivity to 62 websites (social media, news, messaging, privacy tools, human rights organizations) every 15 minutes from your network. Detects:
- DNS blocking — NXDOMAIN, DNS poisoning (compared against Cloudflare DoH)
- TCP resets — connection reset by peer
- TLS/SNI filtering — Server Name Indication based blocking
- HTTP redirects — government/ISP redirect to block pages
- Block page fingerprinting — identifies 13 known blocking entities
Results feed into Voidly's censorship intelligence network — a real-time global censorship dataset used by researchers, journalists, and developers.
Install
pip install voidly-probe
Requirements: Python 3.8+ · No external dependencies (stdlib only) · No root required · No VPN
Quick start
# First run — review consent and register
voidly-probe --consent
# Run continuously (default: every 15 minutes)
voidly-probe
# Single test cycle then exit
voidly-probe --once
# Check your node's status
voidly-probe --status
# Custom interval (minimum 300s / 5 min)
voidly-probe --interval 600
# Run in background (Linux/Mac)
nohup voidly-probe --consent &
# Stop contributing and remove config
voidly-probe --unregister
Docker
# Run in background with persistent config
docker run -d --name voidly-probe \
-v voidly-data:/data/.voidly \
emperormew2/voidly-probe:latest
# View logs
docker logs -f voidly-probe
# Check node status
docker exec voidly-probe voidly-probe --status
# Find your Node ID (for claiming)
docker exec voidly-probe cat /data/.voidly/node.json
# Stop
docker stop voidly-probe
The Docker image auto-consents and starts probing immediately. Config persists across restarts via the volume mount.
Claim your node
After your node is running, link your identity to appear on the leaderboard and be eligible for prizes:
- Find your Node ID and Token:
cat ~/.voidly/node.json - Visit voidly.ai/probes/claim
- Enter your Node ID, Token, and Twitter/X handle
- Your name appears on the leaderboard instead of
cp-xxxxxxxx
Important: Back up
~/.voidly/node.json— your token is shown once during registration and cannot be recovered. If you lose it, you'll need to re-register as a new node.
How it works
┌─────────────┐ ┌──────────────┐ ┌─────────────────┐
│ Your Node │────▶│ api.voidly.ai │────▶│ Voidly Dataset │
│ (probe) │ │ (HMAC auth) │ │ (CC BY 4.0) │
└─────────────┘ └──────────────┘ └─────────────────┘
│ │
│ Tests 62 domains: │ Powers:
│ DNS · HTTP · TLS · SNI │ voidly.ai/probes
│ every 15 min │ Censorship Index
│ │ MCP Server
└───────────────────────────────────────────┘
Each probe cycle:
- DNS resolution — checks if the domain resolves, compares against DoH
- HTTP/HTTPS request — tests connectivity, checks for redirects
- Block page detection — fingerprints known government/ISP block pages
- TLS/SNI probing — tests for SNI-based filtering
- Certificate fingerprinting — detects MITM certificate injection
- Results signed with HMAC-SHA256 and reported to the API
Failed submissions are cached locally and retried next cycle — no data loss even with spotty connectivity.
Configuration
Environment variables:
| Variable | Default | Description |
|---|---|---|
VOIDLY_PROBE_INTERVAL |
900 |
Seconds between probe cycles |
VOIDLY_PROBE_TIMEOUT |
10 |
Timeout per request (seconds) |
VOIDLY_BATCH_SIZE |
20 |
Domains per cycle |
VOIDLY_CONFIG_DIR |
~/.voidly |
Config directory |
VOIDLY_API_URL |
https://api.voidly.ai |
API endpoint (for development) |
Privacy
What we collect
- Domain, blocked/accessible status, latency, blocking method
- Your approximate location (country, city) — detected once during registration
- SHA256 hash of your IP (for deduplication — raw IP never stored)
What we don't collect
- No browsing data
- No passwords or personal information
- No traffic inspection beyond the 62 test domains
- Your raw IP address is never stored
Your rights
- Stop the probe at any time with Ctrl+C
- Run
voidly-probe --unregisterto remove your config - Data is used for censorship research under CC BY 4.0
- Learn more: voidly.ai/probes
Contributing
Found a bug? Have a suggestion? Open an issue.
License
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file voidly_probe-1.0.8.tar.gz.
File metadata
- Download URL: voidly_probe-1.0.8.tar.gz
- Upload date:
- Size: 15.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.10.1
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
eead0fae3fb8138f5af463ab6141e8c61186256731c920f3376823f77f39b5ee
|
|
| MD5 |
483db0b30891dbb5336aacda01479723
|
|
| BLAKE2b-256 |
2c5c41fde5cf2f555e812655f05470bd3088e7e8b3f8dd470e44a70dc3af4304
|
File details
Details for the file voidly_probe-1.0.8-py3-none-any.whl.
File metadata
- Download URL: voidly_probe-1.0.8-py3-none-any.whl
- Upload date:
- Size: 16.1 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.10.1
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
06da157c6411ab0cb55eac7e640a697ff7d0c0a82c6969ef149f892b13c199a8
|
|
| MD5 |
6f062134238a4276aee1030f3c1c2f3c
|
|
| BLAKE2b-256 |
c6a82e72b8a1a4afbc7bb063b42e2183d978aae6c3f755c47792b7d2f8969895
|