99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
DNS
Endpoints
3
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
domaintypefromto
Example Response
domainrecord_typerecordsstatusdnssec_validatedquery_time_mschecked_atwarningsmetameta.served_bymeta.worker_version
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/dns
domaintype
GET
/v1/dns/all
domain
GET
/v1/dns/history
domaintypefromto
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
All Record Types
Query A, AAAA, MX, NS, TXT, CAA, SOA, CNAME, PTR, SRV records.
Fast Responses
Powered by Cloudflare DNS-over-HTTPS for low latency.
Bulk Queries
Use /v1/dns/all to fetch all common record types for one domain, or /v1/dns/bulk to query one record type across up to 25 domains.
DNSSEC Validation
Know if responses are DNSSEC validated.
TTL Information
Get TTL values for proper caching strategies.
JSON Responses
Structured JSON output ready for any application.
Generous Limits
Start free with 10,000 credits per month.
Free to Start
Sign up free and start with 10,000 credits/month.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/dns?domain=google.com&type=TXT"Example Response
{
"domain": "google.com",
"record_type": "TXT",
"records": [
{
"type": "TXT",
"name": "google.com",
"data": "v=spf1 include:_spf.google.com ~all",
"ttl": 300,
"classification": "spf"
},
{
"type": "TXT",
"name": "google.com",
"data": "google-site-verification=abc123",
"ttl": 300,
"classification": "verification"
}
],
"status": "success",
"dnssec_validated": false,
"query_time_ms": 37,
"checked_at": "2026-04-18T21:00:00Z",
"warnings": [
{
"code": "TXT_MULTIPLE_RESPONSES",
"message": "Domain publishes multiple TXT records; use classification to isolate the security ones.",
"severity": "info"
}
],
"meta": {
"served_by": "pop=unknown country=unknown",
"worker_version": "2.0.0"
}
}Frequently Asked Questions
What DNS record types are supported?
We support A, AAAA, NS, MX, TXT, CAA, SOA, CNAME, PTR, and SRV record types. Use the type parameter to specify which record type to query.
How do I query all record types at once?
Use /v1/dns/all when you want all common record types for one domain. Use /v1/dns/bulk when you want the same record type across multiple domains in one request.
Is DNSSEC validation supported?
Yes, the response includes a dnssec_validated field indicating whether the response was validated via DNSSEC.
What does the status field mean?
Status can be "success" (records found), "nxdomain" (domain does not exist), or "error" (query failed).
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.
Start Querying DNS Records