Docs · In practice

Checking and monitoring: where each connection went

Routekeeper shows what goes through the proxy, what goes direct and what went around it. Start with the one-minute check, and for full certainty, compare with your own server.

All docs sections

There are five places to check, from simple to detailed.

Menu bar

Whether the proxy works and which IP websites see.

Overview

The main thing in one line, and what to do about it.

Monitor

Every connection: which app, where to, and by which route.

Leaks

What went direct from apps that should go through the proxy.

Your server

An independent check: whether connections from your Mac arrive.

The one-minute check

  1. Click the Routekeeper icon in the menu bar. If everything works, there is a green status line under the name, and below it a line like IP 203.0.113.10 · NL. This is the external IP that websites see when traffic goes through the main proxy (the one most apps go through), and the country code. While the check is running, the line says Checking IP….
  2. Compare this address with your usual one: they should be different. If the proxy is your own server, you’ll see the server’s IP.
  3. Check the app itself. In a browser that goes through the proxy, open any page that shows your IP. In Terminal, if it goes through the proxy, run the command below. The address should match the IP in the menu bar.
    curl https://ipinfo.io/ip
  4. If there is no IP line, the status line is orange or gray. Open Overview: it says what happened and what to do.

The IP in the menu bar shows that the proxy works. It doesn’t prove that a specific app goes through the proxy. For that, use step 3 or the monitor.

You can also check each proxy on its own: the Proxy section, the Check button. It shows “Working”, the latency and the external IP, or the error text. For details, see Checking on the Proxies page.

Details: where the IP and latency come from

Routekeeper itself opens a connection through the proxy to the ipinfo.io service on port 80 and asks for the external address and country. The latency is the time it takes to open a connection through the proxy. This takes several round trips to the server, so for a distant server that works fine, 500–800 ms is normal.

The menu bar rechecks the main proxy when you open it, but no more than once a minute. While the main proxy is unreachable, it’s rechecked once a minute on its own. What else Routekeeper sends over the network is described on the Privacy page.

Overview

The main screen of the Routekeeper window, ⌘1. At the top is one line about the most important thing. Below it are what’s waiting for your answer, the routes, the counters and what’s going through the proxy right now. In a wide window, the routes and Through Proxies Now are on the left, and the Leaks and traffic cards are in a narrow column on the right.

  1. The headline: the most important thing in one line. “Everything works” means the routes work; below it, how many proxies they go through and what uses them. If something is wrong, the problem shows here (see the table below).
  2. A row for each proxy that routes go through: the dot (green means it answers), the country and external IP, the latency and its chart for the last hour, the icons of what goes through the route (a click lists it all; in a wider window the names show too), the speed and the share of traffic. The last row, Direct, is everything else.
  3. The “⋯” menu of each proxy: Check Again, Move Routes To (only this proxy’s routes) and All Proxies….
  4. The cards on the right: how many connections went around the proxy (if none, how many apps are being watched) and how much traffic went through the proxies, with a 3-minute chart. In a narrow window they sit side by side under the routes.
  5. Apps that sent data through a proxy in the last minute: which proxy, how many connections, the speed.
A sketch of the Overview section in a wide window with two proxies, both answering. The data is made up.

The headline: what happened and what to do

The headline always shows the most serious problem. In the table, the states go from most to least serious.

HeadlineWhat it meansWhat to do
Routekeeper is offThe Routekeeper On switch is off. Rules don’t apply, and everything goes direct.Click Enable.
All connections are blockedRoutekeeper couldn’t read its settings, so it blocks everything to make sure nothing goes around the proxy.Follow the banner above the headline. For details, see All connections are blocked.
Proxy provider isn’t running, Extension not responding and similarThe part of Routekeeper that runs in the system isn’t running or isn’t responding.See the banner above the headline and Settings → Extension. For details, see Reinstalling and stopping the extension.
No apps through a proxyNo route leads through a proxy.Click Add App….
Proxy “…” is unreachable, Proxies are unavailableNone of the proxies that your routes use answered. Connections from these apps break off and don’t go direct.Click Check Again, check the server, or move the routes to another proxy. For details, see the recipe The proxy stopped answering.
Leaks detectedIn the last hour, an app that should go through the proxy sent UDP direct, or one of its processes went outside the rule.Click Details in the line below the headline and apply the fix. For details, see Leaks.
Partly workingYou have several proxies, and some of them aren’t answering. What goes through them waits; the other routes work.In that proxy’s row, click Move to “…” or Check Again.
DNS queries go directThe main traffic goes through the proxy, but in the last hour an app sent DNS queries direct. The DNS provider may see your IP and the names of sites.In Leaks: for an app, Block DNS; for a browser, DNS over HTTPS.
Everything worksThe routes work. Below the headline is a summary: which apps go through which proxy, for example “Through “Amsterdam”: Slack, Chrome and others”. Whether there were leaks is shown by the Leaks card.Nothing.

One exception: if Settings → Network → If the proxy is down, go direct is on, connections go direct when the proxy is unreachable, but the headline won’t say so.

In version 0.2.1, any leak, including DNS, showed the Leaks detected headline, and there was no separate headline for DNS.

Below the headline

Lines appear here when there is something to do:

Routes

There is one row for each proxy that routes go through. The last row is Direct: everything else goes through your usual connection.

If a proxy doesn’t answer, its row is highlighted, and there are two buttons below it: Move to “…” (to another proxy, if possible one that passed its check) and Check Again. Check All is in the window’s toolbar, and the All Proxies link is next to the Routes heading. While Overview is open, Routekeeper rechecks the proxies used in your routes, but each one no more than once a minute.

To move all apps to another proxy in one go, use the panel at the bottom of the sidebar or the menu of the menu bar icon (there, if you have two or more proxies). For details, see Switching to another proxy.

Counters and “Through Proxies Now”

Monitor

A list of connections: which app, where to, and by which route. Open Monitor in the sidebar (⌘5) or in the menu of the menu bar icon.

The counters are filters

At the top are five cards: Through Proxy, Direct, Blocked, Leaks, Errors. Each shows a number and its share of all connections. Click a card, and only those connections stay in the list. Click it again to show all of them. Next to them is the Proxy Traffic card: the speed right now and how much has gone through the proxy since counting started.

The search field in the toolbar searches by domain, IP and app name.

Three views

Use the switch at the top of the window. The filter and search work in all three views.

A connection row

Select a row, and a panel with details appears below the table: IP, process number (PID), Decision (why the connection went this way: which rule, the mode, an automatic permission), Duration. For connections through the proxy, there are also Proxy latency and Traffic. For an error, the panel gives its cause; for a leak, a tip.

The buttons on the panel:

Right-click a row to open a menu: Create Rule…, Block This Host, This Host Through “…”, Copy Host, Copy IP. For several rows: Copy Hosts or ⌘C.

Pause, export and clearing

Map

Details: what is stored, and how much
  • The network extension keeps the last 5000 connections in memory and doesn’t write them to disk. After the extension or the Mac restarts, the list starts over.
  • The counters count from the moment the extension started or from the last Clear.
  • While the Routekeeper On switch is off, connections aren’t recorded.
  • The Direct counter also includes leaks: they went direct too. The Direct filter doesn’t show them; they’re in the Leaks filter.

Leaks

The Leaks section, ⌘6. It shows connections from apps that should go through the proxy but went direct. If there are none, the section is empty and says No Leaks.

Rows are grouped by process and kind, so two helpers of one app show up as two rows with the same name. Each row shows the app, the kind, how many times it happened (× N), up to four addresses, a tip and a fix button. The most serious are at the top.

  1. The Leaks section. The number next to it is how many leaks there have been since counting started.
  2. The app, the kind and how many times. The color shows how serious it is: red is Process outside the rule, orange is UDP around the proxy, yellow is DNS around the proxy. The most serious are at the top.
  3. Up to four addresses the connections went to, and a tip on what to do.
  4. The fix button. Through “Amsterdam” adds a rule that sends this process through the main proxy. Block UDP turns on Block UDP and QUIC for the proxy the app goes through.
  5. Browsers get no Block DNS button: turn on DNS over HTTPS in the browser instead, see the recipe DNS over HTTPS in the browser. Other apps do get this button.
A sketch of the Leaks section with all three kinds of leaks. The data is made up.
KindWhat happenedFix button
Process outside the rule
red, the most serious
A process from the same app (or, for command-line programs, from the same developer) wasn’t covered by the app’s rule and connected directly. It’s usually a helper process, when Include Child Processes is off.Through “…” adds a rule: this process through the main proxy. Or turn on Include Child Processes.
UDP around the proxy
orange
The app’s UDP traffic went direct because Block UDP and QUIC is off for its proxy. Most often it’s QUIC in a browser, or calls.Block UDP turns on Block UDP and QUIC for this app’s proxy. If the proxy can’t be determined, it adds a rule that blocks UDP for this process. After that, the app switches to TCP, and calls over UDP stop working. See UDP: calls, voice and games.
DNS around the proxy
yellow, the least serious
The app itself sent a DNS query direct. The main traffic goes through the proxy, but the DNS provider may see your IP and the site’s name.Block DNS adds a rule that blocks port 53 for this process. Browsers don’t get this button; see below.

For more about UDP, see UDP and QUIC. For more about the proxy switches, see DNS through proxy and UDP blocking.

Browsers: DNS over HTTPS instead of blocking

If you close port 53 for a browser, it will stop opening sites. That’s why browsers don’t get the Block DNS button. Instead, turn on “DNS over HTTPS” (DoH) in the browser itself. Then the browser looks up site addresses inside an ordinary HTTPS connection, and that connection goes through the proxy along with the rest of the traffic.

BrowserWhere to turn it on
ChromePaste chrome://settings/security into the address bar. Turn on “Use secure DNS” and choose a provider from the list, not your current one.
Edgeedge://settings/privacy → the “Security” section → “Use secure DNS to specify how to look up the network address for websites”. Choose a provider from the list.
Firefoxabout:preferences#privacy → “DNS over HTTPS” → under “Enable secure DNS using”, choose “Increased Protection” or “Max Protection”.
Bravebrave://settings/security → “Use secure DNS”. Choose a provider from the list.

The names depend on the browser version. If you can’t find the setting, type “DNS” in the settings search. After you turn it on, restart the browser, and new DNS around the proxy rows will stop appearing for it. For step-by-step instructions, see the recipe DNS over HTTPS in the browser.

Details: which DoH option is more reliable, and which browsers are recognized
  • With the current-provider option in Chrome, Edge and Brave, and with “Default Protection” or “Increased Protection” in Firefox, the browser may fall back to ordinary DNS if secure DNS isn’t available. “Max Protection” in Firefox and a provider chosen from the list in Chrome, Edge and Brave don’t do this.
  • Routekeeper treats these apps as browsers: Chrome (all channels), Chromium, Edge (except Canary), Brave, Arc, Vivaldi, Opera, Firefox (including Developer Edition and Nightly), Zen, Waterfox and Yandex Browser.
  • Safari looks up addresses through the macOS system service, so its DNS queries don’t show up in Leaks.
  • The service queries ipv4only.arpa and _dns.resolver.arpa are the same for everyone and say nothing about you. Routekeeper doesn’t flag them.

Notifications

In Settings → General → Notifications, there are two switches, and both are on: About leaks around the proxy and About connections the proxy couldn’t make. So as not to flood you with messages, Routekeeper sends at most one notification every 10 minutes for each kind of problem in a given app.

Notifications arrive while the Routekeeper app is running, even if its window is closed. macOS asks for permission to show them at first launch. If you declined, turn them on in System Settings → Notifications → Routekeeper.

What Routekeeper notices and what it doesn’t

Routekeeper checks only apps whose whole traffic goes through the proxy, that is, apps with the Through Proxy route in the Apps section. If an app is set to go direct, or goes through the proxy only for certain addresses, Routekeeper treats that as your decision, not as a mistake.

SituationNoticed?What you see
An app with a route through the proxy sends a DNS query over UDP by itself (port 53 or 853)YesDNS around the proxy. The query goes direct: Routekeeper flags it but doesn’t block it until you add a rule.
UDP or QUIC from such an app when Block UDP and QUIC is offYesUDP around the proxy.
The same when Block UDP and QUIC is on (the default)Not flaggedUDP is blocked and shown as Blocked in the monitor.
A process from the same app or the same developer isn’t covered by the rule and connects directly over TCPYesProcess outside the rule.
A browser or app goes through the proxy only by domain or service rules, and its own route is DirectNoIts DNS, QUIC and all other addresses go direct as part of its usual route. You can close QUIC with a rule; see the recipe One service in the browser through a proxy.
Name lookups that the macOS system service makes on behalf of an app (this is how most programs and Safari work)NoThe service sends them, not the app, and Routekeeper doesn’t link them to the app.
Apple push notifications (the apsd system process)No, and that’s normalapsd is a separate macOS process, and it goes direct. It isn’t the app’s own traffic.
A program from another developer that the app starts, when Include Child Processes is offNoIt follows its own route or the mode.
Connections in the first seconds after the extension restarts or updatesNoThe extension doesn’t see them. See Pause when the extension restarts.
The Routekeeper On switch is offNoEverything goes direct, and the monitor doesn’t record anything.
An app routed through a proxy connected to an address on a local network: your home network, a corporate VPN, TailscaleNot countedIt goes direct because of the Local networks go direct setting. The Decision field says “local network, past the proxy of the rule for …”.
Connections to the proxy server itself and inside the MacNot countedThat’s as it should be.
Details: the exact checking rules
  • Which app counts as “through the proxy”. Routekeeper takes the rule that would apply to an arbitrary TCP connection from this app to an unknown address. If that rule leads through a proxy, the app is checked. This can be the app’s route or a general “any app → proxy” rule.
  • DNS means ports 53 and 853. Over UDP, such queries don’t go through the proxy: proxies carry only TCP. DNS over HTTPS is an ordinary HTTPS connection to port 443. It goes through the proxy and doesn’t count as a leak.
  • Process outside the rule is checked only for TCP and only for “whole app → proxy” rules. The process must be inside this app’s bundle. If the rule is for a command-line program, any other command-line program from the same developer (Team ID) counts.
  • History. The section shows the connections that are still in the monitor. The counter in Overview also remembers older ones, until you click Clear or the extension restarts.

Checking on your own server

The most independent check is to look on the server and see whether connections from your Mac arrive. The commands below are for a server set up with the Your own proxy server guide: there, the proxy is Caddy on port 443.

  1. Find out your usual address. In a browser that goes direct (for example, Safari, if you haven’t routed it through the proxy), open any page that shows your IP. Write it down.
  2. Connect to the server over SSH, the same way as during installation.
  3. Look at the open connections to Caddy on port 443:
    ss -tnp state established '( sport = :443 )'
    The Peer Address:Port column shows the addresses the connections came from. Your address from step 1 should be among them, and the last column should mention caddy. The address may be written as [::ffff:198.51.100.7]:51234; it’s the same IPv4 address.
  4. Count the connections from your address only, and watch how the number changes. Put in the address from step 1:
    watch -n 2 "ss -tn state established '( sport = :443 )' | grep -c YOUR_IP"
    On your Mac, open an app that goes through the proxy and start using it: the number goes up. Close the app, and the number goes down as its connections close. To exit watch, press Ctrl+C.

Keep in mind that Routekeeper itself checks the proxy through this same server, so one or two connections may show up even when your apps are closed.

On the Mac

Open Terminal and look at the open connections to the server. Put in the server’s IP:

netstat -an -p tcp | grep ESTABLISHED | grep 'SERVER_IP.443'

Each line is one connection to the proxy. macOS writes the port after a dot: 203.0.113.10.443. If the server is entered as a domain in Routekeeper, find out its IP:

dig +short DOMAIN
Details: which process holds these connections

Connections to the proxy are opened by Routekeeper’s network extension on behalf of the apps, so the app names don’t appear here. To see which app went where, use the monitor. To see the process, you need an administrator password:

sudo lsof -nP +c 0 -iTCP@SERVER_IP:443 -sTCP:ESTABLISHED

The COMMAND column will show a process whose name starts with Routekeeper. If you see a different program there, something else is also connecting to the server, for example a proxy client.

Checked against the Routekeeper code (version 0.2.1 and the one after it) on October 4, 2026.