99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
DNS
Endpoints
2
Key Features
8
Frequently Asked Questions
4
Used by people at amazing companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI
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.
10,000
Free allowance
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Authenticate once
Send your API key with the documented header and keep requests consistent across services.
Query with examples
Start from the curl and HTTP samples, then map the parameters into your application code.
Operate and monitor
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
OpenAPI schema
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
domaintypeexpected
Example Response
domainrecord_typepropagation_percentagefully_propagatedconsistentunique_valuesresultssummarysummary.total_serverssummary.successfulsummary.failedsummary.matching_expected
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/dns/propagation
domaintypeexpected
GET
/v1/dns/servers
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Uptime
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
13 Global DNS Servers
Check propagation across major DNS providers worldwide.
Multiple Record Types
Check A, AAAA, CNAME, MX, TXT, NS, and SOA records.
Propagation Percentage
See exactly what percentage of servers have your new records.
Consistency Check
Verify all servers are returning the same values.
Expected Value Match
Optionally verify records match your expected value.
TTL Information
See Time-To-Live values for cache expiration planning.
Response Times
Monitor DNS server performance and latency.
Server Details
Know which DNS providers and locations you are checking.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/dns/propagation?domain=example.com&type=A"Example Response
{
"domain": "example.com",
"record_type": "A",
"propagation_percentage": 100,
"fully_propagated": true,
"consistent": true,
"unique_values": ["93.184.216.34"],
"results": [
{
"server": { "name": "Cloudflare US", "ip": "1.1.1.1", "location": "Global Anycast" },
"success": true,
"records": ["93.184.216.34"],
"ttl": 86400,
"response_time_ms": 12
},
{
"server": { "name": "Google US", "ip": "8.8.8.8", "location": "Global Anycast" },
"success": true,
"records": ["93.184.216.34"],
"ttl": 86400,
"response_time_ms": 15
}
],
"summary": {
"total_servers": 13,
"successful": 13,
"failed": 0,
"matching_expected": 13
}
}Frequently Asked Questions
How long does DNS propagation take?
DNS propagation typically takes 1-48 hours, depending on TTL values and caching. Our tool helps you monitor progress in real-time.
Why might DNS propagation be inconsistent?
Different DNS servers cache records for different periods based on TTL. Some servers may still have old cached values while others have updated.
Which DNS servers do you check?
We check major DNS providers including Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9), OpenDNS, and regional servers in US, Europe, and Asia Pacific.
How can I speed up DNS propagation?
Lower your TTL values before making changes, wait for old TTL to expire, then make changes. After propagation, you can increase TTL again for better caching.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
OK
200
Request successful
Bad Request
400
Invalid parameters
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Server Error
500
Internal error
Bad Gateway
502
Upstream RDAP error
Service Unavailable
503
Upstream service unavailable or temporarily rate limited.
Gateway Timeout
504
Upstream lookup timed out.
Check DNS Propagation Now