Choose by task

JWT, Hash, TLS & Certificate Tools

Distinguish token decoding from signature verification, inspect PEM and live TLS certificates, compute hashes and prepare certificate test material.

Browse these tools ↓

Which tool should you start with?

Readable security data is not automatically trustworthy. Decoding reveals a JWT payload or a Kubernetes Secret value, while verification checks it against a key and explicit rules. Likewise, reading a local certificate tells you about that file; a live TLS check tells you what the endpoint currently serves.

Read claims or prove a token signature

Decode first when you only need to inspect fields. Use the signature verifier with trusted key material when authenticity matters; readable claims alone cannot authorize a request.

JWT Sign & Verify →

Check the certificate users actually receive

Query the live hostname to inspect its certificate chain and expiry. Use the PEM decoder separately for a certificate file that has not yet been deployed.

TLS Certificate Checker →

Compare file or message fingerprints

Compute a hash to compare bytes with an expected digest. A hash does not encrypt the input, and matching a digest only establishes trust when the expected value comes from a trusted source.

Hash Generator →

Check the result before the next step

Use redacted or disposable samples where possible. For a JWT, verify the expected algorithm and trusted key, then check issuer, audience and time claims. For TLS, inspect hostname coverage, validity and the presented chain. A self-signed certificate is useful for controlled tests; public trust requires issuance by a trusted CA and domain control.

Tokens & certificates

8 tools