Capture the web as tamper-evident evidence — not just screenshots.

GetProofAnchor captures web pages as tamper-evident evidence. It creates a verifiable record of what was visible online at a specific time and lets others later verify whether the evidence still matches the original captured state.

A screenshot shows appearance, but by itself it does not reliably prove source, capture time, or later integrity. GetProofAnchor adds structured metadata, cryptographic hashes, timestamps, and verification artifacts so later changes become detectable.

Tamper-evident means changes are detectable. If someone modifies the screenshot, page.html, extracted content, or another part of the package later, verification should show that the evidence no longer matches the original recorded state.

A Proof ID is the permanent identifier of a capture. You can share it as a reference and later use it to load the public proof record or connect it to an exported Evidence ZIP.

The Evidence ZIP is a portable evidence package. Depending on the capture, it can contain a screenshot, extracted content, page.html, proof metadata, a manifest with SHA-256 hashes, timestamp artifacts, and blockchain anchoring artifacts.

It lets evidence leave the platform in a portable form while preserving later verifiability. Instead of sharing just an image, you can share a package that can be independently checked for integrity.

The manifest lists the files in the package together with their cryptographic hashes. During verification, hashes are recalculated and compared. If any file changed, verification should fail.

Yes. The Evidence ZIP is designed for offline or independent verification workflows because it contains the files and integrity data needed to re-check whether the package still matches its original recorded state.

SHA-256 is a cryptographic hash function. It creates a fingerprint of a file or payload. Even a very small change produces a different hash, which is why it is useful for integrity verification.

If someone changes the screenshot, page.html, extracted content, metadata, or package structure, the hashes will no longer match the original manifest or timestamped payload. Verification should then report a mismatch.

An eIDAS-qualified timestamp proves that a specific hash existed at a specific time, based on a trusted timestamping authority. It does not store the webpage itself; it timestamps the cryptographic fingerprint of the evidence payload.

OpenTimestamps anchors a cryptographic hash into the Bitcoin blockchain. That provides public, independently checkable existed-before evidence for that hash. Because the anchor is tied to the hash, it also supports later integrity verification.

Simply recalculating hashes is not enough. That would break the relationship to the original timestamp, manifest, or blockchain anchor. That is exactly why later manipulation becomes detectable.

No. GetProofAnchor provides verifiable integrity and evidence workflows, but it is not legal advice. Admissibility and evidentiary weight depend on jurisdiction, procedure, and circumstances.

Yes. The browser extension captures what you actually see, including authenticated pages you lawfully have access to.

Yes — if you captured it in time. The evidence shows what was published or visible at that moment, even if the page later changes or disappears.

Chain of custody describes how digital evidence is captured, handled, and preserved over time. For credibility, it is essential to demonstrate content integrity, capture time, and traceability of the evidence. GetProofAnchor supports these principles using cryptographic hashes (SHA-256), file manifests, timestamps (including eIDAS), and blockchain anchoring, ensuring that any modification of the evidence can be detected.