Your browser connected without negotiating TLS Trust Anchor IDs (trust_anchors extension) or did not advertise a matching Merkle Tree Certificate (MTC) landmark group ID. To prevent SSL connection errors on standard browsers, the server served a standard Let’s Encrypt WebPKI certificate instead of the compact Landmark-Relative MTC.
chrome://flags/#tls-trust-anchor-ids in a new tab and set TLS Trust Anchor IDs to Enabled.
chrome://flags/#verify-mtcs and set Verify MTCs to Enabled.
chrome://components, locate PKI Metadata Fastpush and click Check for update so your browser has the latest MTC landmark group trust anchors.
chrome://net-internals/#sockets to establish a new TLS connection). Once TAI is negotiated, this page will automatically display the full MTC certificate dashboard!
Command-line alternative: Launch Chrome directly with:
google-chrome --enable-features=TLSTrustAnchorIDs,VerifyMTCs https://demo.mtcs.dev/
Served when client does not send trust_anchors or does not advertise 11129.11.99.3.1.1.78
| Proof Subtree |
[24806, 24807)
|
|---|---|
| Cosigner Signatures | 2 signature(s) |
Merkle Tree Certificate
serial: 281474976735462 (log number 1, entry index 24806)
version: v3
issuer: trustAnchorID=11129.11.99.3
not before: 2026-11-16T00:00:12Z
not after: 2026-11-23T00:00:12Z
subject: CN=demo.mtcs.dev
spki alg: ecPublicKey (1.2.840.10045.2.1)
spki hash: 0b9405102d3ee3301439b51c5c3643fa4c2d66a9cdaf57a3806571df3d362c46 (sha-256)
extensions:
2.5.29.17 subjectAltName DNS:demo.mtcs.dev
MTC proof:
form: standalone, unless its subtree is a landmark subtree (landmark-relative certificates may also carry cosignatures)
subtree: [24806, 24807)
inclusion proof: 0 node(s)
signatures: 2
- cosigner 11129.11.99.3 (2420-byte signature)
- cosigner 11129.11.99.4 (2420-byte signature)