Find the nameserver that disagrees.
A successful DNS lookup tells you that one resolver found an answer. Pingy looks deeper: it queries authoritative nameservers, compares their answers and checks how the domain is delegated. The report gives you the records, response times and findings needed to investigate an inconsistent or broken configuration.
A domain depends on the parent zone directing resolvers to the right nameservers. A stale delegation can keep sending queries to a server you thought you had retired. Pingy compares the parent referral with the nameservers published inside the zone.
Look across the server rows before treating a single green result as the whole story. Address differences can be deliberate with geographic routing; compare findings with your provider's configuration. A shared SOA serial is useful evidence of synchronization, but it does not by itself prove every record matches.
The report groups findings by parent delegation, nameservers, SOA, mail, web and security. Each row includes the evidence and a pass, warning, failure or informational result. Optional records and unavailable answers need context; they are not interchangeable with an outage.
Compare the parent delegation with the new provider's assigned nameservers. Then inspect each authoritative response for the expected address set and zone serial. If one server differs, fix the authoritative configuration before assuming cached answers are the only problem.
Once the servers agree, allow for answers already cached by resolvers and run another check. Keep the collection time with the result when sharing it with your DNS provider.
No. The authoritative report compares the servers discovered for your domain and uses recursive lookups for supporting records. It does not measure worldwide propagation through every ISP resolver.
No. Some findings identify configuration risks or optional records. Read the evidence and compare it with your intended setup. The DNS health grade summarizes delegation, redundancy, performance, zone hygiene, security and mail.
Technical reference
DNS record and SOA reference (RFC 1035)DNS incident walkthrough
Here’s how a website owner can use Pingy’s evidence to investigate a problem.
01 · OBSERVATION
Two authoritative servers return different A records after a DNS change. The DNS report shows each answer and its collection time.
02 · INTERPRETATION
Compare the regional checks and the change timeline. The timing suggests a connection; it does not prove the cause.
03 · ACTION
Review the records with your DNS provider, allow for cached answers, then check again. Keep monitoring to observe recovery.
Pro and Enterprise run scheduled DNS audits hourly. A free public check produces a one-time report. DNS report data has its own collection time; an uptime check does not imply that every DNS test just ran. Scheduled alerts can flag nameserver changes, persistent SOA disagreement, lame delegation, DNSSEC changes, expiring signatures and CAA changes.
Keep an eye on personal sites.
Faster checks and scheduled reports.
Our fastest checks and widest coverage.
Screenshots and SEO data on every plan.
Plans apply per site. Mix Free, Pro and Enterprise in one account. Free needs no card.
Run 3 free public checks per 24 hours, including DNS, SSL, domain details and a screenshot. Scheduled audits are included with Pro and Enterprise.
A quick word on cookies
We use a few cookies to understand how Pingy is used so we can make it better. Decline and we'll keep only what's strictly necessary. Privacy