Did Dipke Deactivate the CJP Website? The OpIndia Claim, Fact-Checked

When CJP's website cockroachjantaparty.org went offline on May 23, 2026, Abhijeet Dipke and multiple mainstream outlets said the government blocked it. OpIndia published an alternative theory: that Dipke deactivated his own site. We fact-check the technical claim.

What OpIndia Claims — and the One Technical Detail It Relies On

OpIndia's article (read it here) constructs its case on three observations: (1) the browser error DNS_PROBE_FINISHED_NXDOMAIN appears when trying to reach cockroachjantaparty.org; (2) a WHOIS lookup shows the domain status as "clientHold"; and (3) no public government order under Section 69A has been published. From those three data points, OpIndia concludes that Dipke voluntarily deactivated his own site.

The argument rests almost entirely on point two — the "clientHold" status code. The other two observations are either expected consequences of clientHold (DNS_PROBE_FINISHED_NXDOMAIN is what happens when a domain is placed on clientHold) or a misunderstanding of how Section 69A works (see below). So the factual question is: does clientHold mean the domain owner switched off their own site?

What "clientHold" Actually Means (And Who Can Set It)

ClientHold is an ICANN/EPP (Extensible Provisioning Protocol) status code. When a domain is placed on clientHold, it is removed from the DNS zone file — which is exactly why browsers return a DNS error. The domain is not deleted; it simply stops resolving.

The critical technical fact that OpIndia's piece does not address: clientHold is set by the domain registrar, not by the domain owner. According to registrar documentation on clientHold (20i registrar docs), the status is applied in three scenarios: unpaid renewal bills, failure to verify WHOIS contact details, and compliance holds — including government orders relayed through the registrar. A registrant who wants to take their own site offline has many simpler options available to them: deleting DNS records, letting the domain expire, pointing the nameservers to nothing. Triggering a clientHold requires contacting or receiving an instruction from the registrar. The domain owner does not set this flag directly.

This is not a minor technical nuance. It is the load-bearing fact in the entire OpIndia argument. The "clientHold" status is precisely the mechanism a registrar would use to implement a government compliance order. Its presence is, if anything, consistent with the government-block story — not evidence against it.

The Timeline That OpIndia Ignores

OpIndia's self-deactivation theory requires Dipke to have voluntarily killed his own flagship website on May 23, 2026. Look at what else happened that same day and in the two days before it.

May 21, 2026: MeitY issued directives under Section 69A citing national security concerns, directing X/Twitter to withhold CJP's account within India. (Business Today) The X withheld notice is publicly visible to Indian users — it is not a matter of dispute.

May 23, 2026: On the same day cockroachjantaparty.org went offline, CJP's Instagram account was hacked and access was lost, Dipke's personal Instagram was hacked, and the CJP backup account was suspended. Business Today specifically reported that MeitY issued a website blocking directive. (Business Today)

The OpIndia theory asks us to believe that Dipke chose — voluntarily — to take down his flagship website on the exact same day his Instagram was hacked, his backup account was suspended, and his personal account was compromised. The coincidence required by that theory is not plausible. The government-block theory requires no coincidence at all: it is a continuation of enforcement actions that had already been confirmed two days earlier.

Dipke's own public statement at the time was unambiguous: "The government has taken down our iconic website — 10 Lakh cockroaches had signed up." (Business Today) He also characterised the broader crackdown as "dictatorial behaviour," asking: "Why is the government so scared of cockroaches?" (The Tribune)

What Multiple Mainstream Outlets Reported

OpIndia is the sole outlet advancing the self-deactivation theory. Every other news organisation that covered the story reported the website as government-blocked.

Al Jazeera reported that Dipke "said on X on Saturday that the government had taken down the 'iconic' website." (Al Jazeera) Business Today confirmed MeitY issued the blocking directive. (Business Today) WION, Deccan Herald, and Telangana Today all carried the same reporting: the website was blocked by the government.

The Internet Freedom Foundation condemned the action, characterising it as an example of "India's opaque digital censorship infrastructure." (IFF on X) IFF monitors Section 69A enforcement; its characterisation of this as state-directed censorship is grounded in documented pattern recognition, not speculation.

Dipke's direct quote on the crackdown — "Why is the government so scared of cockroaches?" (The Tribune) — is consistent with someone fighting a government action, not with someone who turned off his own site.

The "Voluntary Deactivation" Theory Doesn't Survive Dipke's Own Actions

If Dipke wanted to take his website offline, the logical subsequent behaviour would be silence, withdrawal, or at least a reduction in public activity. That is not what happened.

After cockroachjantaparty.org went down, cockroachjantaparty.buzz — the site you are reading — went up as the primary community presence. Dipke continued giving media interviews. The "Cockroaches never die" message was broadcast publicly. He continued pushing back on every platform available to him.

This is not the behaviour of someone who voluntarily shut down their flagship digital presence. Registering a backup domain, continuing the fight publicly, and telling every media outlet that the government took the site down — these actions are incoherent if Dipke himself deactivated the site. They are entirely coherent if the government blocked it and Dipke is responding.

The Broader Pattern — Section 69A, NIA Probe Demands, Instagram Hack

This website takedown is not an isolated incident. See the full blocked accounts timeline for every government action in order.

MeitY's actions followed a sustained escalation. BJP politicians including Rajeev Chandrasekhar called for an NIA probe into CJP over alleged cross-border influence — a claim made without evidence. (Full BJP NIA probe claim breakdown here.) The X/Twitter withheld notice — which is publicly visible — confirms Section 69A was already in use against CJP before the website went down.

A detail that is particularly important here: India's Section 69A blocking orders are legally confidential. The government is under no obligation to publish them. The Information Technology (Procedure and Safeguards for Blocking for Access of Information by Public) Rules, 2009 explicitly protect blocking orders from disclosure. This means the absence of a published government order is not evidence that no order exists — it is the legally mandated expected outcome. The IFF has documented this structural opacity extensively: blocking orders in India are issued, executed, and kept confidential as a matter of standard practice. (IFF source)

OpIndia uses the absence of a published order as a pillar of its argument. That pillar collapses once you understand how Section 69A works.

The OpIndia claim rests on a misreading of a DNS status code and the absence of a public order that, under Section 69A, the government was never required to publish. The convergence of platform removals, the simultaneous X/Twitter withheld notice, and Dipke's own account consistently point to government action. You can check the current status of all CJP platforms at Where Is CJP Now?