Evidence Capture
Capture a public web page as evidence.
Paste a public URL and pay US$9 once by card. No account and no API key. You get one ZIP with a screenshot and the page's HTML from one browser load, the SHA-256 of each file, the time of the render, and a signed PageVerified record that binds them.
What you get
- screenshot.png and page.html, both from one browser render of the page.
- The SHA-256 of each file and the UTC time of the render.
- record.json: the signed record (pvrf/1) that binds those values. Check it at /verify or offline with the open verifier.
- Outside RFC 3161 timestamps on the record when they arrive. They are requested every 15 minutes. Until then the result page says "timestamp pending", and your download link gives the stamped version later.
- A plain-English README of what each file shows and what it does not.
What it shows
- What PageVerified's browser rendered at that URL at that time. The HTML is the page after its scripts ran, not the raw bytes the server sent.
- That the record has not been changed since it was signed, and, once the outside timestamps arrive, since their time.
What it does not show
- Who wrote the page.
- That other visitors saw the same thing.
- Whether anything on the page is true.
A login wall, cookie wall or bot check is captured as what was rendered. If the render looks like one of those, the result page and the README say so.
Refunds and privacy
If the capture fails (the site is down, blocks the browser or times out), it is tried once more. If it fails again, you get a full refund automatically. If the page is too large to store, you get a full refund straight away. With each order we keep the URL, the order's state, the Stripe payment references, the amount paid, the record id and the times for 365 days, and nothing else about you. Separately, to limit how many orders one network can start, a one-way hash of your IP address is kept for an hour. See the refund policy and the privacy policy.
