Domain Age API

GET

Find out how old any domain is, down to the day.

Domain Age returns when a domain was first registered and how old it is in days, months and years, with a readable age, an age bracket and a newly-registered flag. Paid plans add the expiration date and the last registry update.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/domainage?domain=myspace.com

Query parameters

domainstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "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
  }
}

About the Domain Age API

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.

What people use it for

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.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Domain Age

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Domain Age API.

Read the docs →

How many domain age checks does the Starter plan cover?

Starter covers 20,000 domain age checks each month. At 10 credits per request, that works out to $1.50 per 1,000 lookups, or about $0.0015 per call. The Free plan includes 20 checks per month for testing.

What does the Free plan return?

The Free plan returns the creation date, the age in days, months and years, the readable age, the age bracket and the newly registered flag. Paid plans add the expiration date, the last update date and the days since that update.

Where does the creation date come from?

It is read live from the domain's registry over RDAP, with WHOIS as a fallback, at the time of your request. It is not taken from a pre-scraped snapshot.

What happens when a registry doesn't publish a creation date?

Some country-code registries do not publish registration dates. For those domains the API returns a 404 with a clear message instead of guessing an age.

How are the age brackets defined?

ageCategory is new under 30 days, young under 1 year, established under 5 years, mature under 10 years and veteran at 10 years or more. isNewlyRegistered is true for domains under 30 days old.

Request parameters — GET /v1/domainage

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`domain`Required	string	`myspace.com`	The domain to check the age of domain

Example request

1
2

curl "https://api.apiverve.com/v1/domainage?domain=myspace.com" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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.

Response — GET /v1/domainage

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "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
`expirationDate`Premium	string	`"2029-02-23T05:00:00Z"`	ISO 8601 timestamp when the current registration expires
`lastUpdatedDate`Premium	string	`"2023-01-17T00:16:21Z"`	ISO 8601 timestamp of the last change to the registration record
`daysSinceLastUpdate`Premium	number	`1367`	Days since the registration record last changed

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Domain Age calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/domainage

No SDK to install — this is a plain HTTPS call to /v1/domainage with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/domainage" \
  -H "x-api-key: YOUR_API_KEY"

Resources

ReferenceDomain Age API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Call it from Node.js — GET /v1/domainage

No SDK to install — this is a plain HTTPS call to /v1/domainage with your key in the x-api-key header. Swap in a real key and it runs as-is.

Node.js

const res = await fetch("https://api.apiverve.com/v1/domainage", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

ReferenceDomain Age API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Call it from Python — GET /v1/domainage

No SDK to install — this is a plain HTTPS call to /v1/domainage with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/domainage",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

ReferenceDomain Age API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Call it from C# / .NET — GET /v1/domainage

No SDK to install — this is a plain HTTPS call to /v1/domainage with your key in the x-api-key header. Swap in a real key and it runs as-is.

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/domainage");
Console.WriteLine(json);

Resources

ReferenceDomain Age API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Call it from Go — GET /v1/domainage

No SDK to install — this is a plain HTTPS call to /v1/domainage with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/domainage", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

ReferenceDomain Age API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Call it from PHP — GET /v1/domainage

No SDK to install — this is a plain HTTPS call to /v1/domainage with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/domainage");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

ReferenceDomain Age API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Call it from Ruby — GET /v1/domainage

No SDK to install — this is a plain HTTPS call to /v1/domainage with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/domainage")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

ReferenceDomain Age API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Domain Age API

Try it — live request, no key required

About the Domain Age API

What people use it for

Ways to call it

Other ways to use Domain Age

Questions.

Request parameters — GET /v1/domainage

Required

Authentication

Response — GET /v1/domainage

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/domainage

Resources

Call it from Node.js — GET /v1/domainage

Resources

Call it from Python — GET /v1/domainage

Resources

Call it from C# / .NET — GET /v1/domainage

Resources

Call it from Go — GET /v1/domainage

Resources

Call it from PHP — GET /v1/domainage

Resources

Call it from Ruby — GET /v1/domainage

Resources

Zero-code embed — one snippet, no backend

Changelog — Domain Age API

Domain Data

Ready to build with Domain Age? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog