A TLS cipher suite name packs four decisions into one string: how keys are exchanged, how the server is authenticated, which bulk cipher encrypts the data, and which hash provides integrity. This tool unpacks any suite and tells you whether it still meets modern guidance or should be retired.
How it works
You can enter either the IANA name (for example TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) or the two-byte hex code (for example 0xC02F). The tool resolves one form to the other using a bundled slice of the IANA registry, then parses the components:
- Protocol family — TLS 1.3 suites (
TLS_AES_*,TLS_CHACHA20_*) name only the AEAD cipher and hash; older suites name the full key-exchange and authentication pair. - Key exchange / authentication — ECDHE and DHE provide forward secrecy; static RSA, ECDH and DH do not; anonymous variants provide no authentication at all.
- Bulk cipher — AES-GCM, ChaCha20-Poly1305 and AES-CCM are modern AEAD; AES-CBC, 3DES, RC4 and NULL are flagged in increasing order of severity.
- MAC / hash — SHA-256/384 are fine, SHA-1 is legacy, and MD5 is broken.
It then applies BSI/NIST-aligned rules to produce an overall rating with specific reasons.
Example and notes
Decode 0x0005 and the tool resolves it to TLS_RSA_WITH_RC4_128_SHA and rates it insecure, citing RC4 being prohibited and static RSA lacking forward secrecy. Decode 0x1303 and you get TLS_CHACHA20_POLY1305_SHA256, rated secure as a modern TLS 1.3 AEAD suite.
The bundled registry covers the suites you meet in real server configurations. For an exhaustive list consult the full IANA TLS parameters registry, but the ratings here reflect current deployment guidance.