A Typo in a DNS Record Can Take Down Your Entire Business
DNS is the part of your infrastructure everyone assumes just works, right up until someone edits the wrong record, a TTL expires mid-migration, or a registrar-side change silently propagates the wrong value. There’s no error page, no crash log, no alert from your hosting provider. Traffic just stops arriving.
Seabhac.io checks your DNS records on a schedule, from multiple regions, and compares what actually resolves against what you expect.
How it works:
- Define what to expect: Point a check at any hostname and record type — A, AAAA, MX, TXT, or CNAME.
- Resolve from everywhere: Every run queries resolvers from our distributed probe regions, not just one local resolver.
- Alert on drift: If the resolved value, record count, or TTL changes unexpectedly, you're notified before your users notice anything's wrong.
Catch What Propagation Delays Hide
A DNS change that looks correct from your office might not have propagated everywhere yet — or might have propagated incorrectly to some resolvers and not others.
- Multi-region resolution exposes inconsistencies a single
digcommand from your laptop never will. - TTL-aware checks catch stale caching issues that only surface hours after a change goes live.
- Historical record tracking lets you see exactly when a value changed, useful when diagnosing “it worked yesterday” incidents.
Every Record Type That Matters
- A / AAAA confirm your apex and subdomains point where they should, on both IPv4 and IPv6.
- MX verify mail routing hasn’t silently reverted to a default or been hijacked.
- TXT track SPF, verification, and other TXT-based records for unexpected changes.
- CNAME catch broken aliases pointing at decommissioned targets.