99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
Domain Intelligence
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
domain
Example Response
domainregisteredregistrarcreated_dateupdated_dateexpiry_dateage_daysdays_until_expirystatusnameserversdnssecevents
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/profile
domain
GET
/v1/overview
domain
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
RDAP Powered
Direct queries to authoritative RDAP servers for accurate data.
Normalized Data
Clean, structured JSON with consistent field names.
Age Calculation
Domain age in days and days until expiry calculated for you.
Registrar Info
Get the registrar name when available in RDAP data.
Nameservers
List of nameservers configured for the domain.
DNSSEC Status
Know if the domain has DNSSEC enabled.
Status Codes
EPP status codes like clientTransferProhibited.
Event Timeline
Registration, expiration, and update events with dates.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/profile?domain=example.com"Example Response
{
"domain": "example.com",
"registered": true,
"registrar": "Example Registrar Inc.",
"created_date": "1995-08-14T04:00:00Z",
"updated_date": "2024-08-14T07:01:34Z",
"expiry_date": "2025-08-13T04:00:00Z",
"age_days": 10745,
"days_until_expiry": 220,
"status": ["clientDeleteProhibited", "clientTransferProhibited"],
"nameservers": ["ns1.example.com", "ns2.example.com"],
"dnssec": true,
"events": [
{"action": "registration", "date": "1995-08-14T04:00:00Z"},
{"action": "expiration", "date": "2025-08-13T04:00:00Z"}
],
"raw_rdap_link": "https://rdap.verisign.com/com/v1/domain/example.com"
}Frequently Asked Questions
What is the difference between this and WHOIS?
This API uses RDAP, the modern replacement for WHOIS. RDAP provides structured JSON responses instead of free-form text, making it much easier to parse and use programmatically.
Why might some fields be missing?
RDAP responses vary by registry. Some registries provide more data than others. Privacy regulations like GDPR have also reduced the amount of personal data exposed.
What if a domain is not registered?
The API returns registered: false with empty arrays for status, nameservers, and events. This is useful for availability checking.
Is registrant contact information available?
Due to privacy regulations, most RDAP servers no longer expose personal registrant information. The API focuses on technical registration data.
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.
Get Domain Profile Data