voidly

Voidly over Tor

Another
way in.

Reach the public censorship record
through an onion address.

You → TorPublic data

The same record.
A different route.

Read-only. Public data.
No account, key or email.

Open in Tor BrowserFull dataset path
http://aockotxv6jtj6zruldhwikwoux7w7mpdxmjz2icassd6pc2b3xuo3lyd.onion/v1/censorship-index
Open onion URL

Use the complete URL. The bare address and this website’s HTML pages are outside the data allowlist.

  1. Use Tor Browser.

    It knows how to reach an onion service.

    Get Tor Browser ↗
  2. Paste the full URL.

    Keep the path after .onion. The response is machine-readable data.

  3. Read the source.

    Check observation dates, coverage and limitations before using a result.

    Explore the data catalogue ↗

Know the boundary

Public data.
Only.

The door accepts allowed GET requests. Writes, authentication and payments are refused. HEAD and POST are refused too.

Tor changes the network path. Our service can still read the request at its end. The dataset remains public; this service does not promise anonymity or unlinkability.

A public-chain payment remains a public record. If your safety depends on nobody establishing that you paid Voidly, do not pay Voidly. This data access is free.

Supported paths and recorded checks

These GET paths were recorded as answering over Tor on 3 September 2026 (UTC). This is a dated check, not a current uptime claim.

Country index/v1/censorship-index
Open in Tor ↗
Country index · JSON path/data/censorship-index.json
Open in Tor ↗
Incident records/data/incidents
Open in Tor ↗
Version and discovery/data/meta
Open in Tor ↗
Machine-readable methodology/data/methodology
Open in Tor ↗
Model registry/v1/atlas/changelog
Open in Tor ↗

The recorded checks returned 200 for the paths above, and 404 for /v1/pay/* and /admin. Refused routes are an intentional boundary. Do not infer access to unlisted paths.

One recorded index comparison matched the clearnet data after timestamp differences. An ingestion update can make two fetches differ; it is not a permanent byte-match guarantee. Read the original measurement and its basis.

What this route changes—and what it keeps

An onion service provides another route when the ordinary site is blocked by DNS, server-name filtering or routing. Tor itself can also be blocked. Follow the Tor Project’s connection guidance if Tor Browser cannot connect.

The door uses the same upstream data as the ordinary public API. It does not keep an independent mirror. Cached data may still answer during an upstream failure; when usable cached data is no longer available, the door depends on that upstream too.

This address uses http. The onion protocol authenticates the service and encrypts the connection; this service does not offer an HTTPS certificate for its onion name. Read the Tor Project’s explanation.

Fetch with an existing local Tor proxy

If Tor is already running locally with a SOCKS listener on port 9050, this command resolves the onion name through that proxy. Use your own listener’s port if it differs.

curl --fail --show-error --socks5-hostname 127.0.0.1:9050 \
  http://aockotxv6jtj6zruldhwikwoux7w7mpdxmjz2icassd6pc2b3xuo3lyd.onion/v1/censorship-index

This sends a GET request. Do not switch it to HEAD to check availability. Read the payload’s own data dates; request timestamps and response size are not freshness guarantees.

Reuse, citation and the full reference

The access route does not change the license. Voidly-original data uses CC BY 4.0; upstream source data keeps its own terms. Keep source attribution and consult the data catalogue before redistributing raw upstream material.