DNS-AID starts with an agent index.

Guide · experimental agent discovery

DNS-AID draft-02, section 3.2 describes how to advertise an organisation's agent index through DNS. It is an Internet-Draft, not a published standard or a requirement for ordinary business websites.

For operators who have an index

1. Confirm the index hostname and how agents access it with your service operator.
2. Use a separate SVCB record, type 64, at _index._agents.<your-domain>. HTTPS is a different record type (65).
3. Point its TargetName to the real index hostname, without underscores. Configure priority and service parameters for that endpoint.
4. Test the DNS response, the TLS connection and the actual index service. Our checker covers the DNS response only.

; Illustrative template only: replace the domain and index hostname.
_index._agents.example.com. 3600 IN SVCB 1 index.example.com.

This is not a ready-to-publish record. A parameter such as alpn="h2" is only appropriate when the actual endpoint supports it. A bare-domain HTTPS record is not a substitute for the SVCB index entry.

Check the DNS observation

dig _index._agents.example.com TYPE64

Use the DNS-AID checker to query your domain. A record being found is not proof that the target hosts a usable agent index. Resolver failures mean the lookup is unavailable; they do not prove a record is absent.

What this means for your scan

DNS-AID is optional and unscored. It does not change your visibility score or readiness score. We no longer put it in automatic priority fix plans because the scan does not establish that you operate an agent index.

Earlier versions of this guide recommended an HTTPS record pointing at the website host. That advice was incorrect. Check any record added from that advice with the person who operates your DNS and agent service before changing it; this tool does not make DNS changes.

Technical references: DNS-AID draft-02 and RFC 9460 (SVCB and HTTPS records). The index protocol and schema are outside the scope of the cited draft.