Health
How the resolver is actually performing. Latency figures exclude cache hits; those resolve in microseconds and would flatter every number equally.
- Median lookup
- 0.0ms
- Slow tail
- 0ms
- Cache hit
- 0.0%
- Failures
- 0.00%
p50, uncached
p95 · p99 231ms
5,003 served locally
63 SERVFAIL or REFUSED
Where the time goes
Distribution of uncached lookup times. A healthy resolver is a wall on the left with a thin tail; a fat middle means something is consistently slow.
Resolvers
Spread is p95 ÷ p50: how much worse a bad lookup is than a typical one. A high spread is the signature of an upstream that is usually fine and occasionally awful, which is what makes pages hang for no visible reason.
| Resolver | Queries | p50 | p95 | Spread |
|---|---|---|---|---|
| dns10.quad9.net | 4,050 | 45.4 | 55 | 1.2× |
| dns.cloudflare.com | 3,123 | 18.2 | 22 | 1.2× |
| one.one.one.one | 1,695 | 21.4 | 26 | 1.2× |
Validation and transport
- DNSSEC validated
- 0 answers carried a validated signature
- Encrypted transport
- Every client is talking to this resolver in plain DNS over the LAN.
- NXDOMAIN
- 172 names did not exist
- Empty answers
- Resolved without returning an address, often an AAAA lookup on an IPv4-only host
Slowest domains
Averaged over uncached lookups, minimum five queries. Usually an upstream problem wearing a domain’s name.
- dns.google35×49ms
- ctest.cdn.nintendo.net95×47ms
- fonts.googleapis.com281×46ms
- appleid.apple.com39×42ms
- fw-updates.ring.com299×42ms
- cdnjs.cloudflare.com252×42ms
- ws.sonos.com163×41ms
- cloudflare-dns.com24×41ms
- api.netflix.com78×40ms
- www.brother.com35×40ms