Skip to main content

There’s a list of URLs that need to be granted access through firewalls from your KB that float around this forum. In anticipation of a new console going live in five days, are there any new exceptions that need to be made to our clients’ firewalls in order for endpoints to continue checking in?

List of URLs we currently allow traffic to:

*.webrootcloudav.com

Agent communication and updates

(Please note: Some firewalls do not support double dotted subdomain names with a single wildcard mask (i.e. g1.p4.webrootcloudav.com being represented by *.webrootcloudav.com) so some environments might require either *.p4.webrootcloudav.com or *.*.webrootcloudav.com

*.webroot.com

Agent messaging

https://wrskynet.s3.amazonaws.com/*

https://wrskynet-eu.s3-eu-west-1.amazonaws.com/*

https://wrskynet-oregon.s3-us-west-2.amazonaws.com/*

Agent file downloading and uploading 

*.webrootanywhere.com

Management portal and support ticket logs upload 

WSAWebFilteringPortal.elasticbeanstalk.com

Web Threat Shield

Hey there @lls ,

This would be a great question for our business support team. Please reach out to them here: https://www.webroot.com/us/en/business/support/contact


Reply