Up to 10 years of Whois history, in bulk.
Up to 10 years of historical Whois snapshots. 100B+ records covering registrar, registrant, dates, name servers, and status codes across every monitored TLD.
Multi-snapshot Whois state, at internet scale.
The Historical Whois Records Feed is the bulk version of the Whois History API. Where the API answers single-domain history queries, the feed delivers the full corpus for analytical workloads, large-scale enrichment, and offline pivot graphs.
Each record is one Whois snapshot of one domain at one point in time. The corpus exceeds 100B records spanning up to 10 years of observation. Coverage includes registrar, registrant block, creation date, expiry date, last update timestamp, name servers, EPP status codes, and the raw Whois output where preservation is permitted.
Use this feed for ownership-trail analysis, reverse-Whois at corpus scale, infrastructure clustering across long time windows, or any research workflow that benefits from offline indexing of the full Whois history rather than per-domain calls.
Historical bulk export, delivered on demand.
Available as a one-time bulk export or as periodic refreshes against the latest cumulative snapshot. Authenticate with an API token scoped to the feed.
Delivery
Historical bulk export. Single API call returns metadata plus a signed download_url for the full or scoped corpus. S3 and SFTP for large transfers.
Format
JSON or CSV. The dataset is partitioned by TLD and observation year for efficient downstream processing.
Refresh cadence
On-demand bulk export; periodic refresh available. The full corpus reflects up to 10 years of observation.
Authentication
API token in the request header. Per-feed scoping. Reference at docs.deepinfo.com.
What you actually get.
The API response, with the metadata for the latest cumulative snapshot:
{
"download_url": "https://feeds.deepinfo.com/historical-whois/2026-05-02/historical-whois.json.gz?...",
"file_format": "json",
"file_size": 2148374891234,
"file_update_time": "2026-05-02T03:14:27Z",
"line_count": 102438191847,
"coverage_years": 10
}A few representative records from the JSON-formatted file at download_url:
{"domain":"acme.com","snapshot_date":"2018-03-12","registrar":"GoDaddy.com, LLC","registrant_org":"Acme Holdings Inc.","name_servers":["ns1.acme.com","ns2.acme.com"],"create_date":"2002-08-14","expiry_date":"2024-08-14"}
{"domain":"acme.com","snapshot_date":"2021-04-08","registrar":"MarkMonitor Inc.","registrant_org":"Acme Holdings Inc.","name_servers":["ns1-cloud.acme.com","ns2-cloud.acme.com"],"create_date":"2002-08-14","expiry_date":"2026-08-14"}
{"domain":"deepinfo.com","snapshot_date":"2018-06-13","registrar":"GoDaddy.com, LLC","registrant_org":"Deepinfo","name_servers":["ns-cloud-a1.googledomains.com","ns-cloud-a2.googledomains.com"],"create_date":"2018-06-12","expiry_date":"2019-06-12"}Workflows this feed powers directly.
Incident Investigation and Response
Pivot through ownership history at corpus scale. Reconstruct full registrar and registrant trails for any domain across years of state.
Read the use caseThreat Hunting
Run hypotheses against the full Whois corpus offline. Cluster infrastructure by registrant, registrar, or name-server fingerprints across long windows.
Read the use caseMergers and Acquisitions Due Diligence
Validate ownership claims against the historical record. Surface gaps where the data room's narrative diverges from observed Whois.
Read the use case“Ownership trail analysis routinely needs five-plus years of Whois snapshots. The 10-year window in one feed beats hand-stitching from multiple historical archives, and the 100B-record depth covers gTLDs and ccTLDs alike.”
Other historical feeds.
Historical DNS at 100B+ records.
Historical DNS record snapshots including A, AAAA, MX, NS, TXT, CNAME, and SOA. 100B+ records across the long tail of internet observation.
See feed DATA FEEDHistorical SSL/TLS at 20B+ records.
Historical SSL/TLS certificate data across domains and IP addresses. 20B+ records sourced from certificate transparency logs and active TLS scanning.
See feedGet the full Whois history, in bulk.
Most teams scope to a TLD subset or a year range first. We'll set up token access and discuss partitioning that fits your workload.