# Daily Updated Domain Names Feed URL: https://www.deepinfo.com/data-api/feeds/daily-updated-domain-names/ ## 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. [Talk to us about access](https://www.deepinfo.com/contact/?topic=data-api) [Daily Updated Domains reference](https://docs.deepinfo.com/reference/feeds/daily-updated-domains/) ### 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](https://docs.deepinfo.com/reference/feeds/daily-updated-domains/) | Parameter | Type | | Description | | --- | --- | --- | --- | | `file_format` | string | Optional | `json` (default) or `csv`. | Request curl: ```bash curl "https://api.deepinfo.com/v1/feeds/daily-updated-domains?file_format=json" \ -H "apikey: YOUR_API_KEY" ``` Python: ```python 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"]) ``` JavaScript: ```javascript 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 200 OK · application/json ```json { "download_url": "https://…/", "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](https://www.deepinfo.com/data-api/apis/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 History reference](https://docs.deepinfo.com/reference/lookup/whois-history/) Response: ```json [ { "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" ] } ] ``` Request: ```bash 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](https://www.deepinfo.com/solutions/use-cases/attack-surface-management/) Spot a registrar or name server change on one of your domains that nobody on your team requested. #### [Suppliers](https://www.deepinfo.com/solutions/use-cases/third-party-risk-management/) Intersect the file with your vendors’ domains and review any that changed hands or infrastructure. #### [Incident Scope](https://www.deepinfo.com/solutions/use-cases/incident-investigation-and-response/) Check whether the domains in an open investigation were re-registered or moved since the incident began. #### [Lookalikes on Watch](https://www.deepinfo.com/solutions/use-cases/brand-impersonation-protection/) 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](https://www.deepinfo.com/data-api/apis/dns-history/). - **Your assets**: For 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. - **Link**: `download_url` is pre-signed and valid for one hour. Request a new one if your job starts later. - **Access**: Plan-dependent. See [authentication](https://docs.deepinfo.com/getting-started/authentication/) and [rate limits](https://docs.deepinfo.com/getting-started/rate-limits/). ### The Other Daily Files. - [Daily Registered Domain Names](https://www.deepinfo.com/data-api/feeds/daily-registered-domain-names/) (Daily file): Domains registered in the last day. - [Daily Deleted Domain Names](https://www.deepinfo.com/data-api/feeds/daily-deleted-domain-names/) (Daily file): Domains deleted in the last day. - [WHOIS History](https://www.deepinfo.com/data-api/apis/whois-history/) (API): Each distinct registration record of a domain. ### 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. - [Brand Risk Protection](https://www.deepinfo.com/platform/brp/) (BRP) - [Fraudulent Domain Monitoring](https://www.deepinfo.com/platform/brp/fraudulent-domain-monitoring/) (BRP) - [Deep Search & Insights](https://www.deepinfo.com/platform/dsi/) (DSI) ### 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](https://www.deepinfo.com/data-api/feeds/real-time-newly-updated-domain-names-stream/) 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](https://www.deepinfo.com/pricing/#data-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](https://www.deepinfo.com/contact/?topic=data-api) 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. [Talk to us about access](https://www.deepinfo.com/contact/?topic=data-api) [WHOIS History API](https://www.deepinfo.com/data-api/apis/whois-history/)