How to prove a legitimate interest in your .tech domain

How to prove a legitimate interest in your .tech domain. UDRP and ccTLD domain recovery and defense across .tech. Email the firm to assess your case.

A UDRP complaint arrives naming your .tech domain. The complainant alleges bad faith, claims the name is confusingly similar to its trademark, and demands a transfer. You know why you registered it. The question is whether the record you can build will persuade a panel that your interest is real – and whether the complaint itself is an overreach.

To prove a legitimate interest in a .tech domain under the UDRP, a registrant must satisfy at least one of the Paragraph 4(c) safe harbors: a bona fide offering of goods or services before notice of the dispute, demonstrable evidence that the registrant is commonly known by the domain name, or legitimate noncommercial or fair use without intent to mislead. The standard UDRP applies to .tech because .tech is a generic top-level domain (gTLD) governed by the UDRP under ICANN's mandatory rules. A well-assembled factual record – produced within the 20-day response window – is the core of any successful defense.

This page sets out the legal test, the evidence that moves panels, the realistic scenarios for each safe harbor, and what a full respondent defense looks like in practice.

Why the UDRP applies to .tech and what the complainant must first prove

.tech is an ICANN-accredited gTLD, and every registrar that offers it operates under the UDRP as a condition of accreditation. That means the same three-element test decides a .tech dispute as decides a .com dispute – but the tech-sector context of the zone often matters at the margins. To prevail, the complainant must first establish all three elements of Paragraph 4(a): confusing similarity to a mark it holds, absence of your rights or legitimate interests, and registration and use in bad faith. All three must be met. A failure on any one element defeats the complaint.

The second and third elements interact directly with your defense. The complainant carries the burden of proving you have no legitimate interest – but because it cannot read your mind or your filing records, panels routinely shift that burden once the complainant makes a prima facie case. At that point, you must come forward with concrete evidence. That is why building the factual record matters more than most registrants expect.

The .tech zone is popular with technology companies, developers, startups, and domain investors who hold descriptive or generic names in the space. Panels are aware of that context. A complainant whose mark is a moderately distinctive term in the technology sector faces a harder road than one whose mark is wholly invented. In our practice, the zone and the nature of the mark together shape how aggressively we frame the legitimate-interest argument.

If you have received a UDRP complaint naming a .tech domain, the 20-day clock starts at commencement, not at filing. For an assessment of your domain dispute, contact info@cognomenlaw.com.

What does Paragraph 4(c) actually require to prove a legitimate interest?

Paragraph 4(c) of the UDRP sets out three safe harbors, and satisfying any one is sufficient to defeat the complaint on the second element. Each safe harbor carries its own evidentiary demands, and the record you assemble must speak to the specific harbor you invoke.

Safe harbor 1: bona fide offering before notice. This is the most commonly relied-upon ground for commercial registrants. You must show that before you had notice of the dispute – typically, before the complaint was filed – you were making a genuine offering of goods or services using the domain. The operative word is "bona fide." Panels apply several markers: was the domain actually in use, or merely parked? Was the offering plausible given the domain name's words? Did the use predate the mark or the complainant's public presence? Is there any evidence of targeting the complainant specifically?

A .tech domain used for a genuine developer portfolio, a SaaS product, or a consultancy that predates the complainant's market entry typically satisfies this harbor. Where the domain has been pointing at a pay-per-click page since registration, the analysis becomes harder – but not hopeless if the PPC content was generic and unrelated to the complainant's goods.

Safe harbor 2: commonly known by the name. This applies most directly to individuals or businesses whose personal or corporate identity matches the domain string. A developer named Lex Thornton who registered lexthorn.tech has a stronger claim than a speculator holding a brand-like string. Evidence includes business registrations, social media presence, professional profiles, prior use of the name in commerce, and email correspondence predating the dispute.

Safe harbor 3: legitimate noncommercial or fair use. Criticism sites, fan sites, community resources, and informational projects can qualify – provided there is no commercial intent and no attempt to mislead users as to source. The .tech zone lends itself to open-source project pages, developer communities, and technical documentation. A panel will look closely at whether the use actually served that purpose or was a pretext.

How to build the legitimate-interest record before the response deadline

Evidence, not assertion, wins the second element. The 20-day response window is short. We typically begin building the evidentiary record on day one – before any procedural decision is made – because the evidence itself often determines whether to defend, negotiate, or file a supplemental brief seeking additional time.

The core documents to gather immediately include: registration confirmation and the original registrant data; any business registration, LLC certificate, or trade name filing that predates the complaint; screenshots of the domain's historical use (web archives, cached pages, email headers, server logs); invoices, agreements, or client correspondence that place the domain in commercial use before notice; social media accounts, LinkedIn or GitHub profiles, or published content associated with the domain name; and any trademark search or legal advice obtained at or before registration showing the registrant acted with clean hands.

For domain investors holding a .tech name as a portfolio asset, the analysis shifts. Panels recognize that secondary-market trading in domain names is a legitimate industry. The investor must show that the domain was not registered with the specific complainant in mind – not that it was never intended for resale. Generic or descriptive .tech strings (think "cloud.tech", "stack.tech", or similar dictionary-word registrations) attract stronger investor-side arguments because the legitimate interest in a generic name is more intuitive to panels. Highly brand-specific strings in the .tech zone require a more detailed explanation.

In a recent matter (a .tech domain dispute, spring 2025), we represented a registrant who had operated a developer tools company under the disputed name for over two years before the complaint arrived. The record included bank statements showing subscription revenue, cached landing pages, and a GitHub organization predating the complainant's first trademark application. The panel dismissed the complaint on the second element without reaching bad faith.

When is a reverse domain name hijacking finding realistic?

Reverse domain name hijacking (RDNH) occurs when a panel finds that a complaint was brought in bad faith – typically to strip a legitimate registrant of a domain the complainant wants but cannot lawfully take. An RDNH finding carries no monetary penalty; it is a reputational sanction against the complainant and its counsel.

Panels issue RDNH findings in a meaningful minority of cases, and the circumstances that make one realistic are well-settled. The strongest indicators include: the complainant knew of the registrant's legitimate interest before filing; the domain was registered before the complainant's trademark rights arose; the complainant's mark is weak, descriptive, or generic in the technology sector; there was a prior failed acquisition attempt – a buy offer that was rejected – followed shortly by the complaint; or the complaint relied on a trademark registration filed after the domain was registered, in an obvious attempt to work backward to rights.

The .tech zone sees a recurring pattern: a brand owner registers a trademark containing a common technology word, then files a UDRP against a registrant who held the .tech string for years before the mark existed. Where that sequence is clear on the record, we routinely seek an RDNH finding as part of the defense – not merely as a secondary argument but as the primary framing of the response.

What does the respondent need to show? First, that the complainant brought the complaint knowing the registrant had a legitimate interest. Second, that no reasonable panelist applying the Policy correctly could have found bad faith on the part of the registrant. Third, ideally, that the complainant had independent commercial motivation – the prior buy inquiry is the clearest evidence of that. Each element of the RDNH argument is supported by documentary proof, not by narrative alone.

In a second matter we handled (a new gTLD .tech complaint, autumn 2024), the complainant had offered a five-figure sum for the domain six months before filing. The registrant declined. The complaint followed. We presented the email chain, the timeline of the complainant's trademark application (filed two weeks before the complaint), and the registrant's unbroken use of the domain for a technical community project. The panel dismissed the complaint and made an RDNH finding, recording that the complaint was an attempt to use the Policy as a tool for reverse-engineered acquisition.

If a prior acquisition offer was made before the complaint arrived, that evidence can be decisive. To weigh the RDNH argument for your case, email info@cognomenlaw.com.

What evidence actually decides the outcome in .tech disputes?

The evidentiary standard under the UDRP is a balance of probabilities. That is a lower bar than clear and convincing evidence (which governs URS proceedings for new gTLDs), and it cuts both ways – the complainant's burden is lower, but so is the respondent's. What panels actually weigh is the quality, chronology, and internal consistency of the evidence, not its volume.

The chronology is often dispositive. A registrant who can show a dated business registration, an email address in use, and a live landing page all predating either the trademark or the complainant's notice of the domain is in a strong position. The timestamps must be independently verifiable – web archive records, domain registrar logs, and server certificates carry more weight than self-serving screenshots without metadata.

The content of the domain's use matters in the .tech zone specifically. Panels notice whether the content was generic and technology-adjacent (favoring the registrant) or specifically imitative of the complainant's brand, product names, or trade dress (disfavoring the registrant). A .tech domain pointing at a page advertising services that compete directly with the complainant's core product line presents a much harder legitimate-interest argument than one pointing at an unrelated developer resource.

The respondent's conduct after receiving notice also matters. Did the registrant remove the content and go dark? Did it refuse to correspond? Did it demand a payment far exceeding its reasonable out-of-pocket registration costs? Each of those behaviors feeds the bad-faith analysis and can undercut an otherwise defensible legitimate-interest claim. The response strategy must account for the entire behavioral record, not only the documentary one.

How does the .tech respondent defense compare to a .com or ccTLD defense?

The right route and the applicable test depend on the zone. For .tech, the UDRP applies exactly as for .com – three elements, the same Paragraph 4(c) safe harbors, the same forums (WIPO or the Forum), and the same 20-day response window. The zone itself is neutral; the technology context shapes panel expectations about what constitutes a plausible legitimate use, but the legal test is identical.

Contrast a .uk dispute. Nominet's DRS uses a different test: the complainant must show rights in a name and that the registration is an "abusive registration." Critically, the DRS reads the second limb as registered or used abusively – a lower bar than the UDRP's cumulative registered and used in bad faith. A registrant defending a .uk name can sometimes succeed where a .com defense would be harder, because the complainant must sustain both limbs under the UDRP. Nominet also offers a mandatory free mediation stage before any expert decision, which changes the settlement calculus.

For a .de domain, neither the UDRP nor Nominet applies. Disputes go to the German courts, and DENIC offers a DISPUTE entry – a registration block preventing transfer while litigation proceeds. The analysis of legitimate interest in a German court follows German trademark and unfair-competition law, and we engage local litigation counsel in the relevant jurisdiction for that work.

A registrant holding both a .tech and a .de version of the same name faces two separate proceedings under two different rulebooks. The strategy for each must be developed independently, though the underlying factual record – evidence of good-faith registration and genuine use – is shared and should be assembled with both proceedings in mind from the outset.

Among the gTLD forums, most .tech disputes we have seen proceed at WIPO. The Forum is equally available. The Czech Arbitration Court (CAC) is a lower-cost entry point but is less frequently used. Forum selection affects the panelist pool and, at the margins, can affect how a panel reads technology-sector context. That choice is worth a deliberate conversation at the outset.

What the defense process looks like from filing to decision

Once a UDRP complaint is filed at WIPO or the Forum, the registrar locks the domain – it cannot be transferred, deleted, or modified during the proceeding. The forum then formally commences the case and serves the complaint on the registrant. The 20-day response window opens at that point.

A defense that meets the deadline and raises all available safe-harbor arguments is complete on its face. After the response, neither party files further submissions unless the panel invites them (which is rare). The panel is appointed from the forum's roster. A single-member panel is the default; the respondent may request a three-member panel, with the additional cost split between the parties at roughly the higher three-member fee rate.

A standard case at WIPO typically concludes within about two months of filing. If the complainant elects WIPO's expedited option for single-panel cases of up to five domains, the timeline is approximately one month. The decision is published in the forum's online database, identified by case number, and – if a transfer is ordered – the registrar implements it within ten business days unless a court action is filed to stay it.

For the respondent, the practical work runs in three phases. First, intake and evidence collection in the first week. Second, drafting and refining the response, with attention to the complainant's specific factual allegations and the panel's likely questions. Third, any post-decision follow-up – monitoring the registrar's implementation window if the outcome is favorable, or assessing the grounds for a court challenge if it is not. The UDRP has no internal appeal mechanism. A party dissatisfied with the outcome must go to court before the registrar implements the transfer.

Pricing structure: what the .tech respondent defense costs

The filing fees for a UDRP complaint are paid by the complainant, not the respondent. There is no forum filing fee for the respondent. What the respondent pays is legal-fee coverage for assembling and filing the response.

Legal fees for a single-domain UDRP respondent defense vary with the complexity of the factual record. The market range for a straightforward single-domain response is typically in the USD 3,000–7,000 range, reflecting the evidentiary work, the drafting, and the forum mechanics. A more complex matter – one involving multiple domains, a credible RDNH argument that requires a parallel factual narrative, or a complainant with substantial resources – will sit higher within or above that range.

If the respondent requests a three-member panel (which can be tactically wise when the case is close and the RDNH argument is strong), the additional panel cost is split with the complainant. At WIPO, a three-member panel for a single-domain complaint costs USD 4,000, compared with USD 1,500 for a single-member panel. The respondent's share of the uplift is the difference between the two rates, divided equally – a defined, predictable number.

COGNOMEN publishes these figures because fee clarity is a discipline. A registrant deciding whether to defend a .tech domain deserves to know the cost structure before making that decision, not after engaging counsel.

Related at COGNOMEN

• Respondent defense and RDNH – full service overview across gTLD and ccTLD proceedings
• How to respond within the UDRP deadline – practical FAQ for cloud and new-gTLD registrants
• Recovering a .me typosquat – the complainant-side mirror of the respondent defense