ATBAE · Verification Checkpoint

Verify a seal.

Every ATBAE examination concludes with a sealed, signed report. This checkpoint confirms whether a seal is genuine — for anyone, free, forever. Verification is never charged and never metered; regulators and auditors are the reason the instrument exists.

Tamper Warning. A seal acts as a strict cryptographic commitment to exact bytes. Altering a report inherently invalidates its seal. The deliberate submission of altered, fabricated, or mathematically compromised seals to this checkpoint is permanently logged, constitutes a direct violation of our Terms, and may be referred to regulatory authorities. If a seal fails, the artifact is rejected—the instrument remains sound.
Your identity is authenticated, not harvested. Every request requires declaring the requester and the principal; these details are subject to strict verification before any records are released. We do not disclose your inquiry to the commissioning client unless they have enabled Verification Transparency. Should a regulator lawfully direct us to withhold notice—we comply unconditionally.
Independent key channel. Every ATBAE manifest carries two signatures — classical Ed25519 and post-quantum ML-DSA-65 (FIPS 204). Both fingerprints are published here — on this website, separate from any signed package — so they never travel solely inside the document they authenticate:
Current signing station (v3, from 2026-09-03):
Ed25519 · sha256:96ecf6f34451e2f2b939745332f5497954ad4dbb3c99c009be2d5a13b006a580 (SHA256:1MXMNVVEqKraRRz+m5peOSkePETFpH/C9BhRGDSG7QU)
ML-DSA-65 · sha256:e62a6078c8ce3e0a2526a0905205bc03579de3ee9a7742df4eef220cafacf472
Intermediate station (v2, 2026-09-02 only — retired; sealed no client artifacts):
Ed25519 · sha256:b8b4e3d12e157a8de50e6f7fb55d04ae023efce643fdb39b8dfdaa85244f23af
ML-DSA-65 · sha256:22f1f3d1a283bc1df13fd21360d67b6ce851fba229cc711ff9ed75952b812bcd
Legacy station (pre-2026-09-02, retired by transition notice):
Ed25519 · sha256:49f51eb5f575125b393d2ab01c04e76e34b3cb25fe8d4767ecffb6b89e555ac5
ML-DSA-65 · sha256:c0d2c8460ce2df52b6f9ae76d57c7561e2afe9a31b4a0e5d28587987c0f290c9
A signature whose fingerprint matches neither this page's current pair nor — for artifacts sealed before a transition's effective date — the pair that preceded it is not ours, whatever the package claims. Both transitions are on the public record as signed notices: 2026-09-02 (precautionary custody hardening, hybrid-signed by the retiring keys) and 2026-09-03 (v2 passphrases rendered unrecoverable during hardening — no compromise; the notice is signed by the incoming v3 pair and recorded in the revocation registry as a non-revoking key_retired entry). Historical artifacts remain valid under the pair that sealed them, permanently. Manifests sealed before 2026-08-31 carry the classical signature only and verify as such — honestly labeled, never silently upgraded.
What the seal is

Every examination concludes with a sealed report: an immutable artifact bundle whose contents are cryptographically fingerprinted (SHA-256) and catalogued in a signed manifest. Alter a single byte of any constituent file, and the cryptographic verification fails. Each manifest carries two independent signatures issued by our signing station — classical Ed25519 and post-quantum ML-DSA-65. To defend against cryptographic downgrade attacks, a manifest sealed under the current scheme requires both signatures: omitting, stripping, or invalidating either one fails verification — neither may be stripped. Manifests sealed before 2026-08-31 carry the classical signature only and verify as legacy single-signed records, honestly labeled. The manifest is independently time-stamped by an RFC 3161 Trusted Timestamp Authority — the chronological baseline cannot be backdated or postdated, even by us.

What the seal proves — and what it does not

It proves complete provenance and structural integrity: these exact bytes are what the examination produced, attested by our keys, at the stated timestamp. It does not act as an endorsement, a warranty, or a guarantee of future model behaviour — signatures attest the integrity of the record; the empirical evidence speaks for itself. Verification is free, permanent, and unmetered; inquiries are strictly authenticated, never anonymous, and we never disclose who checked to the commissioning client unless that client explicitly elected Verification Transparency.

How to verify

Submit the seal string through the form below, or transmit it directly to our intake. We verify the signature chain, record date, and subject identifier against the active revocation registry. Before trusting any signed report, independently confirm our public signing-key fingerprints against the canonical keys published on this page and in the transmittal cover note.

Standard disclosure · general requestors

Authenticity, nothing more.

A basic verification returns only:

  • whether the seal is genuine,
  • the examination date(s),
  • the subject model identifier recorded at firing.

It never returns results, grades, or findings.

Every verification is additionally checked against our signed, append-only revocation & supersession list: a cryptographically genuine seal on a revoked or superseded report is reported as revoked / superseded — never as clean. Verdicts issued from v3.0.0 onward are version-stamped so a report can always be matched to the doctrine it was examined under; the current doctrine version is v3.2.3 (2026-09-04).

Free · answered by return correspondence
Regulatory disclosure · verified authorities only

The record, for those with standing.

After manual credential verification, a regulatory agency or government body may additionally receive:

  • the examination outcome,
  • the commissioning party,
  • the scope of examination.
Free · days, not hours · no fixed turnaround
I · The seal
The seal appears on the report's sealing page. Copy it whole; a single altered character is a failed verification by design.
II · Who is asking
III · Are you a regulatory agency or government body?
How extended verification works. Credential checks are manual and take days, not hours — we publish no fixed turnaround, because each request is verified individually. We will require: 1) a written request on official government letterhead, sent by postal mail, bearing verifiable phone, email, and postal addresses; 2) an email address on the agency's official domain; 3) an independent callback through the agency's published switchboard to confirm the request and the requestor; 4) where warranted, confirmation through the agency's human-resources or administrative office that the requestor is who they claim to be. Falsely claiming regulatory status is unlawful in many jurisdictions and will be reported.

Pressing this composes your request on this machine, downloads a dated copy for your records, and opens your email client addressed to us. This page stores nothing and transmits nothing on its own — your email is the channel, and verification itself is free.

Request composed

Your verification request is ready.

Your email client should now hold the request, addressed to contact@pinnacleglobal.pro. A dated copy has also downloaded to your machine. Basic verifications are answered by return correspondence; extended regulatory verifications proceed only after the credential checks described above — days, not hours.

Verification reference: