Your domain, checked and fixed.

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

What no outside checker can see

What our side-by-side tests changed

WhenChange
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.

Check your domain nowCheck a record before you paste it