> And that's unlikely to change, because getting nothing at all isn't a very desirable state of affairs. It worked for HTTPS - more and more browser builds ref

> And that's unlikely to change, because getting nothing at all isn't a very desirable state of affairs. It worked for HTTPS - more and more browser builds refuse to show you stuff, with no workaround, even if there is nothing wrong with the certificates ( cough-sha1-cough-or-cough-chrome-cert-transparency-cough ). Yet I don't see any users revolt. Claiming that having an all-or-nothing HTTPS is a-ok, yet having all-or-nothing DNS is unacceptable is... inconsistent.