1.22.1

Storage-wording precision in every production-visible string (the /explore note, MCP server instructions and tool descriptions, human result pages, site pages, README): general claims now read "stores no discovered domain or resource data". No behavior changes. Companion inspect releases 0.1.3/0.1.4: normative Signature-Agent label rule with the Appendix E.2.1 vector defect documented, independent multi-signature validation, and the legacy origin-only directory rule. Changelog: https://nessgate.com/changelog

1.22.0

Web Bot Auth verification implements the IETF WG protocol draft (draft-ietf-webbotauth-httpsig-protocol-00) and passes its Appendix E.2 test vectors: Structured Fields dictionary Signature-Agent with type semantics, covered-member-driven key discovery, thumbprint-required keyid, full profile enforcement, no redirects during discovery, safe multi-signature handling (@nessgate/inspect 0.1.2). MCP initialize-era support extends through revision 2025-11-25. Package release triggers separated; an IP-level lab measurement retired per the privacy policy's stronger wording. Changelog: https://nessgate.com/changelog

1.21.0

MCP-Registry federation returns one record per server name (the registry's isLatest marker wins; deterministic greatest-version fallback). Readiness checks of nessgate.com's own endpoints run through the in-process router instead of misreporting the service unreachable. Deterministic offline gate (npm run gate) now backs CI and both package publish workflows. Dual-era MCP support (2026-07-28 server/discover alongside initialize-based revisions), A2A v1 interfaces, and oversized-read honesty shipped in 1.20.0; library registry federation and declared-pointer delegation in 1.19.0. Companion package @nessgate/inspect 0.1.x: inbound-request inspection with hardened fetching (per-hop redirect validation, DNS checks, size and key caps) and the current Signature-Agent dictionary form. Full changelog: https://nessgate.com/changelog

v1.6.0 — benchmark-driven general rules

Canonical-host fallback (same registrable domain only) in /discover and the library; stricter text-probe validation (HTML behind leading comments rejected); publisher-redirect-candidate class in Related Discovery; single-parse shape checks cutting heavy-route CPU. Library published as @nessgate/resolver@1.4.0. Benchmark data and methodology in benchmarks/.

v1.3.3 — documentation

Corrected the npm package README (accurate exports incl. ADAPTERS, current mechanism list, browser guidance, optional GB/Z 185.5 gateway option) and aligned version labels. No behavior change.

v1.3.2 — evidence-based /explore; version alignment

Adds GET/POST /explore/{domain} (bounded delegated discovery, evidence classes, provenance chains, attributed MCP Registry federation, opt-in candidate verification), honest exact-host empty results, and aligns version labels across the library, MCP server, registry listing, OpenAPI description, and changelog. /discover unchanged.

v1.3.1 — accuracy fixes (AID naming, ARD scope)

Accuracy cleanup (no new protocols):

• AID vs DNS-AID: the _agent TXT v=aid1 adapter is the AID draft, not the IETF DNS-AID draft (SVCB at _agents.<domain>). Renamed the adapter/source/checked id dns-aid → aid and documented that DNS-AID (SVCB) is a separate, unimplemented mechanism.
• ARD scope: ARD v0.91 defines five publication surfaces; NessGate reads three (well-known, rel="ard", robots Agentmap:). Dropped the "complete ARD support" wording; in-page JSON-LD and DNS Service Binding are noted as not-yet-read.

No behavior change beyond the corrected aid label. GB/Z 185.4 / optional 185.5 (from 1.3.0) unchanged.

v1.3.0 — GB/Z 185.4 support

GB/Z 185 (China, 智能体互联) support: normalize 185.4 agent descriptions and, optionally, query a 185.5 discovery gateway.

• 185.4 (ACS): agent descriptions are recognized by content and normalized (source gbz-185-4), preserving the GB/Z fields (aic, provider, securitySchemes, certificate, skills) and provenance. Domain-first — an ACS served at the agent-description location NessGate already reads is normalized; no GB/Z-specific path is guessed.
• 185.5 (optional, Node-only): resolve(domain, { gbz: { gatewayUrl, fetch, query } }) — off unless configured. POSTs to the reference implementation's real {gateway}/acps-adp-v2/discover with a caller-supplied authenticated fetch (bring-your-own mTLS/OIDC). Never auto-discovered; never in a browser or the hosted resolver. Records carry provenance: "gbz-185-5-gateway".

Worker/library/package parity preserved; conformance, parity, and gateway tests added. No guessed endpoints, no fake conformance.

NessGate v1.2.0 — the universal resolver (adapter architecture)

Discovery is now an adapter architecture with four channels (well-known paths, an ARD rel=ard link, an ARD robots.txt Agentmap directive, and a DNS-AID TXT record). Adds Agent Network Protocol, Universal Commerce Protocol, DNS-AID/AID, and completes ARD across all three of its discovery surfaces — every adapter conformance-tested, with worker/library/npm parity. GB/Z 185.4/185.5 is intentionally not implemented (its discovery mechanism is only in the paywalled national standard and appears federated; no fake conformance). Publishes @nessgate/resolver@1.2.0.

NessGate v1.1.0 — the neutral compatibility resolver

Give NessGate a domain and it reads the machine-readable resources that domain publishes across the standard discovery locations (llms.txt, ARD / ai-catalog, A2A agent card, RFC 9727 api-catalog, ai-info.json, OpenAPI, Open Resource Discovery, host-meta) and returns one normalized answer, each record linking back to its source. It reads on demand, stores nothing, and makes no ownership or safety claim. Ships the resolver, the embeddable @nessgate/resolver library, and an MCP server (discover_domain). Apache-2.0; governed by the Charter (https://nessgate.com/charter).