Whois and DNS changes the moment they're detected.
Whois and DNS changes delivered the moment they are detected. The daily updated feed, streamed event-by-event for systems that need low-latency change signal.
One event per change, streamed continuously.
The Real-time Newly Updated Domain Names Stream is the daily updated feed, delivered as it happens. Each detected change becomes an event on the stream within minutes of observation: registrar transfers, name server swaps, registrant block changes, expiry-date jumps, status code transitions.
The stream is built off the same continuous pipeline that powers the daily file. The advantage of the stream is latency: where the daily file bundles 24 hours of changes into one snapshot, the stream surfaces each change as soon as the diff is confirmed.
This is the right input for IR and TPRM systems that need to react to ownership or DNS movement on relevant domains in minutes, not next-day. Pair with the Whois Lookup or Whois History APIs to enrich each event with the before-and-after state.
Streamed, not batched.
Events are delivered through a managed stream endpoint. Authenticate with an API token scoped to the stream.
Delivery
Real-time stream. JSON messages over a managed endpoint; backpressure-aware buffering. Optional Webhook, Kafka, or Kinesis routing.
Format
JSON. One event per change. Schema matches the daily updated feed file format.
Refresh cadence
Continuous. Events appear within minutes of underlying detection.
Authentication
API token in the request header. Per-stream scoping. Reference at docs.deepinfo.com.
What you actually get.
Representative stream events:
{"event":"updated","domain":"acme.com","change":"registrar_transfer","detected_at":"2026-05-02T14:23:08Z"}
{"event":"updated","domain":"contoso.io","change":"name_servers_changed","detected_at":"2026-05-02T14:23:14Z"}
{"event":"updated","domain":"deepinfo.com","change":"registrant_organization_changed","detected_at":"2026-05-02T14:23:21Z"}
{"event":"updated","domain":"example-corp.net","change":"expiry_extended","detected_at":"2026-05-02T14:23:27Z"}
{"event":"updated","domain":"shop.example.shop","change":"status_code_added","detected_at":"2026-05-02T14:23:33Z"}Workflows this stream powers directly.
Incident Investigation and Response
React to ownership and DNS movement on incident-scope domains in minutes. The change event triggers the next investigative pivot.
Read the use caseThird-Party Risk Management
Watch vendor and subsidiary domain churn at portfolio scale, in real time.
Read the use caseBrand Impersonation Protection
Catch silent moves like name-server swaps or registrant changes on already-flagged domains.
Read the use case“Change-event streams replaced a polling job that hit our partner APIs every fifteen minutes. The push model handles volume we couldn't pull through, and we react to ownership changes the same hour they happen.”
Track domain change at stream latency.
We'll set up token access and walk through delivery patterns to match your stack.