How to read your report
A report groups its checks into categories (Parent, NS, SOA, MX, MAIL, WWW, CAA, DNSSEC) and gives each check a status and a plain-English explanation. Here is how to read it.
The statuses
- Pass - this check is fine.
- Info - not a problem, just information worth showing (your NS list, your SOA fields, your MX hosts).
- Warn - works today, but it is fragile, non-ideal, or against a best practice. Worth fixing, not an emergency.
- Error - a real fault that is likely breaking something (mail, the website, or resolution). Fix these first.
- Inconclusive - the tool could not complete this check (a query timed out, or a server never answered), so it makes no claim either way. This is usually transient, and often nothing to do with your DNS; re-running frequently clears it.
- Skipped - the check did not apply or could not run because something it depends on was missing (for example, every check is skipped when there is no delegation to test).
The three views
- Issues - only the errors and warnings, as cards, so you can act on what matters.
- Summary - the consolidated result per check.
- Details - the full per-nameserver breakdown, including the exact wire queries the tool made (you can copy a line and run it with
dig).
Learn more links
Where a finding has a matching knowledgebase article, a Learn more link opens it in place (and can open the full article in its own tab). That is the fastest way to go from "what is wrong" to "how to fix it."
Sharing and re-running
Every report has Share this report, which captures a point-in-time snapshot at its own link (useful for a ticket or a second opinion). Reports are served from a short cache; use the re-run option to force a fresh check after you make a change - remember that resolvers, and this tool's cache, honour TTLs, so give a change time to propagate.