On 10 November 2026, at the KubeCon + CloudNativeCon North America conference in Salt Lake City, the Linux Foundation announced that Agent Name Service (ANS) had become one of its projects. This open standard ties an AI agent's identity to a domain name whose operator has proven control, then makes it verifiable by a third party using certificates and a public log. A company that exposes an agent to its customers, suppliers or other agents thus has a way to prove who is speaking, built on DNS rather than on a cloud provider's registry.

ActuIA reported on 2 June the launch of DNS-AID, another foundation project, dedicated to agent discovery via DNS. ANS addresses the related question of identity. The Linux Foundation had announced its intention on 23 June. Less than five months later, there is a charter, a technical committee, code and a readable specification, still in version 0.x.

The seven specification documents remain in version 0.x

The specification repository contains seven documents, numbered ANS-0 to ANS-6: identity and proof of control, registration and lifecycle, versioned naming, DNS publication, transparency log, integrity monitoring, agent-to-agent authentication. Consulted on 19 November, all carry the mention "Status: DRAFT v1.0" and a version number 0.1.0 or 0.2.0. A proposal filed on 16 November by Connor Snitker of GoDaddy, a member of the technical committee, aims to replace this mention with "Active" without changing the protocol requirements. It had not been merged on 19 November. The project website warns that the published specifications are "drafts under active development". The 10 November press release, for its part, speaks of a specification "now formalised".

The reference implementation, written in Go and published under the MIT licence, includes a registration authority, a transparency log and an offline verifier. Its code was first published under GoDaddy's GitHub account.

An agent's identity starts from a domain name whose operator proves control

For an agent to obtain an ANS identity, it needs a host name. Each registration must be anchored to a fully qualified domain name, the only mandatory identity requirement of the standard (ANS-0). The operator proves control to a registration authority through an ACME challenge, the protocol already used to issue TLS certificates for websites. The agent then receives a name of the form ans://v1.0.0.agent.example.com, which includes its version. A consumed version number cannot be reused, even after a failed registration (ANS-2).

The operator then publishes in its DNS zone the records indicated by the authority. By default, this is an SVCB record per access point, in the DNS-AID format, supplemented by a mandatory TXT record _ans-badge that points to the transparency log (ANS-3). DNSSEC is not required. The TLSA record, which publishes the server certificate fingerprint, is optional and is only checked in signed zones. The identity certificate, linked to the agent's versioned name and issued by the registration authority's private certification authority, is also optional, but this choice is final for a given registration (ANS-1).

The identity of the organisation operating the agent can be attached to the registration. This capability is optional and its profiles are not all active. The repository classifies did:web and did:key as "Active", and the LEI profile, the legal entity identifier used in finance, as "Postponed". The June press release cited LEIs among the supported systems.

An agent verifies three proofs before believing another

ANS-6 describes this verification. Three facts, all linked to the same certificate, must be established. The certificate is sealed in the log for this agent. The registration is valid at the time of the call and has not been revoked. The peer holds the corresponding private key. Verification is done online, by querying the log, or offline from a signed receipt and a short-lived status token, a path the document recommends for new implementations. The caller proves it holds its key through mutual TLS or through a DPoP proof (RFC 9449) carried in an HTTP header, which survives gateways where the TLS connection terminates.

The text specifies that these procedures authenticate a peer and say nothing about what it is allowed to do. Authorisation remains the responsibility of the called application, and delegation, i.e. the case of an agent acting for a user or another agent, is excluded from this revision. Revocation is not instantaneous: with the default settings of the offline path, the delay can reach 2 h 10 in the worst case. The project website adds that sealed fingerprints can link published metadata to a registration but "do not attest to the code running on a remote machine". In June, the foundation presented a framework for verifying an agent's permissions and whether its code remains "authentic and unchanged". ANS-6 and the project website describe a narrower field, while the specification repository's home page still writes that the certificate records what code runs.

ANS adopts the DNS-AID format for agent discovery

The Linux Foundation launched DNS-AID on a basis developed by Infoblox. In a joint press release of 14 May, Infoblox and GoDaddy presented the two standards as complementary, ANS being focused on agent identity and DNS-AID on their discovery. ANS's default discovery profile takes up the parameters of the DNS-AID draft. The version of this draft filed with the IETF on 2 November counts among its authors Scott Courtney of GoDaddy, also co-author of the ANS draft.

The Agent Directory service of AGNTCY, another Linux Foundation project, supports ANS, according to the 10 November press release. The ANS Finder tool implements Agentic Resource Discovery (ARD), a discovery specification.

GoDaddy holds three of the five seats until the first election

The project's technical charter is dated 9 November 2026. It entrusts technical oversight to a committee of five to nine seats, in which a single organisation must hold less than half of the voting members. This limit only applies at the end of a twelve-month startup period, or at the first election if it occurs earlier. Until then, the initial committee has five members. Three are affiliated with GoDaddy. The other two are Ken Huang (DistributedApps.ai), who says in the press release that he led the initial development of ANS, and Michael Kantor (Hashgraph Online, HOL). The document itself notes that this composition exceeds the cap "on purpose".

The MuleSoft documentation, owned by Salesforce, describes the registration of agents with "GoDaddy ANS". The reference implementation allows anyone to deploy their own registration authority.

Eleven organisations have contributed to the standard or adopted it since June, according to the foundation: Cisco, Cloudflare, DigiCert, DistributedApps.ai, GoDaddy, HOL, Infoblox, Radix, Salesforce, OWASP and TrustModel.ai. Eight of them already spoke in the 23 June press release, to which are added DigiCert, Radix and TrustModel.ai. Amazon Web Services, Google and Microsoft do not appear in this list. Jeffrey Damick of Amazon, however, is among the authors of the DNS-AID draft. Microsoft, for its part, assigns an identity to each agent within the enterprise environment, a problem distinct from identity between organisations.

At the IETF, ANS is not carried by any working group. The ANS v2 draft filed with the IETF is an individual submission. The DAWN (Discovery of Agents With Names) working group deals with agent discovery, and its charter excludes identity management from its initial phase. Its schedule provides for the delivery of its protocol specifications to the IESG by December 2027.

ANS can already be tried locally

Moving under the Linux Foundation gives the project a charter, licences and public contribution rules. It guarantees neither the stability of the text nor the plurality of operators. Evaluating ANS does not require heavy investment, since it relies on the domain, certificates and DNS zone that the company already owns, and the reference implementation runs a registration authority and a log locally. Building a production chain on documents in version 0.x, however, exposes one to revisions of the text. The first election of the technical committee must be completed by 9 November 2027 at the latest.

Quotes translated from English by ActuIA.

Our articles will then appear first in Google Top Stories.