Public verification

Verify a capture. No account needed.

Every Permavault capture is sealed with cryptographic fingerprints and stored on Arweave. Paste a fingerprint, transaction id, or capture id below to confirm the capture exists and see when it was sealed.

Accepted formats: 64-character hex hash, 43-character Arweave transaction id, or a capture id in UUID form. The format is detected automatically.

or

Drop a file here or click to browse

The SHA-256 is computed in your browser. The file itself never leaves your device; only its hash is looked up.

What this verifies, and what it does not

  • Existence and timing. This page confirms that a Permavault capture exists and shows when it was sealed: the content hashes, the Arweave transaction, and the Bitcoin anchor on record. Captures with a Legal certificate also show a qualified electronic timestamp, applied to the signed manifest when the certificate was issued.
  • Integrity is checked independently. To prove a file is byte-for-byte what was captured, download its evidence package and run the included verify.sh with standard tools (shasum, openssl, curl). No Permavault account, no trust in this website. Try the sample package or read the Guide.
  • What a match does not prove. That the captured content is true, accurate, or complete. A match proves a capture exists, what its bytes hash to, and when it was sealed. It does not vouch for what the source page claimed.
  • Storage is designed for permanence. Captures live on a permanent decentralized network of roughly 300 independent nodes, funded by a long-term storage endowment, so the record stays checkable even if Permavault the company is gone. Any Arweave transaction id can be checked here, not just Permavault captures.