Inside India's Internet Censorship System: How It Works

India's Internet Censorship System Is More Complex Than Most People Realize

When a website fails to load in India, users rarely receive an explanation. There is no official error message citing a legal basis, no public record of when the block was applied, and often no straightforward way to challenge it. This is not an accident. India's internet censorship regime, built primarily around the Information Technology Act of 2000, is structured in a way that makes government-ordered website blocking both legally broad and practically difficult to scrutinize.

Understanding how this system functions matters not just for policy researchers and lawyers, but for the hundreds of millions of people who use the internet in India every day.

The Legal Framework: IT Act Sections 69A and 79

The two central provisions governing online content blocking in India are Section 69A and Section 79 of the IT Act, 2000.

Section 69A grants the central government the authority to direct any government agency or intermediary, including internet service providers, to block public access to online content. The stated grounds include threats to national sovereignty, national security, public order, and relations with foreign states. Crucially, the blocking orders issued under this section are kept confidential. The websites being blocked, the reasons behind those orders, and the identities of those requesting them are not routinely disclosed to the public.

Section 79 operates differently. It provides a "safe harbour" for intermediaries, protecting platforms and ISPs from liability for third-party content, provided they comply with government takedown and blocking directives. In practice, this creates a compliance incentive that reinforces the blocking infrastructure.

Courts can also order website blocks independently, adding another layer to an already fragmented system.

Inconsistent Blocking and the ISP Problem

One of the least-discussed consequences of India's censorship framework is the inconsistency in how blocks are actually implemented across internet service providers.

When the government issues a blocking directive, it is sent to ISPs for enforcement. However, there is no standardised technical mechanism that all ISPs are required to use. Some providers use DNS-based blocking, others use IP blocking, and some use deep packet inspection. The result is that a website blocked by one ISP may remain fully accessible through another. Users in different parts of the country, or on different networks, can have entirely different experiences of what the open internet looks like.

This patchwork implementation is not a bug being addressed by regulators. It is an embedded feature of a system that lacks centralised enforcement standards and independent auditing.

The Opacity Problem: Limited Oversight and Judicial Review

Perhaps the most significant concern raised by legal scholars and civil society organisations is the absence of meaningful independent oversight.

Under the current framework, blocking orders issued by the government under Section 69A are reviewed internally by a committee of officials. There is no independent judicial body that routinely examines whether individual blocking orders are proportionate, accurate, or constitutionally sound before they take effect. Affected website owners or users typically have no notification mechanism, no guaranteed right to respond before a block is imposed, and a limited practical pathway for challenging orders after the fact.

The Supreme Court of India, in the 2015 Shreya Singhal judgment, struck down Section 66A of the IT Act as unconstitutional, demonstrating that judicial review of internet law is possible. But the structural opacity of Section 69A blocking orders means that many restrictions never reach a court at all.

This raises serious questions about whether the current system is compatible with Article 19 of the Indian Constitution, which guarantees freedom of speech and expression, and with the democratic principle that state power should be exercised transparently and with accountability.

What This Means For You

If you access the internet in India, the practical implications are straightforward: the version of the internet you can reach may not reflect the full scope of available information, and you may have no way of knowing what has been removed from your view or why.

For journalists, researchers, businesses, and ordinary users, this matters. A content block that applies to one ISP but not another creates unequal access to information. The confidentiality of blocking orders makes it nearly impossible to assess whether restrictions are proportionate. And without independent oversight, the risk of overreach grows.

Civil society groups and digital rights organisations in India have been documenting these issues for years, calling for greater transparency, a public blocklist, and stronger procedural safeguards before content is restricted. These are debates worth following closely.

Key Takeaways

• India's website blocking regime operates primarily under Section 69A of the IT Act, which allows government-ordered blocks without mandatory public disclosure.
• ISPs implement blocks using different technical methods, resulting in inconsistent access across networks and regions.
• There is no independent body that reviews blocking orders before or after they are issued, limiting accountability.
• Legal challenges are possible but structurally difficult given the confidentiality of the orders.
• Digital rights organisations continue to push for reform, including public blocklists and stronger judicial oversight.

The conversation around internet censorship in India is not a fringe debate. It sits at the intersection of constitutional rights, democratic governance, and the practical realities of how information flows in one of the world's largest online populations. Staying informed about how these systems work is the first step toward meaningful public engagement with them.