Menu

LinkedIn (www.linkedin.com): Post-Quantum TLS Check

Does LinkedIn (www.linkedin.com) support post-quantum TLS 1.3 with X25519MLKEM768?

Yes. In our latest test on , www.linkedin.com negotiated the hybrid post-quantum key exchange X25519MLKEM768. Observed Source · Methodology

Last confirmed Oct 17, 2026; no reading on Oct 18, 2026 (1 check without a reading). We keep showing the last confirmed value for up to 3 days after it was confirmed; after that the value is shown as unknown until a new reading.

What this means for you

In our TLS 1.3 test of www.linkedin.com on Oct 17, 2026, the server chose X25519MLKEM768, a hybrid key exchange that combines classical X25519 with ML-KEM-768, the NIST FIPS 203 post-quantum standard. A browser that offers the same group can get the same key exchange; the session keys of such a connection are designed to resist decryption later with a quantum computer, even if the traffic is recorded today.

For your own site, the key exchange is decided by whatever ends the TLS connection (your web server, your host or your CDN): our hosting checker names the provider behind a domain, and our hosting price tracker shows what the plans we check cost at purchase and at renewal.

We also read which AI crawlers linkedin.com asks to stay away in its robots.txt: the linkedin.com rules and their history.

History and how we checked

24 checks since Sep 28, 2026 · the listed value moved between checks

How we got this number

  • What we tested: a TLS 1.3 connection to www.linkedin.com; we record the key exchange the server chooses. Source: www.linkedin.com
  • Checked: Last confirmed ; no reading on ; tracked since Sep 28, 2026
  • Shown in: Switzerland
  • Checks so far: 24 checks on 20 days since Sep 28, 2026
  • What changed: the listed value moved between checks since Sep 28, 2026; see the record history
  • Page updated:

Changes

The listed value moved between the 24 checks since Sep 28, 2026; every reading is in the record history below.

  1. — First check: Yes
  2. Short-lived or unconfirmed moves are not shown as changes.
Record history 24 records for 1 question
Last record
Shown in
Switzerland
TimeValueStatus
Oct 17, 2026YesObserved
Oct 16, 2026YesObserved
Oct 15, 2026YesObserved
Oct 14, 2026YesObserved
Oct 13, 2026NoObserved
Oct 12, 2026YesObserved
Oct 11, 2026YesObserved
Oct 10, 2026YesObserved
Oct 9, 2026YesObserved
Oct 8, 2026YesObserved
Oct 7, 2026NoObserved
Oct 6, 2026YesObserved
Oct 5, 2026YesObserved
Oct 4, 2026YesObserved
Oct 3, 2026YesObserved
Oct 2, 2026YesObserved
Oct 1, 2026YesObserved
Sep 30, 2026YesObserved
Sep 29, 2026YesObserved
Sep 28, 2026YesObserved
Sep 28, 2026YesObserved
Sep 28, 2026YesObserved
Sep 28, 2026YesObserved
Sep 28, 2026YesObserved
Download JSON Download CSV