Domain Age
Registration date, exact age, expiry and registrar, straight from the registry.
curl -X POST https://api.1lookup.dev/v1/domain-age \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"domain":"example.com"}'{
"success": true,
"data": {
"domain": "example.com",
"registered": true,
"created_at": "2014-03-18T16:22:07Z",
"updated_at": "2026-02-20T09:11:43Z",
"expires_at": "2027-03-18T16:22:07Z",
"age": {
"years": 12,
"months": 8,
"days": 1,
"total_days": 4629
},
"registrar": {
"name": "Example Registrar, Inc.",
"url": "https://registrar.example"
},
"status": [
"clientTransferProhibited",
"clientDeleteProhibited"
],
"nameservers": [
"ns1.dnshost.example",
"ns2.dnshost.example"
],
"source": "rdap"
},
"meta": {
"credits_used": 2,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
domainstring<domain>requiredDomain. Example: example.com
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.created_atstringWhen the domain was registered, as recorded by the registry.
data.age.total_daysnumberAge in days, with a years, months and days breakdown beside it.
data.expires_atstringWhen the current registration term ends.
data.updated_atstringThe last time the registry record changed, for example after a renewal or transfer.
data.registrar.namestringThe company the domain is registered through.
data.statusarrayRegistry status values such as clientTransferProhibited or pendingDelete.
data.nameserversarrayThe nameservers listed on the registry record.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
2 credits. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases