Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is OONI?
OONI is the Open Observatory of Network Interference, a global community project that measures internet censorship and network interference. It combines a free testing tool, OONI Probe, with OONI Explorer, an open dataset of censorship measurements collected from more than 200 countries since 2012.
What it actually does
- Tests for blocking of websites and apps, using OONI Probe.
- Measures network speed and performance, so you can distinguish censorship from ordinary slowdowns.
- Publishes measurements openly, so journalists, researchers and rights advocates can examine patterns rather than rely on anecdote.
Who it's for
| User | Typical use |
|---|---|
| Everyday users | Check whether a site or app is blocked on their connection |
| Researchers and journalists | Analyse country-level censorship trends over time |
| Advocates and policymakers | Document interference with health, news or social platforms |
A practical example
If a reproductive-health website fails to load, a single failed page tells you little. Running OONI Probe and comparing results with OONI Explorer data from other networks in the same country helps show whether the block is widespread and consistent — the difference between a local outage and deliberate filtering.
Trade-offs to know
Censorship measurement is observational, not a verdict. A test can suggest blocking, but causes such as DNS issues, server downtime or ISP misconfiguration need checking. Results are also most useful when many volunteers test the same targets across different networks and times.
Next step: if you want to contribute, install OONI Probe and run tests on your own connection; if you want to investigate, start with OONI Explorer and filter by country, date and test type. Related projects worth knowing include The Tor Project for circumvention and The Citizen Lab for academic research on network interference.
How can I use OONI Probe to test my own network for censorship?
Install OONI Probe on your phone or desktop, run a test while connected to the network you want to check, and then read the results in the app or on OONI Explorer. OONI is a community project that measures internet censorship worldwide; its two main tools are OONI Probe (the testing app) and OONI Explorer (the public data map and dataset).
What a test actually does
OONI Probe runs a set of measurements rather than a single "is my internet censored?" check. Typical tests look at:
- Website blocking — whether specific sites load or fail in ways consistent with filtering.
- App and service reachability — whether messaging or circumvention tools can connect.
- Network performance — speed and latency, so you can separate slowness from blocking.
- Middlebox interference — signs that equipment on the path is tampering with traffic.
A practical way to run it
- Install OONI Probe and open it on the device and connection you care about (home Wi-Fi, mobile data, office network).
- Run the default test group once to get a baseline.
- If you suspect blocking of a particular site or app, run the relevant test for that category.
- Repeat at different times of day and, if possible, on a second network — a result on one connection alone is weak evidence.
- Open OONI Explorer and compare your measurements with others from the same country and network.
For a concrete scenario: a journalist in a country where a news site is intermittently unreachable can run the website test on their home connection in the morning and evening, then check Explorer to see whether other users on the same ISP report the same failure. That pattern — repeated, network-specific, matching other users — is far more meaningful than a single failed load.
Reading results without over-claiming
A failed connection is not automatically censorship. Sites go down, DNS misbehaves, captive portals block traffic, and VPNs change what you see. Treat results as signals to investigate, and look for consistency across tests, times and networks. Because measurements are contributed publicly, they also help researchers and advocates document blocking patterns — the kind of evidence behind reports on blocked reproductive health sites and throttling during protests.
Where to go next
If you want to contribute data rather than just check your own connection, run tests regularly and let them upload; the project's value comes from many people testing many networks. For methodology and terminology, the FAQ and glossary on OONI explain how each test works and what its results can and cannot show.
How do I interpret OONI's measurements to tell whether a website is blocked or just down?
OONI's measurements are built to separate a network-level block from an ordinary outage. The distinction comes from what the test actually observes when it tries to reach a site or service.
What OONI records
OONI Probe runs a request and captures the outcome, then compares it against a control measurement taken from outside the tested network. The key signals are:
- Failure type. A connection that is reset, timed out, or refused looks different from a DNS lookup that returns a wrong or missing answer.
- DNS consistency. If the name resolves to an unexpected address, or does not resolve at all, that points to DNS tampering rather than a dead server.
- HTTP response. A block page, an unexpected status code, or a response body that differs from the control suggests interference.
- TCP reachability. If the TCP handshake never completes, the connection is being dropped before any content is exchanged.
- Control comparison. The same measurement taken from a non-censored vantage point shows whether the anomaly is local or global.
How to tell blocked from down
The practical test is whether the failure is selective and reproducible. A site that is genuinely down tends to fail for everyone, everywhere, with a consistent server-side error. A blocked site tends to fail only from certain networks or countries, often with reset connections, DNS mismatches, or block pages.
Use OONI Explorer to look at measurements for the specific site and country over time. If anomalies cluster on particular ISPs or appear suddenly, that is a censorship pattern. If failures are scattered and match global outages, it is more likely an infrastructure problem.
A concrete example
Suppose you cannot reach a news site. On OONI Explorer you see that measurements from your country show TCP connections being reset, while measurements from other countries reach the site normally. That combination — local failure plus working control — is strong evidence of blocking. If instead every country shows the same timeout and the site's own status page confirms an outage, the site is simply down.
Next step
Run OONI Probe on your own network for the site in question, then compare your result with measurements from other networks in OONI Explorer. Differences between your network and others are the clearest signal of censorship rather than an outage.
What steps can I take to contribute measurements or help expand OONI's coverage in my country?
You can contribute in three ways: run measurements yourself, recruit others to run them in underserved networks, and help make the data more useful through translation, documentation or analysis. OONI's own framing is a global community measuring internet censorship, with two main tools: OONI Probe for testing, and OONI Explorer for tracking results worldwide.
Start by running OONI Probe on networks that are underrepresented
Coverage gaps usually exist in specific places: smaller ISPs, mobile carriers, campus or corporate networks, and regions where few volunteers have installed the app. If you run the tests from a home connection only, you add data for one network; if you also test from mobile data, a workplace network or a friend's connection, you widen the picture considerably.
Practical steps:
- Install OONI Probe and run the standard test suite, including website and app blocking tests plus network performance measurements.
- Run tests periodically rather than once — censorship changes with events, elections and protests.
- Test on different connection types and at different times of day.
- If you are in a country with little data, your runs may be among the few available for that network.
Recruit testers rather than testing alone
One volunteer rarely covers a country. Coverage grows when several people test different ISPs and regions. Useful audiences to approach are digital rights and press freedom groups, university network and security courses, hacktivist or tech communities, and journalists who already report on blocking. Give them a concrete reason: OONI Explorer turns their measurements into citable evidence, and OONI's research posts show how such data has been used to document blocking of health information, streaming-related IP blocking and throttling during protests.
Help where measurement is not the bottleneck
Some countries already have measurements but lack interpretation, translation or local context. Contribution options include translating OONI materials and the Explorer interface into a language your community reads, writing local documentation or guides, and analysing existing measurements for a specific event or ISP. If you have research skills, pairing OONI data with interviews or local reporting produces findings that raw measurements cannot.
Decide what to do first
| Situation in your country | Best first step |
|---|---|
| Few or no measurements | Run OONI Probe regularly across several networks and ISPs |
| Measurements exist but only from one ISP | Recruit testers on other carriers and connection types |
| Data exists but is not understood locally | Analyse it, translate materials, or write a local explainer |
| Active censorship controversy | Coordinate testing around the event and document results |
A concrete next step
Pick one week, run OONI Probe on every network you can access, and note the ISP and connection type for each run. Then check OONI Explorer for your country to see which networks and test types are missing, and ask two people on different providers to do the same. For background on methods and terminology, use OONI's FAQ and glossary, and for context on how results have been reported, see their research posts at OONI.
How can journalists or researchers use OONI Explorer to find and cite evidence of censorship events?
Journalists and researchers use OONI Explorer as a public archive of network measurement data: millions of measurements collected from more than 200 countries since 2012. Instead of relying on anecdotal reports that a site is blocked, you can locate measurement records tied to a country, time window and tested service, then cite the dataset alongside your own reporting or analysis.
A practical workflow
- Define the event narrowly. Pick a country, a date range and the specific service or category (for example, a news site, a messaging app or a reproductive health resource) rather than "censorship in country X."
- Pull matching measurements in Explorer. Filter to that country and period, then look for anomalies such as connection failures, DNS tampering or blocked responses on the targeted service.
- Check the pattern, not one result. A single failed measurement can reflect a local outage or misconfiguration. Look for the same anomaly recurring across networks, cities or days.
- Compare against a baseline. See whether unrelated services tested in the same period and place behaved normally. That contrast is what turns a raw failure into evidence of selective blocking.
- Cite the measurement, not just the conclusion. Reference the country, date range, tested service and the fact that the data comes from OONI's open dataset, so others can reproduce your query.
What OONI Explorer is good for — and its limits
| Strength | Trade-off to account for |
|---|---|
| Large longitudinal dataset spanning many countries and years | Coverage depends on where volunteers run tests, so some regions and networks are thinly measured |
| Open data you can query and cite directly | Measurements show technical anomalies; they don't by themselves prove who ordered a block or why |
| Near-real-time tracking of censorship events | Volunteer-collected data can include false positives from local network problems |
For a concrete scenario: a reporter covering an election-period shutdown could filter Explorer to the country and voting week, identify which platforms showed anomalies, compare them with services that stayed reachable, and then seek on-the-record confirmation from users or officials. The measurement data establishes what happened on the network; interviews and documents explain why.
Next step
Start with a single well-defined query in Explorer for the country and service you care about, note the date range and the specific anomaly types you find, and treat that as your evidence base. Pair it with OONI's published research and methodology pages to describe accurately how the measurements were collected.
What are the limitations of OONI's data, and how should I account for them when drawing conclusions?
OONI's data is a large, open, volunteer-collected set of network measurements, not a complete census of what is blocked. Treat it as strong evidence of what happened on specific networks at specific times, and weaker evidence for broad claims like "country X blocks Y."
Main limitations to keep in mind
- Volunteer coverage is uneven. Measurements come from people who choose to run OONI Probe. A country with many contributors and diverse networks produces richer data than one with a handful of tests on a single ISP.
- Network and location skew. Results reflect the vantage points used. If most tests run from one mobile carrier in the capital, they say little about fixed-line users or rural regions.
- Timing gaps. Censorship can be intermittent, event-driven, or rapidly changing. A test run before or after a block window may miss it.
- False positives and inconclusive results. A test can fail because of a local misconfiguration, a captive portal, DNS resolver quirks, or transient network problems rather than deliberate censorship. OONI's methodologies distinguish anomalies from confirmed blocking, but you still need to read the classification carefully.
- Method-specific blind spots. Different tests probe different layers (DNS, TCP/IP, HTTP, TLS). A site may appear reachable at one layer while being interfered with at another, and encrypted or domain-fronted traffic can be harder to interpret.
- Not a measure of everything. OONI Probe tests specific websites and apps; it does not automatically tell you about every blocked service, the intent behind a block, or the experience of users who never run tests.
How to draw conclusions responsibly
- Ask "blocked where, when, and on which network?" rather than "is it blocked in this country?"
- Look for corroboration. Multiple networks, repeated measurements over time, and consistent anomalies across independent tests make a blocking claim much stronger.
- Check the test type and the anomaly. Confirm whether the result is confirmed blocking or an anomaly, and which measurement layer flagged it.
- Pair with other evidence. Combine OONI data with local reporting, legal documents, or user reports. OONI's own research posts and country reports show how this is done in practice.
- State uncertainty. Report the scope ("on these networks, during this period") and note gaps rather than generalizing.
A useful next step is to browse OONI Explorer for the country and time window you care about, then read the methodology notes before forming a conclusion. OONI's own site is OONI, and for broader context on internet freedom measurement you can compare with Freedom House and Access Now.
User reviews (0)