Web Routing Problems
If A/AAAA records are missing, wrong, or stale, browsers can resolve to the wrong destination or fail entirely. Validate this first before spending time on app-layer debugging.
Network Tools
Check DNS records quickly, understand what they mean, and troubleshoot domain issues with confidence.
This tool helps you validate web routing, email routing, and verification entries by checking A, AAAA, CNAME, MX, NS, and TXT records in one place.
For full incident triage, combine this with the Website Down Checker, the HTTP Status Checker, and our DNS outage troubleshooting guide.
We fetch common DNS record types and show all returned values in a clear table.
DNS is often the first place to check when users say a site is down, email stops delivering, or verification tokens fail.
If A/AAAA records are missing, wrong, or stale, browsers can resolve to the wrong destination or fail entirely. Validate this first before spending time on app-layer debugging.
CNAME chains can point to retired hosts or create unexpected dependencies after migrations. If you see mismatches, verify redirect behavior in the Redirect Checker.
MX and TXT checks help identify why inbound delivery, SPF, or domain verification flows are failing. This is critical when status updates and reset emails stop reaching users during incidents.
NS records show where authority lives. Wrong delegation can make updates appear correct in one place but not globally, which is a common source of “works for me” reports.
Confirm both records point where you expect. Missing AAAA can create IPv6-only failures even if IPv4 works.
Check alias destinations for deprecated hosts, typoed endpoints, or old platform targets left after cutovers.
If updates do not appear, confirm the domain is delegated to the correct nameservers before changing records again.
When login emails or transactional messages fail, broken MX or SPF-related TXT entries are a frequent root cause.
It checks A, AAAA, CNAME, MX, NS, and TXT records. Together, these cover core web routing, mail routing, delegation, and domain verification use cases.
Look for missing or unexpected A/AAAA values first. If those look right, validate CNAME/NS consistency. If all DNS records are healthy, the issue is likely in the CDN, TLS, firewall, or application layer.
DNS confirms where traffic should go. It does not prove the destination is healthy. Servers can still return 5xx errors, time out, or block requests even when DNS resolves correctly.
Indirectly, yes. TXT is often used for SPF, DKIM, verification, and security policies. Broken TXT data can disrupt email flows and integrations tied to incident communication.
Yes. It is free for normal diagnostics and quick incident troubleshooting workflows.