Protocol Simulations / TLS 1.3 Simulator

What you will do: Configure the client and server panels — cipher suites, key exchange groups, an RSA-2048 or ML-DSA identity, optional client verification — then Start Full Interaction to run a real OpenSSL TLS 1.3 handshake.

Worked example: With the defaults (X25519MLKEM768 offered first, RSA-2048 certificates) the summary names the negotiated cipher and key exchange, how many KB the handshake moved, and notes that hybrid ML-KEM plus ECDH was used.

Runtime and privacy: The cryptographic exercise runs in this browser. Review the site privacy terms before entering sensitive material; use synthetic inputs for learning and evaluation.

Browse all Crypto Lab tools · Learn with TLS Basics

For your role

Developer / Engineer
Choose a key share such as X25519MLKEM768 and a signature algorithm such as mldsa65 on the client and server panels, then Start Full Interaction: the TXT and HEX views show every handshake message and the Config File tab is the OpenSSL configuration that produces it.
Security Architect
Compare the handshake with P-256 against ML-KEM-768 and a hybrid: the message sizes and the Trusted Root CA and mTLS options show what a PQC certificate chain adds to every connection.
Researcher / Academic
The supported set is listed at the top (pure ML-DSA certificates, hybrid key shares per the IETF drafts); use INSPECT and the HEX view to check the key share and signature encodings against the drafts.
IT Ops / DevOps
Set the server side the way your edge is configured, tick Require Client Certificate (mTLS) if you use it, and run the interaction: the Config File tab is the snippet shape you will deploy, and the Learn module holds the Apache, nginx, HAProxy and Caddy versions.
Curious Explorer
Leave the settings as they are and press Start Full Interaction: your browser runs a real TLS 1.3 connection whose key exchange (X25519MLKEM768) is post-quantum, while the RSA certificate that proves who the server is stays classical. It is a teaching run, not a test of any product or of what your own browser uses.

TLS 1.3 key exchange and authentication

  • Key exchange. Try X25519 for a classical baseline, or X25519MLKEM768, SecP256r1MLKEM768, or SecP384r1MLKEM1024 for hybrid key agreement (RFC 10024). Standalone ML-KEM groups are also available.
  • Sample certificates. The client and server offer RSA-2048, ML-DSA-44 and ML-DSA-87 identities. The peers negotiate a handshake signature independently of the key exchange group.
  • Composite certificates. Explore X.509 Composite ML-DSA (RFC 10073) in the Hybrid Certificates Playground. The TLS working group’s Composite ML-DSA draft proposes the handshake signature schemes. Here the simulator runs the RSA and single-algorithm ML-DSA identities listed above.

TLS Client

Application Data (Messaging)

Received from Server
Client Identity (mTLS)
Client Identity:

Needed if the Server requests a client certificate (mTLS).

Sample-default CA

The peer certificate and trusted CA are separate choices. An edited or imported CA stays selected until you change it. A sample run does not establish trust in a deployed system.

Import the Root CA that signed the server's certificate.


Cipher Suites (TLS 1.3)
TLS_AES_256_GCM_SHA384
TLS_AES_128_GCM_SHA256
TLS_CHACHA20_POLY1305_SHA256
TLS_AES_128_CCM_SHA256

Key Exchange Groups
Classical (ECDH)
PQC (ML-KEM)
Hybrid (Classical + PQC)
▸ Key share size reference (FIPS 203, RFC 9846)
GroupKey Share (ClientHello)
X25519key share: 32 B
P-256key share: 65 B
P-384key share: 97 B
P-521key share: 133 B
ML-KEM-512pk: 800 B · ct: 768 B
ML-KEM-768pk: 1,184 B · ct: 1,088 B
ML-KEM-1024pk: 1,568 B · ct: 1,568 B
X25519MLKEM7681,216 B combined (ML-KEM-768 1,184 + X25519 32)
SecP256r1MLKEM7681,249 B combined (P-256 65 + ML-KEM-768 1,184)
SecP384r1MLKEM10241,665 B combined (P-384 97 + ML-KEM-1024 1,568)

Signature Algorithms

SLH-DSA (FIPS 205) is not listed: OpenSSL registers no SLH-DSA TLS signature schemes, so it cannot be negotiated here. No IETF working-group draft yet specifies SLH-DSA for TLS 1.3 (an individual draft exists; signatures are 7–50 KB).

Signature and public key sizes

The public values below omit the SubjectPublicKeyInfo wrapper. RSA-2048 also needs the exponent. Measure the actual encoded key and certificate when sizing a buffer.

TLS signature and public key encodings
Signature schemeSignaturePublic key value or component
mldsa442,420 B1,312 B raw key
mldsa653,309 B1,952 B raw key
mldsa874,627 B2,592 B raw key
ecdsa_secp256r1_sha256Up to 72 B DER65 B uncompressed point
rsa_pss_rsae_sha256256 B with RSA-2048256 B modulus
rsa_pss_pss_sha256256 B with RSA-2048256 B modulus
ed2551964 B32 B raw key

FIPS 204 sizesRFC 5480 EC pointsRFC 8017 RSA public keysRFC 8032 Ed25519

Configuration will be generated automatically based on selection.

TLS Server

Application Data (Messaging)

Received from Client

Server Identity
Server Identity:

Selects the Key/Certificate pair used by the server.


Cipher Suites (TLS 1.3)
TLS_AES_256_GCM_SHA384
TLS_AES_128_GCM_SHA256
TLS_CHACHA20_POLY1305_SHA256
TLS_AES_128_CCM_SHA256

Key Exchange Groups
Classical (ECDH)
PQC (ML-KEM)
Hybrid (Classical + PQC)
▸ Key share size reference (FIPS 203, RFC 9846)
GroupKey Share (ClientHello)
X25519key share: 32 B
P-256key share: 65 B
P-384key share: 97 B
P-521key share: 133 B
ML-KEM-512pk: 800 B · ct: 768 B
ML-KEM-768pk: 1,184 B · ct: 1,088 B
ML-KEM-1024pk: 1,568 B · ct: 1,568 B
X25519MLKEM7681,216 B combined (ML-KEM-768 1,184 + X25519 32)
SecP256r1MLKEM7681,249 B combined (P-256 65 + ML-KEM-768 1,184)
SecP384r1MLKEM10241,665 B combined (P-384 97 + ML-KEM-1024 1,568)

Signature Algorithms

SLH-DSA (FIPS 205) is not listed: OpenSSL registers no SLH-DSA TLS signature schemes, so it cannot be negotiated here. No IETF working-group draft yet specifies SLH-DSA for TLS 1.3 (an individual draft exists; signatures are 7–50 KB).

Signature and public key sizes

The public values below omit the SubjectPublicKeyInfo wrapper. RSA-2048 also needs the exponent. Measure the actual encoded key and certificate when sizing a buffer.

TLS signature and public key encodings
Signature schemeSignaturePublic key value or component
mldsa442,420 B1,312 B raw key
mldsa653,309 B1,952 B raw key
mldsa874,627 B2,592 B raw key
ecdsa_secp256r1_sha256Up to 72 B DER65 B uncompressed point
rsa_pss_rsae_sha256256 B with RSA-2048256 B modulus
rsa_pss_pss_sha256256 B with RSA-2048256 B modulus
ed2551964 B32 B raw key

FIPS 204 sizesRFC 5480 EC pointsRFC 8017 RSA public keysRFC 8032 Ed25519

Server preference will prioritize these ciphers.

Run simulations with different configurations to compare overhead.
Production Tool Capabilities & Verification Requirements

What this sample check establishes: Runs a real OpenSSL 3.6 WASM in-memory TLS 1.3 handshake (`SSL_CTX`) negotiating hybrid (`X25519MLKEM768`) or pure PQC groups and PQC certificates.

Browser sandbox limitation (non-certification boundary): Uses in-memory BIO buffers without kernel TCP/IP segmentation, middlebox DPI inspection, or real WAN packet loss.

What to require and test in your production tools:

  • TLS 1.3 hybrid key exchange (`X25519MLKEM768`, codepoint `0x11EC`) enabled on production TLS libraries, CDNs, and ingress controllers.
  • RFC 8879 TLS Certificate Compression (Brotli/Zstd) and TCP Initial Congestion Window (`initcwnd >= 10`) tuning for multi-kilobyte PQC cert chains, enabled where supported, and measured against your own chains.
  • Active monitoring for middlebox clientHello drops on multi-packet TCP ClientHellos (`> 1,500 B`).

Try it

  1. 1. Predict before you run it.
  2. 2. Run or change the tool above.
  3. 3. Explain what the result shows.

Choose X25519MLKEM768 as the key share and mldsa65 as the signature, then Start Full Interaction. Where does the certificate chain size appear?

Next step

Turn it into a plan: MTI Negotiator

This tool practises the TLS Basics module, phase 5 (Pilots & Migration); MTI Negotiator produces a deliverable of that phase.

Next in Protocol Simulations