Firewall and proxy settings

If your organization uses a firewall, make sure to set it up so people in your organization can use Google services. Firewall rules should connect to the supported hosts and routes in this article. Otherwise, people might be blocked from their services or unable to use some features.

Set the hosts and routes in this article to Allowed in your firewall rules. They should be allowed even if you turn off the corresponding service in your Google Admin console. These hosts and routes are required for communication with Google and Google Workspace services.

Keep in mind:

Even if there's no current activity at these hosts, there might be future activity. IP addresses used by various domain names don't necessarily fall within any specific range.
The connection between your service and Google depends on factors such as the browser, the browser version, and networking conditions.
Some domain names resolve to IP addresses that don’t fall within any given address range.
Other Google services can use the same IP addresses that you use.

Firewall and proxy settings by service

Expand all | Collapse all

Drive and Sites hosts and settings

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

Google Drive for desktop proxies

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

Supported proxy discovery methods
- Windows—Domain Name System (DNS) and Dynamic Host Configuration Protocol (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.

Was this helpful?

How can we improve it?

Firewall and proxy settings

Firewall and proxy settings by service

Google Drive for desktop proxies

Related topic

Was this helpful?

Need more help?

Try these next steps: