Domain Dispute Evidence: What Panels Actually Weigh

This guide is for complainants and respondents in UDRP and ccTLD disputes. It explains what evidence panels actually weigh, how to prepare an annex file, and the mistakes that lose cases. If you have just received a complaint, read the response guide first and then return here for the evidence strategy.

Quick answer: what evidence decides a domain dispute

Domain disputes are decided on the written record. There is usually no hearing, no cross-examination, and no live witnesses. The panel weighs the documents the parties submit, the annexes they index, and the public records it can verify. The complainant bears the ultimate burden of proving all three elements on the balance of probabilities. For the second element, a prima facie case shifts the burden of production to the respondent. The evidence that persuades panels is contemporaneous, dated, verifiable, and connected to the legal test — not volume, not adjectives, and not after-the-fact reconstruction.

Key facts at a glance

The burden of proof: who has to prove what

The complainant’s ultimate burden

The complainant must prove all three elements on the balance of probabilities. The panel must be satisfied that it is more likely than not that:

1. The domain is identical or confusingly similar to the complainant’s mark.
2. The respondent has no rights or legitimate interests in the domain.
3. The domain was registered and is being used in bad faith (or, under some ccTLD policies, registered or used in bad faith).

The burden does not shift on Elements 1 and 3. It remains on the complainant throughout.

The prima facie case and the burden shift

Element 2 is different. Proving that a respondent lacks rights or legitimate interests is often described as “proving a negative” — the information is primarily within the respondent’s knowledge or control. To avoid an impossible burden, panels apply a burden-shifting framework:

1. The complainant makes a prima facie case that the respondent lacks rights or legitimate interests.
2. The burden of production shifts to the respondent to come forward with relevant evidence.
3. The burden of proof remains on the complainant.

WIPO Overview 3.0, section 2.1, summarises the consensus: if the respondent fails to come forward with relevant evidence, the complainant is generally deemed to have satisfied the second element.

What a prima facie case looks like:

• The WHOIS record shows the respondent is not commonly known by the domain.
• The domain resolves to a parked page, an error page, or no active website.
• There is no trademark or business registration matching the domain.
• The respondent has not used the domain for a bona fide offering.
• The respondent has offered to sell the domain, or has a pattern of similar registrations.

The balance of probabilities

The standard is the balance of probabilities — more likely than not. Panels may draw inferences from the facts and circumstances. They are not required to apply the criminal standard, and they are not required to resolve every factual dispute with live evidence.

In CAC-UDRP-105436, the panel applied the balance of probabilities and found that a pending trademark application did not create UDRP-relevant rights. In D2022-0954, the panel applied the standard to assess the respondent’s claims and found them unsupported.

What “proving a negative” means in practice

A complainant does not need to prove a negative in the abstract. It needs to build a record that makes the absence of a legitimate interest more likely than not. The respondent then has the opportunity to rebut it. If the respondent stays silent, the complainant’s prima facie case usually carries the day — but the panel still reviews the complaint for sufficiency.

Not sure who has to prove what? We map the burden before drafting, so the evidence targets the right element. Book an evidence review →

Evidence for Element 1: rights and confusing similarity

Registered trademark evidence

The strongest evidence is a registered trademark certificate showing:

• The mark.
• The registration number and jurisdiction.
• The goods and services covered.
• The registration date and expiry.
• Proof that the registration is in force.

A pending application is not enough. Panels have consistently held that pending applications do not create UDRP-relevant rights. In CAC-UDRP-105436, the panel verified the complainant’s status on the USPTO website and found only a pending application, which was insufficient.

Common-law and unregistered rights

Where the complainant relies on common-law rights, the evidence must show:

• Duration and nature of use — sales records, invoices, advertising.
• Consumer recognition — media coverage, awards, surveys.
• Distinctiveness — the mark identifies the complainant’s goods or services.
• Geographic scope — use in the relevant market.

In The Scent Stories decision, the respondent produced sales records and invoices showing use of the mark in India since at least 2022, plus a valid Indian trademark registration. The panel found no bad faith and denied the complaint. The evidence was contemporaneous and commercial, not a narrative.

Confusing similarity evidence

The panel compares the domain to the mark. Useful evidence includes:

• A side-by-side comparison of the domain and the mark.
• Evidence of the mark’s distinctiveness.
• Evidence that the domain’s additional elements are descriptive or generic.
• Evidence of actual confusion, if available.

In HCL.ai, the panel found the domain identical to the HCL mark and placed significant weight on the pairing of “HCL” with the “.ai” extension, given HCL’s established presence in artificial intelligence. The evidence was contextual, not just a spelling comparison.

What panels disregard

• The gTLD itself.
• Letter case.
• Hyphens and punctuation that do not change the mark.
• Assertions that the domain is different without evidence.

Evidence for Element 2: no rights or legitimate interests

The complainant’s prima facie case

The complainant should build the prima facie case with affirmative evidence:

• WHOIS/RDDS records showing the registrant’s identity and the registration date.
• Website captures showing parking, monetisation, or no active use.
• Search results showing the respondent is not commonly known by the domain.
• Business registry searches showing no matching entity.
• Trademark database searches showing no matching registration.
• Correspondence showing the respondent’s awareness of the complainant.

In D2024-4598, the panel found the complainant had established a prima facie case, and the respondent’s response was “notable more for what it does not say than what it does say.” The respondent did not explain why it registered the domain, and the panel found no bona fide offering.

The respondent’s paragraph 4(c) evidence

The respondent can rebut the prima facie case with evidence under paragraph 4(c):

Bona fide offering evidence

The evidence must be contemporaneous and pre-notice. In Dio2022-0045, the respondent claimed a business idea for a residential mortgage service but provided no evidence of business formation, investment, or a genuine business plan. The panel found the mere configuration of two email accounts insufficient.

The panel listed the kind of evidence that would have helped:

• Evidence of business formation-related due diligence, legal advice, or correspondence.
• Evidence of credible investment in website development or promotional materials.
• Proof of a genuine business plan and credible signs of pursuit.
• Bona fide registration and use of related domain names.
• Other evidence pointing to a lack of cybersquatting intent.

Commonly known by the domain

Evidence includes:

• Business registration or trading name.
• Invoices and contracts using the name.
• Social media profiles and press coverage.
• Customer or supplier statements.

In The Scent Stories, the respondent’s Indian trademark registration and sales records supported its genuine business activities, and the panel found no bad faith.

Fair use and noncommercial use

Fair use evidence must show that the use is genuine, noncommercial, and not a pretext for commercial gain or tarnishment. A criticism site with no advertising and a chronological content record is stronger than a site that mixes criticism with affiliate links.

Evidence for Element 3: bad faith

Bad-faith registration

Bad-faith registration requires evidence that the respondent knew or should have known of the complainant’s mark at the time of registration, and registered the domain for an improper purpose.

Evidence includes:

• The complainant’s mark predated the domain registration.
• The respondent’s prior correspondence or dealings with the complainant.
• The respondent’s pattern of registering domains matching third-party marks.
• The respondent’s sophistication as a domain investor.
• The absence of a plausible alternative explanation for the registration.

In HCL.ai, the panel relied on the surrounding facts rather than direct evidence of intent: the strength of the HCL mark, its recognition in the technology sector, the respondent’s sophistication as a domain investor, and the absence of a plausible alternative use. The panel found the respondent either knew or should have known of HCL’s rights.

Bad-faith use

Bad-faith use requires evidence of:

• An offer to sell, rent, or transfer the domain for more than out-of-pocket costs.
• A pattern of blocking registrations.
• Disruption of a competitor’s business.
• Commercial gain from confusion.
• Phishing, impersonation, or malware.

In Michelin, the panel found the domain was a typosquatting attempt and represented a phishing risk through active MX records, which resulted in a transfer order. The MX records were technical evidence of deceptive use.

Paragraph 4(b) evidence

Circumstantial evidence and inference

Panels may infer bad faith from the totality of the circumstances. In HCL.ai, the panel inferred knowledge from the mark’s strength and the respondent’s sophistication. In D2024-4598, the panel inferred intent from the respondent’s description of the complainant as “one of the world’s most renowned healthcare institutions” and its use of the exact mark in a TLD representing the complainant’s sphere of operations.

But inference must be grounded. In the MF.com decision, the panel firmly rejected fabricated evidence and found RDNH. The panel anchored its analysis in first principles: targeting must be proven, not presumed.

Phishing, impersonation and MX records

Technical evidence is increasingly important:

• MX records showing the domain is configured to send or receive email.
• SPF, DKIM, and DMARC records.
• SSL certificates for lookalike domains.
• Screenshots of fake login pages with the URL bar visible.
• Email headers showing deceptive sending.

In Thales-Raytheon, WIPO transferred the domain due to phishing risks. In Michelin, active MX records supported the bad-faith finding.

Evidence decides bad-faith findings. We build the record around the paragraph 4(b) circumstances and the technical evidence panels expect. Get an evidence review →

The evidence that panels actually weigh

Contemporaneous documents

The strongest evidence is created at the time, not reconstructed for the dispute. Invoices, contracts, purchase orders, bank records, advertising, and customer correspondence carry more weight than a witness statement written after the complaint arrived.

Dated screenshots and URL bars

Screenshots should include:

• The full page, not a crop.
• The URL bar, showing the domain.
• The date and time, either visible in the capture or in metadata.
• The context — how the page was reached, what it showed, and why it matters.

A screenshot without a date or URL is easy to challenge. A dated screenshot with the URL bar is verifiable.

Wayback Machine captures

Panels routinely consult the Internet Archive’s Wayback Machine to ascertain archived uses of a domain. WIPO Overview 3.0, section 4.8, confirms that panels may undertake limited factual research into matters of public record, including historical resources such as the Internet Archive.

Wayback evidence is particularly useful for:

• Showing how the domain was used before notice.
• Rebutting claims that the domain was always used for a legitimate purpose.
• Showing a change in use after the complainant’s mark became known.
• Establishing the respondent’s prior business or lack thereof.

In D2022-0954, the panel referred to the Wayback Machine to ascertain archived uses. In other decisions, panels have used Wayback captures to confirm or contradict the parties’ claims.

WHOIS and historical WHOIS

WHOIS/RDDS records show:

• The registrant’s identity and contact details.
• The registration date.
• The registrar.
• Privacy or proxy services.

Historical WHOIS shows transfers, prior registrants, and changes in ownership. It is useful for:

• Establishing the registration date.
• Showing a pattern of transfers.
• Rebutting claims of continuous legitimate use.
• Identifying the respondent’s prior conduct.

Panels also consider prior UDRP proceedings involving the parties, particularly where there are contradictory claims or a pattern of conduct (see Philip Morris USA Inc. v. Farris Nawas, WIPO Case No. D2014-2282).

Invoices, contracts and business records

For respondents, business records are the core of a legitimate-interest defence:

• Invoices showing sales under the name.
• Contracts with customers or suppliers.
• Advertising and marketing materials.
• Bank records showing commercial activity.
• Tax registrations and business licences.

These records must be contemporaneous and connected to the domain. A business that exists but does not use the domain is weaker than a business that uses the domain in trade.

Witness statements and declarations

Witness statements are admissible but not required. The UDRP is a simplified procedure; sworn affidavits are not mandatory, and technical rules such as hearsay are not rigidly enforced. The weight of a witness statement depends on:

• Specificity — does it explain the registration, the business, and the use?
• Corroboration — is it supported by documents?
• Timing — was it created contemporaneously or after the dispute?
• Credibility — is it consistent with the public record?

In Malaga Cars, the panel accepted the respondent’s signed notarised declaration that he had no knowledge of the complainant or its Spanish trademark. The notarisation added credibility.

Notarised and sworn evidence

Notarisation is not required, but it can strengthen a declaration, particularly where the facts are contested and the respondent has no other corroboration. A notarised declaration is harder to dismiss as an after-the-fact narrative.

Evidence that panels discount or reject

Unverifiable assertions

Statements without documents are weak. “I have a legitimate business” is not evidence. “I have operated a business under this name since 2019, and here are the invoices, contracts, and tax records” is evidence.

Cropped or undated screenshots

A cropped screenshot that omits the URL bar or the date is easy to challenge. Panels prefer full-page captures with visible URLs and dates.

After-the-fact reconstructions

A narrative written after the complaint arrived is less persuasive than contemporaneous documents. Panels are alert to after-the-fact explanations that are not supported by the record.

Fabricated or implausible evidence

In MF.com, the panel found the complainant had submitted fabricated evidence — implausible emails — and found RDNH. The panel’s approach was to rigorously test the evidentiary record before drawing inferences of bad faith. Fabrication is not just unsuccessful; it can expose the complainant to an RDNH finding and reputational harm.

AI-generated filings without verification

In The Scent Stories, the panel noted internal drafting notes in the complaint and observed that it appeared likely to have been prepared using an AI platform. The panel declined to admit an unsolicited supplemental filing and criticised the lack of verification. AI-assisted drafting is not prohibited, but it must be reviewed and verified. Unverified AI-generated assertions can undermine credibility.

A disorganised or overstated annex file undermines credibility. We review the record for gaps, inconsistencies, and risks before filing. Get an evidence review →

Preparing the annex file

The annex schedule

Every annex should be numbered and described in a schedule. The schedule tells the panel what each item proves and why it matters.

Numbering and labelling

• Number every annex (Annex 1, Annex 2, etc.).
• Label files clearly (e.g., Annex-05-Website-Screenshot-2025-03-14.pdf).
• Refer to annexes by number in the submission.
• Do not submit a document without a schedule entry.

File size and format limits

At WIPO and Forum, the limits are typically:

• 10MB per attachment.
• 50MB total for all submitted materials.
• PDF, Word, or Excel formats.

Compress images where possible, but do not reduce readability. Split large annexes into parts if necessary.

Redaction and personal data

Redact personal data where necessary, but do not redact the evidence itself. If a document contains third-party personal data, redact only the personal data and explain the redaction in the schedule.

Translation

If the proceeding is in a language other than the language of the documents, provide translations. In the CNDRP, the proceedings default to Chinese; in the .eu ADR, the language is usually the language of the registration agreement. Translations should be certified where the provider requires it.

Word limits and what counts

The 5,000-word limit

At WIPO, the word limit for the complaint and the response is 5,000 words for the substantive submission. The limit applies to the grounds section, not the annexes. The same limit applies to the response under paragraph 5(b)(i) of the Rules.

Annexes and schedules

Annexes and schedules are not counted toward the word limit. This is why the evidence file can be extensive even when the submission is short. The discipline is to put the argument in the 5,000 words and the proof in the annexes.

Supplemental filings

Unsolicited supplemental filings are generally discouraged. Panels may accept them only in exceptional circumstances, and the party submitting must show relevance and why the information could not have been provided earlier. In The Scent Stories, the panel declined to admit a supplemental filing because the material could reasonably have been anticipated and investigated before the complaint.

Panel discretion and independent research

Visiting the website

Panels may visit the disputed domain name to assess disputed claims about its use. This is common practice, particularly where the parties disagree about whether the site is active, parked, or monetised.

Consulting the Wayback Machine

Panels commonly refer to the Wayback Machine to ascertain archived uses. WIPO Overview 3.0, section 4.8, confirms this practice.

Checking prior UDRP proceedings

Panels may assess previous UDRP proceedings involving a party, particularly where there are contradictory claims or a pattern of conduct.

USPTO and trademark databases

Panels may verify trademark rights on public databases. In CAC-UDRP-105436, the panel checked the USPTO website and found the complainant’s application was pending, not registered. The panel’s independent research was decisive.

Panels verify the record. We make sure the public record supports your submission before you file. Book an evidence review →

Evidence in ccTLD procedures

Nominet DRS

The DRS uses a 2,000-word response limit and a 15-working-day response deadline. The evidence must address rights and abusive registration. Mediation is free and automatic once a response is filed. The evidence should be focused and indexed, because the word limit is tight.

auDRP

The auDRP uses a 10-page limit for the complaint and response, excluding annexes, and a 20-calendar-day response deadline. The evidence must address the “registered or used in bad faith” test. The page limit forces discipline: lead with the strongest evidence.

CDRP

The CDRP requires affirmative evidence that the registrant has no legitimate interest. The panel will not infer a lack of legitimate interest from default alone. The evidence should include business registry searches, website captures, and any correspondence showing the registrant’s awareness of the complainant’s rights.

CNDRP

The CNDRP defaults to Chinese and has a 20-calendar-day response deadline. The evidence must address civil rights, not just trademarks. The three-year limit is a threshold issue: if the domain is older than three years, the complaint will not be accepted.

SACI-Adm

The SACI-Adm bad-faith standard is stricter: direct evidence of knowledge at registration is required. Circumstantial evidence such as a parked page may not be enough. The evidence should be built around the registration date, not the date of the complaint.

usDRP

The usDRP uses a 20-day response deadline and a disjunctive bad-faith test. The evidence should address registration or use, and the Nexus requirement should be documented where relevant.

Case studies: evidence in action

HCL.ai

HCL, a global technology company, filed a UDRP complaint over HCL.ai. The respondent, a professional domain investor, argued that “HCL” is a common three-letter acronym with multiple meanings. The panel found the domain identical to the HCL mark and ordered transfer. On legitimate interest, the panel acknowledged that domain investment can be legitimate but requires a credible rationale that does not rely on the trademark owner’s goodwill. The respondent offered no such rationale. On bad faith, the panel relied on surrounding facts — the strength of the mark, its recognition in the technology sector, the respondent’s sophistication, and the absence of a plausible alternative use — rather than direct evidence of intent.

Evidence lesson: Context can prove knowledge. The pairing of the mark with the .ai extension, the respondent’s sophistication, and the absence of an alternative explanation supported the inference.

The Scent Stories

The complainant filed a UDRP complaint over thescentstories.com. The respondent produced sales records and invoices showing use of the mark in India since 2022, plus a valid Indian trademark registration. The panel found no bad faith and denied the complaint. The panel also declined to admit an unsolicited supplemental filing and noted that the complaint appeared to have been AI-assisted without adequate verification.

Evidence lesson: Contemporaneous commercial records defeat a bad-faith allegation. AI-assisted drafting must be verified.

MF.com and fabricated evidence

The complainant alleged that the respondent had admitted registering the domain to hold it “hostage” and demanded US$50 million. The respondent alleged that the emails were fabricated. The panel rigorously tested the evidentiary record, rejected the fabricated evidence, and found RDNH. The panel anchored its analysis in first principles: targeting must be proven, not presumed.

Evidence lesson: Fabrication is fatal. Panels test the record, and an abusive complaint can lead to RDNH.

Karolinska

In D2024-4598, the respondent argued that the complainant’s trademark rights did not extend to Türkiye and that its US trademark post-dated the registration. The panel found the respondent had no legitimate interest: it did not explain why it registered the domain, its claimed patient forum was not supported by evidence, and the use of the exact mark in a TLD representing the complainant’s sphere of operations amounted to impersonation. The respondent’s own description of the complainant as “one of the world’s most renowned healthcare institutions” left no doubt that it intended to refer to the complainant.

Evidence lesson: The respondent’s own words can prove knowledge. A weak or inconsistent explanation for the registration can support the complainant’s case.

Lendscape

In Dio2022-0045, the respondent claimed a business idea for a residential mortgage service but provided no evidence of business formation, investment, or a genuine business plan. The panel found the mere configuration of two email accounts insufficient and upheld the complaint.

Evidence lesson: Assertions without documents are not enough. Demonstrable preparations require evidence.

The evidence checklist

Use this checklist before filing or responding.

Complainant

• Trademark rights: Registration certificate, status record, goods/services.
• Common-law rights: Sales, advertising, media, recognition.
• Confusing similarity: Side-by-side comparison, evidence of distinctiveness.
• Prima facie case: WHOIS, website captures, search results, business registry searches.
• Bad faith: Paragraph 4(b) evidence, technical evidence, prior conduct.
• Annex schedule: Numbered, described, and indexed.
• Screenshots: Dated, full-page, URL bar visible.
• Wayback captures: Historical use, pre-notice.
• WHOIS history: Registration date, transfers, prior registrants.
• Word limit: Substantive submission within 5,000 words.
• File limits: 10MB per attachment, 50MB total.
• Verification: Public record supports the claims; no fabricated or AI-generated material.

Respondent

• Paragraph 4(c) evidence: Bona fide offering, commonly known, fair use.
• Contemporaneous documents: Invoices, contracts, advertising, bank records.
• Business registration: Trading name, tax records, licences.
• Website captures: Dated, full-page, URL bar visible.
• Witness statement: Specific, corroborated, notarised where appropriate.
• Priority: Registration date, evidence of good-faith choice.
• No bad faith: No offer to sell, no pattern, no commercial gain from confusion.
• RDNH: Evidence of the complainant’s knowledge, failed acquisition, or abuse.
• Annex schedule: Numbered, described, and indexed.
• Word limit: Response within 5,000 words.

Ready to build the record? We prepare the annex file, test the evidence against the legal elements, and draft the submission. Get an evidence review →

How counsel.domains can help

If you are filing a complaint, we build the evidence file around the three elements, prepare the annex schedule, and draft within the word limit.

If you have received a complaint, we assess the complainant’s evidence, identify the gaps, and build the respondent’s record.

If the case involves technical evidence — MX records, phishing pages, lookalike domains — we coordinate the technical and legal analysis.

counsel.domains Domain name disputes, worldwide. Get an evidence review → · [email protected]

Disclaimer: This website provides general information about domain name dispute resolution. It is not legal advice and does not create a professional relationship. Procedures and fees change; check the relevant policy and provider before acting. counsel.domains is not affiliated with WIPO, ICANN, Forum, Nominet, auDA, CIRA, NIXI, CNNIC, EURid, Registro.br, or any registry or dispute-resolution provider.