GET · DNS zones & records
Check a DNS record's propagation across public resolvers
Check a DNS record's propagation across public resolvers
/api/v1/dns/propagation
Description
Asks every resolver in the panel for name/type (default A) and returns one resolvers[] row each — {resolver, status, answers[], matchesExpected?} — plus consistent and, when an expected value is given, propagated. For a single quick lookup use dns_lookup; for the authoritative records of a zone you own use list_dns_records.
Query parameters
| Name | Type | Description |
|---|---|---|
name
required
|
string |
The hostname to check, e.g. example.com or www.example.com.
|
type
|
enum |
Which record type to check. Defaults to A. One of A, AAAA, CNAME, MX, TXT, NS, CAA, SRV, SOA.
|
expected
|
string |
The value you expect (e.g. the new IP after a change). When given, each resolver reports matchesExpected and the response carries an overall propagated.
|
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.