Does this API perform WHOIS lookups inline?
No. Domain Lookup returns WHOIS link metadata (whois.url and whois.available) so you can fetch full registration data from the WHOIS API when needed.
Domain Lookup API
TLD category
DNS flags
Batch: 50
What kind of domain is this?Category, region, and DNS readiness.
Enrich domains with TLD classification, regional metadata, DNS infrastructure checks, and WHOIS link references — without parsing registration data inline. Batch up to 50 domains per POST.
tld · categorydnsCheck · A/MX/TXTwhois · link metadataPOST · enrichment
Why Domain Lookup API
Domain metadata, structured.
TLD Classification
Extract TLD and map to category labels like commercial, organization, or government.
Regional Metadata
Region associations for ccTLDs and global TLDs — useful for content filtering and compliance.
DNS Presence Flags
Real-time checks for A, AAAA, MX, and TXT record availability via dnsCheck booleans.
WHOIS Link Metadata
Each result includes a whois.url reference to fetch full registration data when you need it.
Batch up to 50
Pass domain as a string or array. Invalid entries return per-item errors without failing the batch.
No Inline WHOIS
Core enrichment avoids registrant PII — ideal for onboarding flows and risk scoring without WHOIS parsing.
/api/v1/domain-lookup
Endpoints, at a glance.
POST-only enrichment. GET routes are for health and metrics — not domain lookups.
POST/domain-lookup
Domain enrichment
Send `domain` as a string (single) or array (batch ≤50). Returns TLD metadata, dnsCheck flags, and WHOIS link references.
PRIMARY
GET/domain-lookup/health
Service health
Service status and uptime.
GET/domain-lookup/metrics
Prometheus metrics
Enrichment counters and processing duration metrics.
| Parameter | Type | Required | Description |
|---|---|---|---|
| domain | string | array | yes | Single domain (e.g. "stripe.com") or array of up to 50 domains in JSON body. |
Requests & responses.
POST a single domain for enrichment, or batch an array — invalid items error per row.
Single domain
TLD metadata, DNS flags, and WHOIS link.
POST https://datpaq.com/api/v1/domain-lookup
Content-Type: application/json
{
"domain": "stripe.com"
}Batch (≤50)
Per-item validation errors without failing the call.
POST https://datpaq.com/api/v1/domain-lookup
Content-Type: application/json
{
"domain": ["stripe.com", "invalid-domain-format"]
}Health
https://datpaq.com/api/v1/domain-lookup/health
Metrics
https://datpaq.com/api/v1/domain-lookup/metrics
Error reference
Predictable errors, always structured.
Batch requests return per-item errors on invalid domains while successful items still enrich.
400Missing Domain
Required domain field not provided in the JSON body.
400Invalid Domain Format
Per-item error for malformed domains. Returned inline in batch responses as { "error": "Invalid domain format" }.
400Batch Size Exceeded
More than 50 domains in a single batch. Split into smaller requests.
401Unauthorized
API key missing or invalid. Pass as x-api-key header or api_key query parameter.
500Enrichment Failure
DNS check or internal processing error. correlationId included for support.
FAQ
API questions developers ask first.
Can I look up domains with GET?
Domain enrichment is POST-only. GET routes on this service return health and status information, not domain metadata.
How do I authenticate with this API?
Create an API key in your Datpaq dashboard and send it with each request as a bearer token in the Authorization header.
Is there a free tier?
Yes. Datpaq APIs include a free tier for building, testing, and small production workloads before you move to a paid plan.
What format do requests and responses use?
Datpaq APIs use REST over HTTPS and return JSON by default. Endpoint docs show the supported methods, query parameters, request bodies, and response fields.
Where can I see limits and errors?
Each API documents rate limits, validation rules, and error responses in the landing page and API docs so integrations can retry and fail cleanly.
Domain enrichment, without WHOIS parsing.
Classify domains, inspect DNS readiness, and attach WHOIS references — built for onboarding flows and CRM enrichment.