Assess my case

Step-by-step: seek a reverse domain name hijacking finding for a .ch…

Step-by-step: seek a reverse domain name hijacking finding for a .ch. UDRP and ccTLD domain recovery and defense across .ch. Email the firm to assess your case.

You registered a .ch domain years before any complainant had a trademark. Now a corporate legal team has filed a dispute through SWITCH's designated procedure, and you are staring at a complaint that rests on a registration date you can prove predates their rights. That is not just a defense. That may be an opportunity to obtain a reverse domain name hijacking (RDNH) finding – a formal ruling that the complainant brought the proceeding in bad faith to deprive a legitimate registrant of a domain.

To seek a reverse domain name hijacking finding for a .ch domain, a respondent must first defeat the complaint on the merits – demonstrating rights or legitimate interests under the applicable safe harbors – and then show the complainant knew, or should have known, the case could not succeed. The governing procedure for .ch is administered by SWITCH, Switzerland's ccTLD registry, whose dispute-resolution rules apply a test distinct from the UDRP in several respects. An RDNH finding carries no monetary penalty but creates a public record of complainant bad faith.

This guide walks each step, flags the trap it hides, and explains what evidence actually decides the outcome in a SWITCH proceeding.

What governs .ch disputes, and how does RDNH fit into those rules?

SWITCH administers .ch and .li domains under its own dispute-resolution procedure, separate from the UDRP. The SWITCH rules do not mirror the three-element UDRP test word for word, and that gap matters for an RDNH argument. Before building a defense, a respondent must confirm exactly which published SWITCH rules were in force when the complaint was filed – because the governing national procedure applies, and its text controls every element of the analysis.

Why does that distinction matter for RDNH? Because the RDNH concept itself is borrowed from the UDRP tradition: Paragraph 4(b)(i) of the UDRP and the equivalent abuse-of-process language in compatible ccTLD rules identify a complaint filed in bad faith as a basis for a finding against the complainant. In SWITCH proceedings the equivalent provision authorizes a determination that the complaint constitutes an abuse of the procedure. The label may differ; the substance – a complainant weaponizing dispute resolution to acquire a domain it cannot legitimately claim – is the same.

Panels and decision-makers applying ccTLD rules closely related to the UDRP have consistently held that an RDNH finding requires more than losing the dispute. The complainant must have launched the proceeding with knowledge that a core element was missing, or with reckless disregard for the respondent's evident rights. That threshold is significant. Meeting it demands a defense strategy built from the first filing, not retrofitted at the decision stage.

Step 1: Read the complaint precisely – where does it overreach?

The single most important step in any RDNH strategy is a close reading of the complaint itself for the overreach that makes it abusive, not merely unsuccessful. Losing a dispute does not produce an RDNH finding. Bringing a complaint the complainant should have known was deficient does.

Look for these recurring patterns of overreach in .ch complaints:

Document every overreach you identify. Each one is a building block for the RDNH argument you will advance after establishing your own legitimate interest.

Step 2: Build the legitimate-interest record before drafting the response

An RDNH finding is only available once the respondent has won – which means the legitimate-interest defense must be airtight. Paragraph 4(c) of the UDRP, and equivalent safe-harbor language in SWITCH-compatible rules, provides three routes: a bona fide offering of goods or services before any notice of the dispute; being commonly known by the domain name; or legitimate noncommercial or fair use. The trap in this step is treating record-building as a document search rather than a legal analysis.

In our practice, respondents who succeed on legitimate interest – and then go on to obtain an RDNH finding – share a common discipline: they gather primary evidence, not summaries. What does that mean in practice?

One trap is deadline compression. Under SWITCH's procedure, a response must be filed within a set period after commencement, and that window is short. We regularly advise registrants who come to us mid-window that the quality of the evidence record assembled before the first draft of the response is a larger determinant of outcome than the prose of the response itself.

To weigh UDRP against a court action for your case, email info@cognomenlaw.com. An early assessment of the overreach in the complaint is the single step most likely to shape both the defense and the RDNH argument.

Step 3: Evaluate whether the RDNH threshold is actually met

Not every failed complaint supports an RDNH finding. This step is where an honest legal evaluation saves time and credibility. Filing an RDNH argument in a case that does not meet the threshold can actually undermine the legitimacy of the defense – and decision-makers notice when a respondent overstates the case.

The question to ask is specific: what did the complainant know, and when? An RDNH finding requires that the complainant either knew the complaint was deficient or acted with reckless indifference to the respondent's evident rights. Factors that reliably support the threshold include:

Factors that tend not to support the threshold on their own: the complaint was weak on bad faith, the complainant lost on one element, or the complainant's trademark is in a different class. Losing is not bad faith. Knowing you should lose before you file – and filing anyway – is.

In a recent matter involving a .com domain (spring 2025), we secured an RDNH finding for a long-standing registrant whose domain had been registered well before the complainant's trademark existed. The complaint contained no allegation addressing the temporal gap, despite the registration date being visible in the RDDS. The decision-maker specifically cited the complainant's failure to address that obvious deficiency as evidence of bad faith in filing.

How does the SWITCH procedure differ from UDRP, and does that affect the RDNH analysis?

SWITCH operates its own published dispute-resolution process for .ch and .li, and the rules it applies are not identical to the UDRP administered by WIPO, the Forum, CAC, or ADNDRC for gTLD domains. That procedural difference has real consequences for an RDNH strategy.

First, confirm the current SWITCH rules with counsel before filing. The governing national procedure applies, and SWITCH's rules – including the precise elements of the test and the abuse-of-process remedy – are authoritative. Do not assume UDRP precedent translates directly; it informs the analysis but does not bind a SWITCH decision-maker.

Second, the fee structure and timeline for SWITCH proceedings differ from gTLD forum fees. WIPO charges USD 1,500 for a single-member UDRP panel covering one to five domains. SWITCH's own fee schedule is separate and published by the registry; verify the current figure with counsel, as it may differ from that WIPO rate. Response windows, panel appointment mechanics, and appeal routes also follow SWITCH's own rules.

Third, if the same brand name is also registered as a .com or other gTLD domain, the complainant may file parallel proceedings – a UDRP for the .com and a SWITCH complaint for the .ch. That parallel-track risk requires coordinated defense strategy, because a loss in one forum may be used as context (though not as binding precedent) in the other. We have handled cases where coordinating the two response records, and identifying RDNH arguments across both tracks, produced better outcomes than treating each proceeding in isolation.

The practical upshot of the SWITCH/UDRP distinction for RDNH purposes: the abuse-of-process remedy exists in the SWITCH procedure, but its precise contours follow SWITCH's rules, not UDRP boilerplate. Cite UDRP decisions on RDNH as persuasive context, not controlling authority. Build the argument on the text of the SWITCH rules first.

Step 4: Draft the response – structure for both defense and RDNH

A response in a SWITCH proceeding that aims for both a successful defense and an RDNH finding must be structured deliberately. The two arguments are sequential, not parallel: first show the complaint fails on the merits; then, in a separate section, show why the failure was foreseeable to the complainant before filing.

The structure that works in our practice follows this order:

  1. Jurisdictional and procedural baseline. Confirm the applicable SWITCH rules, the relevant registration date, and any preliminary procedural objection (for example, a complaint filed under the wrong procedure version).
  2. Rights and legitimate interests. Lead with the strongest safe harbor. If registration predates the trademark, state it in the first sentence of this section and attach the primary evidence. Do not bury the knockout fact in a later paragraph.
  3. Bad faith in registration – the complainant's failure. Walk through each bad-faith indicator the complainant alleged, and show why the evidence does not support it. If the complaint omits a required element entirely, say so explicitly – that omission is evidence for RDNH.
  4. Reverse domain name hijacking. Open with the specific overreach identified in Step 1. State what the complainant knew or should have known. Identify the public records that made the deficiency apparent before filing. Avoid hyperbole; the argument carries its own weight if the facts support it.
  5. Relief requested. Request denial of the complaint and a finding of abuse of the procedure.

One trap in drafting: the RDNH section is not the place to relitigate the facts of the defense at length. Decision-makers read RDNH arguments more favorably when they are precise and tethered to specific conduct by the complainant – not a general expression of grievance about the filing.

Step 5: Submit and manage the proceeding to the decision

Filing a strong response is not the end of the respondent's active role. Several procedural moments between filing and the decision carry traps that can cost a registrant a favorable outcome.

Supplemental filings. SWITCH procedures, like most domain-dispute rules, do not automatically allow additional submissions after the response. If new material evidence emerges after filing – for example, a newly published trademark filing by the complainant that further confirms the temporal gap – assess immediately whether the procedure permits a supplemental filing and whether that filing actually helps. An unsolicited late submission that reads as argument-padding can irritate a decision-maker and shift attention from the strong core of the defense.

Settlement approach. After a response is filed, some complainants open settlement discussions. A settlement that returns the domain or dismisses the complaint with no RDNH finding may be acceptable in some situations – and unacceptable in others, particularly where the registrant wants the public RDNH record as protection against future abusive filings on the same or related names. We regularly advise registrants on this trade-off, and the right answer depends on the specific facts and the registrant's portfolio strategy.

Decision and implementation. Once a decision issues, the registry implements it within the timeframe set by SWITCH's rules. A denial of the complaint means the domain remains with the registrant. An RDNH finding, if granted, is published alongside the decision. That public record can deter future abusive filings against the same registrant, particularly if the complainant operates in a space where brand owners routinely monitor domain dispute outcomes.

In a recent matter involving a .ch-adjacent domain dispute (autumn 2024), a registrant we advised obtained a denial and an abuse-of-process ruling after the complainant filed on a term the registrant had used commercially for more than a decade – predating the complainant's brand by several years. The ruling cited the complainant's failure to conduct a basic registration-history check before filing as the dispositive factor on the RDNH question.

What evidence actually decides the RDNH outcome?

Decision-makers who grant RDNH findings are not rewarding respondents for making a persuasive argument. They are acting on a record that shows the complainant's bad faith in filing. The evidence that moves the needle falls into three categories.

Temporal evidence. A domain registration date that clearly predates the complainant's earliest trademark rights – the filing date, not just the registration date, of the oldest claimed mark – is the single most powerful piece of evidence in an RDNH case. If that date gap is wide and publicly visible in the RDDS record, the question becomes: why did the complainant file anyway?

Correspondence record. Pre-complaint demand letters, settlement negotiations, or legal correspondence in which the complainant acknowledged the registration date or made an offer to purchase the domain are all probative. A demand letter offering to buy the domain for a fixed sum, followed by a complaint alleging bad faith by the registrant, is a pattern panels and decision-makers find difficult to reconcile.

The complaint's own text. A complaint that omits any analysis of a required element, that misrepresents the trademark registration date, or that cites inapplicable precedent creates its own RDNH record. We have seen complaints that copy-paste allegations from gTLD UDRP filings without adapting them to the SWITCH procedure – a failure that simultaneously weakens the merits case and supports the abuse argument.

What does not decide the RDNH outcome: the size of the complainant, the commercial value of the domain, or the fact that the complainant has trademark rights somewhere. RDNH is about the complainant's conduct in filing this proceeding, not about its general standing as a brand owner.

For an assessment of your domain dispute, contact info@cognomenlaw.com. We can review the complaint, identify the overreach, and advise on whether the evidence supports an RDNH argument in your specific proceeding.

Related at COGNOMEN

Frequently asked questions

How long does it take to seek a reverse domain name hijacking finding for a .ch domain?

The timeline depends on SWITCH's current rules, which set specific windows for the response, panel appointment, and decision. As a general guide, ccTLD proceedings of this kind typically resolve within a few months of the complaint being filed. Verify the precise procedural calendar with counsel before filing, as SWITCH's rules govern and may differ from WIPO UDRP timelines of roughly two months. An RDNH finding issues as part of the final decision, not as a separate ruling.

What does it cost to seek a reverse domain name hijacking finding for a .ch domain at SWITCH?

SWITCH publishes its own fee schedule for .ch and .li dispute proceedings; that schedule is separate from WIPO's gTLD filing fees. The WIPO filing fee for a standard single-member UDRP panel starts at USD 1,500, but .ch disputes follow SWITCH's own rates. Verify current SWITCH fees with counsel, as they are set by the registry and may differ. Legal fees for respondent defense are additional and depend on the complexity of the evidence record and the RDNH argument advanced.

Do I need a lawyer to seek a reverse domain name hijacking finding for a .ch domain?

No rule requires legal representation in a SWITCH proceeding, but an unrepresented respondent faces real risks. Assembling the temporal evidence, invoking the correct safe-harbor provisions, and structuring the RDNH argument as a discrete section of the response – rather than a general complaint about the filing – requires procedural precision. An RDNH finding is only available once the defense succeeds on the merits; a poorly organized response that fails on legitimacy forecloses the RDNH argument entirely, regardless of how strong the underlying facts are.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Related

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.