Signed PDF certificate
The court-ready affidavit summarising URL, capture time, hashes, and signature.
To certify a webpage as legal evidence, use a service that captures the URL the browser actually resolved, the HTML and screenshot the server returned, and a qualified RFC 3161 timestamp. The result is a signed PDF that is much harder to dispute than a screenshot.
A screenshot is a picture of what your screen showed. A certified capture is a record of what the server actually returned, when, and to what URL.
Every Website certificate ships the same evidence chain.
The court-ready affidavit summarising URL, capture time, hashes, and signature.
The page as rendered by the controlled browser at the moment of capture.
The page's rendered HTML as captured, alongside the screenshot.
A single-file archive of the page with its assets inlined, for offline review.
The final URL the browser arrived at β after any redirects.
Every request the browser made β proof of which servers returned what.
Qualified independent signature on the captured content.
Manifest, signature, public key, hashes, timestamp request/response.
The entire flow takes a few minutes per URL.
Before you capture, check whether the site captures cleanly or serves bot-protection (a captcha or human-verification check). Cookie/consent banners are dismissed automatically, so they no longer block a capture. If a site is genuinely blocked, a blocked automated capture is never billed β and you can still capture it yourself with assisted capture, a human-driven session where you clear the challenge before the page is certified. Learn more about bot protection β
Go to /certificates/new and select Website. Enter the URL, and the platform opens a controlled browser, captures the full page, takes a HAR log, and binds everything to an RFC 3161 qualified timestamp. The result is a signed PDF with verification URL.
Screenshots are technically admissible but routinely challenged. A certified webpage capture is far harder to dispute because it binds the URL, the server response, and an independent timestamp into a signed package.
Yes. Use a Browser Session instead of a Website certificate. The isolated browser lets you log in and interact, then records the entire session with video, HAR, and signed timestamp.
The capture is performed by a controlled browser that fully renders JavaScript. The HAR log records every request, including those triggered after page load.
No. This service creates technical evidence artifacts. Legal admissibility depends on jurisdiction and circumstances. Consult qualified legal counsel for advice specific to your situation.
One URL, one certificate. The page is preserved before anyone can deny it ever existed.