RAPTOR · Chain of custody

Has this file been altered?

When RAPTOR captures a still or a clip, it computes a SHA-256 digest at the moment the file arrives and records it. If the file you hold produces the same digest, it is byte-for-byte the file that was captured. If a single byte has changed, it will not.

This page is for whoever needs to check that independently — an insurer, an attorney, a body corporate. It needs no account, and it belongs to nobody’s case.

Check a file

Choose the file you were given. It is hashed here in your browser and never uploaded — only the resulting digest is sent, and a digest cannot be turned back into a file.

Or paste a digest

If you already have the SHA-256 — from a report, or computed yourself with sha256sum or Get-FileHash — paste it here.

What this does and does not tell you

It tells you the file is unaltered since capture — or that it is not. That is the question a digest can answer, and it answers it conclusively.
It does not tell you who captured it. No organisation, incident, site, filename or location is returned, because the person asking is anonymous and the operator did not consent to being identified to them.
It does not give you the file. If you do not already hold it, this page cannot help you — which is also why it is safe to leave open to anyone.
“Not on the register” is not proof of tampering. It means this exact file was not captured through RAPTOR. It may have been re-encoded, cropped, or captured by different software entirely — all of which change the bytes and therefore the digest.

A file may be on the register while the file itself has been destroyed under the operator’s retention policy. That is POPIA §14 working as intended: the personal information goes, the record of it stays, and a report from last year still refers to something real.