Skip to content

Public verification

Is the document in your hands genuine?

Every ekspertiz report and Service Record Document is signed with Ed25519; change a single field and verification fails.

Public · No sign-in · 0.4 s on average · KVKK compliant

Design demonstration. The sample queries on this page, and the VIN, plate, mileage and measurements they return, are examples — they are not taken from real vehicles or customers. Query a real document you hold and the result comes from the live record.

Paste a report number, a service receipt code or a QR link — or click one of the sample queries.

What we check

Six independent layers of evidence.

Verification is not a single signature check. Every query examines six separate layers together; if any one of them fails, the report drops to unverifiable.

Chain of sealsThree record plates stand side by side. Inside each plate sits a double-framed seal. Between the plates sits an orange square: that square is the fingerprint of the record on its left, and it is also written inside the record on its right — it is what binds the records together. The first square on the left is drawn with a dashed outline, because nothing comes before the first record.#4a9f#c17e
Fingerprint (SHA-256): the digest of the record on its left, written inside the record on its right
First record — nothing before it
Ed25519 seal: binds the record to whoever issued it
Verification checks the whole sequence, not one signature. Editing a record in the middle changes its fingerprint; because that fingerprint was written into the next record, the rest of the chain stops matching. The only way to hide a forged edit is to re-seal every record after that date — and the sealing key stays with the centre.

Digital signature

Ed25519

Every report is signed with the Ed25519 key of the branch manager who signs it off. Anyone can verify it with the public key.

Chain hash

SHA-256

Every report carries the hash of the one before it; changing a single field anywhere in the chain invalidates every record that follows.

Photographic evidence

Images per module

The photos the technician takes for each module — instrument screens, sections of the car, the plate — are attached to the report and written into the chain. They cannot be changed later.

Revision log

Nothing is deleted

Even when a report is updated, the earlier version is kept permanently. The revision counter goes up and the number stays the same.

Timestamp

RFC 3161

The time a report is issued is fixed by a trusted timestamping authority, so the date cannot be moved forwards or backwards.

Centre identity

TSE-HYB

The TSE-HYB number and digital seal of the centre that issued the report have to match. A forged centre signature shows up during verification.

Privacy

Verification leaves no trace.

The report verification endpoint collects no personal data. The IP address making the query is not stored; only a total counter goes up. The report shows nothing identifying the vehicle's owner — only the plate, the VIN and the technical measurements.

Personal data (owner identity, contact details) is reachable only by authorised staff at the inspection centre and by the owner through their own OtoTasdik account. Retention periods are documented under Turkish data protection law no. 6698 (KVKK).

Trust the record, not the seller.

The 15 test modules behind a sealed report, the Ed25519 sealing process and the VIN chain.

Request a demo

How it works →