Domain Expiration Checker is a simple tool for checking the expiration date and age of a domain. It returns the expiration date and age of the domain provided.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Domain Expiration response payload
}
}
About the Domain Expiration API
Domain Expiration Checker works by analyzing the domain provided and checking the expiration date. It uses advanced algorithms to check the expiration date of the domain and returns the expiration date.
What people use it for
- Domain Management
- Use the Domain Expiration Checker API to check domain expiration for domain management. Use the data to monitor domain registrations, renew domains, and maintain ownership
- SEO Optimization
- Check domain expiration by using the Domain Expiration Checker API for SEO optimization. Use the data to find expiring domains, improve rankings, and enhance visibility
- Brand Protection
- Use the Domain Expiration Checker API to check domain expiration for brand protection. Use the data to secure domains, prevent expiration, and protect brand identity
- Domain Registration
- Check domain expiration by using the Domain Expiration Checker API for domain registration. Use the data to find available domains, register new domains, and establish an online presence
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
Other ways to use Domain Expiration
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Domain Expiration API do?
How do I authenticate Domain Expiration API requests?
How much does the Domain Expiration API cost?
How fast is the Domain Expiration API?
What response formats does the Domain Expiration API support?
What HTTP method does the Domain Expiration API use?
Request parameters — GET /v1/domainexpiration
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 |
|---|---|---|---|
domainRequired | string | myspace.com | The domain to check the expiration date of domain |
curl "https://api.apiverve.com/v1/domainexpiration?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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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/domainexpiration
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.
{
"status": "ok",
"error": null,
"data": {
"domain": "myspace.com",
"expirationDate": "2029-02-23T05:00:00Z",
"daysToExpiration": 1164,
"expirationStatus": "healthy",
"createdDate": "1996-02-22T05:00:00Z",
"lastUpdatedDate": "2023-01-17T00:16:21Z",
"daysSinceLastUpdate": 1064,
"domainAgeDays": 10890,
"domainAgeYears": 29.8
}
}
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 name checked for expiration |
expirationDatePremium | string | "2029-02-23T05:00:00Z" | ISO 8601 timestamp of domain expiration date |
daysToExpiration | number | 1164 | Number of days until domain expiration |
expirationStatus | string | "healthy" | Domain health status: expired, critical, warning, healthy |
createdDatePremium | string | "1996-02-22T05:00:00Z" | ISO 8601 timestamp when domain was created |
lastUpdatedDatePremium | string | "2023-01-17T00:16:21Z" | ISO 8601 timestamp of last domain update |
daysSinceLastUpdatePremium | number | 1064 | Number of days since last domain update |
domainAgeDays | number | 10890 | Domain age in days (total lifespan) |
domainAgeYears | number | 29.8 | Domain age in years with decimal precision |
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 Expiration 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.
Call it from cURL — GET /v1/domainexpiration
No SDK to install — this is a plain HTTPS call to /v1/domainexpiration with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/domainexpiration" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/domainexpiration
Install the Node.js SDK, then call the Domain Expiration API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/domainexpirationconst res = await fetch("https://api.apiverve.com/v1/domainexpiration", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/domainexpiration
Install the Python SDK, then call the Domain Expiration API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-domainexpirationimport requests
res = requests.get(
"https://api.apiverve.com/v1/domainexpiration",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/domainexpiration
Install the C# / .NET SDK, then call the Domain Expiration API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DomainExpirationusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/domainexpiration");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/domainexpiration
No SDK to install — this is a plain HTTPS call to /v1/domainexpiration 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/domainexpiration", 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
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/domainexpiration
No SDK to install — this is a plain HTTPS call to /v1/domainexpiration with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/domainexpiration");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/domainexpiration
No SDK to install — this is a plain HTTPS call to /v1/domainexpiration with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/domainexpiration")
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.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Domain Expiration form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Domain Expiration API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Domain Expiration API.
Domain Data
- BIMI Record Validator
- DKIM Validator
- DMARC Validator
- DNS Lookup
- DNS Propagation Checker
- DNSSEC Checker
- Domain Availability
- Domain Expiration
- Fully Qualified Domain
- MX Lookup
- Reverse DNS Lookup
- SPF Validator
- SSL Certificate Checker
- Subdomain Finder
- URL Lookup
- URL Title
- URL Unshortener
- WHOIS Lookup
Related articles
All articles →
7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read 
WHOIS Data: Domain Intelligence for Business and SecurityWHOIS data reveals domain ownership, age, and infrastructure. Use it for lead qualification, research, and fraud detection.Read 
Domain Expiration Was Not On Our Alerting ChecklistThe domain expired on Saturday. By Monday, competitors bought it. Here's how to avoid this disaster.Read