QILAHK / EVIDENCE & VERIFICATION EXAMPLE

See how a credential
changes over time.

Signed evidence, explicit boundaries and a visible lifecycle.

SYNTHETIC SANDBOX — NO PRODUCTION TRUSTMARK. All devices and findings are fictional. The signing key was generated only for this demonstration. This page checks a packaged snapshot, not QILAHK’s live registry or real device state.

Choose a verification case

What is being checked?

Credential DEMO-QK-0001 covers three reported configuration attributes for fictional device DEMO-001. It makes no organizational, compliance or attack-prevention claim.

Verification time is simulated and shown below. The key is pinned inside this example; it is not a production issuer trust anchor.

Ready to verify

Select a case and run the check.

How verification works

  1. Validate the credential and lifecycle signatures with the pinned demo public key.
  2. Match the evidence hash, credential identity, event sequence and chained event hashes.
  3. Check event times, validity period and latest status present in the selected snapshot.
  4. Reject tampering and display suspension, revocation or expiration explicitly.
View signed bundle
Offline snapshots can omit newer events. Production verification needs an authoritative, fresh status service, protected signing keys and independently distributed trust anchors. This demonstration cannot establish current production status.
Supporting materials