← back to v147 · x25519kyber768-key-encapsulation-for-tls
conformance · v147
v147 · x25519kyber768-key-encapsulation-for-tls — conformance probe
8 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
8
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
subtle-crypto-available |
SubtleCrypto API is exposed on the window.crypto object. spec ↗ | typeof | … | |
crypto-subtle-generate-key |
crypto.subtle.generateKey is a function used to generate cryptographic key pairs. spec ↗ | typeof | … | |
crypto-subtle-derive-bits |
crypto.subtle.deriveBits is a function used to derive bits for key agreement. spec ↗ | typeof | … | |
crypto-subtle-derive-key |
crypto.subtle.deriveKey is a function used to derive keys for key agreement. spec ↗ | typeof | … | |
webcrypto-x25519-generate |
WebCrypto supports generating keys for the X25519 algorithm for application-layer key agreement; this is adjacent to, but not proof of, TLS hybrid KEM negotiation. spec ↗ | script | … | |
performance-nexthopprotocol-exists |
PerformanceNavigationTiming exposes nextHopProtocol as an application/network protocol token such as h2, h3, or http/1.1; it is not the selected TLS NamedGroup or KEM. spec ↗ | script | … | |
nexthopprotocol-not-kem-token |
The current navigation's nextHopProtocol value does not expose X25519Kyber768, ML-KEM, or another TLS KEM name. spec ↗ | script | … | |
secure-context-required |
The document is loaded in a secure context (HTTPS or localhost), which is required for WebCrypto APIs. spec ↗ | script | … |