About

Namespace trust infrastructure for machine decision-making

ZoneProof publishes machine-readable records that help software understand what a DNS namespace means before it acts on a name. The service is designed for agents, search systems, registries, relying parties, and developers who need structured trust signals instead of vague brand heuristics.

At a practical level, ZoneProof answers questions such as who operates a zone, whether a namespace is open or restricted, what verification pattern it claims to enforce, where the canonical record lives, and what source links support those assertions.

What ZoneProof publishes

• Public `/.well-known` namespace records for TLD-level trust metadata.
• Structured schema documents for namespace and credential-bearing entity/domain records.
• MCP endpoints so agents can query trust metadata through standard tool calls.
• Operator, agreement, and restriction metadata normalized for machine use.

Why this exists

A domain name is not just a string. In many namespaces, the suffix carries policy meaning: it may imply professional licensure, regulated activity, community membership, brand control, geography, or other constraints. Software increasingly makes decisions based on names, but most systems still lack a clean way to inspect namespace policy before taking action.

ZoneProof is meant to close that gap. The goal is not to replace primary authorities or legal compliance systems. The goal is to make namespace-level trust metadata easier to discover, normalize, cite, and consume.

Current public scope

The current public surface focuses on TLD namespace records and public MCP discovery. That keeps the data boundary simple while establishing a stable machine interface for agents and integrators.

Over time, ZoneProof is intended to grow from generic namespace metadata into deeper namespace-specific trust layers where the underlying policy and data sources justify it.

Trust model and limitations

ZoneProof aggregates and republishes metadata from registries, public standards bodies, and related public sources. It is an explanatory trust layer, not a guarantee. Consumers should treat ZoneProof as a discovery and interpretation aid, then decide whether to perform their own verification, compliance checks, or contractual review.

For that reason, the service emphasizes provenance, source links, machine-readable schemas, and explicit scope boundaries rather than broad claims of certification.

Next direction

The longer-term product direction is to support richer trust interpretation for credentialed and policy-bearing namespaces including `.cpa`, `.bank`, `.coop`, and `.pharmacy`.