Drive and Sites firewall and proxy settings

This article is for network administrators.

For users on your network to access Google Drive, Google Docs editors, and new Google Sites, connect your firewall rules to the following hosts and ports. Otherwise, users might be blocked or denied access from these services.

Note: When a host includes [0–9], you should allow a host with each single decimal digit. For example, for *.clients[0–9].google.com:443/HTTPS, you allow *.clients0.google.com:443:HTTPS, *.clients1.google.com:443:HTTPS, *.clients2.google.com:443:HTTPS, and so on.

• www.google.com:443/HTTPS
• accounts.google.com:443/HTTPS
• googledrive.com:443/HTTPS
• drive.google.com:443/HTTPS
• *.drive.google.com:443/HTTPS
• drive.usercontent.google.com:443/HTTPS
• drive-data-export.usercontent.google.com
• drive-data-export-eu.usercontent.google.com
• docs.google.com:443/HTTPS
• *.docs.google.com:443/HTTPS
• *.c.docs.google.com:443/HTTPS
• sheets.google.com:443/HTTPS
• slides.google.com:443/HTTPS
• takeout.google.com:443/HTTPS
• gg.google.com:443/HTTPS
• script.google.com:443/HTTPS
• ssl.google-analytics.com:443/HTTPS
• video.google.com:443/HTTPS
• s.ytimg.com:443/HTTPS
• apis.google.com:443/HTTPS
• *.clients[0–9].google.com:443/HTTPS
• *.googleapis.com:443/HTTPS
• *.googleusercontent.com:443/HTTPS
• *.gstatic.com:443/HTTPS
• *.gvt1.com:443/HTTPS
• lh[0–9].google.com:443/HTTPS
• [0–9].client-channel.google.com:443/HTTPS
• clients[0–9].google.com:443/HTTPS
• inputtools.google.com:443/HTTPS
• sites.google.com:443/HTTPS
• sites.google.com:80/HTTP
• sites.google.com:443/HTTPS
• *.sites.google.com:443/HTTPS
• *.googlegroups.com:443/HTTPS
• ipv4.google.com:443/HTTPS
• ipv4.google.com:80/HTTP

About IP addresses and proxies

Techniques that Drive and Sites use to connect to Google servers depend on the browser, browser version, networking conditions, and so on.

IPs

• The IP addresses that some domain names resolve to don't necessarily fall within any given address range.
• Other Google properties might use the IP addresses that Drive and Sites use.
• Even if you don't see activity at the addresses previously listed, there could be future activity.

Google Drive for desktop proxies

To ensure your users can use Drive for desktop successfully, review the following proxy information.

Supported proxy discovery methods

• Windows: Domain Name System (DNS) and DHCP
• macOS: DNS

Decrypting proxy

Drive for desktop encrypts all network traffic and validates host certificates to protect against man-in-the-middle (MITM) attacks. If you use a decrypting proxy, configure the TrustedRootCertsFile setting for Drive for desktop.

Buffered proxy

If you use a buffered proxy, you may need to disable buffering in the proxy for the following host: fcmconnection.googleapis.com.

Authenticated proxy

Drive for desktop doesn't support authenticated proxies with a password.

Related topics

Configure Google Drive for desktop