CONTINUOUS INTERNET TELEMETRY24H DRIFT1,971 material changesacross 1,776 domains · -107 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination alidns.com · +1 vs yesterdayEMAIL DRIFT8 domains switched email providertop destination google.comCERT DRIFT46 domains switched issuing CA24hNOW1,840 curated domains not answering+714 vs yesterdayERRORS13,179 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED35,356 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT1,971 material changesacross 1,776 domains · -107 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination alidns.com · +1 vs yesterdayEMAIL DRIFT8 domains switched email providertop destination google.comCERT DRIFT46 domains switched issuing CA24hNOW1,840 curated domains not answering+714 vs yesterdayERRORS13,179 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED35,356 throttled or blocked our scanner429 rate-limit / 403 bot-block

DomainDrift for webmasters

Know before your customers do.

You run the sites. When DNS drifts, a certificate lapses, or a domain quietly stops resolving, the wrong way to find out is a customer email. Put certificates, DNS, registration, and reachability under one watch and take the alert first.

How do I know if my DNS records changed?

DomainDrift baselines every record type on your domains: A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, SRV. When a record changes you get an alert that shows the record before and the record after, classified material or noise, so routine churn never pages you. Uptime checkers watch one signal; this is the whole surface of the domain.

SSL certificate expiry monitoring

Certificates ride the same watch: issuer, names covered, validity dates. The expiry ladder fires at 90, 60, 30, 14, 7, and 1 day out, for the certificate and for the domain registration itself, so a lapse stops being a thing that happens to you.

Who changed my nameservers?

Every change event is signed and timestamped: what the nameservers were, what they became, and when the change was observed. The after-incident question gets a record instead of a memory, and the same events cover the registrar and status planes.

Website down. Is it DNS?

Reachability probes classify every outcome: up, redirecting, blocked by a WAF, TLS failure, connection refused, server error, DNS failure. On any domain page the probe panel reruns the checks from your own browser: your resolver over DNS over HTTPS, the registry over RDAP, your own route to the site. And because the watch spans ~1,006,000 domains, the reachability board shows you when a provider moved under everyone, and it is not just you.

Check the record yourself

Every observation is Ed25519 signed the moment it is made and chained to the previous scan, against published keys. The verifier checks any receipt in your browser, and on any domain page the probe panel reruns the live checks from your own network: your resolver, the registry, your own route to the site. A signature proves who observed something and that the record has not been altered since. DomainDrift puts its name on every observation, permanently.

Start free

A free account puts 5 of your own domains under watch in a group, with signed webhook alerts on change and the complete signed record open. Paid plans raise the dials; pricing is on its own page.

Watching something we have not built for yet? Tell us what you would watch.