On corporate network

This graphic is an example of how ETP Client functions when it’s on a corporate network.

Network flow of ETP Client on corporate network
These steps apply:
  1. Requests are directed to ETP DNS. If DNS over TLS is enabled, requests are encrypted with TLS.
  2. If a threat is detected, ETP Client handles the request based on the policy configuration. For example, if a threat category is assigned the block action with an error page response, the request is resolved to the IP address of the Website Access Prohibited error page. This page does not include any of the customization that is configured for error pages in ETP.
  3. If no threat is detected, requests are forwarded to the corporate (local) DNS resolver for resolution. Requests to websites in the internal network are resolved by the corporate resolver. If a domain is not resolved by the corporate DNS resolver, it is resolved by ETP.