Docs

DomainDrift documentation

DomainDrift scans over a million domains continuously - what runs each one, how it is secured, and what changed - and Ed25519-signs every observation, so anything it tells you can be checked.

Your first call, right now

One command. No account, no key:

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

Back comes the latest scan of that domain - who runs its DNS, mail, and CDN, the certificate issuer and expiry, reachability, and a pointer to the signed receipt. The response (values will be current when you run it):

{
  "domain": "netflix.com",
  "scanned_at": "…",
  "providers": { "dns": ["AWS Route 53"], "email": ["Google Workspace", …] },
  "certificate": { "issuers": ["DigiCert"], "expires_in_days": 203, "status": "ok" },
  "reachability": { "http_status": 200, … },
  "receipt": { "id": "rcpt_…", "url": "https://domaindrift.io/receipts/rcpt_…" }
}

Swap in any domain you care about. Then: mint a key for the complete record, or verify the receipt you just got.

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, keys, lists, history, live streams. VerificationWhat a receipt proves, how to check one, and how to carry the evidence elsewhere. Plans & limitsWhat is public, 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.
Solutions - live prices and every limit, straight from the catalog and the meter.

Getting started →