Domain Mail-preflight
MX/SPF/DMARC preflight; not mailbox verification.
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.002 / callPOST /domain/mail-preflightx402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- is email configured for this domain
- check SPF DKIM and DMARC records
- which mail hosts serve this domain
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
{
"domain": "example.com"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/domain/mail-preflight
Related capabilities
- Domain Preflight — Resolve a bare public domain into operational registration, DNS, HTTPS/TLS and mail-policy state using IANA-routed RDAP, DNS, MX/TXT/SPF/DMARC and a bounded TLS probe. No registrant personal data, vulnerability scanning, mailbox existence or deliverability claim. Provider uncertainty is explicit.
- Domain Registration-state — Read public RDAP registration state for a domain: registrar or managing entity when published, registration and expiry dates, and registry status codes. This is a registration/ownership-lifecycle lookup only; it does not perform DNS, mail, TLS or website checks.
- 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.
- 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.
- 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.