CONTINUOUS INTERNET TELEMETRY24H DRIFT10,789 material changesacross 10,408 domains · +160 vs yesterdayDNS DRIFT757 domains changed DNS providertop destination cloudflare.com · -23 vs yesterdayEMAIL DRIFT176 domains switched email providertop destination google.com · +6 vs yesterdayCERT DRIFT221 domains switched issuing CA24h · -9 vs yesterdayNOW1,164 curated domains not reachable-185 vs yesterdaySITE ERRORS19,144 sites serving errorslast probe · 5xx / 404 / TLSTHROTTLED95,136 throttled or blocked our scanner429 rate-limit / 403 bot-block
Docs

DomainDrift documentation

DomainDrift reads the public surface of the internet, continuously: what runs a website, who registered it, how it is secured, and what changed since yesterday. It observes ~1,006,000 domains plus any domain you add, and signs every observation with Ed25519 the moment it is recorded, so anything it tells you can be checked. These pages explain everything the product does and how to use all of it.

Try it right now

One command, no account, no key. It returns a real, current preview of the signed record for any domain:

curl https://domaindrift.io/v1/domains/netflix.com

Swap in any domain you care about. What comes back is live data from the latest scan, with a pointer to the signed receipt that commits to it.

Find your way

Getting startedFrom a keyless curl to a monitored portfolio in five steps. The signed recordEverything DomainDrift observes about a domain, and how each piece is collected. Live viewsThe full catalog of pages that read the corpus: drift, migrations, concentration, posture, and more. Monitoring & alertsWatch your domains, group them, approve baselines, and get alerted on material change. The APIOne door for humans and agents: keyless preview, free keys, lists, history, live streams. VerificationWhat a receipt proves, how to check one, and how to carry the evidence elsewhere. Plans & limitsWhat is free, what paying raises, and how credits meter API use.

What makes the data different

Every observation DomainDrift records is signed at the moment of observation and chained to the one before it. A signature proves who recorded the data and that it has not been altered since - added trust on top of the reading itself, not a claim that the reading is infallible. You can verify any receipt yourself, offline, against published keys: see Verification.

That property runs through the whole product. The change feed, the evidence reports, the exports, the badges: each one traces back to signed observations, so what you cite is what was seen.

Where to go next

  • The API console - the interactive reference, with your key and your live meter once you sign in.
  • The playground - run real read-only queries from the browser.
  • The machine front door - discovery endpoints, OpenAPI, and llms.txt for AI agents.
  • Pricing - live prices and every limit, straight from the catalog and the meter.
Getting started →