DNS Cache Checker — Resolver Latency & Record Timing
Measure per-record resolver latency to infer cache warmth and authoritative response speed
How to Use This Tool
- Enter the domain whose DNS cache and timing you want to assess.
- Six parallel timed queries run for A, AAAA, MX, TXT, NS, and SOA.
- Each probe records latencyMs, recordCount, and status.
- Failed probes report null latency with ERROR status.
- averageMs and slowest summarize successful probes only.
- Compare runs over time or after TTL expiry for cache behavior hints.
About This Tool
DNS caching hides authoritative slowness until TTL expires — then users see latency spikes on first miss. Operators searching DNS cache checker need timing signals: are answers fast because resolvers cache hits, or slow because authoritative NS is distant or bloated? VSPIC DNS cache checker calls action dns-response-time: six parallel timed probes for A, AAAA, MX, TXT, NS, and SOA against your domain through Google Public DNS, returning probes array with latencyMs, recordCount, and status per type plus averageMs, slowest, and summary text.
Low latency on repeat runs often indicates warm resolver cache along the measurement path; uniformly high latency across types may point to authoritative distance or heavy answers. This is a single-origin snapshot — not sustained p95 monitoring — but invaluable after DNS changes when you need quick cache and performance context before TTL cycles complete worldwide.
Common use cases
- •View all DNS records of a domain after migration
- •Confirm DNS records after domain changes
- •Test for DNS leaks when using a VPN
- •Debug email delivery with MX and TXT records
Why use VSPIC for ?
- Six record types timed in one run.
- Per-type latency isolates bloated TXT or MX sets.
- averageMs and slowest for quick triage.
- recordCount explains latency from large answers.
- Parallel probes minimize wall-clock wait.
- Free on-demand timing via dns-response-time action.
DNS caching and why timing matters
Resolvers cache answers until TTL expires. First query after expiry contacts authoritative NS — slow authoritative responses hurt every cache miss worldwide until TTL warms again.
Per-type timing reveals whether delay is record-specific (bloated TXT) or systemic (distant authoritative NS). DNS cache checker frames dns-response-time results for cache-oriented investigation workflows.
dns-response-time backend
Action dns-response-time with domain parameter fires parallel A, AAAA, MX, TXT, NS, and SOA probes via Google Public DNS JSON API. probes array entries include type, latencyMs, recordCount, and status.
averageMs aggregates successful probes. slowest highlights maximum latency type — first optimization target.
Inferring cache warmth from latency
Popular domains on Google Public DNS often show low latency on first page load due to warm shared cache — not proof your authoritative NS is fast globally. Repeat tests after waiting beyond your apex TTL for a colder picture.
Compare timing before and after DNS record changes. Unexpected elevation on one type after TXT edits points to SPF bloat rather than general network loss.
Per-record type interpretation
Fast A with slow TXT is common when SPF includes recurse on receivers — our TXT probe measures authoritative answer time for your zone apex TXT set. Slow MX may mean oversized zone files or distant authoritative region.
NS and SOA timing reflects delegation metadata speed — persistent elevation across all types suggests resolver path or network issues.
Relationship to dns-response-time-test
Same API and JSON shape. dns-response-time-test emphasizes benchmark SEO; DNS cache checker emphasizes cache and resolver latency language. API action is identical.
Pair with dns-ttl-checker when planning how long changed records linger in caches after edits.
Optimizing after slow probes
When TXT dominates slowest, audit SPF includes. When all types are slow, review authoritative NS placement and anycast DNS hosting. Lowering TTL increases query frequency — fix answer weight before TTL tuning for perceived speed.
Google Public DNS measurement path
Results describe Google anycast resolver path, not corporate forwarders or ISP DNS. Internal AD DNS may cache differently. Use this tool for internet-facing authoritative tuning; use local dig from office networks for employee DNS analysis.
Scheduling checks around changes
Run immediately after DNS edits, again after minimum TTL elapsed, and weekly on high-traffic zones. Archive JSON to prove performance did not regress after SPF or MX updates.
Incident response for slow loads should capture timing snapshot alongside traceroute and SSL checks.
Limits and privacy
Single-shot sampling misses transient spikes. Repeat runs or external synthetic monitoring fill p95 gaps. Timing queries public DNS for domains you submit — we do not permanently store searches.
Important notes & limitations
- Google Public DNS path only — not your ISP resolver.
- Single sample per type — not percentile stats over hours.
- Cannot directly read resolver cache TTL remaining.
- Does not query authoritative servers by NS IP.
- Network jitter between runs shifts numbers slightly.
Frequently Asked Questions
Yes. VSPIC offers this DNS cache checker at no cost with no account required. Results load in real time.
We do not permanently store your queries on our servers. Some tools run entirely in your browser; others fetch public data for the request only.
Yes. Open the page in any modern phone or tablet browser. Results work on Wi‑Fi and mobile data.
dns-response-time with domain parameter — same as dns-response-time-test.
No. It measures lookup latency, not cached TTL seconds remaining.
Large TXT sets, deep SPF includes, or heavy MX lists increase answer size. Investigate that record type first.
No. Only successful latency measurements contribute to averageMs.
No. This measures Google Public DNS path. ISP or corporate resolver timing may differ.
Cache checker uses dns-response-time per record type on one path. DNS benchmark compares multiple resolver providers.
Next step for your check
Continue with dns response time test on VSPIC.
Related Tools
Explore more free VSPIC tools for IP, DNS, security, and network diagnostics.
DNS Response Time Test
Measure resolver latency per record type — A, MX, TXT, NS, SOA
Use Free →DNS TTL Checker
Show TTL for all DNS record types on a domain
Use Free →DNS Benchmark Tool
Benchmark Cloudflare, Google, Quad9, and OpenDNS latency
Use Free →DNS Lookup Tool — DNS Checker
Free DNS lookup tool and DNS checker — query A, AAAA, MX, TXT, NS, CNAME, and SOA records for any domain.
Use Free →Reverse DNS Lookup
Resolve IP addresses to hostnames via PTR records
Use Free →Hostname Lookup
Resolve a domain name to its hostname and IP addresses
Use Free →
Trusted by Users Who Value Privacy
Always Free
No premium plan ever
100% Private
Files processed in browser
Instant Results
Convert in seconds
Works Everywhere
Any device, any OS