FeaturesHow it worksUse casesPricingHelpLog inSign up
Use cases

Start with the problem you are trying to solve

You do not need to know which DNS test to run first. Pick the situation that sounds like yours.

You changed a DNS record

Your question: Has the new value reached the internet yet?

Enter the expected value. DNSReach compares usable resolver answers, authoritative DNS and geographic evidence without treating timeouts as wrong DNS values.

You moved a website or service

Your question: Are people still being sent to the old server?

Compare A, AAAA, CNAME and related records across resolver caches. Use TTL and authoritative answers to understand what is still changing.

You changed nameservers

Your question: Which DNS source is now authoritative?

Check NS and SOA information and compare the authoritative path with what recursive services return.

A customer says it works in one place but not another

Your question: Is this really geographic?

Use real DNSReach nodes for location evidence. Do not confuse a global anycast resolver with a DNS query made from a specific city.

Mail or verification records are failing

Your question: Are MX, TXT, CAA or related records visible and consistent?

Compare returned values and authoritative data before changing a configuration that may already be correct.

You run hosting, MSP or support services

Your question: Can I give the customer evidence rather than a guess?

Use repeatable checks, shareable results and technical details to shorten DNS troubleshooting and escalation.