Agents Have Credentials Everywhere and Identity Nowhere. DNSid Is the First Serious Fix.

On June 29, 2026, the IETF received a draft proposing a layer no agent identity stack currently has: a durable, DNS-anchored record of who owns an agent, designed to outlive every credential that agent will ever carry. The draft is called DNSid, and behind it sits Vint Cerf, who left Google after 20 years to advise the group publishing it.

Your production agents already have plenty of identities. An IAM role in AWS. A workload identity in your cluster. An OAuth token from the SaaS platform it calls. A SPIFFE ID if your platform team is ahead of the curve. Every one of those identities shares the same property: it is scoped to the environment that issued it, and it dies at the boundary of that environment. Migrate the agent to another cloud, swap the underlying model, rotate the credential after an incident, and the identity chain breaks. Whatever accountability was attached to it breaks with it.

Two Questions, and Today’s Stack Answers Only One

Runtime identity answers the question “may this agent act here, right now?” That question is well served. OAuth, OIDC, SPIFFE, workload identity federation: mature protocols, mature tooling, real adoption. We have covered that territory before, from the credential exchange layer Vercel shipped to the isolation architecture for non-human insiders.

Risk and audit teams block production on a different question: “who is accountable for this agent, and will we still be able to prove it in eighteen months?” That question has no protocol today. It gets answered with spreadsheets, tribal knowledge, and a service-account naming convention someone invented in 2023. When Amazon and Perplexity ended up in court over an agent’s identity, the dispute was possible partly because no neutral record existed of who operated what. And as agent traffic overtakes human traffic, the volume of unattributed actors compounds quarterly.

DNSid is the first credible attempt to give the accountability question a protocol. Not a product with an SDK and a pricing page. A record format anyone can publish and anyone can verify.

What the Draft Actually Specifies

The IETF draft (draft-ihsanullah-dnsid-01, authored by Naveed Ihsanullah of Identity Digital) is short and concrete. An agent gets a fully qualified domain name. At _dnsid.<agent-fqdn>, the owner publishes a TXT record starting with v=DNSid1. The record carries an entity signature that verifiers check against a JWKS document served over HTTPS, so the ownership claim is cryptographically bound to the domain holder. A separate operational key handles day-to-day signing, which means the entity key can stay cold. Every lifecycle event, from issuance through rotation and revocation to retirement, lands in an append-only log. DNSSEC is optional but recommended.

The design resolves to three anchors. DNS gives you the owner: a name that exists independent of any cloud account. PKI gives you proof in the moment: the signature verifies now, against keys the owner controls. The append-only log gives you the receipt that survives an audit: when the credential rotated, when the agent was retired, who authorized it. Ownership, proof, and history each live in a layer built for that job.

None of this replaces your runtime stack. The draft is explicit that DNSid sits beneath OAuth, OIDC, and SPIFFE. Those protocols keep deciding whether an agent may act in a given context. DNSid records who answers for the agent when the acting is done.

The Birth Certificate Layer

The launch material uses an analogy worth keeping: a birth certificate does not get you a job or through airport security. A passport does, a badge does, a driver’s license does. But every one of those credentials traces back to the birth certificate. It is the durable root that outlives every document derived from it.

Agent infrastructure has passports and badges in abundance. It has no birth certificate. Each platform issues its own credentials, rooted in its own trust domain, meaningful only inside its own walls. The result is the situation most enterprises are in right now: credentials everywhere, identity nowhere. An agent can hold five valid credentials simultaneously and still have no answer to “who owns you?” that survives contact with a compliance review.

The choice of DNS as the root is the interesting engineering decision. DNS is the one namespace that is already global, already neutral in operation, already surviving four decades of platform churn. Companies die, clouds get migrated away from, model vendors get swapped. Domain names persist through all of it. Anchoring ownership there means the record’s lifetime matches the accountability requirement, which is measured in years, while credentials are measured in minutes.

Who Is Behind It, and Why That Cuts Both Ways

Innovation Labs, a division of the domain registry operator Identity Digital, launched DNSid on April 27, 2026. Vint Cerf’s move from Google to advise the lab is the strongest signal attached to the project. His stated reason, per TechCrunch: “I felt like I might be able to help them in a period of time when naming and identification is becoming increasingly important.” Allie Kline serves as interim CEO, and TechCrunch reports hyperscalers and identity companies trialing the standard, though none are named. Fadi Chehade, the former ICANN CEO, argued in a July Newsweek op-ed that open accountability standards are what keep the agent economy from fragmenting, the way DNS itself kept the early internet from splitting into walled gardens.

Now the honest part. This is an individual IETF submission, not a working-group document, and it expires December 31, 2026 unless refreshed. No adopter has put their name on it. The 50-to-1 ratio of agents to humans that the DNSid site cites is a vendor claim, not an independent measurement. And Identity Digital sells domains: a standard that anchors every agent’s identity in a domain name grows the registry business directly. That does not make the design wrong. DNS being commercially convenient for a registry and technically correct for durable naming can both be true. But you should evaluate the draft on its merits, and price in that the loudest advocate profits from adoption.

There is also no independent critical review yet. The trade coverage so far restates the announcement. Treat the architecture as promising and unproven.

What to Do With This Now

You do not need to adopt a draft standard this quarter. You need to start asking the question the draft exists to answer.

First, add one question to every agent-platform vendor conversation: “what survives when the credential rotates?” If the answer is a platform-scoped ID that dies on migration, you now know the accountability chain has a hole, and you know its shape. Vendors who have thought about durable identity will answer in seconds. Vendors who have not will describe their OAuth flow.

Second, run a one-hour inventory. For each production agent, write down the identifier that would still be meaningful after a cloud migration, a model swap, and a credential rotation, all three. For most teams the honest answer is a row in a spreadsheet, owned by someone who might leave. That is your current durable-identity layer. Decide whether that is acceptable on the record.

Third, run the cheap experiment. Publishing a _dnsid TXT record for one internal agent costs an afternoon and a subdomain. You will learn more about the draft’s practical fit from that afternoon than from any analysis, including this one. If the standard dies in December, you lost a TXT record. If it becomes the accountability layer regulators start asking about, you have an eighteen-month head start on proving who owns your agents.

The runtime identity problem is being solved by well-funded platform teams. The durable ownership problem was unclaimed until April. Watch whether the unnamed hyperscalers put their names on it. That is the signal that turns this from a registry’s bet into infrastructure.

---

This analysis synthesizes DNSid - The Birth Certificate for AI Agents (Innovation Labs / Identity Digital, April 2026), DNS-Anchored Durable Identity for AI Agents, draft-ihsanullah-dnsid-01 (IETF individual submission, June 2026), Vint Cerf Is Working on a Plan to Unleash AI Agents on the Open Internet (TechCrunch, July 2026), and Identity Digital Launches DNSid (GlobeNewswire, April 2026).

Victorino Group helps engineering organizations design agent identity and accountability layers that survive audits, migrations, and vendor changes. Let’s talk.