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.
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.
CuliPulse resolves your records from our edge using DNS-over-HTTPS — no agent required, and no resolver caching surprises. Checks run on your normal monitor interval (not daily), so a hijack or unexpected change is caught fast.
Type a hostname and click “Discover records” — CuliPulse resolves every record type for that name live and pre-fills them as your expected baseline. No manual value typing.
Watches A, AAAA, CNAME, MX, TXT and NS — plus CAA (catch an unauthorized certificate authority) and SRV — in a single monitor. Bundle multiple assertions on one hostname; DOWN if any selected record fails.
Pick how strict each assertion is: exact (value must equal the set exactly), contains (expected values must be present, extras allowed), or present (record just needs to exist).
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.
Optional resolver cross-check. 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. Best for stable records — a CDN's A/AAAA legitimately differ by resolver, so use present there.
Type a hostname, click Discover records — CuliPulse resolves every record type live and pre-fills your expected values as the baseline. No spreadsheet, no digging through DNS dashboards.
Discovery finds every record type for the hostname you provide. It cannot enumerate subdomains — for subdomain coverage, add separate monitors for each name.
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.
CuliPulse sends you a Telegram message as soon as a DNS assertion fails — with the hostname, which record type failed, and what was resolved vs. what was expected.
Type a hostname, discover records, save. Every feature is on the free plan.
Start free