How accurate is DNSFix?
Short answer: every result is read live from public DNS when you ask, by our own rules, and we say "couldn't check" instead of guessing. We regularly run the same domains through DNSFix and other well-known DNS checkers side by side, and fix anything we got wrong. This page lists what we can't see, and what those tests changed.
How we check
- Every result is stamped with when it was checked and where from: the date and time in your own time zone (tap it for the exact UTC time), and the data centre that ran the check, for example Tokyo or Ashburn. Records for email (MX, SPF, DKIM, DMARC) are the same everywhere; website addresses can differ by country because of content networks, so the stamp tells you which view you are reading. Monitoring checks say "DNSFix scheduled check".
- Every result is checked live when you ask: we query public DNS straight away (a big public resolver, with a second one as a backup), never an old copy, unless the report says it's from an earlier check.
- The rules are our own code. No AI decides a grade or a finding.
- When a lookup fails or times out, we say "couldn't check". We never turn a failed lookup into a problem.
- Nameserver details, the DNS path and the DNSSEC chain are asked of your own nameservers directly where we can reach them.
What no outside checker can see
- DKIM: there's no public list of a domain's DKIM keys, so we try the names mail services use. If yours uses another name, send us a test email and we'll see the real signature.
- TTLs: public resolvers count TTLs down and some cap them (one big resolver caps them at 6 hours). Where it matters we ask your nameserver for the real value.
- Nameservers on our own cloud host's network: our checker runs on that same network, so it can't time them directly. Those rows say so instead of showing a number.
- Site speed: measured by our own check of your home page (server response, size, scripts), not a full phone test.
- Known software flaws: we only flag versions in our own reviewed table (jQuery, nginx, Apache, old PHP). Software that isn't in it shows nothing, never "no flaws".
- Records your DNS host keeps private (anything not published under the usual names) can't be seen by any outside checker, including ours.
What our side-by-side tests changed
| When | Change |
|---|---|
| A domain parked or listed for sale no longer gets business-website advice or an "expired" warning. | |
| Hosts that sign DNSSEC with short-lived signatures are no longer warned that signatures expire soon. | |
| A null MX written as "0" is recognised, so locked-down domains aren't asked to lock down again. | |
| Fix records suggest your own report address until DNSFix's report mailbox is authorised to receive for other domains. | |
| The SPF check follows the whole include tree when it looks for your mail provider (some big mailbox services nest theirs). | |
| A private IP address on your website is a problem; a root CNAME is a warning. | |
| Checks no longer time out when many run at once: at most 5 outside requests run together. | |
| DNSSEC: a broken chain (signed answers rejected) is told apart from DNSSEC being off. |
Think we got something wrong? Email support@dnsfix.com with the domain and what you expected. We check every report.