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.
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.001 / callPOST /dns/changedx402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- has this DNS record changed
- should I refresh the saved DNS result
- what changed in DNS answers
What Forest guarantees
- bounded normalized public-source lookup
Boundaries
- provider-specific guarantees
- unpublished facts
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
{
"name": "example.com",
"type": "A",
"previous_hash": "sha256:0000000000000000000000000000000000000000000000000000000000000000"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/dns/changed
Related capabilities
- 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.
- 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 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.
- Commerce Availability — Resolve public product or listing availability with explicit normalized states. It reports only provider evidence and never infers inventory, reserves items or places an order.
- Commerce Buyability — Report whether a public item appears buyable with explicit blockers such as out-of-stock or unknown. This is a preflight only: it never signs in, buys, creates an order or guarantees checkout.