Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: cheater87 on March 15, 2014, 04:54:31 AM

Title: Does Browser Protection module block bad sites if they are red?
Post by: cheater87 on March 15, 2014, 04:54:31 AM
My friend is wondering if it can.
Title: Re: Does Browser Protection module block bad sites if they are red?
Post by: Para-Noid on March 15, 2014, 04:07:35 PM
No! The web shield will.
Title: Re: Does Browser Protection module block bad sites if they are red?
Post by: Cast on March 15, 2014, 04:52:14 PM
Yeah the browser protection module will block the site, I have had it block a couple when I had enabled.
Title: Re: Does Browser Protection module block bad sites if they are red?
Post by: Para-Noid on March 15, 2014, 04:55:44 PM
When I was trying out the browser protection (AOS) I found that it did
nothing in the way of site blocking. It was always the web shield that
did the actual blocking.
Title: Re: Does Browser Protection module block bad sites if they are red?
Post by: polonus on March 15, 2014, 05:00:34 PM
Hi Cast,

You'd better have these avast! shields enabled always!
This is the very best part of the overall avast detection and it is very accurate too.
It blocks access to these sites upon detection,
so your computer do not even connects out to malcode and cannot connect to it period!

Disabling it or making exclusions is putting your computer's security on the line.
I know I have been figthing these malsite contents  from within the trenches on the virus and worms every day over the last 10 years.
Want proof of this puding  ;), read here now: http://forum.avast.com/index.php?topic=147639.msg1072105#new

polonus
Title: Re: Does Browser Protection module block bad sites if they are red?
Post by: Cast on March 15, 2014, 05:01:32 PM
Well in my case I know it wasnt the webshield blocking it because at the time I had a extension that acted as a proxy enabled and avast wasnt scanning my webtraffic in Dragon. The extension still blocked the page.

Edit: I use the webshield, just at the time because of the extension the traffic wasnt being scanned. I dont use the proxy extension anymore anyway.