Webroot has been installed on my computer for about 9 months, with no untoward events until today. Now our online edition of the local newspaper which we have subscribed to for years is coming up with the warning "Phishing attack ahead", which seems ludicrous. And if I click on "Tell me more about it" and then on "Unblock page and continue" it goes to a dark gray page with "Webroot SecureAnywhere" at the top and no way of getting out of it. The only way to read the paper that I could find is to turn off the anti-phishing function. Is there some way to exempt specific sites?
Page 1 / 1
Hello ?, Welcome to the Webroot Community.
I have to say that I've never experienced this issue.
But I did find an excellent post from our Silver VIP member ?
I would post the info here but it's much easier just to point you to the thread.
You can find it here.
If the steps he suggests don't work for you then please submit a trouble ticket so that support can have a look.
I hope this info helps,
BD
Thanks for info. Haven't had time to reinstall WSA, but wil give it a try. Since its only one site and only once a day its almost as easy to just turn off the anti-phishing while on the site. BTW this is happening on a recent install of Win 10.
Chances are that the 'block' is being triggered by an ad, or a specific 'ad server'. You can submit a request to have the site reviewed and the block removed by either submitting a Trouble Ticket with the web site in question and addressed to "For the BrightCloud Team" OR you can fill out the reclassification request form
It does take 24 to 48 hours usually for a site to be reviewed, but they DO check sites that are submitted. I requested a phishing link being shared on Facebook to be reviewed and it was blocked in well under 24 hours.
It does take 24 to 48 hours usually for a site to be reviewed, but they DO check sites that are submitted. I requested a phishing link being shared on Facebook to be reviewed and it was blocked in well under 24 hours.
Thanks for the suggestions. Right after I received an Adobe Reader update the problems disappeared. Since the problem site uses pdf files, I can only assume that was the problem. We shall see.
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.