How Delhi High Court Handles Online Reputation Cases

Delhi HC's Jurisdiction Over Online Defamation

This has made Delhi HC one of the most active courts in India for online reputation litigation, with a well-developed body of case law on interim relief, platform compliance, and anonymous poster identification.

Under Section 20 of the Code of Civil Procedure, a suit can be filed where any part of the cause of action arose, and the Delhi High Court's original side applies that rule to suits above its pecuniary limit. Courts have not read this uniformly in the online context. Some have treated publication to readers in Delhi as enough, wherever the content was uploaded; in Banyan Tree Holding v. A. Murali Krishna Reddy (2009), a passing-off case, a Division Bench of the Delhi High Court required the website to have targeted users in the forum.

For practitioners advising clients outside Delhi, this reach matters, within limits. A client in Chennai or Ahmedabad can sue in Delhi only where Delhi jurisdiction can be shown (the defendant is there, or part of the cause of action arose there), and then on the Delhi High Court's original side only if the suit is valued above ₹2 crore; a smaller suit goes to the Delhi district courts. Where Delhi is a proper forum, the client reaches courts with extensive experience in digital defamation and in orders against platforms including Google, Meta, and Twitter/X.

Why Delhi High Court Is India's Most Significant Online Defamation Forum

Delhi High Court has emerged as the primary forum for online defamation and reputation litigation in India for several interconnected reasons. First, a suit that names Google India Private Limited or another platform's Indian entity can be served, and its orders enforced, without the complications of foreign service.

Second, Delhi HC has developed a body of precedent on online defamation that is more comprehensive than any other Indian court. Judgments from Delhi HC on John Doe orders, platform compliance, and the Right to Be Forgotten have been cited by courts across India and have shaped the standard practice for online reputation litigation nationally.

Third, Delhi HC's urgent listing mechanism is among the most responsive in India. Matters involving irreparable harm — including defamatory content that is actively spreading — can be mentioned before a bench on the day of filing for urgent consideration.

Fourth, Delhi HC's contempt jurisdiction is robust and actively exercised. Where a platform fails to comply with a court order, the court can punish the failure as contempt, with a fine or imprisonment under the Contempt of Courts Act 1971, and can summon the platform's officers to explain it. This is what makes a court order meaningfully different from a takedown request — it carries judicial authority that a platform disobeys at its own risk.

Key Delhi High Court Judgments on Online Defamation (2015–2026)

The case of Swami Ramdev v. Facebook Inc. (CS(OS) 27/2019) was a landmark moment for online defamation jurisprudence in India. In its judgment of 23 October 2019, Delhi HC directed Facebook, Google, YouTube and Twitter to disable access globally, not merely for Indian users, to defamatory videos that had been uploaded from India. The judgment established that a court order to an intermediary can reach the content worldwide where the upload came from India.

In Jorawer Singh Mundy v. Union of India (W.P.(C) 3020/2021), Delhi HC addressed the Right to Be Forgotten in the context of a historical criminal case resolved in the petitioner's favour. The court ordered Google to de-index the petitioner's name from search results that connected him to the historical proceeding, marking one of the clearest applications of Right to Be Forgotten principles to online search in Indian jurisprudence. The judgment drew extensively on the Puttaswamy right to privacy and applied a proportionality analysis.

Against news publications, courts are more cautious. In Bloomberg Television Production Services India v. Zee Entertainment Enterprises (2024), the Supreme Court set aside an ex parte injunction against a news article and held that a pre-trial injunction against journalistic content should be granted only in exceptional cases, where the content is shown to be malicious or palpably false.

On anonymous poster identification, a court can order a platform to disclose the account registration details, linked IP addresses and device identifiers of the account that posted the content, on an application in a suit against an unknown defendant; the John Doe section below sets out how.

John Doe / Ashok Kumar Orders

Where the identity of the online poster is unknown, Delhi HC has consistently granted "John Doe" orders (referred to as Ashok Kumar orders in Indian practice). These orders direct platforms — Google, Meta, Twitter/X — to disclose the IP address and account details of the poster.

Once the poster is identified, the poster can be joined and served as a defendant, and any breach of the court's order pursued as contempt. Delhi HC has also ordered platforms to preserve all data related to an account pending final hearing, preventing the destruction of evidence.

The procedural basis for Ashok Kumar orders lies in Order I Rule 8 of the Code of Civil Procedure, which permits suits against unidentified defendants where there is a common grievance. Courts have extended this rule to online defamation, allowing suits to be filed against "John Doe" with a direction to platforms to provide identity details within a period the court specifies.

Once the poster is identified through the disclosed IP address or account registration details, the complainant can amend the plaint to name the actual defendant, serve summons, and proceed with the full suit. In the interim, the takedown order obtained as part of the John Doe application remains operative, ensuring the content is removed while the identity inquiry is ongoing. This makes anonymity a tactical dead end for online defamers operating against persons willing to seek legal remedy.

John Doe (Ashok Kumar) Orders from Delhi High Court: How They Work

The mechanics of an Ashok Kumar application before Delhi HC are well-established. The applicant files a civil suit for defamation against the anonymous poster and simultaneously files an application under Order XXXIX Rules 1 and 2 CPC for interim injunction and under Order I Rule 8 for John Doe, seeking both a takedown order against the platform and a direction to the platform to disclose the identity of the poster.

The application must demonstrate to the court's satisfaction that the content is prima facie defamatory, that the applicant has been unable to identify the poster through reasonable efforts, and that the platform is technically capable of disclosing the information sought. Evidence of harm — reputational, professional, or financial — strengthens the urgency of the application and speeds the court's consideration.

Platforms served with Ashok Kumar orders are required to comply within the deadline specified in the order, and wilful non-compliance is contempt. A disclosure order typically directs the platform to provide account details including email addresses, linked phone numbers, and IP address logs from the period when the content was posted.

The data disclosed through Ashok Kumar orders can identify anonymous reviewers posting false content on Google Maps, anonymous accounts posting defamatory content on LinkedIn and Twitter, and anonymous contributors to industry-specific forums. The revelation of identity changes the dynamics of the dispute: many posters retract voluntarily and agree to settlement terms once they understand their anonymity has been removed.

Emergency Injunctions at Delhi High Court: The Urgent Track

Delhi HC provides a mechanism for urgent mention of matters that cannot wait for ordinary listing. Where a party can demonstrate that the defamatory content is actively causing ongoing and escalating harm — including content that is going viral, content published immediately before a significant business event, or content making criminal allegations being widely shared — the matter can be mentioned urgently before the bench presiding officer for out-of-turn listing.

In genuinely urgent matters, Delhi HC can grant ex parte interim injunctions — orders obtained without notice to the defendant. The applicant must satisfy the court of three conditions: a strong prima facie case that the content is defamatory; that the balance of convenience favours removal; and that the harm, if not stopped, will be irreparable.

Courts commonly treat reputational harm to a professional, business, or public figure as irreparable — it cannot be adequately compensated in money after the fact, because the damage to trust and relationships caused by defamatory content cannot be undone by a damages award. This makes the "irreparable harm" element relatively straightforward to satisfy in well-documented defamation matters.

The ex parte order, once obtained, is served on the platform, which must act on it within three hours under Rule 3(1)(d) of the IT Rules 2021. The ex parte ad interim order is then taken up at the next hearing, when the defendant or the platform can be heard on whether it should continue as an interim injunction until the suit is decided.

Ex Parte Interim Injunctions

In urgent cases, Delhi HC can grant ex parte interim injunctions — relief obtained without notice to the defendant — where the applicant demonstrates irreparable harm and a prima facie case.

The standard applied is the three-pronged American Cyanamid test: prima facie case, balance of convenience, and irreparable harm. Courts have held that reputational harm to a professional or business is inherently irreparable and difficult to quantify in money.

Importantly, ex parte orders are temporary by nature and subject to confirmation at the next date of hearing. At the confirmation hearing, the defendant has the opportunity to contest the grant of the interim injunction. If the defendant demonstrates that the content is true, constitutes protected opinion, or falls within one of the exceptions in BNS 2023 s.356 (formerly IPC 499), the court may decline to confirm the interim order. Where the court confirms the order, the injunction operates until the suit is decided.

Delhi HC has also exercised its ex parte jurisdiction to issue blocking directions — orders requiring internet service providers to block specific URLs — in cases where the platform is foreign-hosted and has no meaningful Indian presence. These orders are served on ISPs through the Department of Telecommunications, and the targeted URL becomes inaccessible to Indian users even without the source platform's cooperation.

How Delhi High Court Handles Google Non-Compliance

Google India and Google LLC maintain a dedicated legal response team for Indian court orders. A platform that fails to comply within the deadline the order specifies faces contempt proceedings and can be ordered to pay costs.

The drafting, filing and appearances in Delhi HC are handled by RepuLex's partner law firm, Unified Chambers And Associates; RepuLex coordinates the follow-up to ensure court orders translate into actual content removal — not just paper victories.

Where Google has received a valid Delhi HC order and failed to delist within the specified period, the standard escalation path is a contempt petition under Section 12 of the Contempt of Courts Act, 1971. The petition is filed against Google India's designated officer — typically the Managing Director or Legal Counsel on record as the authorised representative. The court can require these individuals to appear in person before the bench to explain non-compliance.

The threat of personal appearance by a senior executive is a powerful compliance driver. In addition to contempt proceedings, the court can award costs against a platform that fails to comply without reasonable justification.

The Right to Be Forgotten at Delhi High Court

The Right to Be Forgotten has been applied by Delhi HC in a series of petitions filed since the Puttaswamy judgment of 2017 established privacy as a fundamental right under Article 21. The key precedent is Jorawer Singh Mundy v. Union of India (2021), in which the court ordered Google to de-index search results connecting the petitioner to a historical criminal case in which he had been fully exonerated. The court applied a proportionality analysis: the continuing prominence of the historic case in search results was disproportionate to any legitimate public interest in its continued accessibility.

Delhi HC has distinguished between categories of historical content in its Right to Be Forgotten jurisprudence. Content concerning persons acquitted of criminal charges, content based on subsequently disproved allegations, and content about private individuals with no ongoing public role have been held appropriate subjects for de-indexing orders. By contrast, content concerning public figures in relation to their exercise of public functions, and content of genuine ongoing public interest, falls outside the scope of the Right to Be Forgotten.

The procedural vehicle for Right to Be Forgotten petitions at Delhi HC is typically a writ petition under Article 226 of the Constitution, seeking a direction to Google and other search engines to de-index specific URLs. The petition must demonstrate the petitioner's identity, the specific URLs sought to be de-indexed, the harm caused by continued indexing, and why no countervailing public interest justifies continued indexing.

The partner law firm structures Right to Be Forgotten applications in conjunction with defamation grounds where both apply — a combined approach that presents the court with multiple independent bases for the relief sought. This is particularly effective where the underlying article may have been accurate at the time of publication but has since become misleading, such as after acquittal, exoneration, or resolution of a business dispute.

Platform Compliance with Delhi HC Orders

Google India and Google LLC maintain a dedicated legal response team for Indian court orders. A platform that fails to comply within the deadline the order specifies faces contempt proceedings and can be ordered to pay costs.

The drafting, filing and appearances in Delhi HC are handled by RepuLex's partner law firm, Unified Chambers And Associates; RepuLex coordinates the follow-up to ensure court orders translate into actual content removal — not just paper victories.

In practice, Delhi HC orders directed at Google are served on Google India's legal team and on the registered agent for Google LLC. Google maintains a process for handling Indian court orders and treats a Delhi HC order as binding on the Indian entity. A de-indexing order reaches beyond Google.in only where the court directs it, as the Delhi High Court did in Swami Ramdev v. Facebook, Inc. (2019) for content uploaded from India.

Where the court grants global reach, it is a significant practical advantage. A person whose name is damaged by content indexed on Google.com — the global default for most Indian users — needs an order that operates on the global index, and the application must ask for that reach expressly.

Pre-Litigation vs Litigation: When to Go to Delhi HC

Not every online defamation matter requires litigation. A substantial proportion of cases resolve at the pre-litigation stage through formal legal notices — either defamation notices to the poster citing BNS 2023 s.356 (formerly IPC 499/500), or formal notices to the platform invoking the IT Rules 2021. Where the poster is identifiable and has a business reputation of their own to protect, or is a small operator without the resources or appetite for litigation, the notice alone is frequently sufficient to secure voluntary removal.

The threshold for moving from notice to court is crossed when: the poster has not removed the content within the demand period and has not responded to the notice; the platform has rejected the notice or failed to act within the statutory period; the content is escalating in reach and the harm is actively compounding; or the poster is anonymous and the John Doe mechanism is required to identify them.

Timing is critical. The longer defamatory content remains accessible, the deeper it indexes in search engines and the more it is shared, cited, and archived by third parties. Early intervention — whether by notice or by court filing — limits the damage. RepuLex advises all clients to take action within the first 72 hours of becoming aware of defamatory content, because the reputational damage compounds exponentially with each day of continued access.

The cost of litigation at Delhi HC — court fees, stamp duty, counsel fees, and ancillary costs — is an important consideration. For matters involving serious reputational or financial harm, the investment in High Court litigation is typically justified by the quality and enforceability of the relief obtained. For lower-stakes content, a focused notice strategy with a clear escalation path may be the more proportionate and cost-effective approach.

Delhi High Court Orders vs Google's Global Policy

Google's standard content removal policy operates under its own Terms of Service and Community Guidelines, which do not automatically treat defamatory content as removable simply because a third party asserts that it is defamatory. Google's legal team reviews defamation claims and will typically request a court order before removing content from Search, particularly where Google's position is that it is a neutral indexer of third-party content.

A Delhi HC order cuts through this standard review process entirely. When Google receives a court order from a competent Indian court directing the removal or de-indexing of specific URLs, it processes the removal as a matter of court compliance rather than policy discretion. The distinction is significant: Google's own review process is discretionary, while court order compliance is mandatory and refusal constitutes contempt of court.

In practice, Delhi HC orders directed at Google are served on Google India's legal team and on the registered agent for Google LLC. Google maintains a dedicated process for handling Indian court orders and treats a Delhi HC order as binding on the Indian entity. A de-indexing order reaches beyond Google.in only where the court directs it, as the Delhi High Court did in Swami Ramdev v. Facebook, Inc. (2019) for content uploaded from India.

Global reach, where the court grants it, is a significant practical advantage for clients dealing with defamatory content. A person whose name and reputation are being damaged by content indexed on Google.com needs an order that reaches the global index, and the application must ask for that reach expressly, on the reasoning the court accepted in Swami Ramdev.