Set up SSL inspection on Chrome devices

1) Set up a hostname whitelist

For Chrome devices to work on a domain with SSL inspection, some hostnames need to be exempt from inspection. This is because certificates can only be imported at the user level and are only honored for user-level traffic. Some device-level traffic doesn’t use the SSL certificate to protect users against certain kinds of security risks.

To ensure that Chrome devices work with SSL inspection, you need to whitelist the following hostnames on your proxy server. For details on how to whitelist hostnames, check with your web filter provider.


  • December 22, 2017: Added alt*
  • July 13, 2017: Added[country].
  • March 1, 2017: Added hostname to whitelist for Chrome devices using Android apps
  • January 19, 2017: Removed
  • September 28, 2016: Added
  • December 2, 2015: Added hostnames to whitelist for single-app kiosk devices.
  • August 5, 2015: Added

Hostname whitelist for all Chrome devices[country]1

1 For[country], use your local top-level domain for [country]. For example, for Australia use, and for United Kingdom use

2If you're running Chrome OS version 62 and you're seeing the error "Device cannot connect to any wireless network" or "Network not available," you may need to whitelist the host alt* through your firewall on port 80. If this doesn't resolve the issue, see this full list of hosts to whitelist.

Additional hosts to whitelist

If you're using a Chrome device as a single-app kiosk or the Google Play Store on a Chrome device, you need to whitelist the additional hostnames below for SSL inspection to work correctly.

Hostname whitelist for single-app kiosk devices

If you use single-app kiosk devices, whitelist the following hostnames in addition to the hostnames listed above:

Hostname whitelist for Chrome devices using Android apps (Google Play Store)

If you use Android apps on Chrome devices (Google Play Store), whitelist the following hostname in addition to the hostnames listed above under Hostname whitelist for all Chrome devices.

Was this article helpful?
How can we improve it?