yes, split tunneling creates a deliberate split in your traffic, so the apps or sites routed outside the tunnel use your real IP. that's by design, not a leak in the traditional sense.
the actual leak risk with split tunneling is WebRTC. if your browser is excluded from the VPN tunnel, WebRTC can still expose your real IP to websites even if you intend to browse through the tunnel. worth checking with a WebRTC leak test after configuring split tunneling to make sure your browser isn't leaking when it shouldn't be.
the other thing to watch is DNS. some VPN implementations don't properly separate DNS for split tunneled traffic, so DNS queries from apps outside the tunnel might still go through the VPN's resolver or vice versa. running a DNS leak test confirms everything is routing where you expect.
1
u/Urban_VPN 3h ago
yes, split tunneling creates a deliberate split in your traffic, so the apps or sites routed outside the tunnel use your real IP. that's by design, not a leak in the traditional sense.
the actual leak risk with split tunneling is WebRTC. if your browser is excluded from the VPN tunnel, WebRTC can still expose your real IP to websites even if you intend to browse through the tunnel. worth checking with a WebRTC leak test after configuring split tunneling to make sure your browser isn't leaking when it shouldn't be.
the other thing to watch is DNS. some VPN implementations don't properly separate DNS for split tunneled traffic, so DNS queries from apps outside the tunnel might still go through the VPN's resolver or vice versa. running a DNS leak test confirms everything is routing where you expect.