Step-by-step: defend a generic-word .ch domain

Step-by-step: defend a generic-word .ch domain. UDRP and ccTLD domain recovery and defense across .ch. Email the firm to assess your case. Transparent fees, re…

You hold a .ch domain built around an ordinary word – a product category, a common noun, a descriptive term. Then a complaint lands. The claimant is a brand owner who registered a trademark over that word after you registered the domain, or one who now argues the name was always theirs. You have 20 days to respond under the applicable rules before a default is entered against you. What matters is how you use those 20 days.

Defending a generic-word .ch domain turns on one question: do you have a legitimate interest in the name, and can you document it? Swiss .ch domain disputes are administered through SWITCH, Switzerland's national registry, applying its own dispute-resolution rules – not the UDRP directly, though the conceptual overlap is substantial. The respondent who holds a generic-word .ch registration and can show descriptive, commercial, or good-faith use of the term will generally prevail; the one who cannot will lose the name.

This guide follows the seven steps a registrant should take, in order, to build the strongest possible defense. Each step identifies the trap hidden inside it.

Step 1: What rules actually govern a .ch dispute?

SWITCH, the registry for .ch (and .li), operates its own dispute-resolution procedure rather than the UDRP. A complainant challenging your .ch domain files under SWITCH's published rules. Those rules share the UDRP's conceptual architecture – confusion, legitimate interest, bad faith – but the text, the standards, and the forum are specific to Switzerland. The applicable rules are SWITCH's current dispute-resolution regulations; you or your counsel should pull the current version directly from the SWITCH registry, because the rules can be revised and any outdated copy creates risk.

The trap in this step is assuming your UDRP knowledge fully translates. It does not. The UDRP requires that a domain was registered and used in bad faith – a cumulative test. Some national procedures read that limb as "registered or used" abusively, a lower bar that advantages complainants. Understanding exactly how SWITCH reads the bad-faith element in your case is not a detail to defer.

SWITCH also does not use WIPO's roster of panelists directly. The dispute is decided by an expert appointed under SWITCH's own procedure. If you are accustomed to WIPO or the Forum's submission formats, you will need to adjust. Procedural non-compliance is one of the easiest ways to weaken a defense before the substantive arguments are ever read.

If you have received a SWITCH dispute notice and are unsure which rules apply, contact info@cognomenlaw.com for an early assessment before your response window closes.

Step 2: Is the disputed word actually generic – and what does that buy you?

Proving that a word is generic or descriptive is the foundation of every legitimate-interest defense in a .ch domain dispute. Generic-word registrations occupy a privileged position: a claimant cannot monopolize a common noun, a product category, or a geographic descriptor by registering it as a trademark and then pursuing every domain registrant who holds the same string.

But "generic" is not self-defining. You need to demonstrate it. What evidence supports the argument?

• Third-party usage: industry publications, dictionaries (in German, French, Italian, or English, depending on the relevant Swiss linguistic context), and competitor websites that use the word in an ordinary descriptive sense.
• Trademark register evidence: showing the complainant's mark is weak, diluted by third-party registrations, or not registered at all in the relevant class.
• Your own registration date: if your .ch predates the complainant's trademark, the bad-faith-at-registration argument is structurally very difficult for the claimant to sustain.
• Domain registration intent: your own contemporaneous evidence – business plans, correspondence, invoices, website archives – showing you registered the word for its descriptive value, not to target the complainant.

The trap: assuming that because the word is obviously generic to you, no argument is needed. Experts are not Swiss-market natives for every industry. An assertion without documentation will not carry the point. Panels have consistently held that a respondent bears the evidential burden of production once a prima facie case is established – and a facially weak claim still establishes that prima facie case.

Step 3: How do the Paragraph 4(c) safe-harbor analogues apply here?

The UDRP's Paragraph 4(c) safe harbors enumerate the circumstances that demonstrate a respondent's legitimate interest: a bona fide offering of goods or services before notice of the dispute, being commonly known by the domain name, and legitimate noncommercial or fair use. SWITCH's procedure contains conceptually equivalent safe harbors, though the precise text differs.

For a generic-word .ch registration, the most useful analog is the bona fide offering category. You do not need to have been trading under the exact domain. You need to show that the generic term was the rational, commercially grounded reason for the registration – and that this reason existed before you had any notice of the complainant's claim.

How do you build that record? Concrete documentation is everything.

• Website archives (Wayback Machine captures, hosting logs, or your own backups) showing live content predating the complaint.
• Business correspondence mentioning the domain or the descriptive term in a commercial context.
• Registration platform records showing the registration date and the registrant's stated business at that time.
• Evidence of ongoing use: analytics data, inbound links, revenue attributable to traffic through the domain.

The trap in this step is the gap between what you know and what you can prove. We regularly advise registrants who are confident in the legitimacy of their use but whose documentation is scattered or incomplete. A defense built on "I can explain this to the panel" instead of "here is the exhibit" is a defense that underperforms. Assemble the documentary record first; write the argument around what it proves.

A second trap is the timing of use. A legitimate-interest defense based on a bona fide offering is strongest when the use predates notice of the dispute. Panels have found that use initiated after receipt of a demand letter – however genuine – attracts skepticism. If you only began using the domain after being put on notice, your defense will need to address that sequence directly.

Step 4: How do you assess the complainant's actual strength?

Before you write a word of your defense, you need an honest read of the complainant's case. A generic-word complaint that looks aggressive can still carry real legal weight if the facts align. And an apparently weak complaint can reveal a stronger record on closer analysis.

Assess the following, in order:

1. Trademark registration date versus your domain registration date. If the trademark postdates your domain, the bad-faith-at-registration limb is almost certainly unavailable to the complainant. That is a structural gap in their case, not just a factual point – it goes to whether the policy's bad-faith element can be satisfied at all.
2. The scope of the trademark registration. Is it a word mark covering the exact string, or a device/stylized mark? A stylized mark offers a weaker basis for a domain challenge than a plain-word registration.
3. Whether the complainant has filed UDRP or other domain disputes before. A pattern of aggressive domain complaints is relevant to a Reverse Domain Name Hijacking argument.
4. The commercial relationship between the parties, if any. Prior dealings, licensing discussions, or even a prior demand letter can inform both the strength of the complaint and whether the complainant knew of your legitimate interest before filing.

In our practice, we have seen complainants file against long-held generic .ch domains on the strength of a trademark registered in a jurisdiction entirely unconnected to the domain's use. That does not make the claim frivolous on its face, but it does set up a clear defense. Know what you are working with before you file the response.

Step 5: When is an RDNH finding realistic – and how do you position for one?

Reverse Domain Name Hijacking is a finding that the complainant brought the proceeding in bad faith – essentially, to strip a legitimate registrant of a domain the claimant has no genuine right to. An RDNH finding carries no monetary penalty, but it is a public record in the decision and it damages the complainant's credibility for future proceedings.

When is RDNH realistic in a .ch or SWITCH-type dispute? The strongest fact patterns share most of these features:

• The complainant's trademark was registered after the respondent's domain.
• The generic or descriptive nature of the term was obvious at the time of filing – the complainant could not have genuinely believed the domain was registered to target their mark.
• The complainant (or its counsel) had actual or constructive knowledge of the respondent's legitimate use before filing.
• The complaint contains misrepresentations about the respondent's use or about the relationship between the domain and the mark.

Positioning for RDNH requires a specific tactical choice. The argument must be made explicitly in the response – experts do not typically raise it on their own initiative. And it must be grounded in the record. An RDNH allegation without documentary support is worse than no allegation at all: it can read as a distraction from the substantive defense, and it risks alienating an expert who might otherwise have been sympathetic.

We have built respondent defenses specifically around the RDNH angle in cases where a later-filed trademark was used as a pretext to attack a legitimately held generic registration. The argument is distinct from the underlying legitimate-interest defense, but it reinforces it: if we can show not only that our client had rights, but that the complainant knew it, the entire complaint collapses as an abuse of process.

If you believe the complaint against your .ch domain is opportunistic or based on a post-registration trademark, email info@cognomenlaw.com to discuss whether an RDNH position is available in your case.

Step 6: What is the format and strategy for the written response?

The written response is your one substantive submission. Under most domain dispute procedures, there is no oral hearing and no right to file supplemental material without the expert's leave. Everything the expert will read from your side is in that document. Format and argumentation structure matter more than registrants usually expect.

A well-structured response to a generic-word .ch complaint covers, in order:

1. A procedural summary: registration date, registration history, and a one-paragraph factual overview that establishes the timeline before anything else.
2. A direct answer to each of the complainant's three elements, point by point. Even if your strongest ground is element two (no legitimate interest in the respondent), address elements one (confusion) and three (bad faith) in full. A gap in element three, even when element two is strong, can be exploited in a reply if the procedure allows one.
3. The positive case for legitimate interest, supported by the documentary record assembled in Steps 2 and 3.
4. The RDNH argument, if applicable, in a discrete subsection after the main defense.
5. Exhibits, clearly numbered and cross-referenced within the text.

The trap in this step is length for its own sake. A response that buries the key arguments in discursive background text does not serve the registrant. Experts read many responses. The argument that is clear, structured, and fully documented on the first read is the one that succeeds. We have seen meritorious defenses lose traction because the legitimate-interest evidence was presented as an afterthought on page twelve.

Step 7: What are the realistic outcomes, and what comes next?

The decision in a SWITCH domain dispute is binary: the domain is transferred to the complainant, cancelled, or left with the registrant. No monetary awards are available, and no costs order follows the outcome – the same as under the UDRP. The expert does not take sides on the underlying business dispute; the only question is whether the complaint meets the applicable test.

If the decision goes against you, your options depend on whether the national procedure provides an appeal mechanism and what rights of recourse exist under Swiss law. Switzerland's court system is accessible, and a domain transfer ordered under SWITCH's procedure can in some circumstances be challenged before Swiss courts. That path requires local litigation counsel in Switzerland and is materially more costly than the administrative proceeding. Whether it is worth it depends on the commercial value of the domain and the strength of the ground not fully ventilated in the first proceeding.

If the decision is in your favor – or includes an RDNH finding – the outcome is not automatically the end of the matter. A complainant who believes strongly in their position can in principle pursue the question through the Swiss court system. In practice, a clear expert decision that addresses the evidence fully tends to end the dispute. We have not seen routine appeals by complainants who received a well-reasoned adverse decision on generic-word grounds.

One further question worth addressing directly: is the defense worth pursuing at all? For a domain with genuine commercial value, the answer is almost always yes. The 20-day window closes fast. A default – where you do not respond – results in a transfer order without any consideration of your rights. The only safe default is a deliberate strategic choice, and for a legitimately held generic .ch domain, it is very rarely the right one.

Related at COGNOMEN

• Respondent defense and RDNH across gTLD and ccTLD proceedings
• Defending a domain on fair-use and descriptive grounds in .ae
• Case study: pre-acquisition due diligence on a .cn domain portfolio