99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
OSINT
Endpoints
1
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
query
Example Response
querytypestatusrdaprdap.objectClassNamerdap.handlerdap.namerdap.startAddressrdap.endAddressrdap.ipVersion
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/rdap
query
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
Native RDAP Support
Direct queries to RDAP servers, not scraped WHOIS data.
Structured JSON
Machine-readable responses following RDAP standards.
Registry Status Codes
Get EPP status codes like clientTransferProhibited.
Event Data
Registration, expiration, and last update timestamps.
IANA Bootstrap
Automatic routing to correct RDAP servers via IANA bootstrap.
Availability Detection
Accurately determine if domains are available for registration.
Smart Caching
Intelligent cache with configurable TTLs for optimal performance.
Error Handling
Graceful fallbacks when RDAP servers are temporarily unavailable.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/rdap?query=example.com"curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/rdap?type=ip&query=8.8.8.8"curl -G -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/rdap" \
--data "type=ip" \
--data-urlencode "query=2001:4860:4860::8888/128"curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/rdap?type=autnum&query=AS174"Example Response
{
"query": "8.8.8.8",
"type": "ip",
"status": "found",
"rdap": {
"objectClassName": "ip network",
"handle": "NET-8-8-8-0-2",
"name": "LVLT-GOGL-8-8-8",
"startAddress": "8.8.8.0",
"endAddress": "8.8.8.255",
"ipVersion": "v4"
}
}Frequently Asked Questions
What is RDAP?
RDAP (Registration Data Access Protocol) is the modern replacement for WHOIS. It provides structured JSON responses, better internationalization support, and is the IETF standard for domain registration data.
How is RDAP different from WHOIS?
RDAP returns structured JSON instead of free-form text, supports HTTPS for security, handles international characters properly, and provides standardized response formats across all registries.
Do you cache RDAP responses?
Yes, we implement intelligent caching to provide fast responses and reduce load on RDAP servers. Use skip_cache=1 to force a fresh lookup when needed.
Which RDAP servers do you query?
We use the IANA RDAP Bootstrap to automatically route queries to the correct authoritative RDAP server for each TLD.
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.
Access RDAP Data Now