Visual origin check

Who published this image first?

Upload an image. Get an instant decision.

Then certify it before it becomes a dispute.

Try image check View documentation

Image check 10 / day · no account

Checking…

🔍

Drop an image to check

Drag & drop or click to browse

JPG PNG WebP TIFF SVG up to 5MB

Preparing…

first_seen n/a

copies_detected n/a

platforms n/a

origin n/a

trust_index n/a

+ more matches hidden

See full report

SBIX provides verifiable timestamps and detection signals.

Check another image

Why it matters

Why proof matters

Proving a file existed is not a legal formality. It is a technical necessity.

Disputes are decided by timestamps

When ownership or authorship is contested, the question is always the same: who had it first? A verifiable timestamp answers that.

Databases can be altered. Cryptographic proof cannot.

Your internal logs and database records are under your control. Which means they can be questioned. RFC-3161 proof is anchored externally and independently verifiable.

Independent verification, no trust required

Anyone can verify a SBIX proof without contacting us. No account. No dependency on our availability. The proof stands on its own.

How it works

Three steps. One proof.

Submit a file, receive a proof record, verify it at any time.
Your file is never stored. Only its cryptographic fingerprint exists.

Submit a file

POST your file to the API. SBIX computes its SHA-256 hash. The file is never stored. Only its fingerprint is used to generate proof.

Proof is generated

A timestamp is issued and sealed. This creates a verifiable record that the file existed at that exact moment.

Verify at any time

Anyone can verify the proof using the proof_id or hash. No account required.

API

One endpoint to start.

One API call, one verifiable proof. Integrate in minutes. The API returns a structured proof object you can store, share, or submit as evidence.

Used by platforms, compliance teams, and legal departments.

POST /api/v1/certify

Submit any file. Get a proof with a hash, a timestamp, and a public verification link.

proof_idUnique identifier for this proof record

hashSHA-256 of the submitted file

timestampRFC-3161 qualified timestamp (ISO 8601)

verify_urlPermanent public verification endpoint

Read the docs

Response · /api/v1/certify

{
  "proof_id":   "prf_a3f8c2d1e9b4...",
  "hash":       "sha256:e3b0c44298fc...",
  "timestamp":  "2026-04-15T13:41:00Z",
  "algorithm":  "SHA-256",
  "tsa":        "qualified",
  "verify_url": "https://verify.sbix.io/prf_a3f8...",
  "status":     "verified"
}
      

Use cases

Built for two problems.

Proof of existence has clear, concrete applications. We focus on the ones that matter.

Platforms

Prevent upload disputes

When a user uploads content to your platform, generate a proof at the moment of upload. If a dispute arises, you have a verifiable record of exactly when the file was received.

Timestamped record of every upload Immutable proof, independent of your database Works at any upload volume via API

Legal & compliance

Prove a file existed

When a file's existence needs to be proven (contracts, evidence, reports), SBIX creates a verifiable timestamp that can be checked independently at any time.

RFC-3161 qualified timestamps Exportable evidence package eIDAS-compliant for EU jurisdictions

Without proof: you rely on your database and logs.
With SBIX: you have a verifiable timestamp, independent and checkable by anyone.