ZTDS.ai RFC v1.0 Standard
Get Certified →
Offline Cryptographic Validator · RFC 8032

ZTDS™ Conformance Certificate Offline Ed25519 Signature Validator

Verify Ed25519 signatures, RFC v1.0 invariant conformance, and SHA‑256 build digests in browser RAM — 100% offline with 0.00 bytes egress.

Algorithm: Ed25519 (RFC 8032) Privacy: 0.00 Bytes Egress Canonical: RFC 8785 JCS SubtleCrypto: Web Crypto Native
ZTDS-CERT-v1
Segments: Header . Payload . Sig (64B)
0 chars Awaiting Input
Load Preset Test Tokens:
Independent CLI Verification

To verify this certificate inside an air-gapped terminal or automated CI/CD pipeline without opening a web browser:

npx ztds-verify <TOKEN_STRING>

Awaiting Certificate Token

Paste a token or select one of the test tokens on the left. Cryptographic verification is computed directly in your browser using standard Web Crypto primitives.

Root Key: MCowBQYDK2VwAyEAg3N98ZgL4Uqbu0PmqvG8KN8vUicYkgKfUNVgwlLObr4=
3-Tier Accreditation Architecture

Verified Organizations, Engines & Protected Web Domains

ZTDS separates full organizational compliance (Level 3 Corporate Members), core sanitization software (Level 2 Verified Registry), and websites enforcing client-RAM form protection (Level 1 Protected Web Domains).

Level 3 · Organizations /companies/ →

Corporate Adopters & Enterprise Pool

Organizations enforcing ZTDS across internal LLM pipelines, employee AI workflows, and CISO governance with published case studies.

BrandMeWeb Level 3 ↗
Founding Corporate Member & Audit Partner
PrivacyScrubber Level 3 ↗
Pioneer Certified Commercial Implementation
Browse All Companies → Apply for Level 3 ↗
Level 2 · Software & SDKs /registry/ →

Verified Software & SDK Engines

Audited libraries, headless SDKs, MCP stdio gateways, and CMS plugins with SHA-256 build receipts and zero cleartext network egress.

@privacyscrubber/sdk & mcp-server Level 2 ↗
30 Industry Profiles · Headless Node/Python & MCP
PrivacyScrubber WordPress Guard WordPress.org ↗
Plane 6 RAM Guard · Zero-PII MySQL & 1-Tap #ztds_seal
Explore Software Registry → SDK Docs ↗
Level 1 · Protected Domains Plane 6 Form Guard

Verified Web Form Intake Domains

Production websites running PrivacyScrubber ZTDS Guard to mask high-risk inputs in browser RAM (<0.4ms), store 100% Zero-PII MySQL logs, and deliver 1-Tap Staff Lead Cards.

barrelswood.com ↗ Verify Cert →
BarrelsWood B2B Intake · Smart CRM + Zero-PII MySQL + #ztds_seal
Verify Any Protected WordPress Site
Append ?domain=your-site.com to this URL or install from WordPress.org to enable your Level 1 Domain Seal.
WordPress.org Plugin ↗ Docs ↗

How ZTDS Cryptographic Verification Works

Designed for strict Zero-Trust environments, allowing Chief Information Security Officers, developers, and compliance auditors to independently attest software authenticity without contacting any verification server.

01

Deterministic JSON Canonicalization

The certificate payload is serialized strictly conforming to RFC 8785 (canonical key sorting, uniform UTF-8 normalization), ensuring byte-for-byte identical hashing across disparate programming languages and runtimes.

02

RFC 8032 Ed25519 Signatures

Signatures are computed over the Edwards-curve Digital Signature Algorithm (Ed25519). The 64-byte signature is immune to side-channel timing attacks and cannot be forged without the Consortium master key.

03

SubtleCrypto In-RAM Validation

Verification runs entirely inside browser client volatile RAM via window.crypto.subtle. 0.00 bytes of data are sent to vendor or third-party cloud infrastructure.

Direct Answer Knowledge Base

Ed25519 Cryptographic Certificate Validator FAQ

How does the ZTDS Cryptographic Certificate Validator verify conformance tokens offline? ↓
The validator parses the ZTDS-CERT-v1 token, canonicalizes the JSON payload according to RFC 8785 (JSON Canonicalization Scheme), and verifies the detached Ed25519 signature (RFC 8032) directly in browser volatile RAM using the Web Crypto API (window.crypto.subtle) with zero external server calls.
What public key is used to authenticate official ZTDS-CERT-v1 certificates? ↓
All official ZTDS conformance certificates are verified against the consortium SPKI Ed25519 root public key (MCowBQYDK2VwAyEAg3N98ZgL4Uqbu0PmqvG8KN8vUicYkgKfUNVgwlLObr4=), which is published in the open specification and machine-readable llms.txt corpus for independent air-gapped verification.
Can enterprise procurement teams verify certificates via the command line in CI/CD pipelines? ↓
Yes. Security engineers and procurement auditors can validate any certificate token or registry slug in air-gapped environments by running npx ztds-verify --strict, which exits with code 0 only when the Ed25519 signature and all four invariants are mathematically valid.
Does verifying a certificate transmit any corporate data or telemetry to ZTDS.ai? ↓
No. Certificate signature verification and A4 PDF conformance certificate rendering occur 100% locally within client browser memory, transmitting 0.00 bytes of telemetry or verification metadata over the network.