LOCAL FILE · SHA-256 · RECEIPT-BOUND

Verify the bytes.
Know what that proves.

Compare a local file against an evidenced SHA-256 digest without uploading the file. Official installer options appear only when the public distribution authority exposes an installer plus a parseable checksum receipt.

LOCAL SHA-256 VERIFIER

Verify bytes without uploading the file.

Official evidenced artifactExpected SHA-256Local artifactThe file remains in your browser; this verifier does not upload it to D’AUBE.

A SHA-256 match verifies byte integrity against the supplied digest. It does not by itself verify platform code signing, notarization, store publication, malware absence, regulatory approval or product safety.

02 · VERIFICATION LADDER

One green check must never imply five different assurances.

D’AUBE separates evidence layers so a checksum match cannot silently become a signature, store, security or regulatory claim.

Byte integrity

SHA-256 of the local file equals the published digest.

Release provenance

Digest and artifact are bound to a governed public release record.

Code signing

Requires platform-specific signature/certificate evidence; SHA-256 alone is insufficient.

Store / notarization receipt

Requires the actual provider receipt when the distribution claim depends on it.

Supply-chain evidence

SBOM, VEX and build provenance are surfaced only when attached to the release.

Independent assessment

External security/conformity claims require separately verifiable external evidence.

03 · SECURITY BOUNDARY

A matching digest is necessary evidence, not universal trust.

Use the Security Center, Trust Center and platform signature/store evidence together when the risk level requires stronger assurance.

Verify the bytes.Know what that proves.

Verify bytes without uploading the file.

A matching digest is necessary evidence, not universal trust.

Verify the bytes.
Know what that proves.