Is this photo or video real?
Drop the file below and this page tells you whether it was signed by the camera that took it, and whether anything changed since. The file never leaves your browser — no upload, no account, no server of ours.
Drop the file here
a sealed photo or video
Invisible watermark: not checked
Reading a mark out of pixels needs a model of about 34 MB. This page never downloads it on its own and never keeps it.
The proof came as a separate .vcap file
When the proof travels beside the file rather than inside it (<filename>.vcap). It is read here, not looked for anywhere. Dropping both files on the zone above works too.
What this page trusts
Every check below can be switched off, and switching one off never turns a verdict into an error — it turns a line of evidence into not evaluated, which is a weaker answer and an honest one.
Transparency logs
A sealed file can prove its signing key was published in a transparency log before the capture. Checking that needs the log's public key, so this page ships with a set — visible here, switchable, replaceable with your own. The same set is published beside this page as logs.json: fetch it, recompute each log_id from its key, and decide for yourself.
A proof naming a log you do not follow reads log not trusted. The rest of the verdict is unchanged.
Timestamping authorities
A sealed file can carry an RFC 3161 token binding its proof to an instant. Checking it needs that authority's root certificate, so this page ships with a set, published beside it as tsa.json. Unlike the logs above these authorities are run by other people — which is what makes a token worth having, and why what it proves has to be stated narrowly.
With all of them off, a timestamp reads trusted time not evaluated and certificates are validated at the instant the device claims instead.