Voidly Probes
Your network.
A clearer picture.
Measure what your connection can reach. Contribute observations to the public censorship record—one vantage point at a time.
Measurement traffic is observable. Read the risks before you install. Participation is not a promise of payment.
The network, with its sources.
Nodes are not independent operators. The active-node total requires both core and community counts; incomplete figures are not filled with estimates.
Loading network sources…
Most of this fleet is ours. "Community" here means a node that registered through the public path, not an independent operator: on 2026-08-23 the registry reported 18 community nodes operated by Voidly, 0 confirmed third-party, and 151 unclassified — and unclassified means no evidence either way, not evidence of a volunteer. Of the 39 nodes reporting that day, at least 33 were Voidly hardware. Live figures: api.voidly.ai/v1/probe/network and /v1/community/nodes.
Metric sources and reporting windows
The community registry supplies lifetime probe and block counters. The probe-statistics response is a fallback with its own returned scope; listed-node blocks are explicitly labeled when only leaderboard records are available.
Country coverage combines the core country list with community records seen in the last 24 hours, or uses the whole-fleet statistics response. A network timestamp is not a timestamp for every source.
Add a vantage point.
Start with the risks.
Choose a desktop download or a command-line client. Probing tests the network it runs on; using a VPN changes the observation point unless the client explicitly bypasses that tunnel.
macOS download notes
Signed and notarized by Ai Analytics LLC. If macOS cannot verify the downloaded app, verify its source before deciding whether to allow it in System Settings → Privacy & Security.
Probes connect to the served target list from your network. Your ISP can observe those destinations. Review the full risks and inspect the current list.
Contributions, on the record.
Reported node scores, not verified unique people or payments. Open a profile to inspect its contributions.
Ranked by all-time score.
No entries in this response.
You can still read the participation guide and install a probe.
A measurement.
Not a hidden service.
The probe client makes outbound measurements and submits the results. It does not carry another person’s traffic. Check the client and the served target list before participating.
Understand
Read the target list and operational risks.
Install
Choose the app or a command-line client.
Measure
Test reachability from your own network.
Contribute
Submit observations to the public record.
More perspectives make the record more useful.
Check measured coverage for gaps. Only contribute from a network where you understand the risks and have permission to run measurements. Sparse coverage is not a reason to put yourself at risk.
Read this before you install.
Repeated connections to blocked destinations are observable. Country, city and measurements become public. If you need to be unlinkable, do not run a probe.
Operational risks, publication and stopping
The probe makes ordinary DNS, TLS and HTTP requests. It does not tunnel or obfuscate them. An ISP, a national middlebox or anyone on your local network sees the destinations — including news sites, VPN vendors, Tor and human-rights organisations — and sees them on a fixed schedule, which is itself distinctive. We cannot make that traffic look like anything else, and we do not claim to.
On startup and once a day after that, the probe replaces its built-in list with whatever api.voidly.ai/v1/probe/domains returns. If that fetch fails, the probe falls back to a smaller list baked into the client. So the set of things your connection reaches can change without you upgrading anything. Read that endpoint before installing if the answer matters to you; it is public and needs no key.
The probe is not a relay, a proxy, a VPN or an exit node, and there is no setting that turns it into one. It makes outbound requests to its own target list and reports the results. Nothing another person does on the internet can be attributed to your connection because you ran a probe. That is the one guarantee on this page that is structural rather than a promise.
Every request carries VoidlyProbe/<version> in its User-Agent. We do not disguise the probe. A measurement tool that lies about what it is cannot honestly ask anyone to trust its numbers — but it does mean your traffic is identifiable as measurement traffic, to anyone watching.
In some jurisdictions, running measurement infrastructure or reaching circumvention sites carries legal risk to you, not to us. The probe prints a warning when it registers from CN, IR, KP, TM, ER, RU, SA, CU, SY, MM or BY, but that list is our guess and it is not legal advice. A VPN moves the observation point; it does not remove it — and it also changes what the measurement means, since you are then measuring the VPN's network rather than yours. Assess the risks to you and anyone sharing your connection before deciding to participate.
Your node's country, city and measurements are published openly under CC BY 4.0, and appear on the leaderboard above. Your IP is hashed, never stored raw — but a city plus a timestamped measurement series is not anonymous against someone who already suspects you. If you need to be unlinkable, do not run a probe.
Stop the process and delete ~/.voidly/node.json. Measurements already submitted stay in the public dataset — they are cited research data and we cannot retract them from downstream copies.
Security policy ↗ · Read the source ↗ · security@voidly.ai
Know what you share.
Measurement is not anonymity. Public records can be copied downstream, and a location plus a measurement timeline may identify a node.
Measurement data
- Domain and blocked / accessible result
- Latency and detected blocking method
- Country and city, determined via ipinfo.io
- Hashed IP for deduplication
No browsing-history collection is required for these probe measurements. The configured probe list is not a list of websites you visited.
Read the served target listWhere is my node identity?
The Node ID and token are stored in ~/.voidly/node.json. Do not post that file or share the token. Use the claim page to manage your public profile.
Can I run on a VPS or spare computer?
The download and CLI options above support several environments. Measurements describe the network where that machine runs, not necessarily where you live. Review the source and the host’s rules first.
What happens when I stop?
Stop the probe process to stop new measurements. Previously submitted observations remain in the public dataset and may already have downstream copies.
Follow your measurements into Atlas.
The useful outcome is a better-grounded record. Inspect observations and evidence, not only scores.