Domain Takedown Evidence: What to Capture Before You Report
Takedown channels, whether abuse desk, UDRP panel, or court, act on documented observations, not assertions. A complete package holds the current registration record, DNS answers, timestamped full-page captures, and all correspondence, preserved before the operator is warned and can delete it.
Updated
- WIPO filing form annexes
- Trademark proof + website screen capture
- Standard of proof
- Preponderance of evidence
- Golden rule
- Capture before you contact
Evidence decides each channel. A registrar abuse desk can only act on what it can verify for itself. A UDRP panel decides on the preponderance of the evidence (more likely than not), and WIPO panels hold that conclusory statements unsupported by evidence will normally be insufficient. What is attached often decides whether a report leads anywhere.
Capture first, contact second
A common mistake is acting before preserving. A cease and desist letter or an abuse report warns the operator, who can delete the hosted content or move it in response. Once the phishing page is gone, your report describes something nobody can verify. Preserve everything before anyone is notified.
The layers of a complete package
Registration record. Save the full RDAP or Whois record as it exists today: sponsoring registrar and abuse contact, creation timestamp, status codes, name servers, and registrant data where visible. During a UDRP case the registrar also confirms its registration data to the provider, so your saved record can be checked against it. The abuse contacts tool pulls this record for any domain.
DNS state. Record the answers, not conclusions: the A/AAAA records resolving the name, MX records if the domain is set up to receive mail, and NS records showing where it is delegated. Note the resolver and the UTC time of each query.
The site content. WIPO’s filing form asks for a screen capture of the offending website among the annexes. Capture full-page screenshots that include the browser address bar, save the exact URLs of each offending page, and note form fields that ask for credentials or payment data. Record the precise UTC timestamp of each observation.
Correspondence. Keep the full exchange: your demand letter and proof of delivery, their reply, any offer to sell. WIPO panels generally admit settlement discussions where they are relevant to the respondent’s motivation, though negotiating does not by itself indicate bad faith.
Inbound email. When the abuse arrives as mail rather than a site, such as fake invoices or impersonating replies, preserve the original message with full headers intact. The Received chain records which servers handled the message, and the envelope sender (Return-Path), the DKIM signing domain (d=), and the SPF result tie the mail to the lookalike registration. MX records only show that the domain can receive replies.
What each audience needs
| Audience | Decides on | Needs most |
|---|---|---|
| Registrar abuse desk | Deceptive or malicious use | The observed content, DNS facts, timestamps |
| Hosting provider | The hosted material | Exact URLs and what they serve |
| UDRP panel | Three policy elements | Registration data, content captures, rights evidence |
| Counsel | The whole picture | Everything, with an unbroken timeline |
Each row is a reason to collect broadly: the package that satisfies a registrar is a subset of what a panel needs, and a subset again of what counsel wants.
The product shortcut
notolens keeps this record automatically. Each domain match carries an append-only record of each observation (registration data, DNS answers, and what the site served where it was captured), and the Evidence PDF export packages the verifiable facts a third party can rely on: the registration record, the DNS records, and the captured page where one exists, each with its observation time, without interpretation layered on top.
Evidence decays in both directions: content disappears when you act, and a subject that reappears after a takedown needs a fresh record of what it serves now. Domain monitoring re-checks the matches you watch or have in takedown, and any match you refresh manually, so the package you send describes what was observed.
Sources
- WIPO: online UDRP complaint filing form
- WIPO: guide to the UDRP
- ICANN: Uniform Domain-Name Dispute-Resolution Policy Rules (paragraph 3 filing requirements)
- WIPO Overview 3.1: panel views on evidence, archives, and settlement statements
- RFC 5321: Simple Mail Transfer Protocol (MX lookup, trace fields, Return-Path)
- RFC 6376: DomainKeys Identified Mail (DKIM) signatures
- RFC 7208: Sender Policy Framework (SPF)
Frequently asked questions
UDRP Rules paragraph 3(b) requires the complaint to identify the domains in dispute, describe the grounds, and annex documentary evidence. WIPO’s filing form says the annexes should normally include proof of trademark rights and a screen capture of the offending website, and WIPO panels cite dated screenshots and correspondence between the parties as the kind of evidence bad-faith claims need. Panels decide on the preponderance of the evidence (a fact is proven when it is more likely than not true), and conclusory statements without evidence will normally be insufficient.
Not for a WIPO UDRP case: WIPO says the complaint does not have to be certified or notarized. A screenshot should still show the full browser address bar and you should record the URL and the exact UTC time it was taken. Undated captures of partial pages invite challenges that full-frame, timestamped ones do not.
Yes where possible. A capture in a third-party archive such as the Wayback Machine corroborates what the page contained at a given time. Respondents can block archivers via robots.txt. WIPO panels treat a robots.txt block as neutral on its own, but a block put in place only after notice of potential trademark abuse may support an inference that the respondent sought to hide incriminating content, so a block and its timing are worth documenting too.
That is the common failure mode this process exists to prevent. Operators delete sites after a demand letter or takedown. If your own captures are gone, archives may still hold a copy. And if the subject reappears later, a monitoring record gives you a fresh, timestamped baseline.
Related tools and resources
Ongoing brand monitoring
notolens checks new domain registrations across 1,570 TLDs and app store results daily, search ads multiple times a day, and trademark registers weekly. When a lookalike domain, conflicting mark, copycat app, or ad using your name appears, notolens checks it, explains the risk, and hands you the records and possible next steps.