🔒All inputs are processed locally in your browser. Nothing is transmitted, stored, or logged. Inputs disappear when you close the tab.

OCG-Industries Showcase · Cluster 13 Machine, AI and Software Integrity

Agent Identity
Verification

Enter a message signature setup, its covered components, key identifier, algorithm, and key publishing declarations, and this tool re-derives the same structural admission checks a receiving service would run against a signed agent request. It counts the covered signature components, confirms the required ones are present, checks that your key identifier appears in the signature input, and produces an admit, challenge, or reject recommendation. This checks the shape of the signature setup. It does not verify a signature, and no key material is fetched or evaluated.

Data: IETF RFC 9421 HTTP Message Signatures · Web Bot Auth Internet-Draft

Signature Setup STEP 1
The quoted component list from the Signature-Input header
Should appear inside the signature input above
Declared signing algorithm
Recommendation
--
Admit, challenge, or reject
Structural Checks
--
Out of 6 possible checks
Covered Components
--
Quoted tokens found in the signature input
Detail
Covered component count--
Required components present--
Key identifier matches input--
Algorithm supported--
Structural checks passed--
Admit recommendation--
Status--
Policy Mandate v2.0 · what is this?