What the checker looks up
The checker queries an SVCB record (type 64) at_index._agents.yourdomain.com, following DNS-AID draft-02. The draft is a work in progress, not a published standard or a requirement for ordinary business websites.
DNS alone does not show that the destination serves an agent index. The checker does not test that endpoint, its TLS connection, or whether an AI engine uses it.
How to use the checker
Go to areyoufoundbyai.com/tools/dns-aid-checker, enter your domain and select Check the record. The result shows:
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.
If you operate an agent index
The live DNS-AID setup guide sets out the requirements. In short:1
Confirm the index with your operator
Confirm the index hostname and how agents access it with your service operator. Only publish an index you actually operate.
2
Publish a separate SVCB record
Use an SVCB record, type 64, at This is not a ready-to-publish record. A parameter such as
_index._agents.<your-domain>. HTTPS is a different record type (65), and a bare-domain HTTPS record is not a substitute for the SVCB index entry. Point its TargetName at the real index hostname, without underscores, and configure priority and service parameters for that endpoint.alpn="h2" is only appropriate when the actual endpoint supports it.3
Test DNS, TLS and the index itself
Check the DNS observation with the checker, or from a terminal:Then test the TLS connection and the actual index service. The checker covers the DNS response only.
Earlier versions of this page, and of the live guide, recommended an HTTPS record pointing at the website host. That advice was incorrect. If you added a record from that advice, check it with the person who operates your DNS and agent service before changing it. The checker does not make DNS changes.