Your network.
A clearer picture.

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.

In continuous mode, the probe fetches the served list on startup and periodically after that (about daily at the default interval), replacing its built-in list with whatever api.voidly.ai/v1/probe/domains returns. If that fetch fails, or you use --once, the Python client uses its smaller bundled list. 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. It makes outbound requests to its target list and reports the results. Other people's traffic is not forwarded through your probe, but your own measurement traffic remains visible to your network operator.

Requests to the Voidly API carry VoidlyProbe/<version> in the User-Agent. Target-site HTTP checks use a browser-like User-Agent, while DNS and TLS checks do not necessarily carry one. Repeated checks of the served target list are still observable and may identify this as measurement traffic.

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 ID, country, city and measurement timeline can become public, and a claimed display name or handle can link the record to you. The client may contact ipinfo.io to determine location unless you configure an override; your ISP and the services you contact can see your connection. An API-side IP hash does not make a city plus timeline anonymous. If you need to be unlinkable, do not run a probe.

Stop the process to stop new measurements. voidly-probe --unregisterremoves the local identity; it does not revoke the remote token or remove the public registration. Check ~/.voidly/pending_results.json for any unsent local results. Previously submitted observations may remain public and may already have downstream copies.