Split Tunnels

Split Tunnels can be configured to exclude or include IP addresses or domains from going through WARP. This feature is commonly used to run WARP alongside a VPN (in Exclude mode) or to provide access to a specific private network (in Include mode).

Warning

Split Tunnels only impacts the flow of IP traffic. DNS requests are still resolved by Gateway and subject to DNS policies unless you add the domains to your Local Domain Fallback configuration.

Because Split Tunnels controls what Gateway has visibility on at the network level, we recommend testing all changes before rolling out updates to end users. It may take up to 24 hours for changes to propagate to clients, depending on how many devices are connected to your organization.

Change Split Tunnels mode

1. In Zero Trust ↗, go to Settings > WARP Client.

2. Under Device settings, locate the device profile you would like to modify and select Configure.

3. Scroll down to Split Tunnels.

4. (Optional) To view your existing Split Tunnel configuration, select Manage. You will see a list of the IPs and domains Cloudflare Zero Trust excludes or includes, depending on the mode you have selected. We recommend making a copy of your Split Tunnel entries, as they will revert to the default upon switching modes.

5. Under Split Tunnels, choose a mode:

   • Exclude IPs and domains — (Default) All traffic will be sent to Cloudflare Gateway except for the IPs and domains you specify.
   • Include IPs and Domains — Only traffic destined to the IPs or domains you specify will be sent to Cloudflare Gateway. All other traffic will bypass Gateway and will no longer be filtered by your network or HTTP policies. In order to use certain features, you will need to manually add Zero Trust domains.

All clients with this device profile will now switch to the new mode and its default route configuration. Next, add or remove routes from your Split Tunnel configuration.

Add a route

1. In Zero Trust ↗, go to Settings > WARP Client.

2. Under Device settings, locate the device profile you would like to modify and select Configure.

3. Under Split Tunnels, check whether your Split Tunnels mode is set to Exclude or Include.

4. Select Manage.

5. You can exclude or include routes based on either their IP address or domain. When possible we recommend adding an IP address instead of a domain. To learn about the consequences of adding a domain, refer to Domain-based Split Tunnels.

add an ip

To add an IP address to Split Tunnels:

1. Select IP Address.
2. Enter the IP address or CIDR you want to exclude or include.
3. Select Save destination.

Traffic to this IP address is now excluded or included from the WARP tunnel.

add a domain

To add a domain to Split Tunnels:

1. Select Domain.
2. Enter a valid domain to exclude or include.
3. Select Save destination.
4. (Optional) If your domain does not have a public DNS record, create a Local Domain Fallback entry to allow a private DNS server to handle domain resolution.

When a user goes to the domain, the domain gets resolved according to your Local Domain Fallback configuration (either by Gateway or by your private DNS server). WARP Split Tunnels will then dynamically include or exclude the IP address returned in the DNS lookup.

You can add up to 1000 combined Split Tunnel and Local Domain Fallback entries to a given device profile.

We recommend keeping the Split Tunnels list short, as each entry takes time for the client to parse. In particular, domains are slower to action than IP addresses because they require on-the-fly IP lookups and routing table / local firewall changes. A shorter list will also make it easier to understand and debug your configuration.

When to use Split Tunnels

Use Split Tunnels when you need to bypass Gateway entirely for a site or allow traffic through the firewall that WARP creates. Common scenarios include:

• Connect to a third-party application which requires the actual IP address of the end-user device (for example, Microsoft 365).
• Optimize voice and video.
• Connect to a third-party VPN endpoint.

When not to use Split Tunnels

Do not exclude a site from Split Tunnels if you want to see the traffic in your Gateway logs. In particular, we do not recommend using Split Tunnels to:

• Solve connectivity issues with a specific website. For configuration guidance, refer to our troubleshooting guide.
• Solve performance issues with a specific website. Since Cloudflare operates within 50 milliseconds of 95% of the Internet-connected population, it is usually faster to send traffic through us. If you are encountering a performance-related issue, it is best to first explore your Gateway policies or reach out to Support.

Cloudflare Zero Trust domains

Many Cloudflare Zero Trust services rely on traffic going through WARP, such as device posture checks and WARP session durations. If you are using Split Tunnels in Include mode, you will need to manually add the following domains in order for these features to function:

• The IdP used to authenticate to Cloudflare Zero Trust
• <your-team-name>.cloudflareaccess.com
• The application protected by the Access or Gateway policy
• edge.browser.run if using Browser Isolation

Domain-based Split Tunnels

Domain-based split tunneling has a few ramifications you should be aware of before deploying in your organization:.

• Routes excluded or included from WARP and Gateway visibility may change day to day, and may be different for each user depending on where they are.
• You may inadvertently exclude or include additional hostnames that happen to share an IP address. This commonly occurs if you add a domain hosted by a CDN or large Internet provider such as Cloudflare, AWS, or Azure. For example, if you wanted to exclude a VPN hosted on AWS, do not add *.amazonaws.com as that will open up your devices to all traffic on AWS. Instead, add the specific VPN endpoint (*.cvpn-endpoint-<UUID>.prod.clientvpn.us-west-2.amazonaws.com).
• Most services are a collection of hostnames. Until Split Tunnels mode supports App Types, you will need to manually add all domains used by a particular app or service.
• WARP must handle the DNS lookup request for the domain. If a DNS result has been previously cached by the operating system or otherwise intercepted (for example, via your browser’s secure DNS settings), the IP address will not be dynamically added to your Split Tunnel.

Valid domains

Split tunnel domain	Matches	Does not match
example.com	exact match of example.com	subdomains such as www.example.com
example.example.com	exact match of example.example.com	example.com or subdomains such as www.example.example.com
*.example.com	subdomains such as www.example.com and sub2.sub1.example.com	example.com

Platform differences

Domain-based Split Tunnels work differently on mobile clients than on desktop clients. If both mobile and desktop clients will connect to your organization, it is recommended to use Split Tunnels based on IP addresses or CIDR, which work the same across all platforms.

Windows, Linux and macOS

Clients on these platforms work by dynamically inserting the IP address of the domain immediately after it is resolved into the routing table for split tunneling. This allows the desktop clients to support wildcard domain prefixes (for example, *.example.com), not just a singular domain (like example.com or www.example.com).

iOS, Android and ChromeOS

Due to platform differences, mobile clients can only apply Split Tunnels rules when the tunnel is initially started. This means:

• Domain-based Split Tunnels rules are created when the tunnel is established based on the IP address for that domain at that time. The route is refreshed each time the tunnel is established.

• Wildcard domain prefixes (for example, *.example.com) are supported only if they have valid wildcard DNS records. Other wildcard domains are not supported because the client is unable to match wildcard domains to hostnames when starting up the tunnel. Unsupported wildcard domain prefixes can still exist in your configuration, but they will be ignored on mobile platforms.

Remove a route

Warning

Removing default Split Tunnel entries may cause users to lose Internet connectivity or block their access to local resources.

1. In Zero Trust ↗, go to Settings > WARP Client.

2. Under Device settings, locate the device profile you would like to modify and select Configure.

3. Under Split Tunnels. select Manage.

4. Find the IP address or hostname in the list and select Delete.

If you need to revert to the default Split Tunnel entries recommended by Cloudflare, select Restore default entries.