CONTINUOUS INTERNET TELEMETRY24H3,953 material changesacross 3,184 domains · -22 vs yesterdayMOVES44 domains changed DNS providertop destination dns.br · +5 vs yesterdayMOVES13 domains switched email providertop destination mimecast.com · +1 vs yesterdayTLS12 domains switched issuing CA24h · -3 vs yesterdayNOW9,764 curated domains not answeringlast probe, steadyMOVERgov.brDNS provider changed: gov.br → dns.br24H3,953 material changesacross 3,184 domains · -22 vs yesterdayMOVES44 domains changed DNS providertop destination dns.br · +5 vs yesterdayMOVES13 domains switched email providertop destination mimecast.com · +1 vs yesterdayTLS12 domains switched issuing CA24h · -3 vs yesterdayNOW9,764 curated domains not answeringlast probe, steadyMOVERgov.brDNS provider changed: gov.br → dns.br
LIVE FEED MAP WHO RUNS IT POSTURE PLAYGROUND PRICING SIGN IN

Privacy Policy - Connor

DRM3 Labs Corp. · Last updated: July 9, 2026

Not legal advice; counsel reviews before external use.

Connor is a DNS reconnaissance and signal scanning platform operated by DRM3 Labs Corp.

This policy supplements the general DRM3 Privacy Policy.

Data Practices

Connor resolves publicly available DNS records via DNS-over-HTTPS (Cloudflare). All data Connor collects about domains - DNS records, WHOIS/RDAP responses, TLS certificates, certificate transparency logs, robots.txt, HTTP probe results - is already public. Connor does not create new data about domain owners; it indexes what is already observable by anyone.

Accounts and Cookies

Since June 27, 2026, Connor's web UI is gated by DRM3 single sign-on. Signing in works through your DRM3 account at drm3.network; after sign-in, Connor sets its own session cookie (`connor_session`) on the Connor host to keep you signed in. The DRM3 account hub separately sets its own cookie on drm3.network domains; that is covered by the general DRM3 Privacy Policy.

  • Cookies are used for authentication sessions only. Connor sets no advertising or third-party analytics cookies.
  • A signed-in session is associated with your DRM3 account identity (account id and display name).
  • Signed-in users can mint a personal API key; that key is stored associated with the account that created it, along with a last-used timestamp.

API Access

Programmatic API access requires an API key for rate limiting and access control. Service keys are associated with service identity; personal keys minted by signed-in users are associated with that user's DRM3 account. Request rate limiting uses client IP addresses held in short-lived in-memory counters. API request content is not stored as a product dataset; standard operational logs may exist for debugging and abuse prevention.

Scanned Domains and Opt-Out

Connor maintains a catalog of domains it scans. DNS is a public protocol, but Connor operates an opt-out registry: a domain owner can request removal, which deactivates the domain in the catalog and blocks it from being re-added while the opt-out stands. Request via the DRM3 publisher opt-out process (drm3.io/publisher-opt-out, Connor section) or support@drm3.io. If you believe Connor is displaying inaccurate information about your domain, contact us.

---

General Privacy Policy · Terms of Use · support@drm3.io

These terms supplement the general DRM3 Terms of Use and Privacy Policy. Questions: legal@drm3.io.