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
Testing internet censorship across Australian mobile and fixed networks
A website that opens on home broadband may fail on a mobile connection, while a page blocked on a phone may load normally over a fixed-line service. That difference does not automatically mean the website is offline. Internet service providers can apply separate filtering policies to mobile and fixed networks, and each connection may use different DNS resolvers, IP routes, address families and traffic-management systems.
A useful censorship test compares the same destination under controlled conditions. The device, browser, URL, protocol and time should remain as similar as possible while the access network changes. In Australia, this usually means comparing a mobile network from providers such as Telstra, Optus or Vodafone with a home NBN service supplied through an ISP such as Telstra, Aussie Broadband, TPG or Superloop.
Results should be treated as indicators rather than absolute proof. A timeout can be caused by congestion, an overloaded DNS server, a broken IPv6 route or a server blocking Australian traffic. Net Neutrality Monitor can help researchers examine DNS, blacklist, probe and country-specific censorship information, while a careful local test supplies the context needed to interpret those records.
Establish a fair test before changing networks
Begin by selecting several test targets instead of relying on one website. Include a known accessible page, the domain under investigation, and, where relevant, a specific IP address or URL path. Test both HTTP and HTTPS when available, because a provider may interfere with DNS resolution while leaving direct IP connectivity untouched, or may block a hostname at a later stage of the connection.
Use the same phone or laptop, browser, operating system and URL on both connections. Clear the browser cache, disable any browser proxy, and record the exact time of each attempt. If the mobile connection is shared through hotspot mode, make a note of that arrangement. A hotspot can introduce an additional layer of network address translation, but it still provides a useful comparison with an NBN, cable or fibre service.
Avoid switching several variables at once. Do not compare a browser on an Android phone with a VPN-enabled desktop and then attribute every difference to the ISP. Record whether the failure appears as a DNS error, connection reset, timeout, certificate warning, block page or ordinary server error. The wording and behaviour of the failure often reveal which part of the connection is being filtered.
Check DNS resolution and direct connectivity
DNS is the first practical comparison point. Run a lookup for the domain on each network and record the returned addresses, response time and any error such as NXDOMAIN or SERVFAIL. A filtered resolver may return no address, provide a block-page address, or redirect a request to an advisory page. A normal response does not prove that the site is reachable, since blocking can occur after name resolution.
Compare A records for IPv4 and AAAA records for IPv6. Australian mobile networks commonly support IPv6, while a home service may use IPv4, IPv6 or both depending on the ISP and router configuration. If the mobile network receives an IPv6 address but the fixed connection does not, the two tests may follow entirely different paths. A failure on only one address family can resemble censorship even when the cause is a routing or server configuration problem.
A controlled resolver comparison can add evidence. Test the ISP-provided DNS service, then repeat the lookup with a reputable independent resolver, while clearly recording the change. If the domain resolves through one resolver but not another on the same access network, DNS filtering is more likely. If every resolver returns an address but the connection fails, investigate IP blocking, transport interference or the destination server before assigning a censorship label.
Compare mobile and fixed-network behaviour
Mobile carriers often apply policies at a national or account level, but the traffic still passes through mobile-specific gateways. Carrier-grade NAT means many customers can share public IPv4 addresses, and the apparent source address may change between sessions. A mobile operator may also use traffic optimisation, parental controls, malware filtering or age-restricted-content settings that are separate from its fixed broadband products.
Fixed broadband has its own variables. An NBN connection may use a different upstream network from the retail brand shown on the bill, and the home router may provide local DNS caching, parental controls or security filtering. A service based on fibre to the premises, fibre to the node or fixed wireless can also have different latency and routing characteristics. In regional Australia, long links and wireless backhaul can make timeouts more common without indicating deliberate blocking.
Repeat each test several times, including after toggling mobile flight mode or reconnecting the home router only when necessary. Note the public IP address, whether it is IPv4 or IPv6, and the approximate latency. A result that changes with a new mobile session may indicate dynamic policy enforcement, a shared-IP reputation problem or ordinary routing variation. A stable block page appearing only on one access type is stronger evidence of network-level filtering.
Use evidence beyond a single browser result
The visible browser outcome is only one layer of the investigation. Command-line tools such as dig, nslookup, curl and traceroute can show whether a failure occurs during DNS, TCP connection setup, TLS negotiation or HTTP response delivery. On Windows, macOS, Linux and Android-based diagnostic applications, equivalent tools can capture much of the same information, though results may be affected by local permissions and app settings.
A TLS certificate warning deserves particular attention. It can indicate interception, a misconfigured website, an incorrect system clock or a captive portal. Do not enter credentials after a certificate warning, especially on public Wi-Fi or an unfamiliar hotspot. A connection reset immediately after a hostname is sent may suggest filtering based on the domain, whereas a failure to reach the destination IP may point to address blocking or routing trouble.
Net Neutrality Monitor is useful for placing a local observation beside broader evidence. Its country results, probe data, DNS information, blacklists and statistics can indicate whether other measurements have observed a similar issue. Users can submit URLs or IP addresses for monitoring and review available results, but a listing should be read as research data rather than a legal ruling or a guarantee that every Australian provider will produce the same outcome.
Interpret results without overclaiming
A blocked result should be classified cautiously. DNS tampering is suggested when the ISP resolver returns a false address or refuses the lookup, while an IP-level block is more plausible when several resolvers agree on the correct address but connections to that address fail. A block page, reset pattern or consistent timeout across multiple devices can provide additional support, although none of these signs is conclusive by itself.
False positives are common. The website may be down, its hosting provider may reject Australian IP ranges, its firewall may rate-limit mobile carrier addresses, or a content delivery network may advertise an unreachable IPv6 address. Local security software, browser DNS-over-HTTPS, a family-safety profile or a corporate network can also alter the result before traffic reaches the ISP.
The comparison below provides a compact way to organise observations before drawing a conclusion.
| Test area | Mobile network | Fixed broadband connection | What a difference may indicate |
|---|---|---|---|
| DNS resolver | Usually carrier-controlled, sometimes with IPv6 support | Often supplied by the ISP or home router | Resolver-level filtering, different DNS policies or local router settings |
| Public address | Frequently carrier-grade NAT and shared IPv4 | May use dynamic IPv4, IPv6 or both | Shared-IP reputation, address-specific blocking or different routing |
| Filtering policy | May include mobile safety, age controls or carrier security services | May have separate home, business or router-level controls | Product-specific censorship or content filtering |
| Failure pattern | Timeouts, resets or block pages through a carrier gateway | Different response, route or DNS result | Network-path or policy variation |
| Best comparison method | Test with handset data and hotspot notes recorded | Test the same device and URL over NBN or another fixed service | Whether the issue follows the access network rather than the device |
A reliable report should include the date, Australian state or city where practical, provider or access type, domain and IP tested, DNS responses, IPv4 and IPv6 observations, browser result, command-line evidence and repeat attempts. Melbourne, Sydney, Brisbane and Perth users may see different routes or local service conditions, while regional users may need to allow for fixed-wireless congestion and longer paths. Those details make the result more useful than a simple statement that a website “does not work.”
The practical takeaway is to test the same destination over both mobile data and fixed broadband, separate DNS failures from connection failures, record IPv4 and IPv6 behaviour, repeat unstable results, and compare local observations with independent censorship measurements before describing an access problem as deliberate filtering.
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






