DNS · Free

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.

Resolver comparison results

API Endpoint

GET /v1/dns/propagation?domain=example.com&type=A

Interactive intelligence tool

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.

Start with the live form

Enter a domain, URL, IP, email, or record and get a focused result without setup.

Review decision-ready signals

Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.

Automate the winning workflow

Use the request and response examples to turn a one-off check into an API call or recipe.

Used by people at amazing companies

What this tool helps you decide

Each page is shaped around a practical operational question, not just a raw lookup.

Signal

See the current DNS, registration, security, pricing, or reputation evidence.

Context

Compare the result with related checks so the next move is easier to trust.

Action

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.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign Up for Free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example Request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Multi-resolver comparison

Query configured public recursive resolvers and compare the answers they return.

Differences made clear

Spot matching values, cached differences, missing records, and lookup errors.

Transparent coverage

See exactly which resolvers were checked without treating them as geographic test locations.

Example Request

Example Request http

GET /v1/dns/propagation?domain=example.com&type=A

Example Response

Example Response json

{
  "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 from the same API surface

The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.

Open API docs All Tools

Frequently Asked Questions

Does this show DNS propagation worldwide?

No. It compares answers from the configured public recursive resolvers. It does not measure every network, country, or geographic location.

Why do DNS resolvers return different answers?

Resolvers may hold records cached at different times. TTLs, recent DNS changes, stale data, and temporary lookup failures can all produce differences.

How long does DNS propagation take?

There is no single fixed time. Recursive resolvers refresh records according to DNS TTLs and their cache behavior, so results can converge at different times.

Support