← back to v131 · x25519kyber768-key-encapsulation-for-tls
conformance · v131
v131 · x25519kyber768-key-encapsulation-for-tls — conformance probe
6 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
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
secure-context |
The page runs in a secure context, which is required for observing modern TLS-backed web APIs. spec ↗ | script | … | |
fetch-exposed-for-https |
fetch is exposed for HTTPS requests negotiated by the browser TLS stack. spec ↗ | typeof | … | |
https-url-parses |
The URL parser recognises https URLs as TLS-backed network requests. spec ↗ | script | … | |
secureconnectionstart-field |
PerformanceResourceTiming exposes secureConnectionStart for HTTPS connection timing. spec ↗ | script | … | |
nexthopprotocol-field |
PerformanceResourceTiming exposes nextHopProtocol for reporting the negotiated protocol. spec ↗ | script | … | |
crypto-subtle-exposed |
crypto.subtle is exposed in secure contexts; TLS key agreement remains browser-internal with no direct JS API for the hybrid KEM. spec ↗ | exists | … |