However, after visiting some of the blacklist sites (like URLvoid.com), I see no listing of this site being blacklisted. If this is a false-positive, what has to be done to remove the page from the avast blockages? Or, if it’s a genuine blacklisted site, upon whose authority was it blacklisted (URL, please)?
By the same token, a server redirect does not necessarily make a site (or the redirected site) toxic.
So, avast will flag a site, merely because it redirects to another site? Perhaps I’m missing something. My inquiry here is based on the fact that (at least) two people I know have visited the site and it was not blocked by their antivirus software … nor have their computers been compromised in any way that their antivirus software can detect.
Hmm. 1 database (spamhaus.org) shows it blacklisted, the other 30 databases do not. So, avast blocks a site based on the say-so of 1 out of 31 databases? I’m not saying this blockage was unwise. But spamhaus.org has been known to be “heavy-handed” in the past in adding sites they don’t like to their database. I suspect that, in part, that’s why the hacking group “Anonymous” subjected them to DDOS attacks last month.
But according to the link you provided me in your last post, and out of the 31 databases listed, only spamhaus.org’s database had them blacklisted. Was there another factor used by avast in determining that the site should be blocked? BTW, if you don’t recall, spamhaus.org listed “Amazon.com” on one of their 2010 blacklists (sigh). It was later discovered to be a false-positive.
This would be funny if it wasn’t so sad. This morning, I received an email from avast! support. It had this subject line (“xx” substituted for “tt” to block link):
And, their message to me read as follows:
avast!: Message body was removed because it contained a virus.
Yup, hehe, either support sent me a message that included a virus … or the nature of their message referred to a false-positive that avast! “still” considers toxic. So, whatever avast! support wanted to say to me was lost due to (ahem) avast! sending it into quarantine.
I just did. But this is apparently not a “Trojan Horse” problem. It’s the way “avast!” alerts customers that the referred site is considered a fraudulent site. And this issue has been talked about as an “avast!” problem since 2011. For example:
In any case, I just asked support to close their support ticket. I got a repeat of their May 2nd email - which I couldn’t read either because “avast!” (on my computer) blocked ITS OWN EMAIL - sending it to the virus vault.