04 · Evidence · Offline · In your browser · Intel TDX

Verify a real Intel TDX quote

A genuine quote from a GCP C3 confidential VM, checked on your machine the same way our Python verifier checks it: four signatures, ending at the Intel SGX Root CA pinned in this page. The latest capture also commits to the key that signed a TRACE record, and the page checks that too. Nothing is uploaded.

See the result What it proves, and what it does not
Three captures, 21 July and 14 September 2026 · Checked against the Python verifier on 5,526 inputs · SEV-SNP and H100 validation
Run it

Check a capture, or bring your own

Capture 3 puts the SHA-256 of a TRACE record's signing key in REPORTDATA. The key was generated inside the trust domain and the record is published beside the quote, with the program that made both. Captures 1 and 2 come from an earlier trust domain and bind manifest digests whose inputs were not published. You can also load a TDX v4 quote file from your own machine. It is read locally and never sent anywhere.

Scope

What this proves, and what it does not

A pass proves genuine Intel TDX silicon produced and signed the quote, through a certificate chain that ends at Intel's root.

For capture 3 it also proves the trust domain committed to the key that signed the TRACE record: SHA-256 of the record's cnf.jwk.x equals REPORTDATA[0:32], and the record carries this quote and claims its MRTD. That is the attested grade in the TRACE runtime evidence profile. The record signature is checked in CI with the Python SDK, not in this page.

It does not show the software inside the trust domain was the image anyone intended. MRTD and RTMRs are shown, not compared against expected values. The record claims no model and no policy: it exists to show the key binding, and says so in its own fields.

It checks signature chains only. It does not appraise whether the platform's TCB is current or check certificate revocation.

Captures 1 and 2 come from one trust domain and share an MRTD. Matching a record's claimed measurement against a quote's MRTD binds the record to a measurement, never to a particular quote. Only the key binding ties a record to one quote.

Certificate validity is checked against your device's clock.

How it matches the original

A port, held to its original

This page runs verify/tdx-verify.js, a port of agent_manifest._tdx_verify: the same parse, the same checks on every length the quote declares, and the same four steps in the same order.

On every change, CI runs both verifiers over the three captures and 5,526 generated inputs: byte flips across every length and type field and the certificate text, a stride over everything else, and truncations at each structure edge. It fails if they disagree on a single one. The same job checks capture 3's record with the Python SDK: its signature, the key binding, the quote and MRTD it carries, and that the published capture program is the one the record names.

To run the original yourself:

Terminal
python -m pip install agent-manifest
curl -fsSLO https://agentrust-io.com/verify/fixtures/gcp-tdx-2026-09-14-keybind_quote.bin
python -c "from agent_manifest._tdx_verify import verify_tdx_quote; print(verify_tdx_quote(open('gcp-tdx-2026-09-14-keybind_quote.bin', 'rb').read()))"

A genuine quote prints True.