Dns Snapshot
Fetch one bounded public DNS snapshot for A, AAAA, CNAME, MX, NS, SOA and TXT in a single call. Forest uses a fixed public DNS-over-HTTPS resolver, distinguishes answers, NODATA, NXDOMAIN and per-type resolver errors, and marks mixed trustworthy/error outcomes as partial instead of converting resolver failure into an empty DNS result.
Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- get all common DNS records for this domain in one call
- snapshot A AAAA CNAME MX NS SOA and TXT records
- inspect a domain DNS configuration before deployment
- collect a bounded DNS inventory for a hostname
What Forest guarantees
- exactly seven fixed common DNS query types: A, AAAA, CNAME, MX, NS, SOA and TXT
- one fixed public Cloudflare DNS-over-HTTPS source; callers cannot select a resolver host, port or protocol
- bounded concurrency, one whole-operation deadline, bounded answers per type and a bounded aggregate answer count
- deterministic answer normalization, deduplication and sorting with strict target-type validation including structured SOA-field validation
- NODATA, NXDOMAIN and resolver failure remain distinct; resolver failure is never represented as a trustworthy empty answer set
- partial is explicit when at least one record type is trustworthy and at least one record type fails or conflicts with an NXDOMAIN result
Boundaries
- authoritative nameserver state, AXFR or a complete DNS zone transfer
- worldwide propagation or agreement across multiple recursive resolvers
- private, split-horizon, local-host or operating-system resolver state
- arbitrary record types or caller-selected DNS servers
Machine contract
The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.
Input example
Canonical paid endpoint
Related capabilities
- Dns Consensus — Compare one public DNS record type across a fixed bounded set of independent public DNS-over-HTTPS resolvers. Answers, TTL ranges and resolver disagreement are normalized; this is not an authoritative or worldwide DNS view.
- Dns Propagation — Check whether a DNS change has reached the configured public resolvers. Compare public DoH answers with an optional expected answer set and return complete, partial, not_observed or unknown. Scope is a fixed bounded resolver set; Forest does not claim worldwide propagation.
- Dns Changed — Detect material public DNS answer changes with a deterministic hash. TTL-only changes do not count and no arbitrary resolver or AXFR operation is exposed.
- Dns Lookup — Resolve one bounded public DNS record type into normalized answers. AXFR, resolver abuse and private-network probing are blocked; TTL and authority are null when unavailable.
- Deploy Readiness — Compose bounded DNS propagation, TLS validity and HTTP health observations into one conservative deployment-readiness state. Optional DNS change evidence is included when a previous hash is supplied; this is not a deployment guarantee or worldwide propagation claim.
- Domain Mail-preflight — MX/SPF/DMARC preflight; not mailbox verification.