Enter a domain, URL, IP, email, or record and get a focused result without setup.
Prepare for a smooth DNS migration with a complete snapshot of your current configuration. Identifies all records, TTL settings, and potential issues before you make changes.
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Enter a domain, URL, IP, email, or record and get a focused result without setup.
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 amazing companies
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.
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
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 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
curl -s "https://domscan.net/v1/recipes/dns-migration?domain=example.com" -H "X-API-Key: $DOMSCAN_API_KEY"
{
"success": true,
"data": {
"current_records": [
"A",
"MX",
"TXT"
],
"ttl_recommendation": 300,
"migration_ready": true
},
"meta": {
"recipe_name": "dns-migration",
"credits_used": 6,
"credits_saved": 9,
"duration_ms": 734
},
"errors": []
}
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
All standard DNS record types including A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, and SRV records are documented.
Yes, the report will recommend lowering TTLs 24-48 hours before migration to ensure faster propagation of changes.
MX records, SPF, DKIM, and DMARC configurations are specially highlighted to prevent email disruption during migration.
Get API access for automation, higher limits, and custom integrations.