Request demo

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 /feeds/daily-updated-domains?file_format=json

daily-updated-domains

file_format
json
file_size
elided
line_count
elided
file_update_time
2026-09-22T10:00:00Z

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.

GET https://api.deepinfo.com/v1/feeds/daily-updated-domains Reference
ParameterTypeDescription
file_formatstringOptionaljson (default) or csv.

Request

curl "https://api.deepinfo.com/v1/feeds/daily-updated-domains?file_format=json" \
  -H "apikey: YOUR_API_KEY"

Response

200 OK · application/json
{
  "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"
    ]
  }
]

Scope of the File.

What countsDomains whose registration record was updated in the last day. For resolution changes, use DNS History.
Your assetsFor domains you monitor in the Deepinfo Platform, the asset_whois_changed and asset_dns_changed notification events report changes directly, instantly or on a schedule.
Linkdownload_url is pre-signed and valid for one hour. Request a new one if your job starts later.
AccessPlan-dependent. See authentication and rate limits.

Questions About Daily Updated Domain Names Feed

What does “the last day” mean for this file?

It is counted back from the file_update_time 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 /feeds/latest 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.