CertifiedData.io
Verify/a1c14a52-40cf-4373-b940-27bcddb7b61d

Certificate verified — production

Certificate integrity · ISSUED · cert.v2 · GENESIS

The certificate exists, its Ed25519 signature is valid, and it has not been revoked. To check that a specific file matches the artifact recorded in this certificate, use the Verify Your File section below.

Certificate Details

Certificate ID

a1c14a52-40cf-4373-b940-27bcddb7b61d

Issuer

Certified Data LLC

Issued

August 26, 2026 at 09:46 AM UTC

Signature Algorithm

Ed25519

Signing Key ID

ed25519-prod-2025-02

Dataset / Project

Notarized Artifact — 2026-08-26

Verification Evidence

Certificate record

Certificate a1c14a52… found (cert.v2)

Canonical signature input

Payload canonicalized with RFC 8785 JCS; the signature covers these exact bytes.

Signing key

key_id ed25519-prod-2025-02 — resolves to the published Ed25519 public key.

Key status

Key is active.

Signature authenticity

Ed25519 signature valid against the published public key.

Verdict: Certificate verified — production

Raw check flags (API)

signature_valid

schema_valid

not_revoked

Certified Artifact Hashes

ZIP artifact SHA-256 (qa.txt)

dc1ab12908a4650ef898be6184ae1e28fd33b33e6a44084f248232a8491abae9

Verify locally without this website:

# Linux / macOS
sha256sum dataset.zip

# macOS alternative
shasum -a 256 dataset.zip

# Windows PowerShell
Get-FileHash dataset.zip -Algorithm SHA256

The output must match the artifact_hash above. Full verification guide →

Verify Your File

Check artifact integrity

Upload the original artifact file to confirm its SHA-256 matches the fingerprint stored in this certificate. Files are hashed server-side; this is independent of certificate-signature verification above.

What This Certificate Proves

This certificate proves that a synthetic dataset was generated by CertifiedData and its contents match the cryptographic fingerprints recorded at issuance time.

The Ed25519 signature covers the full certificate payload including artifact hashes. Any modification to the ZIP file or inner CSV files will produce a different SHA-256 hash that will not match the certified values.

The certificate does not verify statistical quality or differential privacy unless explicitly stated in the generation metadata.

Trust Path