Friday, November 20, 2026

Top 5 This Week

Related Posts

The ANS standard makes the domain name the identity of AI agents


On November 10, 2026, at the KubeCon + CloudNativeCon North America conference in Salt Lake City, the Linux Foundation announced that Agent Name Service (ANS) was becoming one of its projects. This open standard links the identity of an AI agent to a domain name over which its 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 a cloud provider’s registry.

ActuIA reported on June 2 the launch of DNS-AID, another project of the foundation, dedicated to the discovery of agents using DNS. ANS deals with the related question of identity. The Linux Foundation announced the intention on June 23. 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 filing has 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. Accessed on November 19, all are marked “Status: DRAFT v1.0” and have a version number of 0.1.0 or 0.2.0. A proposal filed on November 16 by Connor Snitker of GoDaddy, a member of the technical committee, aims to replace this designation with “Active” without affecting the requirements of the protocol. It was not merged on November 19. The project site warns that the published specifications are “drafts currently in active development.” The press release of November 10 speaks of a specification “now formalized”.

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

The identity of an agent starts from a domain name over which the operator proves control

For an agent to obtain an ANS identity, it needs a hostname. Each registration must be anchored to a fully qualified domain name, the only mandatory identity requirement of the standard (ANS-0). The operator proves that he controls it to a registration authority by an ACME challenge, the protocol which is already used to issue TLS certificates for websites. The agent then receives a name of the form ans://v1.0.0.agent.example.comwhere his version appears. A consumed version number cannot be resumed, even after a failed save (ANS-2).

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

The identity of the organization operating the agent can be traced to the registration. This capability is optional and not all of its profiles are 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 release listed LEIs among the supported systems.

An agent checks three pieces of evidence 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 journal for this agent. The registration is valid at the time of the appeal and has not been revoked. The peer holds the corresponding private key. Verification is done online, by querying the log, or offline using a signed receipt and a short-lived status token, a route that the document recommends for new implementations. The caller proves that it holds its key by mutual TLS or by a DPoP proof (RFC 9449) carried in an HTTP header, which survives the gateways where the TLS connection terminates.

The text specifies that these procedures authenticate a peer and say nothing about what they have the right to do. Authorization remains the responsibility of the called application, and delegation, that is to say the case of an agent who acts for a user or for another agent, is excluded from this review. The revocation is not instantaneous: with the default settings of the offline channel, the delay can reach 2 hours 10 minutes in the worst case. The project site adds that sealed fingerprints can link published metadata to a record but “do not attest to code running on a remote machine.” In June, the foundation presented a framework for verifying an agent’s permissions and whether their code remains “authentic and unchanged.” ANS-6 and the project site describe a narrower scope, while the specification repository home page still states that the certificate records what code is running.

ANS uses the DNS-AID format for agent discovery

The Linux Foundation launched DNS-AID on a basis developed by Infoblox. In a joint press release dated May 14, Infoblox and GoDaddy presented the two standards as complementary, ANS being focused on the identity of agents and DNS-AID on their discovery. The default ANS discovery profile takes over the DNS-AID draft settings. The version of this draft submitted to the IETF on November 2 includes among its authors Scott Courtney of GoDaddy, also co-author of the ANS draft.

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

GoDaddy holds three of five seats until first election

The project’s technical charter is dated November 9, 2026. It entrusts technical supervision to a committee of five to nine seats, in which the same organization must hold less than half of the voting members. This limit only applies at the end of a twelve-month start-up period, or from the first election if it occurs earlier. By then, the initial committee has five members. Three are affiliated with GoDaddy. The other two are Ken Huang (DistributedApps.ai), who said 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 ceiling “on purpose”.

Salesforce-owned MuleSoft’s documentation describes registering agents with “GoDaddy ANS.” The reference implementation allows everyone to deploy their own registration authority.

Eleven organizations have contributed to or adopted the standard 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 out in the press release of June 23, to which are added DigiCert, Radix and TrustModel.ai. Amazon Web Services, Google and Microsoft are not on this list. Amazon’s Jeffrey Damick, 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 separate issue from identity between organizations.

At the IETF, ANS is not supported by any working group. The ANS v2 draft submitted to the IETF is an individual submission. The DAWN (Discovery of Agents With Names) working group focuses on the discovery of agents, and its charter excludes the management of their identities from its initial phase. Its schedule foresees the submission of its protocol specifications to the IESG by December 2027.

ANS can already try it locally

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

Quotes translated from English by ActuIA.

Our articles will be prioritized in Google’s “Featured” section.

Shredder Smith
Shredder Smith
Shredder Smith is the lead curator and digital persona behind topaitools4you.com, an AI directory dedicated to "shredding" through industry hype to identify high-utility software for everyday users. Smith positions himself as a blunt, no-nonsense reviewer who vets thousands of emerging applications to filter out overpriced "wrappers" in favor of tools that offer genuine ROI and practical productivity. The site serves as a watchdog for the AI gold rush, providing categorized rankings and transparent reviews designed to help small businesses and creators navigate the crowded tech landscape without wasting money on low-value tools.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Popular Articles