Find recently blocked websites with search filters

Internet filtering in Australia is rarely as simple as a website being “hidden.” The same domain can resolve on Telstra broadband, fail through an Optus mobile hotspot and behave differently on Vodafone’s fixed-line network. That variation is why blocked-page lists need context. DNS filtering, HTTP resets, expired certificates and ordinary network trouble can look similar from the user’s screen.

Net Neutrality Monitor records where a host or address appears filtered and which network path produced the result. Its search filters move from a broad country view to a specific URL, IP address, provider or DNS resolver. The goal is to identify a recent, reproducible block and preserve enough evidence to compare it with earlier observations.

Start with the address you want to test

Begin with the exact URL when you already suspect a block. Paste the full address, including the scheme and path if relevant, into the search field. A news story and its home page may be treated differently if filtering is applied to a path, hostname or resolved address rather than an entire domain. Searching the hostname without the scheme can therefore miss useful matches.

If no result appears, use the URL or IP submission option to request monitoring rather than assuming the site is unblocked. Enter an IP only when it is the relevant endpoint, because shared hosting can place unrelated pages behind one address. Review country-specific entries, then narrow results by network or resolver.

Local evidence can be more informative than a global label, a principle reflected in community monitoring work from New York. Apply the same discipline in Australia: record whether the test came from suburban Sydney, central Melbourne, a mobile connection or fixed broadband, and retain the time, address and path.

Filter by country, provider, and DNS

Country establishes the legal and geographic setting, but it does not identify the path carrying your traffic. Open the provider filter and select the relevant ISP or network operator; then repeat the query with a specific DNS resolver. A resolver filter is especially useful when a site loads on one connection and returns an unfamiliar address on another. Keep each filter combination narrow enough to remain interpretable.

Australia’s consumer market is concentrated around Telstra, Optus and Vodafone. Many people use fixed-line broadband at home but switch to a phone hotspot, work Wi-Fi or a carrier app during the day. In Sydney and Melbourne, that can mean testing one address across several environments without changing the phone or browser. Compare results before calling a block national.

Legal context does not change technical filters, but it should shape interpretation. ACMA can issue notices directing access providers to block specified material under the Telecommunications Act 1997, while the Assistance and Access Act 2018 provides a separate mechanism for compelled assistance to law enforcement and intelligence agencies. Neither proves that a failed lookup is censorship. Public-facing resources such as the California Peace Officer site remind us that institutional material and volunteer measurements answer different questions, so read each source’s scope before using it as corroboration.

Use status and date to find recent blocks

To find recently blocked websites, combine a blocked status with a date range, then sort the results by the most recent detection or observation. If the interface separates “first seen” from “last checked,” use the former to establish recency and treat the latter as freshness of the measurement. A result updated today may still describe a block first recorded months ago.

Recent does not automatically mean new. Review the detection date, status changes and any earlier record for the same URL. A hostname may move from blocked to reachable after a policy change, while a newly observed domain may be blocked only on one resolver. The useful question is whether the latest evidence shows an active block, not whether the domain appeared near the top of a list.

Keep a trail of the filters used: country, provider, resolver, blocked status and date range. Copy the record rather than relying on a context-free screenshot. This distinguishes a newly detected site from an old result resurfacing after a search.

Distinguish filtering from ordinary failures

A failed page does not automatically mean filtering. DNS filtering may return a wrong or sinkhole IP address, while an HTTP reset looks like a connection that closes mid-load. A timeout can instead reflect an overloaded resolver, a faulty captive portal or a restrictive office firewall. Compare the returned IP with a known resolver response, note the error type and try another transport before labelling the target blocked.

DNS answers can remain cached after a block is lifted. If a check changes from unusable to reachable, follow the procedure to rebuild the DNS cache and retest rather than assuming the first successful page load proves the original block ended.

Use the resolver filter to compare a hostname through an Australian recursive resolver, a public resolver and a different ISP where feasible. Record the response code, returned address and whether failure occurs before or after TLS negotiation. These details explain differing labels and prevent cache effects from being mistaken for a fresh network decision.

Compare the most useful search combinations

Start broad, then narrow. A broad search reveals patterns; an exact search tests a claim. Choose filters according to whether you need discovery, attribution to a network path or verification of one address.

Search combination	Best for	What to check
Country plus blocked status	Finding recently reported blocks	Detection dates, status changes and duplicate hostnames
Country plus provider	Comparing fixed-line and mobile networks	ISP name, connection type and whether the result repeats
Country plus DNS resolver	Isolating resolver-specific behaviour	Returned IP, response code and cached answer
Exact URL or IP	Verifying a reported address	Full path, redirect destination and relevant country entries

No combination is definitive. A country-wide result may contain one block seen through several providers, while a provider result may reveal a hostname failing for an unrelated reason. Re-run the narrowest useful query with one filter removed. If the result changes, that dependency is important evidence.

Build a repeatable monitoring routine

For sites whose reachability may fluctuate, repeat checks rather than relying on one visit. Record the time, network and resolver, and compare consecutive results to separate a stable policy from a transient failure. The guide to automate censorship checks shows how scheduled requests can run on servers you control while preserving the same query parameters. Automation should extend a documented method rather than replace it.

A practical routine can include:

• Start with country, blocked status and the latest date range, then widen the search only if the initial results are sparse.
• Test the same URL through the relevant provider and resolver, followed by one alternate path when the result affects a local user.
• Save the full query, timestamp, returned address and status history so an old result cannot be mistaken for a new detection.
• Recheck after a DNS cache change, network switch or confirmed policy change, and label each observation with the conditions that produced it.

Review results in a fixed order: broad country scan, provider comparison, resolver comparison, then exact-address verification. This prevents a familiar domain from dominating review and makes changes between runs easier to spot. Keep failed and successful checks together, since both establish the conditions behind a classification.

Read the result in its real context

A measurement shows what appeared to happen from a particular path and time. It does not establish who ordered a block, whether a policy was lawful, or whether every Australian user will encounter the same result. That distinction matters in Australia because ACMA blocking notices, provider policies and technical filtering can produce similar symptoms under different arrangements. Net Neutrality Monitor is a beta, volunteer-supported project powered by AirVPN, so its data should be treated as indicative research rather than an authoritative determination.

When documenting a finding, describe the observable event: the exact URL or address, country, provider, resolver, timestamp and error behavior. Note any limits, such as an untested IPv6 route, a shared hosting address or a workplace network. The practical takeaway is to treat a recent block as a reproducible, time-stamped observation: capture those conditions, compare an alternate path, and only then classify the result.