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 →Distinguish token decoding from signature verification, inspect PEM and live TLS certificates, compute hashes and prepare certificate test material.
Browse these tools ↓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.
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 →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 →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 →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.
Decode JWT headers and claims, inspect timestamps, and check expiration locally. Decoding does not verify the signature.
Runs locally SecurityGenerate and verify HS256 or RS256 JWT signatures locally, with algorithm and exp/nbf checks. Tokens and keys never leave your browser.
Runs locally SecurityGenerate SHA-256, SHA-384, SHA-512, or SHA-1 digests from text and local files in your browser.
Runs locally SecurityInspect an X.509 PEM certificate, validity dates, subject, issuer, serial number, and SHA-256 fingerprint locally.
Runs locally SecurityInspect a public website's live TLS certificate, chain, SANs, expiry, fingerprint, protocol, cipher suite, and trust result without installing OpenSSL.
Backend check SecurityGenerate a self-signed RSA X.509 certificate and parse RSA certificates or keys online. Generated material is returned once and never stored.
Backend check SecurityGenerate a self-signed SSL/TLS certificate for a domain name or IP address with the correct Subject Alternative Name, returned as PEM certificate and private-key files.
Backend check Cloud NativeDecode every value in a Kubernetes Secret manifest locally and identify invalid Base64 without exposing credentials.
Runs locally