See how a record is checked · record data stays in this tab

Check an evidence record. See what holds.

For compliance teams who already have a Planisphere record: add ATTESTATION.json to recompute the Merkle root, then add artifact files to check the bytes. Your files never leave this tab; the browser shows what matched, what failed, and what was not checked.

Your record Record check →

Local check Drop files here. ATTESTATION.json required · artifacts check bytes

IndexWaiting for ATTESTATION.json

FilesNot checked yet

RootNot checked yet

SignatureIf present

Same checker as the record check. This page uses your files.

Check status

FilesNot checked

RootNot checked

SignatureChecked when present

Root comparison

Claimed in record

Recomputed in your browser

Record receipt

Artifact ledger

Filename	Claimed sha256	Recomputed sha256	·

01 ·

What gets checked.

Index proves structure · artifacts prove bytes · signature proves key

Index check

ATTESTATION.json reconstructs the claimed root.

This proves the record index is internally consistent. It does not check artifact bytes unless you provide the files.

Artifact check

Provided files are SHA-256 checked against the record index.

A changed artifact fails at the byte layer even if the manifest root still recomputes from its claimed hashes.

Signature check

Ed25519 is checked when present and supported by the browser.

Hash checking proves integrity against the record index; issuer authenticity should be pinned to a trusted key.

Open the record check Methodology preprint