Net Neutrality Monitor analyses how Internet Service Providers resolve, block and inject DNS traffic. The platform tracks servers under examination, surfaces country-level reports, and publishes a live blacklist of injected addresses.
View Country ReportsWhat the platform does
Net Neutrality Monitor provides real-time analysis of the censorship systems used by Internet Service Providers. It tracks DNS servers currently under examination, lists known DNS servers that respond correctly to specific tests, and produces country reports on the types of blocking detected — from gambling and file-sharing to streaming and image hosting.
- DNS probes
- Country reports
- Injected addresses
- ISP scoring
Coverage across the monitored regions
Country reports are available for China, Colombia, Denmark, Estonia, Finland, Italy, Korea Republic of, Sweden, Switzerland, Thailand, Turkey and additional regions as new probes are activated.
- 11+Countries with published reports
- LiveDNS server list under examination
- CC BY 2.5 IT / BY-SA 3.0Content licensing applied
- OpenDonations and probe submissions
Examining the Education Domains Trapped on ISP Blocklists
The way Australians reach the web has shifted over the past decade, with the NBN reshaping how households and schools get online, and state education departments leaning on centralised filtering for student safety. Among the categories ISPs and DNS resolvers use to sort the internet, the education blocklist tends to spark the strongest debate. A site blocked for safety in one context can be a vital learning resource in another, and the line is rarely as clear as policy documents suggest. Learn more about 257438 Data Encryption Standards For Drone Collected Evidence In Criminal Cases.
Net Neutrality Monitor pulls together blacklist, probe, and DNS data from volunteer-run nodes across multiple regions, and the education category is consistently the most reported on. Researchers, teachers, and curious netizens keep submitting library catalogues, open-source learning platforms, and university course portals to see whether they are reachable from a residential Aussie connection or quietly intercepted at the resolver. The result is a long, evolving snapshot of what the public web looks like once you look at actual reachability.
What makes the education slice different from adult content or gambling filters is the variety of domains it covers. A single blocklist entry can affect an entire subject area, a popular revision site, or a niche research database that only a handful of academics use. Looking closely at which educational URLs are flagged, where, and by which operator, reveals more about how local filtering rules are written than any policy white paper ever will.
How Education Domains End Up on a Blocklist
Most Australian ISPs do not curate their blocklists from scratch. They subscribe to commercial feeds, accept court-ordered or ACMA-mandated additions, and apply optional parental-control tiers. Education-related domains can be caught by any of these pathways: a history site tagged as gambling because it covers card games, a coding tutorial flagged as hacking tools, or a teen mental health resource swept into a self-harm category.
Commercial feeds are often aggregated overseas, which is part of the problem. A category that makes sense in one regulatory environment can be a poor fit for an Australian classroom, where the curriculum asks students to engage with content other jurisdictions treat as restricted. When a Brisbane student tries to reach a primary source for a Year 11 history assignment and the page will not load, the school IT team usually has no visibility into which list added the domain or why.
Telstra, Optus, and TPG all offer family-friendly modes that pull from broader child-safety feeds, sometimes enabled by default. A parent who simply wants younger kids off adult content may inadvertently block an older teen's access to a university open-day portal or a TAFE enrolment page. The downstream effect is uneven, and depends on which ISP a household happens to be with.
Reading the Probe Data
The probe infrastructure behind Net Neutrality Monitor is what turns anecdotal complaints into something measurable. Each probe is a small client that, from a residential or VPS connection, attempts to resolve and connect to a list of submitted domains and records what happens. The result is a country-by-country breakdown showing where a given URL works, where it is silently dropped, and where the DNS server returns an unexpected response.
Anyone curious about how this is collected can look at the probe data directly, which lists the active measurement points and what each is currently testing. The dataset crowdsources observations from ordinary users rather than relying solely on data-centre vantage points, which matters for the education category, where reachability from a school or home connection is exactly what people care about.
When a domain is blocked at the DNS level, the user sees a generic ISP-branded landing page explaining that access has been restricted. When it is blocked deeper in the stack, the connection simply times out, and the user has no easy way to tell whether the site is down, the Wi-Fi is playing up, or the resolver is interfering. Sorting these failure modes apart is one of the more useful things the probe data does.
Transparent DNS Versus Encrypted DNS
A lot of the confusion around blocked educational domains comes down to which DNS path a household is using. The default setting on most Australian routers points at the ISP's resolver, which is transparent in the sense that it sees every query, can log it, and can rewrite or refuse answers at will. Switch to an encrypted resolver, and the picture changes: the query is hidden from the ISP, but the destination server still has to answer it, and any IP-level block at the network edge still applies.
The mechanics are explained in more detail in an article on transparent versus encrypted DNS censorship, which walks through what each layer sees and where filtering can be inserted. The short version is that encrypted DNS makes casual ISP-level filtering harder, but it does not defeat every method, and a determined network operator can still intervene further up the chain.
For schools, this is more than a technical curiosity. The decision of whether to push student devices through the school's own resolver, an encrypted public one, or straight to the ISP is made by a small team, often without consulting the teachers who will later complain that a specific resource is unreachable. Understanding the difference helps explain why a Year 9 coding lesson might work in one classroom and fail in the next.
What the Numbers Show Across Australia
Looking at the most recent country reports for Australia, the education category is dominated by legitimate learning platforms that have been over-categorised, niche academic resources that fall foul of broad safety filters, and a smaller cluster of genuinely problematic sites. The middle group is the most interesting, including online anatomy atlases, sex education portals used in Year 10 PDHPE, and chemistry databases that mention controlled substances in a research context.
A domain can be reachable on Monday and blocked by Friday, because a commercial feed has updated, because ACMA has added a new reference to its schedule, or because an ISP has quietly expanded a default filter. The probe infrastructure catches some of these shifts when it re-tests, but the lag between a real-world change and a logged observation can stretch to days. Outside Australia, similar access questions play out in different ways. A look at digital skills bootcamps for youth employment in Sri Lanka shows how connectivity constraints shape what young learners can actually reach.
The reports do not break down filtering by state, even though school filtering policies in New South Wales, Victoria, Queensland, and Western Australia are run quite differently. The Catholic and independent school sectors add another layer of variation, since they negotiate their own filtering arrangements rather than going through a state education department.
Common False Positives in the Education Category
A small set of patterns accounts for a large share of the false positives. The first is keyword over-matching: a domain containing "lab" can be tagged as drugs-related, a site about "firewalls" can land in a hacking category, and a maths revision portal with dice imagery can be flagged as gambling-adjacent. The second is the legacy of older categorisation systems, where a domain correctly classified a decade ago is still on the list even after its content has changed.
A third pattern involves regional reference material. Sites that catalogue Australian history, Indigenous language resources, or local council records sometimes sit on shared infrastructure with content a generic filter considers unsafe. When the blocklist treats the domain as a single unit rather than a path, the entire site becomes unreachable, including the parts a teacher actually wants to use. A fourth, less obvious source comes from cloud hosting: an innocent university project on a large cloud provider can be caught up in a block applied at the IP range level, especially if another site on the same range has been flagged. From a teacher's perspective, the distinction between a domain block and an IP block is invisible.
Comparing How Different Operators Filter Education Domains
| Operator / Resolver | DNS-level filtering | IP-level filtering | Override option | Notes for Australian users |
|---|---|---|---|---|
| Major ISP default resolver | Yes, broad commercial feed | Rare | Family filter toggle | Default on most new accounts, varies by state |
| Encrypted public resolver | No ISP-level rewriting | Depends on path | Manual client config | Bypasses ISP DNS, not network-edge blocks |
| School-managed resolver | Yes, departmental policy | Yes, common | None for students | Heaviest filtering, most false positives logged |
| Mobile carrier resolvers | Yes, lighter commercial feed | Uncommon | Opt-out via account | Often the only path on phone data plans |
The table is best read as a snapshot, not a verdict. A household that switches to an encrypted resolver may see fewer DNS-level blocks, but if the school network in question is doing its filtering on IP ranges, the change will make no difference at all. Reachability depends on the combination of operator, network type, and device, rather than on any single setting.
For a parent in Adelaide or a teacher in regional Tasmania, the practical upshot is to test a blocked URL from more than one connection before assuming the site itself is down. The same resource might be unreachable on a school's managed Wi-Fi, load fine on a Telstra mobile hotspot, and then be blocked again on an Optus home NBN service, all in the same morning.
How to Submit a Domain and Read the Results
Anyone who has hit a blocked education page from an Australian connection can contribute to the dataset by submitting the URL or IP through the main site. The form asks which country the test was run from, what the expected behaviour was, and what was actually observed, which helps the volunteers sort genuine blocklist entries from transient outages.
A few practical pointers for Australian submitters:
- Note the ISP and the type of connection (NBN fibre, FTTN, mobile data) at the time of the test.
- Try the same URL over an encrypted resolver to see whether the block is DNS-only.
- Capture the exact error message or landing page text if one is shown.
- Mention whether the page is needed for a specific year level or subject area.
Once a submission is accepted, it feeds into the country-level statistics and shows up in the public breakdown for the education category. Over time, that accumulation of small observations is what gives the project its weight, and it is the most realistic way for a teacher or parent in Perth or Hobart to push back when a useful resource has been quietly caught in the filter. The kind of rigour applied to [
Transparent, analytical, community-run
The platform documents how ISPs handle neutrality on the wire, with method notes, country breakdowns and a public blacklist of injected addresses. — Project methodology






