dnsdoctor.dev publishes an Agentic Resource Discovery manifest at /.well-known/ard.json, declaring what an AI agent can call on this domain. Everything below is read from that file. First seen by our crawler on 06 September 2026.
| Declared resource | Type |
|---|---|
| DMARC record checkernot yet checked Validate every tag of a DMARC record with plain-English findings and a safely-capped upgrade preview. endpoint: https://dnsdoctor.dev/tools/dmarc-checkeridentifier: urn:air:dnsdoctor.dev:tool:dmarc-checkerpublished to be found for: is my DMARC record valid · check this DMARC record for mistakes tool dns email-authentication | text/html |
| DMARC record generatornot yet checked Generate a ready-to-publish DMARC record, RFC-validated in code — never an AI guess. endpoint: https://dnsdoctor.dev/tools/dmarc-generatoridentifier: urn:air:dnsdoctor.dev:tool:dmarc-generatorpublished to be found for: generate a DMARC record for my domain · what DMARC record should I publish first tool dns email-authentication | text/html |
| DNS Doctor llms.txtanswers in 224ms The site's machine-readable index: what DNS Doctor is, the free tools, the published guides, and where the HTTP and MCP contracts are documented in full. endpoint: https://dnsdoctor.dev/llms.txtidentifier: urn:air:dnsdoctor.dev:docs:llms-txtpublished to be found for: what does DNS Doctor do · where are DNS Doctor's docs for AI agents documentation llms-txt | text/markdown |
| SPF lookup counternot yet checked Count DNS lookups in an SPF record against the 10-lookup limit; nested includes counted recursively. endpoint: https://dnsdoctor.dev/tools/spf-lookup-counteridentifier: urn:air:dnsdoctor.dev:tool:spf-lookup-counterpublished to be found for: my SPF record has too many DNS lookups · count the lookups in this SPF record · how do I fix an SPF permerror tool dns email-authentication | text/html |
| DNS Doctor MCP servernot yet checked Scan, fix and verify a domain's DNS over MCP: SPF, DMARC, DKIM, mail routing, DNS health, blacklists, multi-region propagation and domain/SSL expiry. Every record is generated and validated by a deterministic engine, never a language model. endpoint: https://dnsdoctor.dev/.well-known/mcp/server-card.jsonidentifier: urn:air:dnsdoctor.dev:mcp:dns-doctorpublished to be found for: why is my email going to spam · check this domain's SPF and DMARC records · give me the DMARC record to publish for my domain · has my DNS change propagated worldwide yet dns email-authentication spf dmarc dkim scan_domain get_report build_dmarc_upgrade | application/mcp-server-card+json |
| DNS Doctor REST API v1answers in 246ms The same scanner over plain HTTP: report reads, fresh scans, the deterministic DMARC upgrade record, and the token-authed monitoring reads. endpoint: https://dnsdoctor.dev/api/v1/openapi.jsonidentifier: urn:air:dnsdoctor.dev:api:v1published to be found for: REST API to check a domain's email authentication · programmatically scan a domain for SPF and DMARC problems api dns email-authentication | application/openapi+json |
https://dnsdoctor.dev/.well-known/ard.json, this publisher's own file. Identifiers are reproduced exactly as published.
Of the resources listed, 2 have been probed for reachability.
"Answers" and "no response" describe only whether an endpoint replied when last probed:
services go down and come back, and an entry is demoted rather than removed. None of this
is a trust, quality or safety rating.
https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp.
If this is your domain, the free console shows what a registry
sees when it reads your manifest.