Web evidence you can prove.

Capture any web page and get a signed, timestamped evidence bundle. Anyone can verify the proof independently -- no account, no trust in us required.

No credit card required.
Sign in with GitHub.

Built for teams who need proof, not promises.

Screenshots get challenged. WRL captures produce signed, timestamped evidence bundles designed to support authentication under federal and EU evidence standards:

  • FRE 901(b)(9) -- automated process producing verifiable results, no human in the chain of custody
  • FRE 902(14) -- SHA-256 hash integrity as the digital identification process
  • eIDAS Art. 41(2) -- optional qualified timestamps with legal presumption of accuracy across all EU member states

How WRL supports evidence authentication →

Compliance Archiving

Regulatory audits require evidence that your web-facing content met requirements on specific dates. WRL provides timestamped, tamper-evident records of any public web page. Each capture is independently verifiable -- your auditor can check it without trusting your internal systems.

How verification works →

AI Agent Grounding

When an AI agent reports what a web page contains, the claim is only as good as the source. WRL's MCP server and REST API let agents capture pages and produce signed evidence of what they observed. Ground agent outputs in verifiable snapshots, not ephemeral browser sessions.

MCP server documentation →

Journalism and Research

Sources go offline. Pages get edited. WRL preserves the original with cryptographic proof of when it was captured. Share the verification link with editors, fact-checkers, or readers -- the evidence speaks for itself.

How verification works →

Independently Verifiable by Design

Evidence Integrity

Ed25519 Digital Signatures

Every capture is cryptographically signed. Proves who captured it and that nothing was altered.

Independent Timestamps

A third-party authority records when the capture happened. No one -- not even WRL -- can backdate it.

Public Verification

Share a link. Anyone can confirm authenticity -- no account, no special tools required.

How verification works →

eIDAS Qualified Timestamps

Optional EU-standard timestamps with legal presumption of accuracy across all EU member states.

Legal evidence guide →

CLI Verification Tool

Verify captures offline with a single command. No network, no dependencies on us.

Verification docs →

Developer Experience

REST API

One POST, one signed evidence bundle. Batch captures, scheduled captures.

API reference →

MCP Server

AI agents can capture and verify web pages with cryptographic proof.

MCP docs →

Webhooks

Get notified when captures complete. Integrate into any workflow.

Webhook docs →

WACZ Standard Format

Open archive format created by Webrecorder. Not locked to any vendor.

Self-Hostable

Deploy on your infrastructure. Your keys, your storage, your evidence chain.

Full feature comparison across 10 tools →

How It Works

  1. Capture

    Submit a URL. WRL renders the page in a headless browser, captures a screenshot, the rendered HTML, and HTTP headers -- recording what the page looked like at that moment.

  2. Sign

    Every artifact is hashed, bundled into a WACZ archive, and signed with Ed25519. An independent RFC 3161 timestamp from a third-party authority anchors the capture to a specific point in time.

  3. Verify

    Share the verification link with anyone. They can confirm the content has not been altered and the timestamp is authentic -- no account needed, the cryptography proves it.

How WRL Compares

Comparison of WRL with other web evidence tools
Feature WRL Manual + Notary Webrecorder Wayback Machine PageFreezer
Crypto Signing Ed25519 (every capture) Notary attestation Spec exists (not default) No SHA-256
Independent Timestamps RFC 3161 (default) Notary timestamp In spec (not default) No Proprietary clock
Public Verification Yes (no account) Via notary records Validator tools Public access (no crypto) No
Open Format WACZ N/A WACZ + WARC WARC PDF
Social Media Archiving No No No No 8+ platforms
Scheduled Bulk Monitoring No No Browsertrix Automated crawls Daily+ crawls
Expert Witness Service No Yes No $250 affidavit No

Full comparison across 14 tools -- including where WRL is not the right choice →

When to Use Something Else

WRL does one thing well: on-demand, API-driven evidence capture with cryptographic proof. These tools are better choices for other needs:

Open-source web archiving at scale

Need to crawl and preserve entire websites? Webrecorder created the WACZ format WRL uses and offers Browsertrix for large-scale archiving. Self-hostable, open source, backed by national libraries worldwide.

Bulk compliance monitoring

Need to monitor thousands of URLs daily for regulatory compliance? PageFreezer and MirrorWeb are built for continuous, enterprise-scale archiving with compliance dashboards.

Social media archiving

Need to capture Twitter, LinkedIn, TikTok, or Slack? Hanzo and PageFreezer integrate with platform APIs to capture posts, comments, reactions, and deletions.

Court-ready evidence with expert testimony

Need affidavits, expert witnesses, and established court precedent? Page Vault has had evidence admitted in 10+ federal court cases and provides expert witness services WRL does not offer.

Pricing

On-Premise / Enterprise

Deploy WRL on your own infrastructure. Your keys, your storage, your evidence chain. Custom SLAs and volume pricing available.

Contact us →

Frequently Asked Questions

Why is a screenshot not enough for digital evidence?

Screenshots carry no proof of integrity -- pixels are editable and file timestamps are adjustable. A WRL capture is an Ed25519-signed WACZ bundle with SHA-256 hashes and an independent RFC 3161 timestamp. It includes all page resources, not just a rendered image. Anyone can verify the signatures and timestamps independently -- no account required.

Is web capture evidence admissible in court?

WRL captures provide the technical foundation for authentication under FRE 901(b)(9) and support self-authentication under FRE 902(14). With the eIDAS qualified timestamp option, captures carry an EU-recognized qualified electronic timestamp under Article 41(2). Admissibility depends on jurisdiction and the specific proceeding -- WRL provides the technical evidence foundation. Learn more about the legal framework, and consult qualified legal counsel for your matter.

Can I verify a capture without an account?

Yes. Every capture has a public verification URL. Verification checks signatures and timestamps using the CLI tool or web verifier. No account or API key is required.

What is forensic web capture?

Forensic web capture preserves web content in a way that maintains evidentiary value -- integrity through cryptographic hashing, a documented methodology, and a verified point in time. WRL's automated pipeline aligns with SWGDE best practices: every capture runs in a fresh, isolated browser, each artifact is hashed with SHA-256, and the signed bundle receives an independent RFC 3161 timestamp.

What is chain of custody for digital evidence?

Chain of custody tracks who handled evidence, when, and what they did with it. For digital evidence, it means proving data has not been altered between collection and presentation. WRL establishes a cryptographic chain of custody from capture through signing: the pipeline hashes every artifact, signs the bundle with Ed25519, and obtains an independent RFC 3161 timestamp -- all in a single automated process with no human handling. Learn how WRL documents the evidence chain.

What is defensible web collection?

Defensible collection means the method used to gather electronically stored information can withstand legal scrutiny. It requires a documented, repeatable process with a verifiable chain of custody. WRL's automated pipeline produces a signed, timestamped evidence bundle for every URL -- the process is deterministic, the output is independently verifiable, and the full methodology is documented. See how WRL supports defensible collection.

How do I preserve website evidence for litigation?

Submit the URL to WRL's capture API. The automated pipeline renders the page in an isolated browser, captures a screenshot, rendered HTML, and HTTP headers, then packages everything into a signed WACZ evidence bundle with an independent timestamp. For ongoing preservation, scheduled captures monitor URLs at regular intervals. For bulk collection, the batch API accepts up to 100 URLs per request.

How do OSINT investigators preserve web evidence?

OSINT investigators need to capture web content before it disappears -- social media posts, forum threads, product listings -- while maintaining a provenance record others can verify. WRL provides an API-driven approach: submit a URL, receive a signed WACZ bundle with proof of when the content existed and that nothing was altered after capture. The batch API handles up to 100 URLs per request, and scheduled captures monitor volatile pages automatically.

How do I archive web pages for regulatory compliance?

Regulatory audits require proof that public-facing content met requirements on specific dates. WRL creates a tamper-evident, independently timestamped record of any web page on demand -- your auditor can verify integrity without trusting your internal systems. For recurring obligations, scheduled captures automate regular snapshots. With the eIDAS qualified timestamp option, EU-regulated organizations get timestamps with a legal presumption of accuracy under Article 41(2).

How do I document online trademark infringement?

Trademark enforcement requires evidence that infringing content existed at a specific time on a specific page. Screenshots are easily challenged -- they carry no proof of integrity or timing. WRL produces a signed, timestamped evidence bundle with cryptographic proof of what the page contained and when, verifiable by opposing counsel or the tribunal without special tools. Scheduled captures can document duration and evolution of infringement.

What is an audit trail for web content?

An audit trail for web content is a verifiable record of what a page contained at specific points in time. Built on WRL captures, each record is cryptographically signed, independently timestamped, and stored in WACZ -- an open format not locked to any vendor. Auditors can confirm integrity using the public verification endpoint or the open-source CLI tool, with no account or platform access needed.

Can I self-host WRL?

Yes. WRL's full source code is public on GitHub. You can deploy it on your own Cloudflare Workers infrastructure for internal use. The hosted service at api.webresourceledger.com is the same codebase. The PolyForm Shield license permits all uses except offering a competing web capture service.