Verify
Don’t trust it. Check it.
Enter the identifier of a publicly published ledger entry. The check reports chain integrity and signature validity separately — and says plainly what it does not prove.
Public entry check
Mode: public identifierReport
No check run yetA valid chain and signature show the record is intact and was signed by the listed key. They do not show that the recorded action was correct, or that the key belongs to who you think it does.
Check an exported receipt
Mode: local bundleReport
Local bundleIntegrity, signature, signer trust, tenant binding and coverage are separate results. SUPPORTED never means the evidence is complete or that an external effect happened beyond what the receipt’s own artifacts claim.
Other ways to verify.
Your own receipts
Signed in, your workspace verifies receipts from its canonical record, with your workspace bound as the expected tenant.
Sign inOffline, on your machine
The packaged ardyn-verify CLI runs the same checks with no network and prints the same result digest.
What stays private
Public identifiers resolve only entries that were intentionally published. Knowing a customer’s identifier does not reveal their records.
Trust boundaries