How to defend a .de domain against a UDRP complaint

You registered a .de domain years ago. Now a brand owner's lawyer has sent a complaint — or is threatening one — and you want to know whether you can defend it. The first thing to understand: the UDRP and the German legal system interact in ways that are frequently misunderstood, and that misunderstanding works in a respondent's favor when counsel knows how to use it.

To defend a .de domain against a UDRP complaint, you must understand that there is no UDRP for .de. DENIC, the .de registry, has not adopted the UDRP. Disputes over .de domains proceed through the German courts. If a complainant files a UDRP complaint naming your .de, no accredited UDRP provider has jurisdiction over it — and a well-constructed respondent brief can expose exactly that. Where a .de dispute does proceed, the governing framework is German trademark and unfair-competition law, applied by the German courts, with a DENIC DISPUTE entry used to block transfer pending litigation.

This page covers the full picture: how jurisdiction works for .de, what defenses apply, how to build the legitimate-interest record, when an RDNH finding is realistic, and what evidence decides the outcome.

Why the UDRP does not apply to .de domains — and what does

DENIC, the registry for .de, has never delegated dispute resolution to WIPO, the Forum, CAC, or any other UDRP provider. That is not an oversight; it is a deliberate policy choice. The UDRP applies to all gTLDs (.com, .net, .org, and others) and to ccTLDs that have formally adopted it — but .de is not among them.

A complainant who files a UDRP complaint purporting to cover a .de domain has filed against a domain that falls outside the Policy. The panel will typically have no authority to order DENIC to transfer or cancel the name. In our practice, we have seen complainants attempt to bundle a .de into a multi-domain UDRP complaint — relying on the registrant's inattention to the jurisdictional gap — and we have successfully argued the dismissal of the .de component on that basis alone.

What does apply to .de? German courts. A trademark owner who genuinely believes your .de registration infringes its rights must pursue that claim through German civil proceedings, typically before the regional courts (Landgericht) that handle IP matters. While litigation is pending, the complainant may record a DENIC DISPUTE entry — a registration block that prevents the domain from being transferred to anyone other than the claimant — but the DISPUTE entry does not itself decide ownership. It is a lock, not a judgment.

That distinction matters enormously. The respondent retains the domain and continues to use it during the litigation. The burden of proving infringement under applicable German and EU trademark law falls on the complainant. Time, cost, and procedural complexity all cut in the registrant's favor relative to the UDRP, where a 20-day response window governs and a panel can transfer a .com in about two months.

If you have received a complaint or a threat letter concerning your .de domain, the first step is a jurisdictional assessment. Contact info@cognomenlaw.com to discuss the procedural posture and what it means for your defense.

How does the DENIC DISPUTE entry work, and should you contest it?

A DENIC DISPUTE entry is a unilateral step the claimant takes — not a court order. The claimant submits documentation to DENIC asserting a right to the domain, and DENIC records the entry, which blocks transfer while the dispute is active. The entry does not restrict use, does not change the registrant of record, and does not give the claimant any operational control over the domain.

Contesting the DISPUTE entry directly at the registry level is rarely the most productive step. DENIC is not a dispute adjudicator; it is a registry. The real forum for contesting the underlying claim is the German court. That means the respondent's strategic priority is threefold: continue operating the domain lawfully, assess the strength of the complainant's trademark position, and prepare the factual record that will decide the German proceedings.

German trademark law, harmonized with EU directives, requires the complainant to show, among other things, that its mark is in force, that the domain creates a likelihood of confusion or takes unfair advantage of a distinctive sign, and — critically — that the registrant cannot rely on any of the recognized defenses: prior use, descriptive or generic use, good-faith registration, or a legitimate own-name right. Those defenses track closely to the Paragraph 4(c) safe harbors that respondents invoke in UDRP proceedings, but they are applied with the more detailed evidentiary standards of a German court rather than the compressed timeline of an arbitration panel.

In a recent matter (a .de domain registered by a small regional business, spring 2025), a complainant threatened a DENIC DISPUTE entry and simultaneously filed a UDRP complaint against the respondent's .com. We handled both: the UDRP defense on the .com and a coordinated response on the .de side, ensuring the factual record built for German proceedings was consistent with — and reinforced by — the evidence assembled for the UDRP. Keeping those records aligned prevented the complainant from exploiting inconsistencies between the two proceedings.

What defenses are available when a complainant asserts trademark rights over your .de?

The strongest defenses in .de proceedings — and in any parallel UDRP complaint covering related gTLD domains — share a common architecture: establish that you have a legitimate right or interest in the domain that predates or is independent of the complainant's trademark, and that your registration and use were not designed to exploit the complainant's mark.

The principal defense categories are:

• Prior registration and genuine use. If you registered the .de before the complainant's mark acquired secondary meaning — or before the complainant's German or EU trademark was filed — the timeline is your first weapon. Registration dates, WHOIS/RDDS history, and evidence of active use in the relevant period are central.
• Generic or descriptive terms. A domain consisting of a common German word, a geographic name, or a descriptive phrase enjoys strong protection. Trademark rights in generic terms are inherently weak, and panels and courts are generally reluctant to order transfer or cancellation of a domain that reflects a term anyone in the trade might legitimately register.
• Legitimate business use under your own name or brand. If you are an individual or a business known by the name reflected in the domain, that is a recognized safe harbor — equivalent to Paragraph 4(c)(ii) in the UDRP — and it applies in German court proceedings through the concept of the right to use one's own name (Namensrecht).
• Non-commercial or fair use. Commentary, criticism, and non-commercial fan sites can support a legitimate-interest defense, provided the domain is not used to mislead users into believing it is the complainant's official site.
• Absence of bad faith at registration. If you registered without knowledge of the complainant's mark, or if the mark postdates your registration, the bad-faith element — required in any UDRP analysis and relevant under German unfair-competition doctrine — cannot be established.

Building that record requires contemporaneous documentation: business registration documents, invoices or contracts showing the domain was used in commerce, screenshots of the website with date metadata, correspondence that predates the dispute, and any trademark searches you conducted before registering. Courts and UDRP panels both examine whether the record looks constructed after the fact. Start assembling it now.

When is a Reverse Domain Name Hijacking finding realistic?

Reverse Domain Name Hijacking (RDNH) is a finding by a UDRP panel that the complainant brought the proceeding in bad faith — essentially weaponizing the UDRP to try to seize a domain the registrant holds legitimately. An RDNH finding is reputational, not financial: no damages flow from it, but it is published and it attaches to the complainant's record.

For .de specifically, RDNH arises in a narrow but important scenario: where the complainant files a UDRP complaint that includes .de-related domains or arguments, knowing — or being willfully blind to — the fact that .de is not a UDRP zone. Filing a complaint that overreaches jurisdictionally, or one that asserts bad faith against a registrant with a transparent, documented legitimate interest, is exactly the conduct that supports an RDNH finding in the related .com or gTLD proceeding.

Panels have consistently held that an RDNH finding is appropriate where: the complainant knew the respondent had rights or legitimate interests; the mark was registered after the domain; or the complainant ignored evidence of good faith to pursue an opportunistic filing. In our practice defending registrants, we document each of those factors when they are present and include them in the formal response — not as a threat, but because the record should be complete.

What makes RDNH realistic in a given case? Several indicators: the domain predates the trademark by years; the name is generic or geographic; the complainant is a well-resourced company using the UDRP as a cheaper substitute for a trademark claim it cannot win on the merits; or the complaint materially misrepresents the registrant's use of the domain. Any one of those factors is relevant; a combination of two or more makes the argument worth developing in full.

If the complaint against your domain shows any of the above patterns, an RDNH argument may be available alongside your primary defense. Email info@cognomenlaw.com to assess whether the facts support it.

What evidence decides the outcome of a .de domain dispute?

Evidence is the difference between a defense that holds and one that collapses under cross-examination — whether in a German court or before a UDRP panel on a parallel .com filing. The documents that consistently decide outcomes are:

• Registration chain and date evidence. The original registration confirmation, any prior ownership or transfer history, and WHOIS/RDDS snapshots from around the registration date. These establish the temporal relationship between your domain and the complainant's trademark.
• Evidence of active use. Website screenshots with date metadata (Wayback Machine captures, hosting logs, CMS timestamps), invoices or contracts bearing the domain name, and any marketing material referencing it. Passive holding — owning a domain without active use — is a weakness in any dispute, particularly if the complainant's mark is well-known.
• Business legitimacy documents. Company registration, trade name registration, or professional licenses that establish your right to operate under the name. For individual respondents, personal identification documents showing that the domain reflects your own name are equally important.
• Pre-registration due diligence. Any trademark search you conducted before registering the domain, professional advice you received, or correspondence showing that you were unaware of the complainant's mark. This addresses the bad-faith element directly.
• Third-party use evidence. Evidence that the term in the domain is generic or commonly used in the trade — industry directories, competitor websites, dictionary entries in German — weakens the complainant's distinctiveness argument significantly.
• Correspondence with the complainant. All communications — including cease-and-desist letters, buy-back offers, and any responses — must be preserved and provided to counsel. An offer to sell the domain at a price grossly in excess of registration costs, made by the respondent, is classically cited as bad-faith evidence against the registrant; conversely, a buy-back demand initiated by the complainant at an inflated price is relevant to an RDNH argument.

One evidence question we encounter regularly: a client has used the domain for years but never systematically documented that use. Do not assume the Wayback Machine has captured everything you need. A methodical review of available archives, hosting provider records, and internal files is essential before the deadline passes.

How does a .de defense interact with a parallel .com or gTLD dispute?

Multi-zone disputes — where the complainant targets both a .de and a .com (or several new-gTLD variants) simultaneously — are common. The legal tests are different, but the factual record largely overlaps. A consistent, well-documented account of legitimate registration and use protects the .de in German court and the .com before a UDRP panel, while inconsistencies between the two proceedings can be used against the registrant.

The choice of UDRP forum matters on the .com side. WIPO and the Forum account for the great majority of proceedings. The WIPO filing fee starts at USD 1,500 for a single-member panel; the Forum's entry point is approximately USD 1,300. The respondent does not pay the filing fee — that falls on the complainant — but the respondent does bear the cost of preparing a defense, which is comparable across forums. WIPO also offers an expedited option, potentially shortening a single-panel .com case to approximately one month; a respondent facing an expedited complaint should plan accordingly.

The .de side runs in parallel, on a German court's schedule. German IP proceedings can take substantially longer than a UDRP case. That asymmetry cuts two ways: the complainant faces higher cost and longer timelines to win the .de, which often moderates their posture; but the respondent must also fund a sustained defense across two jurisdictions. Coordination between the UDRP response and the German-law analysis is not optional — it is the core of a multi-zone strategy.

In another recent matter (a .com and .de pair, summer 2024), a brand owner filed a UDRP against a registrant's .com while threatening German proceedings on the .de. We prepared a unified factual record showing the registrant's documented use of both domains for an independent online business predating the complainant's German trademark by several years. The UDRP panel denied the transfer. The German threat was withdrawn following disclosure of the full evidence file. Neither outcome was certain at the outset; both followed from the quality and completeness of the record.

What is the realistic path forward if you hold a .de under dispute?

The path depends on your situation. Three scenarios cover most of what we see in practice.

Scenario A: A UDRP complaint names only gTLD domains (no .de). The .de is not at risk in the UDRP proceeding. Focus on building the UDRP defense, and treat the .de as supporting evidence of your legitimate interest — an independent registration in a separate zone that reinforces the pattern of genuine use. If the UDRP complainant later seeks to record a DENIC DISPUTE entry, a won UDRP defense provides persuasive context, though German courts are not formally bound by UDRP decisions.

Scenario B: A complainant threatens both a UDRP (for .com) and German court action (for .de) simultaneously. This is the most resource-intensive scenario. You need coordinated respondent counsel across both tracks. The UDRP response must be filed within 20 days of commencement; the German court timeline is set by the court's procedural rules. The UDRP moves faster — plan that track first, then integrate the German-law analysis. RDNH is a live argument if the .de facts show clear prior legitimate use that the complainant chose to ignore.

Scenario C: A DENIC DISPUTE entry has been recorded and no UDRP has been filed. The dispute will ultimately be decided by a German court. Your immediate priorities are: confirm the entry has been correctly recorded and identifies the correct claimant; review whether the underlying trademark claim is substantiated; and begin assembling the evidence file described above. Local litigation counsel in the relevant German jurisdiction will manage the court proceedings; COGNOMEN coordinates the strategy and handles any related UDRP or ccTLD components.

Across all three scenarios, the single most common mistake we see is delay. A DENIC DISPUTE entry can be recorded quickly. A UDRP response deadline is fixed. Evidence preservation requires action before records are overwritten or expired hosting accounts are deleted. The sooner counsel is engaged, the more options remain available.

Is defending a .de domain expensive compared to a UDRP defense?

The two cost structures are materially different. A UDRP defense involves no filing fee for the respondent — the complainant pays — but does require counsel fees. Market rates for a UDRP respondent defense are typically in the USD 3,000 – 7,000 range for a straightforward single-domain case, depending on complexity and the evidence required.

German court proceedings carry official court fees scaled to the value in dispute, plus counsel fees under German legal-fee conventions. For IP matters, the value in dispute is often set by the court based on the perceived commercial importance of the domain. Litigation is substantially more expensive than arbitration, which is one reason many complainants prefer UDRP for gTLDs — and one reason the absence of UDRP for .de is a structural advantage for the registrant.

A respondent facing a dual .com/.de attack must budget for both tracks. The UDRP component is bounded and time-limited. The German component is ongoing and potentially extends to appeal. That said, a strong UDRP win on the .com often prompts complainants to reassess the German action — particularly where the cost of pursuing it exceeds the commercial value of the domain to them.

COGNOMEN publishes its service scope and pricing approach transparently. For a dual-track .de/.com defense, we provide a written assessment of both components before work begins, so you understand the scope before committing.

Related at COGNOMEN

• Respondent Defense and RDNH — the full practice overview, covering gTLD and ccTLD defense strategies
• How to defend a generic domain — strategic guide for registrants facing complaints on descriptive names
• Defending a domain registered before the trademark — the prior-registration defense in UDRP and ccTLD proceedings

Author: Anton Grant — Respondent defense and reverse domain name hijacking (RDNH). Meet the team.

Speak with Cognomen Law

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

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

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