How to use Public JWK and JWKS Inspector
- Choose Public JWK or JWKS JSON, or Public SPKI PEM to JWK. For PEM, select RSA/RS256 or P-256/ES256 to match the key.
- Paste the supported public material or select its UTF-8 keys file. A selected file replaces the text for the chosen input format.
- Choose the JSON inventory/JWKS output, or add SPKI PEM exports, then run Inspect public keys.
- Compare algorithms, key sizes, thumbprints and duplicate kid notes. Download the inventory and public JWKS; PEM output adds each supported key file. Establish ownership and trust separately.
Example: Public JWK and JWKS Inspector
Inspect the supplied RSA and P-256 example key set and calculate their public-key thumbprints.
Options
- Local UTF-8 keys file (optional)
- Up to 256 KiB; selected file replaces the pasted keys. Public data only.
- Input format
- Choose Public JWK or JWKS JSON, Public SPKI PEM to JWK.
- Expected PEM key algorithm
- Choose RSA / RS256, P-256 EC / ES256.
- SPKI PUBLIC KEY PEM
- Use BEGIN PUBLIC KEY, not a certificate, CSR or private key. RSA needs at least 2048 bits; EC is P-256 only.
- Public JWK or JWKS
- One public JSON key, or a key set with a "keys" array of up to 20 keys. RSA keys need at least 2048 bits. Only public material is accepted: private fields (d, p, q, dp, dq, qi, oth) and symmetric keys (kty "oct") are refused.
- Public export format
- Every run downloads a JSON inventory and public-keys.jwks.json. Choosing PEM adds an SPKI PUBLIC KEY file for each supported key. Export changes the representation; it does not establish trust.
Supported inputs and limits
- A public JWK or JWKS of up to 20 supported RSA/P-256 keys, or supported RSA/RS256 or P-256/ES256 SPKI PEM.
- Optional UTF-8 input files are limited to 256 KiB.
- RSA keys need at least 2,048 bits.
- Private/symmetric material and mismatched algorithms are refused.
- No certificate-chain validation, key-ownership check, remote JWKS refresh or trust assertion is provided.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A thumbprint identifies key material
The thumbprint uses the required public members in their defined canonical order. Optional identifiers and descriptive metadata do not establish who owns the key. Keep the fingerprint with the independent source from which you obtained the public key; a correctly formed key can still be untrusted.
Questions about Public JWK and JWKS Inspector
Does changing kid change the thumbprint?
The thumbprint covers the required public key members, not the optional kid label.
Can I paste a private JWK?
No. Private and symmetric material is refused. Export a public key in the originating application first.
Does public export establish trust?
No. It changes or records the public representation; it does not authenticate its source.