There have been a lot of times that I have had a call from a customer who is complaining that Webroot is blocking access to a Website that they have accessed many times before, and that others in the company (and also myself) who are using Webroot are not affected.

 

I have also checked the Webroot Brightcloud website checker which has showen the website to be trustworthy.

 

The only way I had gotten around this in the past was to set the policy to 'Unmanaged' and allow the customer to click 'continue' and enter the captcha code which created the override, then changing the policy back.

 

Recently, I tried using a MD5 hash generator and translating 'http://www.example.com' into a MD5 and creating an override for that MD5 as good.

 

The customer responded shortly to advise that they can now get through, but part of me thinks it may just be a coincidence.

 

Would / should this work to allow access to mistakenly blocked websites? Would definitely be a much quicker and practical solution which also makes us and Webroot look better as we are seen to manage it better.

 

Many thanks!

Andrew