WHOIS Lookup API GET

Whois Lookup is a simple tool for checking the registration of a domain name. It returns the name and contact information of the domain owner, the domain registrar, and more.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/whoislookup

Verification

Format

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

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // WHOIS Lookup response payload
  }
}

About the WHOIS Lookup API

Whois Lookup works by querying the WHOIS database to retrieve the registration data of a domain name. It returns the domain owner's name, contact information, domain registrar, and more in a structured format.

What people use it for

Domain Management: Use the Whois Lookup API to check domain registration data for domain management. Use the data to verify ownership, update contact information, and renew domains
Cybersecurity: Enhance cybersecurity by using the Whois Lookup API to check domain registration data. Use the data to identify suspicious domains, prevent fraud, and protect against cyber threats
Brand Protection: Protect your brand by using the Whois Lookup API to check domain registration data. Use the data to monitor domain registrations, detect trademark infringements, and enforce brand rights
Legal Compliance: Ensure legal compliance by using the Whois Lookup API to check domain registration data. Use the data to investigate domain disputes, resolve ownership issues, and comply with regulations

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 WHOIS Lookup

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 WHOIS Lookup API.

Read the docs →

What does the WHOIS Lookup API do?

Whois Lookup is a simple tool for checking the registration of a domain name. It returns the name and contact information of the domain owner, the domain registrar, and more.

How do I authenticate WHOIS Lookup API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the WHOIS Lookup API cost?

Each call spends 8 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the WHOIS Lookup API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the WHOIS Lookup API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the WHOIS Lookup API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/whoislookup

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 name for which you want to get the registration data (e.g., myspace.com) domain

Example request

1
2

curl "https://api.apiverve.com/v1/whoislookup?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/whoislookup

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": {
    "domainName": "MYSPACE.COM",
    "registryDomainID": "3877095_DOMAIN_COM-VRSN",
    "createdDate": "1996-02-22T05:00:00Z",
    "expiryDate": "2029-02-23T05:00:00Z",
    "updatedDate": "2023-01-17T00:16:21Z",
    "domainStatus": [
      "client delete prohibited https://icann.org/epp#client delete prohibited",
      "client renew prohibited https://icann.org/epp#client renew prohibited",
      "client transfer prohibited https://icann.org/epp#client transfer prohibited",
      "client update prohibited https://icann.org/epp#client update prohibited"
    ],
    "dNSSEC": "unsigned",
    "registrar": "GoDaddy.com, LLC",
    "registrarIANAID": "146",
    "registrarURL": "http://www.godaddy.com",
    "registrarAbuseContactEmail": "abuse@godaddy.com",
    "registrarAbuseContactPhone": "tel:480-624-2505",
    "nameServers": [
      "ns-cloud-a2.googledomains.com",
      "ns-cloud-a3.googledomains.com",
      "ns-cloud-a4.googledomains.com",
      "ns-cloud-a1.googledomains.com"
    ],
    "domain": "myspace.com",
    "fetchedAtUTC": "2025-12-17T01:54:05.069Z",
    "tld": "com",
    "status": "active",
    "domainAgeDays": 11094,
    "domainAgeYears": 30.4,
    "isRecentlyRegistered": false,
    "trustScore": 93,
    "trustLevel": "high"
  }
}

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
`domainName`	string	`"MYSPACE.COM"`	The domain name in uppercase format
`registryDomainID`Premium	string	`"3877095_DOMAIN_COM-VRSN"`	Unique registry identifier for the domain
`createdDate`	string	`"1996-02-22T05:00:00Z"`	Domain creation date in ISO 8601 format
`expiryDate`	string	`"2029-02-23T05:00:00Z"`	Domain expiration date in ISO 8601 format
`updatedDate`	string	`"2023-01-17T00:16:21Z"`	Domain last updated date in ISO 8601 format
`domainStatus`	array	`[client delete prohibited https://icann.org/epp#client delete prohibited, ...]`	Array of domain status flags with EPP codes
`dNSSEC`Premium	string	`"unsigned"`	DNSSEC status (signed or unsigned)
`registrar`	string	`"GoDaddy.com, LLC"`	Domain registrar company name
`registrarIANAID`Premium	string	`"146"`	Registrar's IANA ID number
`registrarURL`	string	`"http://www.godaddy.com"`	Registrar's website URL
`registrarAbuseContactEmail`Premium	string	`"abuse@godaddy.com"`	Registrar abuse contact email address
`registrarAbuseContactPhone`Premium	string	`"tel:480-624-2505"`	Registrar abuse contact phone number
`nameServers`	array	`[ns-cloud-a2.googledomains.com, ...]`	Array of authoritative nameserver hostnames
`domain`	string	`"myspace.com"`	Domain name in lowercase format
`fetchedAtUTC`Premium	string	`"2025-12-17T01:54:05.069Z"`	Timestamp when WHOIS data was retrieved
`tld`	string	`"com"`	Top-level domain extension
`status`	string	`"active"`	Current domain registration status
`domainAgeDays`	number	`11094`	Age of the domain in days, derived from the creation date
`domainAgeYears`	number	`30.4`	Age of the domain in years (one decimal), derived from the creation date
`isRecentlyRegistered`Premium	boolean	`false`	Whether the domain was registered within the last 90 days — a common fraud/phishing signal
`trustScore`Premium	number	`93`	0-100 trust score derived from domain age, registration recency, expiry runway and DNSSEC
`trustLevel`Premium	string	`"high"`	Categorical trust level (low, medium, high) derived from the trust score

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 — 8 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	WHOIS Lookup calls	Per 1,000 calls
Free	Free	200	25	Free
Starter	$29.99	200,000	25,000	$1.20
Pro	$99.99	1,000,000	125,000	$0.80
Mega	$299.99	4,000,000	500,000	$0.60

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/whoislookup

No SDK to install — this is a plain HTTPS call to /v1/whoislookup 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/whoislookup" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/whoislookup-apiSource, issues and the examples this page is built from.ReferenceWHOIS Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/whoislookupnpm apiverve-whoislookupPyPI APIVerve.API.WHOISLookupNuGet

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/whoislookup

Install the Node.js SDK, then call the WHOIS Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/whoislookup

Node.js

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

Resources

npm@apiverve/whoislookupThe published Node.js client, versioned and signed.GitHubapiverve/whoislookup-apiSource, issues and the examples this page is built from.ReferenceWHOIS Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-whoislookupPyPI APIVerve.API.WHOISLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/whoislookup

Install the Python SDK, then call the WHOIS Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-whoislookup

Python

import requests

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

Resources

PyPIapiverve-whoislookupThe published Python client, versioned and signed.GitHubapiverve/whoislookup-apiSource, issues and the examples this page is built from.ReferenceWHOIS Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/whoislookupnpm APIVerve.API.WHOISLookupNuGet

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/whoislookup

Install the C# / .NET SDK, then call the WHOIS Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.WHOISLookup

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/whoislookup");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.WHOISLookupThe published C# / .NET client, versioned and signed.GitHubapiverve/whoislookup-apiSource, issues and the examples this page is built from.ReferenceWHOIS Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/whoislookupnpm apiverve-whoislookupPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/whoislookup

No SDK to install — this is a plain HTTPS call to /v1/whoislookup 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/whoislookup", 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

@apiverve/whoislookupnpm apiverve-whoislookupPyPI APIVerve.API.WHOISLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/whoislookup

No SDK to install — this is a plain HTTPS call to /v1/whoislookup 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/whoislookup");
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

@apiverve/whoislookupnpm apiverve-whoislookupPyPI APIVerve.API.WHOISLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/whoislookup

No SDK to install — this is a plain HTTPS call to /v1/whoislookup 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/whoislookup")
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

Also published for

@apiverve/whoislookupnpm apiverve-whoislookupPyPI APIVerve.API.WHOISLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

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

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 Lookup API GET

Try it — live request, no key required

About the WHOIS Lookup API

What people use it for

Ways to call it

Other ways to use WHOIS Lookup

Questions.

Request parameters — GET /v1/whoislookup

Required

Authentication

Response — GET /v1/whoislookup

Response fields

Response headers

Errors

What a call costs — 8 credits per call

Call it from cURL — GET /v1/whoislookup

Resources

Also published for

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

Resources

Also published for

Call it from Python — GET /v1/whoislookup

Resources

Also published for

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

Resources

Also published for

Call it from Go — GET /v1/whoislookup

Resources

Also published for

Call it from PHP — GET /v1/whoislookup

Resources

Also published for

Call it from Ruby — GET /v1/whoislookup

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — WHOIS Lookup API

Domain Data

Related articles

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

Explore the catalog