← sources

Restored in April, blocked again in July: @Nehr_Who returns to the Delhi High Court

source: reddit (reddit:india)published 2026-11-13 06:31ingested 2026-11-14 02:37

extract

[Donate Now](https://internetfreedom.in/donate/?ref=static.internetfreedom.in) # tl;dr On 6 April 2026, the Delhi High Court directed restoration of Kumar Nayan's X account, u/Nher_who, while allowing identified posts to remain temporarily withheld. On 27 July, the account was blocked again, this time on the directions of the Ministry of Information and Broadcasting (MIB). The Union's written submissions disclose that a final order confirming permanent blocking was passed on 9 September. Neither that order nor the interim direction has been supplied to Nayan. His fresh petition challenges the Ministry's jurisdiction, the claimed emergency and the proportionality of blocking an entire account over eight posts. [IFF has provided legal assistance](https://www.internetfreedom.in/delhi-high-court-orders-restoration-of-blocked-x-accounts-of-drnimoyadav-and-nehr_who/?ref=static.internetfreedom.in) to Nayan in contesting restrictions on his account. *Account withholding in India, as recorded in Annexure P-1, pleading page 89.* # Background # The first blocking and the April order Nayan is an electrical engineer and independent political commentator. He created u/Nher_who, known as NehrWho, in October 2016 and uses it for satire and commentary on public affairs. According to his petition, the account had more than 250,000 followers when it was withheld in India. He also received payments through X's creator monetisation programme. The account was an established means of reaching readers and earning income from his work. On 19 March 2026, X informed him that access had been withheld in India pursuant to a direction from the Ministry of Electronics and Information Technology (MeitY) under Section 69A of the Information Technology Act, 2000. He had received neither a hearing nor the blocking order. He sought disclosure and restoration, and approached the Delhi High Court in W.P.(C) 4377/2026. On 6 April, the Delhi High Court directed Nayan to approach the Review Committee and furnish his identity details. Upon verification, MeitY was to identify the allegedly objectionable tweets and provide the blocking order. X was to temporarily withhold those tweets, subject to adjudication by the Committee, and restore the account immediately. All rights and contentions were left open. X confirmed restoration on 8 April, with ten specified posts remaining withheld. The disclosure direction remained unfulfilled, according to Nayan. At a committee meeting on 15 April, Nayan along with Counsel, were shown a redacted order for approximately ten minutes before it was taken back. No copy was supplied. Consequently, compliance was sought through legal notices dated 13 and 29 April. Nayan was then constrained to institute contempt proceedings, CONT.CAS(C) 870/2026. On 14 May, the Delhi High Court issued notice and directed necessary compliance before the next hearing.  # The account is blocked again Ten days after the July hearing, the account was withheld again. At 10:38 pm on 27 July 2026, X informed Nayan of a Section 69A direction from MIB. The Ministry sent a notice on 28 July acknowledging a request to block the account, enclosing eight post URLs and inviting him to an Inter-Departmental Committee hearing the following day. It did not explain how the posts satisfied the statutory grounds for blocking. Nayan missed the 29 July hearing because of a medical emergency in his family and even supplied medical records and sought another opportunity. After rescheduling, he participated on 7 August. His petition alleges that officials questioned his entitlement to comment on geopolitical affairs and accused him of masquerading as an Indian citizen. While the  Union says the evidence was discussed with him and his response considered.  He requested the blocking order on 7 August and again on 16 August. In the latter email, he also disputed the attribution of one listed post. The Union's written submissions dated 1 October disclose that the Secretary, MIB, approved permanent blocking on 9 September under Rule 16(4) of the IT Rules, 2021. They expressly acknowledge that the order has not been supplied to him. # Analysis # Section 69A requires reasons and procedural safeguards [Section 69A](https://www.indiacode.nic.in/bitstream/123456789/1999/1/A2000-21%20%281%29.pdf?ref=static.internetfreedom.in) authorises blocking on specified grounds, including sovereignty and integrity, national security, friendly relations with foreign States, and public order. Reasons must be recorded in writing, and the prescribed procedure and safeguards must be followed. The provision does not confer a general power to remove speech because the government considers it inaccurate or objectionable. The particular statutory ground must be established. In [Shreya Singhal v. Union of India](https://indiankanoon.org/doc/110813550/?ref=static.internetfreedom.in), decided on 24 March 2015, the Supreme Court upheld Section 69A and the Blocking Rules, 2009 by reference to those limits and safeguards. The Court recognised the hearing available to an identifiable originator and the importance of recorded reasons which could be challenged before a High Court under Article 226. The legality of a particular blocking direction therefore depends on how that power has been exercised. Nayan's case concerns an admitted government blocking direction. It is distinct from a platform suspending an account under its own terms, and from the Section 79(3)(b) intimations issued through the Sahyog portal that feature in other recent litigation. The source of the restriction matters because it identifies the authority that must justify its action and the procedure against which it must be tested. # What the eight posts concern The Union invokes India's friendly relations with foreign States. Its submissions describe the posts as unverified, misleading and distorted accounts of foreign policy involving the United States, Israel, Iran, and Venezuela. It says they could create distrust regarding India's diplomatic positions and, considered together, portray its external engagements as coerced or lacking legitimacy. A post dated 7 February satirises ministerial answers about Russian oil and India-US trade negotiations. Posts from March criticise the government's response to events in West Asia. A post dated 6 June shares a clip of Shekhar Suman mocking foreign policy. Other posts concern diplomatic engagements and allegations involving foreign leaders. In his written submissions, served on 2 October, Nayan characterises this material as political criticism and satire. Relying on [S. Rangarajan v. P. Jagjivan Ram](https://indiankanoon.org/doc/341773/?ref=static.internetfreedom.in) and Shreya Singhal, he argues that the apprehended danger must have a proximate and direct connection with the expression. A conclusion that posts could generate distrust leaves unanswered how they endanger friendly relations within the meaning of Section 69A. Criticism of the government's conduct of foreign affairs cannot be excluded from constitutional protection merely because it concerns another country. # MIB must establish its jurisdiction The second blocking also raises a question about which Ministry can exercise the power. The March action came through MeitY under the Blocking Rules, 2009. The July action came through MIB under [Part III of the IT Rules, 2021](https://www.meity.gov.in/static/uploads/2024/02/IT-Intermediary-Rules-2021-updated-on-28.10.2022-2.pdf?ref=static.internetfreedom.in), which applies to publishers of news and current affairs and publishers of online curated content. Nayan submits that he is an individual user of a social media intermediary and falls outside those categories. In fact, the Union describes him as the account holder without alleging that he is a publisher governed by Part III. Rule 8 extends specified provisions to intermediaries, but they argue that this permits implementation of directions concerning publishers' content; it does not bring every user within MIB's jurisdiction. The distinction requires adjudication. Invoking Section 69A does not dispense with establishing the authority to act through the particular Rules relied upon. # The emergency and the notice require scrutiny Rule 16 permits an interim direction without a hearing in an emergency where no delay is acceptable. The request must then be placed before the Committee within forty-eight hours. The Union says it received the request and issued the interim order on 27 July, and the Committee considered it on 29 July. The petitioner's objection concerns the basis for invoking an emergency over this material. Six of the eight posts are dated between 31 January and 15 March 2026, before the first blocking. The remaining two are dated 4 and 6 June. Even the newest was over seven weeks old when emergency powers were invoked. Nayan's submissions question what made immediate blocking of the entire account necessary on 27 July. The notice recorded the request to block the account, but supplied no reasons for treating the eight posts as unlawful or extending the restriction to all other content. It is worth noting that the subsequent reliance on recurrence, cumulative effect and audience size was not put to him. They rely on [Gorkha Security Services v. Government of NCT of Delhi](https://indiankanoon.org/doc/83485553/?ref=static.internetfreedom.in), which requires a notice to make the grounds and proposed action. The Union maintains that he received a hearing but did not submit the further written response he had offered to provide. # Disclosure is necessary for an effective remedy The Union claims confidentiality under Rule 16 of the Blocking Rules, 2009, read with Rule 8(3) of the IT Rules, 2021. It offers, if directed by the Court, to show Nayan the order at an in-person meeting against an undertaking of confidentiality. However, it is Nayan’s stance that Rule 8(3) preserves other laws and remedies, while Part III contains no corresponding confidentiality provision. The Delhi High Court's order in [Tanul Thakur](https://indiankanoon.org/doc/127574175/?ref=static.internetfreedom.in), dated 11 May 2022, required the blocking order to be furnished after redacting material concerning third parties. Nayan's own order of 6 April contains an express disclosure direction. Showing an order briefly leaves the affected person unable to examine its reasoning properly, compare it with the notice and prepare a challenge.. The authorities on confidentiality require care. In [Sublime Software](https://indiankanoon.org/doc/24531884/?ref=static.internetfreedom.in), decided on 2 July 2024, the Delhi High Court accepted confidentiality in a challenge concerning the blocking of the Briar messaging app on national-security grounds and dismissed the petition. That judgment does not direct disclosure. In Nayan's case, the Court must examine the confidentiality claim against the justification advanced for this restriction and the earlier direction to furnish his blocking order. The earlier proceedings were known to the Committee. The Union records that MeitY's representative informed it of the previous blocking and restoration following the April order. Nayan relies on this knowledge, the change of Ministry and the timing after the contempt hearing to allege an improper exercise of power. To this end, Nayan’s petition seeks the complete orders and committee minutes, rather than accepting the second restriction as disconnected from the first. # Blocking an account also restricts lawful and future speech The Union argues that blocking individual posts would inadequately address a recurring pattern. It relies on the account's large audience and says Nayan remains free to use other means of expression, including new accounts. This gives insufficient weight to the readership built since 2016. Starting another account does not restore access to that audience or to the archive made unavailable in India. The restriction also reaches material beyond the eight posts. Readers lose access to lawful commentary, while future expression through the account is withheld before it exists. Nayan challenges this as a disproportionate prior restraint. Reliance in this regard is placed on Rule 15(3), which confines directions to specified content or an enumerated list and prohibits requiring an entity to cease operations. It is contended that the emergency power cannot authorise a wider restriction. In fact, the interim relief sought in the Petition, being opposed by the Union, is to the effect of balancing rights while adjudication takes its course. Nayan asks for restoration of the account while the eight URLs remain withheld, without conceding their illegality. It is also the practical course followed in April. The Union’s characterisation of this interim measure as final relief appears to be based on a misappreciation of the final relief, *i.e.*, quashing of the blocking order itself, sought. # Action On 10 September 2026, the Delhi High Court issued notice in the fresh petition, W.P.(C) 13241/2026, and allowed the Union time to take instructions. On 16 September, the Court directed both sides to file written submissions. Nayan’s second petition will now come up on 23 November 2026. The separate contempt proceedings concern compliance with the earlier disclosure direction will now come up on 27 November. The petition seeks restoration, quashing of the blocking directions and production of the relevant records. These requests for disclosure recur across IFF's work. In [Ila Kazmi's case](https://www.internetfreedom.in/delhi-hc-orders-production-of-secret-sahyog-takedown-orders-behind-journalist-ila-kazmis-instagram-block/?ref=static.internetfreedom.in), concerning a separate Sahyog restriction, the Delhi High Court directed production of the takedown orders on 9 October. Our [23 October update](https://internetfreedom.in/instagram-restores-four-protest-reporters-accounts-after-legal-notices-but-wont-name-the-legal-requirements-it-cited/?ref=static.internetfreedom.in) on four Instagram accounts also recorded restorations without an adequate explanation of the restrictions, and a subsequent renewed withholding of Journo Mirror. Restoration alone leaves the legality of the original action unresolved when its source and reasons remain undisclosed. IFF's position is that a government restricting expression must identify its legal authority, justify the extent of the restriction and furnish the decision necessary for an effective challenge. In Nayan's case, those requirements will be tested against a second permanent block imposed within months of a restoration order. The Court's determination remains pending. # Important documents 1. Union of India's written submissions dated 1 October 2026. \[[Link](https://drive.google.com/file/d/1zx6502rJXO8C8PnHLexFM8QblGzvbeBF/view?usp=drive_link&ref=static.internetfreedom.in)\] 2. Petitioner's written submissions served on 2 October 2026. \[[Link](https://drive.google.com/file/d/1K5tKOkIhEmsl42a2hmX2Xot_1UHQwBLK/view?usp=drive_link&ref=static.internetfreedom.in)\] 3. Delhi High Court order dated 10 September 2026. \[[Link](https://drive.google.com/file/d/1hHM5xEkWQblmoMlQUJK-AbHTjuPGrmy4/view?usp=drive_link&ref=static.internetfreedom.in)\] 4. Delhi High Court order dated 16 September 2026. \[[Link](https://drive.google.com/file/d/1hRyalFPxNv5oiXxKajrVLEy4NGcofBPp/view?usp=drive_link&ref=static.internetfreedom.in)\] [Donate Now](https://internetfreedom.in/donate/?ref=static.internetfreedom.in)

retained text (truncated)

[Donate Now](https://internetfreedom.in/donate/?ref=static.internetfreedom.in)

# tl;dr

On 6 April 2026, the Delhi High Court directed restoration of Kumar Nayan's X account, u/Nher_who, while allowing identified posts to remain temporarily withheld. On 27 July, the account was blocked again, this time on the directions of the Ministry of Information and Broadcasting (MIB). The Union's written submissions disclose that a final order confirming permanent blocking was passed on 9 September. Neither that order nor the interim direction has been supplied to Nayan. His fresh petition challenges the Ministry's jurisdiction, the claimed emergency and the proportionality of blocking an entire account over eight posts. [IFF has provided legal assistance](https://www.internetfreedom.in/delhi-high-court-orders-restoration-of-blocked-x-accounts-of-drnimoyadav-and-nehr_who/?ref=static.internetfreedom.in) to Nayan in contesting restrictions on his account.

*Account withholding in India, as recorded in Annexure P-1, pleading page 89.*

# Background

# The first blocking and the April order

Nayan is an electrical engineer and independent political commentator. He created u/Nher_who, known as NehrWho, in October 2016 and uses it for satire and commentary on public affairs. According to his petition, the account had more than 250,000 followers when it was withheld in India. He also received payments through X's creator monetisation programme. The account was an established means of reaching readers and earning income from his work.

On 19 March 2026, X informed him that access had been withheld in India pursuant to a direction from the Ministry of Electronics and Information Technology (MeitY) under Section 69A of the Information Technology Act, 2000. He had received neither a hearing nor the blocking order. He sought disclosure and restoration, and approached the Delhi High Court in W.P.(C) 4377/2026.

On 6 April, the Delhi High Court directed Nayan to approach the Review Committee and furnish his identity details. Upon verification, MeitY was to identify the allegedly objectionable tweets and provide the blocking order. X was to temporarily withhold those tweets, subject to adjudication by the Committee, and restore the account immediately. All rights and contentions were left open. X confirmed restoration on 8 April, with ten specified posts remaining withheld.

The disclosure direction remained unfulfilled, according to Nayan. At a committee meeting on 15 April, Nayan along with Counsel, were shown a redacted order for approximately ten minutes before it was taken back. No copy was supplied. Consequently, compliance was sought through legal notices dated 13 and 29 April. Nayan was then constrained to institute contempt proceedings, CONT.CAS(C) 870/2026. On 14 May, the Delhi High Court issued notice and directed necessary compliance before the next hearing. 

# The account is blocked again

Ten days after the July hearing, the account was withheld again. At 10:38 pm on 27 July 2026, X informed Nayan of a Section 69A direction from MIB. The Ministry sent a notice on 28 July acknowledging a request to block the account, enclosing eight post URLs and inviting him to an Inter-Departmental Committee hearing the following day. It did not explain how the posts satisfied the statutory grounds for blocking.

Nayan missed the 29 July hearing because of a medical emergency in his family and even supplied medical records and sought another opportunity. After rescheduling, he participated on 7 August. His petition alleges that officials questioned his entitlement to comment on geopolitical affairs and accused him of masquerading as an Indian citizen. While the  Union says the evidence was discussed with him and his response considered. 

He requested the blocking order on 7 August and again on 16 August. In the latter email, he also disputed the attribution of one listed post. The Union's written submissions dated 1 October disclose that the Secretary, MIB, approved permanent blocking on 9 September under Rule 16(4) of the IT Rules, 2021. They expressly acknowledge that the order has not been supplied to him.

# Analysis

# Section 69A requires reasons and procedural safeguards

[Section 69A](https://www.indiacode.nic.in/bitstream/123456789/1999/1/A2000-21%20%281%29.pdf?ref=static.internetfreedom.in) authorises blocking on specified grounds, including sovereignty and integrity, national security, friendly relations with foreign States, and public order. Reasons must be recorded in writing, and the prescribed procedure and safeguards must be followed. The provision does not confer a general power to remove speech because the government considers it inaccurate or objectionable. The particular statutory ground must be established.

In [Shreya Singhal v. Union of India](https://indiankanoon.org/doc/110813550/?ref=static.internetfreedom.in), decided on 24 March 2015, the Supreme Court upheld Section 69A and the Blocking Rules, 2009 by reference to those limits and safeguards. The Court recognised the hearing available to an identifiable originator and the importance of recorded reasons which could be challenged before a High Court under Article 226. The legality of a particular blocking direction therefore depends on how that power has been exercised.

Nayan's case concerns an admitted government blocking direction. It is distinct from a platform suspending an account under its own terms, and from the Section 79(3)(b) intimations issued through the Sahyog portal that feature in other recent litigation. The source of the restriction matters because it identifies the authority that must justify its action and the procedure against which it must be tested.

# What the eight posts concern

The Union invokes India's friendly relations with foreign States. Its submissions describe the posts as unverified, misleading and distorted accounts of foreign policy involving the United States, Israel, Iran, and Venezuela. It says they could create distrust regarding India's diplomatic positions and, considered together, portray its external engagements as coerced or lacking legitimacy.

A post dated 7 February satirises ministerial answers about Russian oil and India-US trade negotiations. Posts from March criticise the government's response to events in West Asia. A post dated 6 June shares a clip of Shekhar Suman mocking foreign policy. Other posts concern diplomatic engagements and allegations involving foreign leaders.

In his written submissions, served on 2 October, Nayan characterises this material as political criticism and satire. Relying on [S. Rangarajan v. P. Jagjivan Ram](https://indiankanoon.org/doc/341773/?ref=static.internetfreedom.in) and Shreya Singhal, he argues that the apprehended danger must have a proximate and direct connection with the expression. A conclusion that posts could generate distrust leaves unanswered how they endanger friendly relations within the meaning of Section 69A. Criticism of the government's conduct of foreign affairs cannot be excluded from constitutional protection merely because it concerns another country.

# MIB must establish its jurisdiction

The second blocking also raises a question about which Ministry can exercise the power. The March action came through MeitY under the Blocking Rules, 2009. The July action came through MIB under [Part III of the IT Rules, 2021](https://www.meity.gov.in/static/uploads/2024/02/IT-Intermediary-Rules-2021-updated-on-28.10.2022-2.pdf?ref=static.internetfreedom.in), which applies to publishers of news and current affairs and publishers of online curated content.

Nayan submits that he is an individual user of a social media intermediary and falls outside those categories. In fact, the Union describes him as the account holder without alleging that he is a publisher governed by Part III. Rule 8 extends specified provisions to intermediaries, but they argue that this permits implementation of directions concerning publishers' content; it does not bring every user within MIB's jurisdiction. The distinction requires adjudication. Invoking Section 69A does not dispense with establishing the authority to act through the particular Rules relied upon.

# The emergency and the notice require scrutiny

Rule 16 permits an interim direction without a hearing in an emergency where no delay is acceptable. The request must then be placed before the Committee within forty-eight hours. The Union says it received the request and issued the interim order on 27 July, and the Committee considered it on 29 July. The petitioner's objection concerns the basis for invoking an emergency over this material.

Six of the eight posts are dated between 31 January and 15 March 2026, before the first blocking. The remaining two are dated 4 and 6 June. Even the newest was over seven weeks old when emergency powers were invoked. Nayan's submissions question what made immediate blocking of the entire account necessary on 27 July.

The notice recorded the request to block the account, but supplied no reasons for treating the eight posts as unlawful or extending the restriction to all other content. It is worth noting that the subsequent reliance on recurrence, cumulative effect and audience size was not put to him. They rely on [Gorkha Security Services v. Government of NCT of Delhi](https://indiankanoon.org/doc/83485553/?ref=static.internetfreedom.in), which requires a notice to make the grounds and proposed action. The Union maintains that he received a hearing but did not submit the further written response he had offered to provide.

# Disclosure is necessary for an effective remedy

The Union claims confidentiality under Rule 16 of the Blocking Rules, 2009, read with Rule 8(3) of the IT Rules, 2021. It offers, if directed by the Court, to show Nayan the order at an in-person meeting against an undertaking of confidentiality. However, it is Nayan’s stance that Rule 8(3) preserves other laws and remedies, while Part III contains no corresponding confidentiality provision.

The Delhi High Court's order in [Tanul Thakur](https://indiankanoon.org/doc/127574175/?ref=static.internetfreedom.in), dated 11 May 2022, required the blocking order to be furnished after redacting material concerning third parties. Nayan's own order of 6 April contains an express disclosure direction. Showing an order briefly leaves the affected person unable to examine its reasoning properly, compare it with the notice and prepare a challenge..

The authorities on confidentiality require care. In [Sublime Software](https://indiankanoon.org/doc/24531884/?ref=static.internetfreedom.in), decided on 2 July 2024, the Delhi High Court accepted confidentiality in a challenge concerning the blocking of the Briar messaging app on national-security grounds and dismissed the petition. That judgment does not direct disclosure. In Nayan's case, the Court must examine the confidentiality claim against the justification advanced for this restriction and the earlier direction to furnish his blocking order.

The earlier proceedings were known to the Committee. The Union records that MeitY's representative informed it of the previous blocking and restoration following the April order. Nayan relies on this knowledge, the change of Ministry and the timing after the contempt hearing to allege an improper exercise of power. To this end, Nayan’s petition seeks the complete orders and committee minutes, rather than accepting the second restriction as disconnected from the first.

# Blocking an account also restricts lawful and future speech

The Union argues that blocking individual posts would inadequately address a recurring pattern. It relies on the account's large audience and says Nayan remains free to use other means of expression, including new accounts. This gives insufficient weight to the readership built since 2016. Starting another account does not restore access to that audience or to the archive made u

document fetched 2026-11-14 00:26 · canonical https://reddit.com/r/india/comments/1xv0mbv/restored_in_april_blocked_again_in_july_nehr_who