JavaScript Restrictor
Network boundary shield
Network boundary shield prevents web pages to use the browser as a proxy between local network and the public Internet. See our blog post and Force Point report for examples of attacks handled by the Network Boundary Shield. The protection encapsulates the WebRequest API, so it captures all outgoing requests.
Generally, you want Network boundary shield protection active, however, some pages can be broken, because they require interaction between public Internet and local network, for example, some Intranet information systems might be broken by the Network boundary shield. JShelter users also reported increased number of false positives when using DNS-based filtering programs. If you use one, make sure that DNS returns 0.0.0.0 for the blocked domains.
You can disable the Network boundary shield by adding the domain (e.g. example.com) to the list below. The domains and all their subdomains listed bellow are not blocked by the Network boundary shield. To selectively deactivate the Network boundary shield, insert the domains to the list (excluding "www", but including all other domains eg. ".com"). We generally do not recommend disabling the Network boundary shield for domains from the public Internet.
Please note, that these domain names are checked with domain hierarchy, so whitelisting example.com does also whitelist news.example.com.