How Domain Monitoring Works (and what it isn't)

Our Domain Monitoring feature (Pro and Business) lets you watch domains and get notified when things change. It’s useful for tracking infrastructure shifts, expiry changes, or when someone adds or removes DNS records. But it’s important to be clear about what it is—and what it isn’t.

What we do

We periodically fetch public data about the domains you choose to monitor:

  • WHOIS / RDAP — Registration and expiry dates, registrar, name servers.
  • DNS — A, AAAA, MX, TXT, and other record types you care about.
  • SSL/TLS — Certificate presence and validity (where applicable).

We store a baseline and compare new snapshots to it. When something changes, we record it and can notify you (email or webhook). No login to the target, no private data—just the same kind of information you’d get from public lookups.

What we don’t do

  • We don’t “hack” or probe behind firewalls. We only query public services (registries, DNS, certificate transparency, etc.).
  • We don’t guarantee real-time detection. We run on a schedule. There will be a delay between a change in the real world and our snapshot.
  • We don’t replace active security monitoring or IDS. This is change detection and alerting for public data, not intrusion detection or incident response.

Good use cases

  • Watching your own domains for unexpected DNS or WHOIS changes.
  • Tracking competitor or target infrastructure (within legal and ethical bounds).
  • Research and OSINT workflows where you need a history of public changes.

Use it as one input in your workflow, not as your only line of defense. For more on how we handle security and data, see our Security Practices and Privacy Policy on dontpoke.me.