Connor is now DomainDrift
Same scanner, clearer name. Around 50,000 domains on a loop, every change signed.
Connor is now DomainDrift. Same product, clearer name. The old address redirects, and every signed receipt still verifies.
This post is the why and the what. Nothing you bookmarked breaks.

Why drift
Drift is the word infrastructure teams already use for configuration that moved since baseline: a new nameserver, a mail record that changed, a certificate that rotated, a host that went dark. That is exactly what this product catches. The old name did not say it. The new one does.
The redesign makes the idea legible. Cyan is the baseline, the scan at rest. Magenta is drift, a field that moved since the last scan. One glance tells you what is steady and what just changed.
Same scanner
DomainDrift scans around 50,000 domains on a loop, a full sweep of the catalog roughly every 21 hours. On each pass it records the DNS, the host, the email posture, and the certificate, and writes an Ed25519 receipt on every observation. When a field drifts, the change is the event: what it was, what it became, and when we saw it, each one signed.
The observation planes are unchanged: DNS across nine record types, TLS from certificate transparency, WHOIS over RDAP, ASN, DNSSEC, and robots.txt. The methodology still documents exactly what it touches and what it never does. It is not a crawler, and it never reads page content.
Nothing in the record breaks
connor.dns.drm3.network now redirects to domaindrift.io with a permanent 301, so old links keep working. The signing keys keep their existing derivation paths, which means every receipt ever issued still verifies against the same published keys, and every badge embedded on a domain page keeps checking out. A rename does not touch the record.
A signature proves who made an observation and that the bytes are intact. It is added accountability, not a claim that the world is a certain way. That is why the receipts are worth keeping, and why a change of name leaves all of them standing.
Take a look
Search a domain at domaindrift.io, watch what is steady and what has drifted, and check any receipt yourself against the published keys. Same scanner it always was. Now it says what it does.
Published by
Robert Christian
Founder and CEO, DRM3 Labs Corp.
More from DRM3 Labs
2026 DRM3 Labs Corp. All rights reserved. DRM3 Labs builds infrastructure for open protocols.
This article is for informational purposes only. Nothing here is financial, investment, or legal advice. Tokens, staking, NFTs, and blockchain protocols are described as technical mechanisms, not investment recommendations. Digital assets carry risk. Do your own research.
Many DRM3 products mentioned are in early alpha. Features, availability, and economics are subject to change. References to the Morpheus network describe the public protocol as documented at mor.org.
