AUTEGRITYPUBLIC LOG
NO ACCOUNT NEEDED

Check that a record
hasn't changed

Every record about a car is chained to the one before it, and every five minutes the newest link of each changed car goes into a checkpoint. Each checkpoint is stamped by an independent timestamp authority and kept in write-once storage, so a record can't be changed or backdated afterwards without it showing, by us or anyone else.

How it works

01 · THE RECORDThe adapter reads the car and the owner's phone signs the result.
02 · A FINGERPRINTA SHA-256 code is made from the record and the one before it. It reveals nothing, and it changes completely if anything changes.
03 · THE CHECKPOINTEvery five minutes, the newest fingerprint of each changed car goes into one Merkle tree, which also holds the previous checkpoint.
04 · THE STAMPThe tree's root is timestamped by an RFC 3161 authority (DigiCert, Sectigo or FreeTSA) and written to storage that can't be deleted for ten years.

WHAT'S PUBLIC

  • Fingerprints of records, and each checkpoint's root
  • When each checkpoint was made and stamped
  • Each checkpoint's timestamp token, to check yourself

NEVER PUBLIC

  • VINs, mileage or any other reading
  • Who owns the car, or where it's been
  • Anything that identifies a person or a vehicle

Checkpoints

NO.STAMPED (UTC)CARSROOTTIMESTAMP AUTHORITYDOWNLOAD
Loading…

A checkpoint is made only when some record changed. A record added in the last five minutes shows as "in the ledger, checkpoint pending" until the next one.

Check it without us

This page is a convenience. If Autegrity disappeared tomorrow, a record could still be checked with the downloaded record file, its checkpoint and that checkpoint's timestamp token: the token is signed by the timestamp authority, not by us.

  1. Download the record file from the shared record page: every record of the car, with its proofs.
  2. Recompute each record's fingerprint and the chain between them.
  3. Recompute the checkpoint root from the proof and check the timestamp token against the authority's root certificate.
$ bun scripts/verify.ts record.json
records      42, chain intact
checkpoint   #1840  ✓ included, root 7c1e…02ab
timestamp    DigiCert  ✓ 17 Oct 2026 08:45 UTC

$ openssl ts -verify -token_in -in 1840.tst \
    -digest <root> -CAfile DigiCertTrustedRootG4.pem