Every Whois snapshot for a domain, across years.
Pass a domain. Get back every Whois snapshot Deepinfo has observed, ordered by snapshot date. Useful for ownership-trail reconstruction and registrar-transfer analysis.
Multi-snapshot Whois state, for one domain.
The Whois History API returns every Whois snapshot Deepinfo has on file for a given domain. Each snapshot is the parsed Whois record at one point in observation time, including registrar, registrant block, dates, name servers, and status codes.
Use this when one domain matters and the question is about how it changed: when did the registrant organization change, when did the name servers move, when was the most recent registrar transfer. The API returns an array of snapshots in chronological order; deltas are obvious from the field-by-field comparison.
For multi-domain or corpus-scale historical analysis, use the Historical Whois Records bulk feed instead.
One endpoint, one required parameter.
Endpoint:
GET https://api.deepinfo.com/v1/analyze/history/whois?domain={domain}
Parameters:
Authentication is by API token in the request header. See docs.deepinfo.com for the full request reference.
See what the API returns.
Real response structure for the Every Whois snapshot for a domain, across years endpoint. Field coverage may vary based on query parameters and data availability.
[
{
"domain_name": "acme.com",
"snapshot_date": "2018-03-12T08:14:00Z",
"parsed": {
"registrar": "GoDaddy.com, LLC",
"registrant": {"organization": "Acme Holdings Inc.", "country": "US"},
"name_servers": ["ns1.acme.com", "ns2.acme.com"],
"create_date": "2002-08-14T00:00:00Z",
"expiry_date": "2024-08-14T00:00:00Z"
}
},
{
"domain_name": "acme.com",
"snapshot_date": "2021-04-08T16:22:00Z",
"parsed": {
"registrar": "MarkMonitor Inc.",
"registrant": {"organization": "Acme Holdings Inc.", "country": "US"},
"name_servers": ["ns1-cloud.acme.com", "ns2-cloud.acme.com"],
"create_date": "2002-08-14T00:00:00Z",
"expiry_date": "2026-08-14T00:00:00Z"
}
}
]
Sample response shown. Real responses depend on query parameters, data availability, and API version. Talk to us for full schema documentation.
Workflows this API plugs into directly.
Incident Investigation and Response
Reconstruct ownership state at the moment of the incident, not just current state.
Read the use caseThreat Hunting
Cluster adversary infrastructure by historical registrant or name-server reuse.
Read the use caseMergers and Acquisitions Due Diligence
Validate ownership claims against the historical record. Surface gaps where the data room diverges from observed Whois.
Read the use case“Ownership-chain reconstruction for fraud cases now runs against years of Whois snapshots in one query. Registrar-transfer analysis that used to require subpoenas to multiple registrars surfaces directly in the data.”
Other history APIs.
Pull the full Whois history, for any domain.
We'll set up token access and walk through how teams plug this into IR and diligence workflows.