You look after clients’ domains.

Every client domain in one place.

Every client’s domains on one screen, grouped by client. One alert feed across all of them, and a report you can hand each client. Any registrar, any host.

~809,000 domains tracked 229,000 scans a day Signed the moment it is observed
A missed renewal is not a small-company problem.
“A major web mail service lost its UK domain in 2003 after a renewal notice went unactioned, and the name returned to the open market.”
The Register, 6 November 2003 ↗

Quoted from a public discussion. Not a customer, not affiliated with DomainDrift, and not an endorsement.

For managed service providers2 minEvery client in one account, grouped by client. The signed baseline is the thing you sell.Transcript

How do I monitor all my clients’ domains in one place?

A group per client. Every domain in it goes under continuous watch: DNS, registration, certificates, reachability, whoever registers or hosts it. A DRM3 account watches one domain; paid plans raise the count across the whole book. For an IT shop running thousands of client domains, see the MSP page.

A client swears nothing changed; the group shows the nameserver a former vendor moved last Tuesday.

One alert feed, not fifty logins

One subscription covers a whole client group, so every material change on that client lands at one destination. Routine churn stays quiet.

A report you can send the client

Pull a client group’s current state as a signed report: what every domain runs on, who carries its mail, its certificate and registration state, each line from a signed reading the client re-checks at /verify. The group report is bought per report. The per-domain signed evidence bundle is separate and included on Pro - both are priced here.

Catch the change an old vendor made

A DNS record edited by access nobody remembered granting lands as a signed event with the value before and the value after, timestamped. What changed and when is a record, not a memory.

Mail stops flowing for a client two hours after an agency that still had access edited an MX record.

How it works

1Check a domain now

Run a check on any client domain. No account needed to see it work.

2Group by client

A DRM3 account watches one domain; paid plans raise the count so you can group your whole book by client.

3One feed, one report

Every change lands in one place, with an export each client can verify.

How you check it yourself

Every reading is Ed25519 signed the moment it is taken and chained to the one before, against published keys. The verifier checks any receipt in your browser: you hash the short proof path yourself and compare it to the root we published. A signature proves who took a reading and that nobody has changed it since, including us - it does not, on its own, make the reading correct. DomainDrift puts its name on the record, permanently.

Start with one domain

A DRM3 account puts one domain of your choosing under watch, keeps its history, and sends a signed alert the moment we see it change. See a sample report. Paid plans raise the dials; what it costs is on its own page.

One domain to start. No credit card. Your signed record is yours to keep and verify anywhere.

CONTINUOUS INTERNET TELEMETRY24H DRIFT10,611 material changesacross 8,371 domains · 24h to ~60m ago · +3,246 vs yesterdayROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 56 moved backa rotation loop, not a migration · 24hCERT DRIFT1 domains switched issuing CA24hREGISTRAR DRIFT1 changed registrar24hNOW637 curated domains not reachablelast probe, steadySITE ERRORS17,653 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 80,375 sites429 rate-limit / 403 bot-block, a posture signal