Skip to main content

Voidly Community Probe — Help measure internet censorship worldwide

Project description

Voidly Community Probe

PyPI Python 3.8+ License: MIT Docker

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:

  1. Find your Node ID and Token: cat ~/.voidly/node.json
  2. Visit voidly.ai/probes/claim
  3. Enter your Node ID, Token, and Twitter/X handle
  4. 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:

  1. DNS resolution — checks if the domain resolves, compares against DoH
  2. HTTP/HTTPS request — tests connectivity, checks for redirects
  3. Block page detection — fingerprints known government/ISP block pages
  4. TLS/SNI probing — tests for SNI-based filtering
  5. Certificate fingerprinting — detects MITM certificate injection
  6. 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 --unregister to 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

MITvoidly.ai

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

voidly_probe-1.0.10-py3-none-any.whl (16.3 kB view details)

Uploaded Python 3

File details

Details for the file voidly_probe-1.0.10-py3-none-any.whl.

File metadata

  • Download URL: voidly_probe-1.0.10-py3-none-any.whl
  • Upload date:
  • Size: 16.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.10.1

File hashes

Hashes for voidly_probe-1.0.10-py3-none-any.whl
Algorithm Hash digest
SHA256 9652590cacc03076bfa2908cb42f83ae2b4eb1d95d32861cb923095fecfd68a3
MD5 1e1b4b6cfad816261cd59e7704cf41a9
BLAKE2b-256 7672ac4ae5130a3d18679d06f987d262f3d220b5000ff1bc19abefe72a232165

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page