Verifier
Verify a receipt, without us.
Drop a delivery receipt (.makbuz.json) or a dispatch record (.sevk.json). Everything is checked in this browser tab: nothing is uploaded, and it works with the network switched off.
- 01RecordThe receipt or dispatch JSON
- 02FileOptional: the file that was transferred
- 03ResultEach check, in plain words
The result appears here as soon as a record is added.
Check a one-way link: did everything arrive?
On a one-way link, such as a serial cable with the return wire left out or a data diode, the sending side cannot be told that a file arrived; that is what one-way means. The usual answer is to compare the logs of both sides by hand. With Kionel both logs are signed, so the comparison can be checked instead of trusted.
On each side open the transfer log and press Download signed records (JSON) for the same period. The sender's records are a file like any other and can travel over the link itself. Drop both here:
For every file the sender signed, the result is one of three: the receiver signed a receipt for exactly that dispatch and both signatures verify; there is no receipt; or one of the two records does not verify. It shows that the receiving device signed for the file, not that anyone has read it, and a file sent before the sender's period started is not in the list.
What this checks
- Delivery signature — the receiving device signed this exact receipt; any edit breaks it.
- Dispatch signature — the sending device signed the file's SHA-256 together with the work order, classification and target system.
- File content — if you add the file, its size and SHA-256 must match what both devices signed.
It does not prove which person operated the devices, and the times are device clock times, not trusted timestamps. The same check runs from the free command-line verifier, licensed under Apache-2.0, so a record stays checkable even if Kionel is gone.