Overview
Domain Age reads the domain's registration record from the registry over RDAP, falling back to WHOIS, and measures the time since the creation date. The flag for newly registered domains is set below 30 days, the window in which most phishing and spam domains are used.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/domainage?domain=myspace.com" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/domainage?domain=myspace.com', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/domainage?domain=myspace.com",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/domainage?domain=myspace.com", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
domainRequired | string | The domain to check the age of domain |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"domain": "myspace.com",
"createdDate": "1996-02-22T05:00:00Z",
"domainAgeDays": 11193,
"domainAgeMonths": 367,
"domainAgeYears": 30.6,
"domainAgeText": "30 years, 7 months",
"ageCategory": "veteran",
"isNewlyRegistered": false,
"expirationDate": "2029-02-23T05:00:00Z",
"lastUpdatedDate": "2023-01-17T00:16:21Z",
"daysSinceLastUpdate": 1367
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
domain | string | "myspace.com" | The domain that was checked |
createdDate | string | "1996-02-22T05:00:00Z" | ISO 8601 timestamp when the domain was first registered |
domainAgeDays | number | 11193 | Domain age in whole days |
domainAgeMonths | number | 367 | Domain age in whole months |
domainAgeYears | number | 30.6 | Domain age in years, to one decimal place |
domainAgeText | string | "30 years, 7 months" | Readable age, such as "29 years, 7 months" |
ageCategory | string | "veteran" | Age bracket: new (under 30 days), young (under 1 year), established (under 5 years), mature (under 10 years) or veteran |
isNewlyRegistered | boolean | false | True when the domain is under 30 days old |
expirationDatePremium | string | "2029-02-23T05:00:00Z" | ISO 8601 timestamp when the current registration expires |
lastUpdatedDatePremium | string | "2023-01-17T00:16:21Z" | ISO 8601 timestamp of the last change to the registration record |
daysSinceLastUpdatePremium | number | 1367 | Days since the registration record last changed |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Fraud and Phishing Scoring
- Score sign-ups, payments and inbound email by the age of the sender's domain, and step up checks when isNewlyRegistered is true.
- Lead Qualification
- Rank inbound leads by how established their company domain is, so a 15-year-old domain gets routed ahead of one registered last week.
- Link and Content Moderation
- Hold links to domains younger than 30 days for review before they appear in comments, chats or user profiles.
- SEO and Domain Investing
- Check the age of expired or for-sale domains before buying, since older domains often carry more backlink history.
Other ways to use Domain Age
Set up Domain Age on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Domain Data: