Query statistics

Every zone reports how many lookups it answered, day by day, split by outcome.

The summary lists every zone together, and the domain, queries and share columns each sort — click a heading to reorder, click again to reverse it. On an account with more than a handful of zones that is the fastest way to find which one is driving the month’s total.

Reading the split

• Answered normally — the query matched a record. This is the number that should dominate.
• NXDOMAIN — no such name. Somebody asked for a name your zone does not contain.
• SERVFAIL — the query could not be answered properly.

A rising NXDOMAIN count usually means a record somebody expects is missing. A service was set up with a hostname that was never created, or one was deleted while something still refers to it. It is the most useful signal on the page, because it is the one that points at a specific mistake.

SERVFAIL means something is genuinely broken. On a signed zone it is often a DNSSEC problem — most often a DS record at the registrar that no longer matches the key here. See DNSSEC.

What is stored

Daily totals per zone, and nothing else. There is no per-query record: no requested names, no source addresses, no resolver identities, no timestamps beyond the day.

That is a deliberate limit rather than a gap. It means the statistics cannot tell you who asked or what they asked for — and it also means there is no store of query data to be lost, subpoenaed or leaked. The Privacy Policy says the same thing, because it has to be true in both places.

History is kept for two years (730 days), the same on every plan. Older daily totals are deleted on a nightly schedule, so the chart always shows you everything still held.

Using it for capacity

Your plan includes a monthly query allowance. The daily figures are how you see whether you are near it before you reach it — a domain that gets busy usually does so gradually.

Last reviewed 2026-09-24.