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.
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.
$0.003 / callPOST /dns/consensusx402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- do public DNS resolvers agree on this record
- compare DNS answers across resolvers
- check DNS resolver consensus before deployment
What Forest guarantees
- bounded fixed public DoH resolver comparison
- normalized answer-set agreement classification
Boundaries
- worldwide DNS propagation
- authoritative nameserver state
- geographic resolver coverage
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
{
"hostname": "example.com",
"record_type": "A"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/dns/consensus
Related capabilities
- 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 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.
- 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.
- Api Readiness — Compose bounded API discovery with one deterministic OpenAPI or Swagger preflight into a concise agent-readiness state. The check does not authenticate, call discovered API operations, or prove business-level API correctness.