Why Websites Are Blocked in One Country and Open in Another

A website can be perfectly reachable from Sydney while returning an error in Jakarta, London or even a different network in the same city. The difference is usually not a fault in the website itself. It may result from national law, an Internet Service Provider’s filtering policy, a DNS response, an IP block, or a commercial decision made for a particular market.

For Australians, this can appear when a page loads over a home NBN connection but fails on mobile data, or when a service works in Melbourne and seems unavailable while travelling overseas. Understanding the distinction between a website being offline and a website being filtered helps users interpret monitoring results without jumping to the wrong conclusion.

Internet Access Is Built From Regional Decisions

The Internet feels global because the same domain name can be entered from almost anywhere. Access, however, depends on local infrastructure. A request from a user in Brisbane passes through an Australian ISP, local resolvers, international transit providers and the website’s hosting network. A request from another country follows a different path and encounters a different set of rules.

Governments can require providers to restrict particular domains, URLs or IP addresses. ISPs may apply those restrictions through their own filtering systems, while DNS operators can prevent a domain from resolving correctly. A website may therefore be available in Australia while being blocked in another country, even when both users use the same browser and enter precisely the same address.

Filtering can also be limited to a network type. A page might work on a home connection but fail on a workplace network, university Wi-Fi or public hotspot. In Australia, a commuter using mobile data near Central Station may see a different result from someone using a fixed connection in the same Sydney suburb.

DNS Responses Can Change the Result

DNS is often described as the Internet’s address book: it converts a domain such as example.com into an IP address. A DNS-based block can return no address, an error, or a substitute address controlled by the provider. The browser may display a generic failure page, making the incident look like a server outage.

The response can vary according to the resolver used. An ISP resolver may enforce a local block, while a public resolver may return a normal answer. This is why raw evidence matters. The guide to raw DNS response logs explains how response codes, returned records and probe locations can reveal what happened before a browser even connected to the site.

DNS evidence does not always prove that a government ordered the block. A provider may act under a court order, follow a regulatory list, or apply a safety policy of its own. It is also possible for a domain to have incorrect DNS records that affect only some regions. Comparing several probes and resolvers reduces the chance of treating a local configuration problem as national censorship.

Laws, Licences and Commercial Rules Matter

Some blocks are driven by legal requirements. Authorities may target material associated with copyright infringement, terrorism, child safety, gambling, fraud or defamation. The legal threshold varies between countries, and enforcement may focus on the website, its hosting provider, a mirror domain or the infrastructure that supports it.

Australia has its own mix of regulation and industry practice. The Australian Communications and Media Authority can be involved in online safety and prohibited-content enforcement, while copyright-related site blocking can follow Federal Court processes. A betting or streaming service may be legal for adults in one jurisdiction but unable to operate in another because it lacks a local licence or fails market-specific rules.

Commercial geography creates another layer. A company may restrict a service to customers in a certain country because of music, film or sports rights. A user in Perth may receive a “not available in your region” message from a streaming platform even though the domain is technically reachable. This is a geo-restriction rather than a network block, although the user experience can look similar.

Researchers who compare policy environments can use resources such as the ICTD research portal to place technical observations alongside broader digital-development and governance questions. Legal context is important because an identical technical symptom can reflect very different causes.

Blocking Can Happen at Several Network Layers

A domain block is often the least precise option. It may stop every page on a website, including harmless information and support content. URL filtering can be narrower, targeting a path or query string. IP blocking can affect multiple unrelated domains when they share a server, cloud address or content-delivery network.

Other techniques include HTTP interference, connection resets and traffic inspection. Some systems identify a hostname in the connection and terminate the session before the server replies. Encrypted connections make inspection harder, but they do not eliminate every way a network can restrict access. A provider may block an IP range, disrupt a protocol or rely on a filtering appliance that is updated from an external list.

The website itself can also refuse access. It may inspect the visitor’s IP address, account country, payment details or browser location. Content delivery networks can send users to different servers based on geography. In that case, the Australian visitor and the overseas visitor reach the same domain but receive different content or different permission decisions.

Reading Monitoring Results Without Overstating Them

Net Neutrality Monitor gathers probe, DNS, blacklist and statistical information about blocked websites and addresses across countries. Its results are useful for identifying patterns: a domain failing consistently from one country, a DNS answer changing by resolver, or an address appearing on a regional blacklist. The project is presented as a beta, volunteer-supported service powered by AirVPN, so its results should be treated as indicative research data rather than a legal ruling or absolute measurement.

A single failed probe is weak evidence. Temporary routing trouble, a misconfigured server, packet loss or a website outage can produce the same result. Stronger evidence appears when several probes in the same country show the same response while probes elsewhere succeed, especially when DNS records or block-page signatures support the finding. For broader background on measuring online restrictions, this censorship research project offers related technical and analytical material.

Signal	What It May Indicate	What It Cannot Prove Alone
Domain does not resolve on one ISP	DNS filtering, resolver failure or a bad record	A national government block
Connection resets after the request	Network interference or an unstable route	The identity of the organisation responsible
Website works on Wi-Fi but not mobile data	Different ISP policy or mobile filtering	That the website is offline
Same IP fails for several domains	IP-range blocking or server trouble	Which domain triggered the restriction
Regional error from the website	Geo-restriction, licensing or account rules	Censorship by the local ISP
Multiple country probes show a pattern	Geographic filtering or service segmentation	The exact legal basis for the action

The most reliable interpretation combines technical and contextual evidence. Check whether the domain resolves, whether the IP responds, whether the failure is consistent across networks and whether the website publishes a regional-access policy. A result marked as blocked should prompt investigation, not an assumption that every user in that country sees the same thing.

Practical Checks For Australian Users

When a page appears unavailable, begin with ordinary comparisons. Try the same address using a home connection and a mobile connection, record the time, and note the exact error message. Do not repeatedly refresh a failing page and mistake a temporary server problem for a stable filter. A service outage affecting users in Adelaide and Canberra is a different event from a block visible only through one provider.

Monitoring tools can add useful evidence, especially when they show country-specific DNS responses or probe results. Keep the domain, full URL, IP address and network type separate in your notes. That distinction matters when a whole site is reachable but one page is restricted, or when an IP address hosts many unrelated services.

Useful Checks Before Drawing A Conclusion

• Compare at least two Australian networks, such as fixed NBN and mobile data.
• Record the DNS answer, error code, timestamp and apparent location.
• Test the domain separately from the specific URL or page path.
• Check whether the website publishes licensing or regional-access conditions.
• Look for matching results from several independent probes.
• Treat a single failed request as an observation, not definitive proof.

A practical diagnosis should answer three questions: where did the failure occur, who controlled that layer, and does the pattern repeat? If the domain resolves normally but the site denies access, investigate the website’s regional policy. If only one resolver fails, investigate DNS filtering or a resolver fault. If several networks and probes show the same country-specific result, the evidence for deliberate geographic blocking becomes much stronger. That simple separation between DNS, network, server and legal context is the most useful first step.