Yes, Steven Winderlich, I agree with you here.

They need not precise what risks the blocked registrar site may have,
but users should be alerted in cases where for instance:
sslv2: server still supports SSLv2 or
possibly risky http-methods are being used,
or redirecting re-directs come from an open proxy.
All insecure methods that attackers could abuse.
Avast should not allow their users to arrive at without an alert,
same as GoogleSafebrowsing, but that also can miss issues and detection.

I think this is something for a new Shield because avast does not for instance scan https.
That is why users here are not using "https: only"because that is a blind angle where the avast detection is concerned.
Avast does not scan https sites…
It ought to be brought in, but when will this be?
With all the coming DNS spoofing and hijacking coming in the foreseeable future,
it sure is a must to pre-check this possible malcode arena and their possible threats,

polonus