Signed PDF certificate
The court-ready affidavit summarising URL, capture time, hashes, and signature.
How to · Website & webpage
How to legally certify a website or webpage as evidence
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.
URL boundResolved by browser
HAR + screenshotServer response captured
RFC 3161Qualified timestamp
Why a screenshot is not enough.
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.
✗
The URL is not cryptographically boundAnyone can edit a URL into a graphic. Certificates bind the resolved URL.
✗
JavaScript-rendered content may be missingStatic screenshots can omit content rendered after page load.
✗
The page could be edited before or afterWithout a timestamp, the "when" is your word against theirs.
✗
There is no proof of the server responseHAR captures what the server actually sent; screenshots do not.
What a certified website capture includes.
Every Website certificate ships the same evidence chain.
Full-page screenshot
The page as rendered by the controlled browser at the moment of capture.
Resolved URL
The final URL the browser arrived at — after any redirects.
network.har
Every request the browser made — proof of which servers returned what.
RFC 3161 timestamp
Qualified independent signature on the captured content.
Metadata ZIP
Manifest, signature, public key, hashes, timestamp request/response.
How to certify a website in four steps.
The entire flow takes a few minutes per URL.
1
Open /certificates/newSelect the Website certificate option.
2
Paste the exact URLUse the canonical, sharable URL — not a transient session link.
3
Wait for the controlled browser to captureThe platform opens an isolated browser, loads the page, takes a full-page screenshot, and records the HAR.
4
Download the certificate packagePDF + metadata ZIP. Share the PDF; verify the ZIP independently.
Common use cases for certified website evidence.
Defamation evidence →Preserve a defamatory article or post URL before it is deleted.
Fake review evidence →Capture suspect reviews before the platform removes them.
IP infringement evidence →Certify an infringing webpage before the seller is alerted.
Landlord-tenant disputes →Preserve a rental listing the day you sign for the property.
Website-certification questions, answered directly.
How do I legally capture a website as evidence?
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.
Is a screenshot of a website admissible in court?
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.
Can I capture a page that requires login?
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.
What about pages with dynamic or JavaScript content?
The capture is performed by a controlled browser that fully renders JavaScript. The HAR log records every request, including those triggered after page load.
Is this legal advice?
No. This service creates technical evidence artifacts. Legal admissibility depends on jurisdiction and circumstances. Consult qualified legal counsel for advice specific to your situation.
Ready to certify?
One URL, one certificate. The page is preserved before anyone can deny it ever existed.