Know when your DNS records change. Before your users do.

DNS changes silently, and it breaks things silently

A registrar compromise swaps your nameservers. A teammate edits an MX record and mail stops arriving. A SaaS tool you cancelled leaves a dangling CNAME that someone else can claim. None of these send you a notification.

Most teams find out from a customer, hours or days later. By then the damage is done: lost mail, a phishing page on your subdomain, or an outage nobody can explain.

How it works

1. 1

   Enable DNS monitoring on a domain

   One toggle on any watched domain. By default we track A, AAAA, MX, TXT and NS records on the apex plus www, and you can add your own subdomains.

2. 2

   We snapshot your records every night

   Domain Sentinel resolves your records daily and stores a snapshot only when something differs from the last known state.

3. 3

   Get a diff, not a vague warning

   The alert email shows exactly what was added, removed or changed, old value and new value side by side.

From the blog

• What is DNS monitoring and when do you need itDNS monitoring records your DNS setup and alerts you when it changes. What it watches, which incidents it catches, and how to decide if you need it.
• DNS hijacking: how it works and how to detect itDNS hijacking redirects your traffic or email by changing DNS answers. The three attack levels, the signals each one leaves, and how to catch it early.
• How to monitor nameserver changes on your domainsNameservers control your whole DNS zone, and unplanned changes are rarely good news. How to get alerted when NS records change, on your domains or others.
• Detecting domain registration changes before they cause damageLearn which RDAP fields change during a domain hijack, how to detect nameserver and registrar changes automatically, and how to respond within hours.