Daily Updated Domain Names Feed
Track the Domains Whose Registration Record Changed in the Last Day.
The Daily Updated Domain Names Feed lists the domains whose registration record was updated in the last day, so your pipeline can check the ones it cares about instead of re-reading all records. Registrations move: a renewal, a new registrar, different name servers, a new owner.
Request
GET /
daily-updated-domains
Against your watchlist
acme.example is in the file
WHOIS History for acme.example
name_servers- before: ns1.hosting.example,ns2.hosting.example
- after: ns1.acme.example,ns2.acme.example
expiry_date- before: 2026-03-14
- after: 2027-03-14
check_dates- before: 2026-07-01,2026-08-01
- after: 2026-09-22
One File Lists Which Domains Moved.
The response has the shape all Deepinfo feeds share: the file’s format, size, line count and build time, and a download link valid for one hour.
| Parameter | Type | Description | |
|---|---|---|---|
file_ | string | Optional | json (default) or csv. |
Request
curl "https://api.deepinfo.com/v1/feeds/daily-updated-domains?file_format=json" \
-H "apikey: YOUR_API_KEY"import requests
meta = requests.get(
"https://api.deepinfo.com/v1/feeds/daily-updated-domains",
params={"file_format": "json"},
headers={"apikey": "YOUR_API_KEY"},
).json()
print(meta["file_update_time"], meta["line_count"])const r = await fetch(
'https://api.deepinfo.com/v1/feeds/daily-updated-domains?file_format=json',
{ headers: { apikey: 'YOUR_API_KEY' } }
)
const { download_url, line_count } = await r.json()
Response
{
"download_url": "https://…/<pre-signed link, valid for 1 hour>",
"file_format": "json",
"file_size": …,
"file_update_time": "2026-09-22T10:00:00Z",
"line_count": …
}
The Feed Says Which, and History Says What.
The file tells you a registration record changed. To see the change itself, intersect the file with the domains you watch, then ask WHOIS History for each match.
WHOIS History returns each distinct registration record Deepinfo has observed for a domain, each with the dates it was seen. Compare the two most recent and you have the registrar, name servers, dates and status codes before and after.
[
{
"whois": {
"registrar": "…",
"name_servers": [
"ns1.acme.example",
"ns2.acme.example"
],
"expiry_date": "2027-03-14T00:00:00Z",
"…": "…"
},
"check_dates": ["2026-09-22T08:00:00Z"]
},
{
"whois": {
"registrar": "…",
"name_servers": [
"ns1.hosting.example",
"ns2.hosting.example"
],
"expiry_date": "2026-03-14T00:00:00Z",
"…": "…"
},
"check_dates": [
"2026-08-01T08:00:00Z",
"2026-07-01T08:00:00Z"
]
}
]curl "https://api.deepinfo.com/v1/analyze/whois-history?domain=acme.example" \
-H "apikey: YOUR_API_KEY"
Watch the Domains That Matter to You.
Your Portfolio
Spot a registrar or name server change on one of your domains that nobody on your team requested.
Suppliers
Intersect the file with your vendors’ domains and review any that changed hands or infrastructure.
Incident Scope
Check whether the domains in an open investigation were re-registered or moved since the incident began.
Lookalikes on Watch
A quiet lookalike that suddenly gets new name servers is worth a second look.
Scope of the File.
| What counts | Domains whose registration record was updated in the last day. For resolution changes, use DNS History. |
|---|---|
| Your assets | For domains you monitor in the Deepinfo Platform, the asset_ and asset_ notification events report changes directly, instantly or on a schedule. |
| Link | download_ is pre-signed and valid for one hour. Request a new one if your job starts later. |
| Access | Plan-dependent. See authentication and rate limits. |
See This Data at Work in the Deepinfo Platform
Brand Risk Protection matches these newly seen domains against your brand names, down to letters from other alphabets, and keeps the evidence for a takedown.
Questions About Daily Updated Domain Names Feed
What does “the last day” mean for this file?
It is counted back from the file_ in the response. Store that timestamp with each run so consecutive files line up in your pipeline.
Is there a real-time version?
Not as a public endpoint. Real-time updated domains compares the routes that exist today.
Can we check for a new file without requesting a link?
Yes. GET / lists each feed’s files with their format, size, line count and update time, and creates no download link.
How is the daily feed priced?
Data feeds are priced on their own, by volume and frequency, separately from the platform. See Data & API pricing.
Can we use the file inside our own product?
How the data can be used and shown in your product is part of the agreement. Talk to the data team about your case.
Notice When a Domain Changes Hands.
We set up access to the daily feed and the history APIs, and walk your team through matching the file against your watchlists.