When the Indian government blocked the Cockroach Janta Party's X account and then its website within two days of each other in May 2026, a single law made both actions possible: Section 69A of the Information Technology Act. Most people had never heard of it. After the CJP block, searches for "Section 69A" spiked across India. This post explains the law in plain language — what it says, how it is used, and why it raises serious questions in CJP's case.

For the full timeline of what the government did and when, see the CJP crackdown timeline. For the fact-check on whether the website was actually government-blocked or voluntarily deactivated, see the OpIndia claim fact-check.

What Is Section 69A of the IT Act?

Section 69A was inserted into the Information Technology Act, 2000 by the Information Technology (Amendment) Act, 2008. It gives the Central Government — specifically, the Ministry of Electronics and Information Technology (MeitY) — the power to direct any intermediary to block public access to any online content.

The exact language of the law reads: the Central Government may direct any agency of the Government or intermediary to block access "in the interest of sovereignty and integrity of India, defence of India, security of the State, friendly relations with foreign States or public order or for preventing incitement to the commission of any cognizable offence relating to above." (India Code, Section 69A)

Those grounds — sovereignty, security, public order — are broad. They are the same grounds used in Article 19(2) of the Constitution to place limits on free speech. The difference is that Section 69A lets the executive branch act unilaterally, issuing a secret order to an intermediary without a court order, a public hearing, or a published reason.

Intermediaries covered by the law include social media platforms, web hosts, internet service providers, and domain registrars. If MeitY directs them to block something, they must comply or face penalties.

What Happened: How the Government Blocked CJP

The CJP crackdown happened in two distinct moves under Section 69A.

On May 21, 2026, MeitY issued a direction under Section 69A citing an Intelligence Bureau report that alleged CJP's X account posed a threat to India's national security and sovereignty. X/Twitter complied, and the @cockroachjantaparty account was geo-restricted for users in India. (Business Today)

On May 23, 2026 — two days later — cockroachjantaparty.org was separately blocked under Section 69A. Founder Abhijeet Dipke told Al Jazeera: "The government has taken down our iconic website — 10 Lakh cockroaches had signed up on our website as members." (Al Jazeera)

Dipke's response to the escalation was pointed: "You can hack and withhold the accounts but you cannot hack this movement." (Business Today)

The actual text of the blocking orders has not been made public. Under Indian law, it does not have to be. Section 69A orders are confidential by default — which is itself part of the story.

The Blocking Procedure: Did CJP Get a Chance to Respond?

The Information Technology (Procedure and Safeguards for Blocking for Access of Information by Public) Rules, 2009 — known as the Blocking Rules — set out two procedures for how a Section 69A block can be executed.

Rule 8 (standard procedure): Before a block is issued, the designated officer is supposed to notify the originator or intermediary and give them 48 hours to respond. A review committee then considers the case before a final order is issued.

Rule 9 (emergency procedure): In cases the government considers urgent, an interim block can be issued immediately with no prior hearing. The standard review process follows afterwards — but the content is already blocked while that review happens.

The CJP block appears to have used the emergency path. The X account was blocked within days of CJP becoming a national news story, and there has been no public indication that Dipke or CJP received any notice or opportunity to respond before the block was executed. However, because blocking orders are confidential, the exact procedure followed has not been confirmed publicly. (Internet Democracy Project, Section 69A and the Blocking Rules)

The confidentiality of the orders is not accidental. The Blocking Rules explicitly protect blocking orders from disclosure. This means the people or organisations being blocked often do not know the specific legal basis for the action against them, cannot access the order text, and have no straightforward path to contest it.

Why Did X Comply So Quickly?

The speed of X's compliance with the Section 69A direction is not accidental — it is the law working as designed.

Non-compliance with a Section 69A order carries serious consequences for intermediaries. An intermediary that fails to comply can face imprisonment of up to seven years for the responsible personnel, plus financial penalties. Given that X operates in India and has staff and assets subject to Indian jurisdiction, non-compliance is not a realistic commercial option.

This is why X used the "country withheld" mechanism rather than removing the account globally. By geo-restricting the account within India while keeping it accessible elsewhere, X fulfilled its legal obligation under Indian law while minimising the impact on users in other countries. The CJP account remains fully accessible outside India. (india.com)

The practical effect for users in India: they see a "country withheld" notice. The practical effect for the movement: its main social media megaphone — which had grown to millions of followers — was cut off from its primary audience overnight, with no appeal and no public explanation.

Can a Section 69A Block Be Challenged in Court?

Technically, yes. In practice, it is difficult.

The landmark case on Section 69A is Shreya Singhal v. Union of India (2015), in which the Supreme Court struck down Section 66A of the IT Act as unconstitutional, but upheld Section 69A. The court's reasoning was that Section 69A contained adequate safeguards: the blocking orders must be reasoned, they must relate to specified grounds, and they are subject to review by a committee. The court held that this made the provision sufficiently narrow to survive constitutional scrutiny. (indconlawphil.wordpress.com, Shreya Singhal analysis)

Critics argue, however, that the Shreya Singhal safeguards are largely theoretical in cases like CJP's. The reasoning for the block has not been made public. The order text has not been disclosed. The affected party has no formal mechanism to obtain the order, review the reasoning, or contest the factual basis before a neutral decision-maker. Civil liberties organisations including the Internet Freedom Foundation have documented that India's Section 69A blocking infrastructure is structurally opaque — orders are issued, executed, and archived in confidential government files with no public accountability. Critics argue that the CJP block raises exactly the due-process questions the Shreya Singhal court said the law was designed to prevent. Whether those arguments would prevail in a legal challenge is an open question, not a settled fact.

Why Can People Outside India Still See CJP's X Account?

Because a Section 69A order is an order of the Indian government, binding on intermediaries operating within Indian jurisdiction. It does not have — and cannot have — legal effect in other countries.

When X/Twitter complies with a Section 69A direction, its legal obligation is to prevent access within India. The standard mechanism for doing this is called country withheld: the platform uses geo-IP detection to serve a "withheld" notice to users whose traffic originates from India, while serving the normal account page to users everywhere else. The account is not deleted. It is not suspended globally. It is specifically hidden from Indian IP addresses. (india.com)

This is also why a VPN can bypass such blocks. A VPN routes traffic through a server in another country, making it appear to originate from outside India. The platform sees a non-Indian IP address and serves the content normally. The government block remains technically in place, but the content is accessible to anyone who routes around the geo-restriction.

For the full story of what the .buzz domain is and why it was not blocked alongside cockroachjantaparty.org, see Cockroach Janta Party Website — Real URL and Verification.

You Are Reading This Because We Exist

You are reading this on cockroachjantaparty.buzz because this site is still live — because 503 people chose to fund it. The government already silenced CJP's X account and their original website under Section 69A — a law designed to be secret, with no public order and no appeal. The badge you buy today is what keeps this page indexed, live, and findable.

The law that blocked CJP does not reach this site. Yet.

The digital badge is the signal that keeps this domain indexed and this article findable. The cockroach survives because it adapts. So does this community.

Buy the digital badge →

Read next

Sources

  1. India Code — Section 69A, Information Technology Act, 2000: indiacode.nic.in
  2. Business Today — "Swatting the Roaches: Cockroach Janata Party website blocked after action on X, Insta handles" (May 23, 2026): businesstoday.in
  3. Al Jazeera — "Cockroach Janta Party's founder says Indian government took website down" (May 23, 2026): aljazeera.com
  4. Internet Democracy Project — Section 69A and the Blocking Rules: internetdemocracy.in
  5. india.com — CJP X account blocked, country withheld (May 2026): india.com
  6. indconlawphil.wordpress.com — Shreya Singhal v. Union of India Supreme Court analysis: indconlawphil.wordpress.com