Verify an export
Drop a Message Vault export here. Your browser computes its SHA-256 fingerprint locally and asks our seal registry whether that fingerprint has been sealed. The file itself is never uploaded.
A seal proves this file has not changed since it was sealed, and when our server first saw its fingerprint. It does not prove the messages were complete or true at that time.
Drop an export file here, or click to choose one.
PDF, CSV, or JSON export. You can also drop its .mvseal.json alongside it. Nothing is uploaded.
or paste a fingerprint
How the check works
- Your browser hashes the file with SHA-256 (WebCrypto). A single changed byte produces a different fingerprint.
- It looks the fingerprint up at
/api/seal/<sha>. If a record exists, it shows when our server first received that fingerprint. - It checks the record’s receipt, an Ed25519 signature over
sha|manifestHead|receivedAt|id, in your browser against the public key below. That proves the record came from us and was not edited. - If a public timestamp authority also answered when the seal was made, you can download that RFC 3161 token and verify it with OpenSSL, so the time claim does not depend on trusting us.
Public seal key
Ed25519, raw 32 bytes, base64. The same key is embedded in the Message Vault app.
BM9rpTxshftgEKaWHFOi0QORICD4ovNQb/d0JbtQmTI=