DNS for AI Discovery (DNS-AID)
A DNS TXT record listing agent endpoints lets agents find services at the DNS layer.
- Category
- Discoverability
- Standard
- Emerging checkEmerging
- Off by default, turn on in settings
Who supports it
No agent or browser has announced support yet.
27 others: no evidence yet. See every agent and browser
What it checks
The extension looks up TXT records for the site’s host and for _agent. in
front of it (for example _agent.example.com), using DNS over HTTPS through
Cloudflare’s public resolver. It passes if any record mentions agent, mcp,
ai-discovery or aid.
DNS-AID is an emerging standard, so this check is off unless you turn on emerging checks in the extension’s settings.
Results
| Status | When |
|---|---|
| Pass | An agent-related TXT record was found |
| N/A | No agent-related TXT record was found |
How to fix
DNS-AID is not yet finalised, so there is nothing most sites need to do. If you
run agent or MCP endpoints and want to experiment, follow the current draft for
the exact record format, since it may change. The draft’s main mechanism is
SVCB records under an _agents label (such as _index._agents.example.com),
with TXT records only as a fallback. This check looks only for TXT records, so
it will not detect SVCB records.
Support by agent and browser
Announced means the vendor’s own docs or announcement say so. Published is the date on the vendor’s own page, where it has one. Checked is the last time our weekly research found that page still saying so.
No agent or browser has announced anything about this yet.
No evidence yet27
- ChatGPT
- Claude
- Gemini
- Perplexity
- Copilot
- Meta AI
- ChatGPT Atlas
- Comet
- Dia
- Gemini in Chrome
- Edge Copilot Mode
- Claude Code
- Cursor
- Codex
- GitHub Copilot
- Windsurf
- CCBot
- Applebot
- Amazonbot
- Bytespider
- Cohere
- Mistral
- DuckAssist
- Chrome
- Edge
- Firefox
- Safari
Names and marks belong to their owners and are used only to identify products. None of these vendors is affiliated with Sitebulb. Spotted something out of date? Send a correction.
Adoption on the top 100 sites
1 of 100 measured sites implement it
Sites implementing it1
- #116 bitly.com (via bit.ly)
Overview
How this rating is worked out3 of 9 points
| Factor | Points | Why |
|---|---|---|
| Vendor support | 0 / 3 | 0 vendors supporting, 0 partly or planned |
| Top-100 adoption | 1 / 3 | 1% of measured sites |
| Spec maturity | 2 / 3 | Standards-track draft |
8 or more points is Established, 5 to 7 is Gaining traction, 2 to 4 is Speculative and under 2 is Stalled. A feature is also Stalled when more vendors have said no than yes. Read the spec.
Community insights
No community insights for this feature yet.
Quotes are from public posts, checked against the original before they appear here. Suggest an insight, or ask for yours to be removed.