Capturing Evidence for UDRP Domain Name Disputes
Published April 2, 2026
Someone registered a domain name that is identical or confusingly similar to your trademark. The site is parked with pay-per-click ads, redirecting to a competitor, or displaying content designed to mislead your customers. You need the domain transferred to you - and you need to prove why.
The fastest path is a UDRP complaint. But the strength of that complaint depends entirely on the evidence you attach to it.
What Is a UDRP Complaint?
The Uniform Domain-Name Dispute-Resolution Policy (UDRP) is an arbitration process established by ICANN that allows trademark holders to challenge domain name registrations without going to court. If you can prove that a domain is identical or confusingly similar to your trademark, that the registrant has no legitimate interest in it, and that it was registered and used in bad faith - the panel can order the domain transferred to you or cancelled.
UDRP complaints are filed through approved dispute resolution providers. The World Intellectual Property Organization (WIPO) is the largest, handling thousands of cases each year. Other providers include the Forum (formerly NAF), the Asian Domain Name Dispute Resolution Centre, and the Czech Arbitration Court. The process typically takes 45 to 60 days from filing to decision.
Complainants are usually brand owners, companies, and trademark holders whose marks are being exploited by cybersquatters - people who register domains in bad faith to profit from the confusion.
Why Evidence Is the Make-or-Break Factor
UDRP panels decide cases on the papers alone. There is no hearing, no cross-examination, no opportunity to explain what you meant. The panel reads your complaint, reads the respondent's response (if they bother to file one), and makes a decision based on the evidence submitted.
This means your evidence has to speak for itself. And there is a critical timing problem: once the respondent is notified of the complaint, they often take the infringing site down, replace its content, or switch it to a blank page. If your evidence was not captured before they received notice, the panel may never see what the site actually looked like when it was causing harm.
Panels have explicitly noted this problem. A screenshot taken after the respondent has cleaned up the site proves nothing about the bad faith use that motivated the complaint. You need evidence captured while the infringing content is still live.
What UDRP Panels Want to See
To prove bad faith registration and use, panels typically look for these categories of evidence:
- Screenshots of the infringing site - full-page captures of the homepage and key inner pages showing how the domain is being used. Pay-per-click parking pages, competitor redirects, and sites mimicking your brand are all strong indicators of bad faith.
- WHOIS registration records - showing when the domain was registered, by whom, and through which registrar. This helps establish the timeline and whether the registrant knew of your trademark when they registered the domain.
- Pay-per-click or advertising evidence - screenshots showing that the domain resolves to a page monetized through ads, especially ads related to your trademark or industry. This is one of the clearest signals of bad faith use.
- Confusingly similar content - evidence that the site uses your logos, brand colors, product descriptions, or other elements that could mislead consumers into thinking it is affiliated with your brand.
- Timestamps on everything - panels need to know when evidence was captured. Undated screenshots carry little weight, and screenshots with timestamps from after the complaint was filed are essentially useless for proving pre-complaint bad faith.
How to Capture Strong UDRP Evidence
Follow these four steps to build an evidence package that gives the panel everything it needs.
Step 1: Screenshot the homepage and key pages of the disputed domain
Capture the full page - not just the visible viewport, but the entire scrollable content. Include the URL bar and the date of capture. If the site has multiple pages (an about page, a contact page, product listings), capture those too. Each page is a separate piece of evidence showing how the domain is being used.
Use a server-side capture tool rather than a manual browser screenshot. A server-side capture proves the page was visited independently - there is no possibility that you modified the content using browser developer tools before taking the screenshot.
Step 2: Capture the HTML source
A screenshot shows what the page looks like. The HTML source shows what the page actually contains. Hidden elements, meta tags stuffed with your trademark terms, affiliate tracking codes, ad network scripts - all of this is invisible in a screenshot but can be decisive evidence of bad faith.
A complete DOM capture preserves every element, every link, every script tag, and every hidden div. If the respondent argues they were not targeting your trademark, the HTML source can reveal keyword-stuffed meta descriptions, hidden text, or redirect scripts that tell a different story.
Step 3: Get a trusted timestamp
The date on your computer is trivial to fake. A panelist has no way to verify that a screenshot was really taken on the date you claim. This is where RFC 3161 trusted timestamps matter. An RFC 3161 timestamp is issued by an independent Time Stamp Authority - a third party whose clock and signing key you cannot control. It cryptographically certifies that your evidence existed at a specific moment in time.
Combined with a SHA-256 hash of your screenshot and HTML capture, this creates a mathematically verifiable chain: the content was captured at this exact time, and it has not been altered since. WIPO panels and other UDRP providers recognize this level of verification.
Step 4: Generate a professional PDF report
UDRP complaints are formal filings. A collection of loose screenshot files and text documents looks unprofessional and makes the panel's job harder. Package your evidence into a clean PDF report that includes the screenshots, the URL, capture timestamps, hash values, and the timestamp certificate - all in a format that is easy for a panelist to review.
How Snapoena Handles All of This Automatically
Doing each of these steps manually requires coordinating multiple tools - a headless browser for screenshots, a DOM extraction script, a hashing utility, an RFC 3161 timestamp service, and a PDF generator. It is slow and error-prone, especially when you are under time pressure to capture evidence before the respondent takes the site down.
Snapoena handles all of this in a single step. Paste the URL of the disputed domain, click capture, and Snapoena's server:
- Visits the URL independently and takes a full-page screenshot with the URL and UTC timestamp embedded directly in the image
- Captures the complete HTML source and DOM structure of the page
- Computes a SHA-256 hash of the screenshot and source
- Sends the hash to an independent RFC 3161 Time Stamp Authority for cryptographic certification
- Packages everything into a downloadable evidence bundle ready to attach to your UDRP complaint
Run one capture for the disputed domain. Run another for your own site to document the legitimate trademark use. You now have a complete, timestamped, cryptographically verified evidence package - captured before the respondent had any reason to take the site down.
Capture First, Then File
UDRP complaints succeed or fail on the evidence. Panels decide on the papers alone, and once the respondent is notified, the site content you need to prove bad faith may disappear. The window for capturing evidence is before you file - not after.
Document the infringing domain thoroughly, get a trusted timestamp on every capture, and submit evidence that a panel can verify independently. That is how you win a UDRP dispute.
Filing a UDRP complaint?
Capture the disputed domain with a server-side screenshot, HTML source, SHA-256 hash, and RFC 3161 timestamp. Free to use.
Capture Evidence Now