Why it matters
- The IETF's DNS-AID draft proposes that a site publish its agents' services in DNS, under
_agents: an index at_index._agents, A2A agents at_a2a._agents, MCP servers at_mcp._agents, with SVCB records that carry the address and connection details. - It asks that they be signed with DNSSEC, so that an agent can trust the record comes from the domain's owner.
- This is information: a draft, not yet a standard, that few sites follow.
How to fix
Add a record for each service to the domain's zone, and sign the zone with DNSSEC:
text
_mcp._agents.example.com. 3600 IN SVCB 1 mcp.example.com. alpn="h2" port=443How we detect
In the agent-readiness tool alone: we ask a DNS-over-HTTPS resolver (with the DO bit) for SVCB and HTTPS records at _index._agents, _a2a._agents and _mcp._agents under the site's name, and under its name without www. when it starts with it, and for TXT at _index._agents. The rule passes with a record of priority above zero that the resolver marked AD, validated with DNSSEC.