Verify the record you hold.

Bring an original ECL-1 evidence bundle and a trust policy: a file naming the issuers, keys, permitted uses and rules you choose to accept when checking a record. The verifier checks those bytes against that policy. It does not ask G-14 whether the result should pass.

After a runtime example on the home page has run, download its bundle and policy. Nothing is preloaded, and no policy is chosen for you.

Development-key limit. Local development runs use public test keys whose private halves anyone can derive. Anyone can produce a bundle that passes under that policy. A passing result does not establish G-14 as its origin, protected key custody or independent assessment. Production evidence needs its own identified issuers and trust policy.

These fields are processed in this browser; this form does not submit them to G-14. Do not paste private keys or confidential customer data.

Evidence bundle, or a JSON array of bundlesTrust policy (required)

No policy is selected for you. A valid signature under a supplied policy does not establish who published that policy or how its keys were protected.

Browser input limits: 100 bundles, 2 MiB of combined bundle JSON and 256 KiB of policy JSON. The verifier also limits each bundle to 1 MiB. Single bundles and array members are checked from their supplied text, not rewritten JSON.

What a passing result means

Checks on the supplied record

Envelope signatures and payload digests, under the keys and purposes in your supplied policy.
The required links between request, decision, authority and applicable execution events for that path.
Recorded timing and authority-window requirements. Those times remain the producers’ assertions.

Questions it cannot settle

Who published the policy, who actually controls its keys, or whether you should trust them.
Whether a reported effect happened in the receiving system, or whether an earlier observation is still current.
Trusted time, undisclosed events, complete populations, or independent assessment of the deployment.
Other G-14 authority, development, production or custody objects that do not use these ECL-1 action-evidence schemas.

Each result lists its checks and the hash of the bytes checked. If your clock is earlier than a record’s stated time, the tool discloses the alternate evaluation time it used; that is not a trusted-time attestation.

Keep verification separate from custody.

Keep the original bundle, the policy and the verifier version you reviewed. A whole-run download also includes verification material, but its assembly time and expiry are unsigned package metadata, not a certificate of freshness or completeness.

Command-line verifier and test sources in Python, TypeScript, Go are public on GitHub (new window) under Apache-2.0. Choose the verifier version appropriate to the record and review it together with the policy you intend to trust.

ECL-1’s specification and assessment requirements are separate from tool availability. Read the standard’s guarantees and limits.