Inspect a JSON Web Key Set

Review the local keys[] inventory, filter by kid, find duplicate key IDs, and catch accidental private-key members before sharing a JWKS.

Filter by kid (optional)

Summary

—Keys

—Matched kid

—Duplicate kids

—Keys with private members

#	kid	kty	alg	use	crv	Private members

Structural inspection does not fetch an issuer, validate certificates, choose a trusted key, or prove that a JWKS belongs to any identity provider.

Local developer workflow

This v10.72 layer keeps high-frequency developer jobs browser-local and connects focused tools without replacing their established engines. JSON, Base64, URL, UUID and JWT content is processed in the browser; YAML may use the existing optional parser library when available, with its documented local fallback.

Trust and standards boundaries

Formatting is not schema validation, Base64 is not encryption, URL normalization is not a privacy guarantee, UUID metadata is not provenance, and decoded JWT claims are not trusted until cryptographic and application-specific validation succeeds. RS256 tools accept explicit PEM key formats and do not fetch issuer keys or make authorization decisions.

How to use this JWKS Inspector

Inspect JWKS key metadata locally, filter by kid, find duplicate key IDs, and flag private-key members without fetching or trusting an issuer.

Enter, paste, upload, or choose the inputs shown in the tool above.
Adjust the available options for the result you need.
Review the output before copying, downloading, or using it elsewhere.

What this tool does

Review keys[] structure, kty/alg/use/crv fields, and accidental private material in a pasted JSON Web Key Set.

Practical tips and limits

Review the inputs and result before using the output elsewhere. Keep the original data when the operation changes or replaces content.