Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

Your proxy settings live in your operating system network configuration, and every browser except Firefox reads them from there. The fastest way to view them is from the command line: run netsh winhttp show proxy on Windows, scutil --proxy on macOS, or env | grep -i proxy on Linux. If you prefer a GUI, each OS exposes the same information under its network settings, which this guide walks through screen by screen.
Knowing exactly where to read your current proxy matters for testers and developers: a stale or mismatched proxy will silently break a local tunnel, a CI job, or a Selenium run against a cloud grid like TestMu AI. This page focuses purely on viewing and confirming your existing configuration, per OS, per browser, and from the command line. If you instead want to configure, disable, or troubleshoot a firewall and DNS, see the related questions at the end.
Windows actually keeps two proxy stores: the WinINET proxy used by browsers and most desktop apps, and the WinHTTP proxy used by Windows services and many command line tools. Checking both avoids the classic surprise where a browser works but a service or test runner cannot reach the network.
On macOS, proxies are configured per network service (Wi-Fi, Ethernet, VPN), so the answer can differ depending on which interface is active. The graphical view and the command line read the same configuration, but the command line is faster and scriptable.
Linux has no single proxy switch. Most tools read proxy environment variables, while desktop environments such as GNOME keep their own setting, and individual tools like apt and git can carry their own proxy. Check each layer that applies to your workflow.
Browsers split into two camps: those that inherit the OS proxy and Firefox, which maintains its own. This distinction is the single most common reason a proxy appears to be set in one app but not another.
When your settings show a PAC URL instead of a fixed proxy, the real routing rules live inside that script. The PAC URL surfaces as Use setup script on Windows, Automatic Proxy Configuration on macOS, and Automatic proxy configuration URL in Firefox.
A proxy can be configured yet still not be used, for example when a bypass rule excludes the host you are testing. The reliable check is to confirm your outbound IP address actually changes when the proxy is in effect.
Behind a corporate proxy or firewall, a local testing tunnel and your Selenium or Cypress jobs need the correct proxy details to reach the cloud grid. If the host or port is wrong, connections time out and tests fail before they even start. Checking your current settings first, then passing those exact values to TestMu AI Tunnel via the proxy flags documented in Lambda Tunnel Modifiers, prevents the most common class of local-testing failures. You generally do not need to change the OS proxy itself, only confirm it and reuse it.
Run a single command for your platform. On Windows, netsh winhttp show proxy prints either Direct access (no proxy server) or the configured proxy and bypass list. On macOS, scutil --proxy lists every active proxy. On Linux, env | grep -i proxy shows the proxy variables in your shell. If any returns a host and port, you are behind a proxy.
Manual settings specify an explicit proxy address and port that every request uses. Automatic settings either auto-detect the proxy with WPAD or point to a PAC script URL that decides, per request, which proxy or direct connection to use. When checking, note which mode is active, because automatic setups hide the real proxy address inside the PAC file.
Chrome, Edge, and Safari inherit the operating system proxy, so they always match the OS network settings. Firefox keeps its own independent proxy store, so it can be set to No proxy or a manual proxy even when the OS uses one. Always check Firefox separately in its Network Settings if your traffic is not routing as expected.
A PAC (Proxy Auto-Config) file is a JavaScript file containing a FindProxyForURL(url, host) function that returns which proxy a given URL should use, such as PROXY host:port or DIRECT. Its URL appears as Use setup script on Windows, Automatic Proxy Configuration on macOS, and Automatic proxy configuration URL in Firefox. Open the URL in a browser to read the script and see the real proxy rules.
Use netsh winhttp show proxy on Windows, scutil --proxy or networksetup -getwebproxy "Wi-Fi" on macOS, and env | grep -i proxy on Linux. These read the live configuration without opening any settings UI, which makes them ideal for scripts, CI jobs, and remote sessions.
If your machine sits behind a corporate proxy or firewall, your local test tunnel must be told about that proxy or its connection to the cloud grid will fail. You usually do not change the OS proxy itself; you pass the same host and port to the TestMu AI Tunnel. Check your current settings first, then supply them. Configuring or disabling the proxy is covered in the related questions below.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance