Post-quantum · On-chain · Independently verifiable

Trust you can
verify for yourself.

Herald Verify seals domains and documents with a record on KXCO's post-quantum chain, and lets anyone confirm it independently, without trusting KXCO. Checking is free. Identity for people and AI agents is live, through KXCO Herald.

Check a domain → How it works

Live on

Why it matters

Three things your badge proves — that no screenshot or certificate authority can.

🔐

Instant trust signal

Visitors see a badge that links directly to an on-chain record. No middleman, no expiry delay, no PDF to download.

⛓

Tamper-evident forever

The attestation is written to KXCO Armature. It cannot be altered, back-dated, or removed, even by KXCO.

🛡

Post-quantum ready

Recorded on KXCO's post-quantum chain, which verifies ML-DSA-87 and ML-DSA-65 signatures in consensus. ML-DSA is the post-quantum signature standard NIST published as FIPS 204 for the quantum era.

🔍

Independently verifiable

Anyone can verify your attestation directly via RPC using open-source tools. KXCO's servers are not in the verification path.

How it works

Three steps. Live in 24 hours.

Request

Tell KXCO which domain or document to attest. We confirm scope and eligibility.

We attest

KXCO's scanner evaluates your domain and writes the attestation to KXCO Armature, which verifies ML-DSA-87 and ML-DSA-65 signatures in consensus.

Embed & go

Add one line of HTML to your site. The badge queries the chain in real time and turns grey the moment it's revoked.

Live attestations on-chain:

kxco.ai

livetradingnews.com

target150.com

What “Verified” means — and what it doesn’t

We say what we can prove. Nothing more.

✓

Cryptographic proof of integrity. The artifact matches the record on chain. If configuration has changed since attestation, its hash no longer matches.

✓

Tamper-evident, permanent record. Anchored on KXCO Armature and publicly readable. Verifiable without asking KXCO for anything.

✓

Post-quantum chain. Recorded on KXCO's post-quantum chain, which verifies ML-DSA-87 and ML-DSA-65 (NIST FIPS 204) signatures in consensus. ML-DSA is designed to resist attacks by quantum computers.

✗

Herald Verify does not attest to the content of documents, legal validity, or regulatory status of any verified party.

Verify free. Get attested through KXCO.

Anyone can check an attestation for free. Issuing your own is part of a KXCO engagement.

Verify

Free

Check any domain or attestation yourself: no account, no fee. Verification reads the record on KXCO Armature with open-source tools.

Check a domain →

Get attested

Enterprise

Domain, document and publisher attestations, provisioned alongside sign.kxco.ai as part of your platform engagement. Identity for people and AI agents is live, through KXCO Herald.

Talk to us →

Questions

Can someone fake the badge?

No. The badge is served live from KXCO Armature: it queries the actual on-chain record every time it loads. A copied badge image would be static and obviously fake. The real badge turns grey the moment an attestation is revoked or a subscription lapses.

What happens if an attestation lapses?

The badge enters a 30-day grace period (grey, unverified). After 30 days it displays the red Expired badge. The on-chain record remains permanently — only the active gate changes. Renewing the attestation restores the verified badge instantly.

How do I verify independently, without going through this site?

Use any JSON-RPC client pointed at the public Armature RPC, https://api.purse.kxco.ai/rpc/armature, and call latest(keccak256(domain)) on the registry contract. This does not use the Herald Verify API. See the developer docs for a ready-to-run example.

What are ML-DSA-87 and ML-DSA-65, and why do they matter?

ML-DSA-87 and ML-DSA-65 are parameter sets of ML-DSA, the post-quantum digital signature standard NIST published as FIPS 204. It is designed to resist attacks by quantum computers; ECDSA (used by most TLS certificates today) is not. Herald Verify records every attestation on KXCO's post-quantum chain, which verifies ML-DSA-87 and ML-DSA-65 signatures in consensus.

How long does it take to go live?

Typically within 24 hours of confirmed scope. You'll receive the one-line embed code by email. The badge is live the moment the attestation transaction confirms on-chain.

Check any domain

Verify whether a domain has an active on-chain attestation.

Trust you canverify for yourself.