Skip to content
Local worksheet

Hop map

List each TLS hop from the browser to your internal services, then record key agreement and authentication separately. They change on different schedules and are verified in different ways.

Why this matters. Providers can enable hybrid key agreement at the edge while every hop behind it stays classical. A map of hops shows which changes are yours to make and verify.

Key terms 4
TLS
Transport Layer Security: the protocol that authenticates servers and encrypts traffic for HTTPS and many other services.
Hybrid key exchange
Key agreement that combines a classical method with a post-quantum one, so the session stays protected while either remains secure.
KEM
Key encapsulation mechanism: a method for two parties to establish a shared secret during key agreement.
Crypto-agility
The ability to replace algorithms, keys and certificates through a tested process without redesigning the system.

Hybrid key agreement on the first hop says nothing about the hops behind it. Mark what you know; leave the rest as unknown. This map records your understanding, not an assessment.

Read the article this instrument accompanies: You are not migrating to post-quantum. Your CDN is.

4 hops hybrid observed on 0 key agreement unknown on 4 authentication unknown on 4 4 without an owner

Hop 1 Browser → Edge / CDN

A public hop can be observed directly. Observe a hostname you control

Hop 2 Edge / CDN → Origin load balancer

Hop 3 Load balancer → Application

Hop 4 Application → Internal API or database

Take it into a conversation
The map is saved only in this browser tab. Export it, or open an encrypted enquiry from this tab: the map is attached to the encrypted message, and you can remove it there.