About Snapoena
snap-OH-en-ah - from "snapshot" + "subpoena"
Snapoena was built out of frustration. When filing a domain complaint to a registrar, the founder needed a credible screenshot with the URL and timestamp visible. Browsers can capture pages, but the output is just an image - no metadata, no verification, no proof of when it was taken. The only options were expensive enterprise tools ($15-30 per capture) or manually editing screenshots in an image editor.
Snapoena fills the gap: documented website screenshots in one click. Server-side capture means a third party (our server) visited the URL - you never touched the raw image. The URL, timestamp, and SHA-256 hash are permanently embedded. RFC 3161 timestamps from a trusted authority prove exactly when the capture was made.
Our Mission
We believe everyone deserves access to court-ready digital evidence tools, not just those who can afford expensive forensics firms.
Built for people who file complaints, send cease & desist letters, report trademark infringement, and preserve web evidence.
How It Works
Every capture follows the same evidence-grade pipeline, whether triggered from the web app, the API, or the browser extension.
- Capture. The page is rendered server-side with Playwright (a headless Chromium browser) or captured client-side via the browser extension. Server-side capture means an independent third party - our server - visited the URL, not you.
- Hash. A SHA-256 cryptographic hash is computed over the raw screenshot bytes. Any alteration to the image - even a single pixel - produces a completely different hash.
- Timestamp. The hash is sent to an independent RFC 3161 Timestamp Authority (TSA). The TSA signs the hash with its own key and returns a timestamp token, proving the capture existed at that exact moment. Snapoena cannot forge this - the signature comes from the TSA, not from us.
- Store. The screenshot, metadata, and timestamp token are stored on Cloudflare R2 with Litestream replication for durability. The URL and timestamp are also embedded directly into the image itself.
- Package. All evidence - the screenshot, SHA-256 hash, RFC 3161 timestamp token, page source, and capture metadata - is bundled into a single downloadable package you can attach to a legal filing or send to opposing counsel.
Open Standards
Snapoena is built on open, well-documented standards - not proprietary formats that lock you in. Any qualified expert can independently verify a Snapoena capture without our involvement.
| Standard | Purpose |
|---|---|
| SHA-256 (FIPS 180-4) | Cryptographic hash for tamper detection |
| RFC 3161 | Trusted timestamps from independent authorities |
| HAR 1.2 (W3C) | HTTP archive format for full network activity capture |
| RFC 2557 (MHTML) | Single-file web page archive with all resources embedded |
Contact
Questions, feedback, or partnership inquiries? Email hello@snapoena.com.
For legal or compliance questions, include "Legal" in the subject line and we will prioritize your request.