Enter a domain, URL, IP, email, or record and get a focused result without setup.
DNS Propagation Checker
Choose a DNS record type and compare current answers across configured public recursive resolvers. This is a resolver comparison, not a worldwide or geographic measurement.
GET /v1/dns/propagation?domain=example.com&type=A
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at these companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Check live service health and documented failure responses before you integrate.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 1,000 free credits every month. Need more? Pick a monthly plan or buy a one-time pack.
Key Features
Query configured public recursive resolvers and compare the answers they return.
Spot matching values, cached differences, missing records, and lookup errors.
See exactly which resolvers were checked without treating them as geographic test locations.
Example request
GET /v1/dns/propagation?domain=example.com&type=A
Example response
{
"domain": "example.com",
"record_type": "A",
"measurement_scope": "configured_recursive_resolvers",
"propagation_percentage": 100,
"consistent": true,
"propagation_summary": {
"resolver_count": 4,
"successful_count": 4,
"unique_value_count": 1
}
}
Built on the same API
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently asked questions
No. It compares answers from the configured public recursive resolvers. It does not measure every network, country, or geographic location.
Resolvers may return different answers because their caches refreshed at different times. For example, one may still return an old A record while another has the updated address, and a cached NXDOMAIN can persist for a while after a name is created. Timeouts or failed queries are uncertain results, not proof a record is absent. This check compares only its configured recursive resolvers, not every network or location.
There is no fixed global time. Resolvers refresh cached answers as their TTLs expire, and negative answers can be cached too, so different resolvers may show different results for a while. This checker reports responses from its configured resolvers at check time; it cannot guarantee when every network will see the change.

