Skip to content

Is the document in your hands genuine?

Ekspertiz reports and Service Statements issued through OtoTasdik are sealed. Enter the report number or the 8-character code printed on the Service Statement. You will see whether the document is exactly as it was sealed or was changed afterwards.

  • No sign-in or account needed
  • We don't ask for your name or email

Enter a code and the result appears here: whether the document is exactly as it was sealed, and who issued it.

The sample queries do not belong to real cars. The VIN, plate, mileage and measurements they return are for demonstration and do not come from real vehicles or customers. When you check a real document, the result comes from the live record.

What verification checks on a document

A result reads “Verified” only when the seal, the content and the order all hold. If one of them fails, the result names what failed.

  • The sealReports and statements are sealed with OtoTasdik's signing key when they are closed. The public key is published, so anyone can check the seal without an account.
  • The contentVerification recomputes the fingerprint from the document's stored content. If a single field has changed, the fingerprint no longer matches and the result reads “Altered”.
  • Order of recordsEach record carries the fingerprint of the previous record on the same car. For a Service Statement this link is checked as well, so a record slipped in later does not fit the order.
  • Time of sealingThe moment of sealing is written into the fingerprint, so changing the date breaks it. OtoTasdik's server records that time; no separate timestamping authority is involved.
  • Issuer and statusThe result shows the shop that issued a statement and its city; shop accounts open only after the tax registration certificate is approved. If the shop voided the statement later, the result says so.
Technical verification details
The seal
Ed25519 signature, verified with the published public key
Fingerprint
SHA-256 over JSON with sorted keys
Order of records
Each record contains the SHA-256 digest of the previous one on the same VIN
Time of sealing
Server time, part of the signed data
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. That 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: shows the record was sealed through OtoTasdik
Verification checks the whole sequence. 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. Hiding a forged edit would mean re-sealing every record after that date, and the sealing key is kept on OtoTasdik's server.

Checking a document does not ask who you are

A check needs no account and no name. As with every request, the server keeps your IP address in its technical logs and uses it to limit excessive queries. The result never shows who owns the car, only details of the car and the document.

The owner's name and contact details appear in no verification result; they are visible only in signed-in accounts. How the data is processed is set out in the privacy notice under Turkish data protection law no. 6698 (KVKK).

Your centre's reports can be checked here too

We run an invitation-only pilot with ekspertiz centres. In a call we walk you through the modules of a report and how it gets sealed, step by step.

Request a demoHow it works