> ## Documentation Index
> Fetch the complete documentation index at: https://areyoufoundbyai.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Check a DNS-AID Index Record (Experimental, Unscored)

> Look up the experimental DNS-AID SVCB index record at _index._agents on your domain. An unscored DNS observation, not an endpoint check, and only relevant if you operate an agent index.

DNS-AID is an experimental Internet-Draft that describes how an organisation can advertise its **agent index** through DNS. The DNS-AID Checker looks up the SVCB index record for your domain and tells you what DNS returns. It is an unscored DNS observation, not an endpoint check.

<Warning>
  **Most business websites need no DNS-AID record.** A homepage, an `llms.txt` file or a marketing page does not by itself establish an agent index. If you do not operate an agent index, there is no DNS-AID setup task for your site. DNS-AID is optional and does not change your visibility score or readiness score.
</Warning>

## What the checker looks up

The checker queries an **SVCB record (type 64)** at `_index._agents.yourdomain.com`, following [DNS-AID draft-02](https://www.ietf.org/archive/id/draft-mozleywilliams-dnsop-dnsaid-02.html#section-3.2). 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](https://areyoufoundbyai.com/tools/dns-aid-checker), enter your domain and select **Check the record**. The result shows:

| Field | What it means |
| - | - |
| Queried name | The name looked up, `_index._agents.<your-domain>` |
| Record type | SVCB (64) |
| Target | The record's target hostname, or "Not verified" |
| DNSSEC | Whether the resolver reports an authenticated DNS answer |

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](https://areyoufoundbyai.com/guides/dns-aid) sets out the requirements. In short:

<Steps>
  <Step title="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.
  </Step>

  <Step title="Publish a separate SVCB record">
    Use an SVCB record, type 64, at `_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.

    ```text theme={null}
    ; 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.
  </Step>

  <Step title="Test DNS, TLS and the index itself">
    Check the DNS observation with the checker, or from a terminal:

    ```bash theme={null}
    dig _index._agents.example.com TYPE64
    ```

    Then test the TLS connection and the actual index service. The checker covers the DNS response only.
  </Step>
</Steps>

<Note>
  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.
</Note>

## What this means for your scan

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

The draft and [RFC 9460 (SVCB and HTTPS records)](https://www.rfc-editor.org/rfc/rfc9460) are the technical references. The index protocol and schema are outside the scope of the cited draft.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.