DNS record monitoring
Know the moment a DNS record changes under you.
A hijacked A record, a fat-fingered MX change, or a deploy that silently repointed your apex domain — DNS drifts fast and breaks everything quietly. CuliPulse watches your records and alerts you as soon as they stop matching what you expect. No agent to install.
No credit card · no agent to install
What it catches
The DNS changes that hurt.
An A or AAAA record silently swapped to a different IP — malicious redirect, compromised registrar, or DNS provider breach. CuliPulse flags it at the next check interval.
A deploy script repoints your apex A record to a new server, or forgets to update a CNAME. Traffic starts landing in the wrong place before your team notices.
An MX change gone wrong means email bounces silently — hard to spot until users start complaining. Watch your mail routing the same way you watch your site.
CDN provider swaps, TXT record drift (SPF, DKIM, ownership tokens), or an NS delegation change all show up immediately.
How it works
Baseline in seconds, not minutes.
CuliPulse resolves your records using DNS-over-HTTPS — no agent required. Checks run on your normal monitor interval (not daily), so a hijack or unexpected change is caught fast.
- Type a hostname
Click Discover records — CuliPulse resolves every record type for that name live.
- Keep what matters
The results pre-fill your expected values as the baseline. TXT starts unticked, since other services add entries there. No spreadsheet, no digging through DNS dashboards.
- Save
Watches A, AAAA, CNAME, MX, TXT and NS — plus CAA and SRV — in a single monitor. DOWN if any selected record fails.
Match modes
Strict or flexible — your call.
The resolved value set must match the expected set exactly. Best for MX and NS records where any change is meaningful.
The expected values must all be present in the result — extra values are fine. Good for TXT where providers add their own records.
The record just needs to exist — any value passes. Ideal for A / AAAA behind a CDN where IPs rotate, or for confirming a delegation exists.
CDN caveat: if your hostname is CDN-fronted, its A / AAAA addresses rotate across edge nodes. Use present (or watch the stable CNAME instead) — Discover records always pre-selects present for A / AAAA, because those addresses can change by location.
Alerts you can act on
An alert the moment records drift.
CuliPulse alerts you as soon as a DNS assertion fails — with the hostname and which record type failed. The monitor’s page shows each record’s expected value next to what was actually resolved.
Resolver hiccups and transient DoH errors are reported as inconclusive — they never produce a false “down”. Your status only goes red when the record genuinely fails the assertion.
Flip one toggle to corroborate every answer across several independent public resolvers — Cloudflare, Google, NextDNS, AdGuard & DNS.SB. The monitor goes down only when a majority disagree, so a poisoned or stale resolver is caught (and shown per-resolver in the detail) without false alarms.
Set up DNS monitoring in under a minute.
Type a hostname, discover records, save.