Verify a JWS signature (auto-detecting, JAdES-aware)

Verifies a JWS and reports the cryptographic verdict plus key metadata. Serialization is AUTO-DETECTED — both RFC 7515 §7.1 Compact (three dot-separated segments) and §7.2 JWS JSON Serialization inputs are accepted with no serialization parameter. The wire shape is uniform: single-signature for SIMPLE keys, multi-signature for COMPOSITE hybrid keys.

Qualified timestamp (JAdES B-T, informational). When the verified JWS carries an embedded RFC 3161 qualified timestamp (JAdES sigTst), the response surfaces an informational qualifiedTimestamp block — present, trustStatus (VALID/UNTRUSTED/REVOKED/EXPIRED/TIME_ANOMALY), genTime, serialNumber, policyOid. This block is purely informational and NEVER flips the boolean valid: a cryptographically valid signature with an absent, untrusted, or revoked timestamp still returns valid = true. The block is omitted for a compact or an unstamped JWS.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

JSON object with one field: the typed JWS General JSON Serialization
(RFC 7515 §7.2) payload to verify.

Request object for verifying a JWS (General JSON Serialization).

jwsToken
object
required

Typed JWS token to verify (General JSON Serialization).

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json