Docs · Reference

Glossary: terms in plain words

Short explanations of the words used in the docs. For each one: what it is and how it relates to Routekeeper.

All docs sections

The terms are grouped by topic. Other docs pages link here the first time a term appears.

Proxy · SOCKS5 · HTTP CONNECT · HTTPS proxy · Fail-closed · VPS · SSH · Domain · A record · IP address · Port · TCP · UDP · QUIC · DNS · DoH · TLS · Network extension · Child process · Code signature · localhost · Local network · Subnet (CIDR) · Wildcard *.domain

Proxies

Proxy (proxy server)

A go-between server between your Mac and a site. An app sends its connection to the proxy, and the proxy connects to the site on its own behalf. So the site sees the proxy’s IP address, not yours. Unlike a VPN, a proxy doesn’t work for the whole Mac, only for the connections that are sent to it.

In Routekeeper: you decide which apps and services go through a proxy; you add the proxies themselves in the Proxy section. See Proxies.

SOCKS5

A general-purpose proxy protocol: it carries any TCP connection without looking into its content. Clients running on the same Mac often open it, for example at 127.0.0.1:1080. SOCKS5 itself doesn’t encrypt the connection to the proxy, so for a proxy somewhere on the internet, an HTTPS proxy is a better fit.

In Routekeeper: the SOCKS5 type, default port 1080. Strings that start with socks5://, socks5h:// or socks://, and strings with no scheme, are treated as SOCKS5.

HTTP proxy (HTTP CONNECT)

A proxy that an app talks to over HTTP. With the CONNECT command, the app asks the proxy to open a tunnel to the right site and port, and after that the data goes through as is. HTTPS sites stay encrypted, but the connection to the proxy itself isn’t: the login, the password and the site names can be seen on the way. Such proxies are common in office networks.

In Routekeeper: the HTTP type, default port 8080. Authentication works only with a login and password (Basic); NTLM, Kerberos and PAC files aren’t supported.

HTTPS proxy

The same HTTP CONNECT, but the connection to the proxy is protected by TLS, like a site with https://. Neither the login and password nor the names of the sites you open can be seen on the way. The server proves that it’s genuine with a certificate issued for its domain name.

In Routekeeper: the HTTPS type, default port 443. In the Server field, enter the domain, not the IP: the certificate is checked against it. The script from Your own proxy server installs such a proxy on your own server.

Fail-closed: if the proxy is down, connections don’t go direct

This is the name for behavior where a failure doesn’t open anything up. If the proxy is down, the connection is cut instead of going direct. The app shows a network error, but your real address isn’t revealed. The opposite behavior is called fail-open.

In Routekeeper: this is how it works by default. To let connections go direct when the proxy is down, turn on Settings → Network → If the proxy is down, go direct. Exceptions: DNS over UDP, UDP when Block UDP and QUIC is off, and a couple of seconds while the extension restarts or updates. See Limitations.

Servers and addresses

VPS

A virtual server that you rent from a hosting provider, usually by the month. It has its own permanent public IP address and usually runs Linux, such as Debian or Ubuntu. You manage it remotely, over SSH.

In Routekeeper: you can install your own HTTPS proxy on a VPS with one script. See Your own proxy server.

SSH

A secure way to manage a server from Terminal on your Mac: you type commands, and they run on the server. Connecting looks like this: ssh root@203.0.113.7, that is, the user name, @ and the server’s address. The first time you connect, SSH shows the fingerprint of the server’s key and asks whether to trust it.

In Routekeeper: you need SSH once, to run the proxy install script on the server. See Your own proxy server.

Domain (domain name)

A human-friendly name of a site or a server, for example example.com. A subdomain is a name inside a domain: proxy.example.com. Domains are bought from a registrar, and there are also free names like my-name.duckdns.org.

In Routekeeper: an HTTPS proxy needs a domain, and rules can be written for domains. See a domain for your own server and how to write an address in a rule.

A record

A record in DNS that links a domain name to an IPv4 address. This is how computers find out that proxy.example.com is, for example, 203.0.113.7. You create it where you manage the domain; a new record usually starts working within a few minutes.

In Routekeeper: for your own server, the domain’s A record must point to your VPS’s IP, or the server won’t get a certificate. See Your own proxy server.

IP address

The numeric address of a device on a network: IPv4, like 203.0.113.7, or IPv6, like 2001:db8::1. Your external IP is the address that sites see your connection coming from; at home, it’s usually your provider’s address. Through a proxy, sites see the proxy’s IP.

In Routekeeper: the proxy’s external IP is shown in the icon’s menu and after you click Check; in rules, you can use an IP address or a subnet.

Port

A number that tells apart different services at the same address, like an apartment number in a building. HTTPS sites use port 443, HTTP sites use port 80, and DNS uses port 53.

In Routekeeper: a proxy has a port (by default 1080 for SOCKS5, 8080 for HTTP, 443 for HTTPS), and a rule can be limited to a port, for example “port 443 · UDP”.

How data travels

TCP

A way of sending data that sets up a connection and confirms delivery: if a piece gets lost, it’s sent again. Sites, email and most apps run on TCP.

In Routekeeper: TCP is what goes through the proxy.

UDP

A way of sending data with no connection and no confirmations: the data is simply sent. This is faster, so UDP is used by calls, real-time video, games, DNS and QUIC.

In Routekeeper: SOCKS5, HTTP and HTTPS proxies don’t carry UDP, so for apps that go through a proxy, UDP is either blocked or goes direct and is flagged. See UDP and QUIC.

QUIC

A modern way to load sites over UDP; HTTP/3 runs on it. Browsers use it where the site supports it. If QUIC isn’t available, the browser quietly switches to regular HTTPS over TCP.

In Routekeeper: the Block UDP and QUIC switch turns QUIC off for apps that go through a proxy, and browsers switch to TCP, which goes through the proxy.

DNS

The internet’s lookup service: it turns a name like example.com into an IP address. Usually lookups go to your provider or your router, and they see which names your Mac asks about. Regular DNS lookups go over UDP to port 53 and aren’t encrypted.

In Routekeeper: DNS through proxy passes the site name to the proxy, so that the proxy looks up the address. For what still goes around the proxy, see DNS.

DoH (DNS over HTTPS)

DNS lookups inside a regular encrypted HTTPS connection. No one on the way can see which names you look up. In browsers, you turn it on in the settings; the setting is called “DNS over HTTPS” or “secure DNS”.

In Routekeeper: if the whole browser goes through a proxy, its DoH lookups go through the proxy along with the rest of its traffic; this way, the “DNS around the proxy” flags for the browser go away. See the recipe.

TLS

Encryption of a connection; it’s what https:// in the address bar runs on. It hides the content from everyone on the way, and with a certificate it confirms that you’re talking to the very server whose name is given. A certificate is issued for a domain name, for example for free by Let’s Encrypt.

In Routekeeper: an HTTPS proxy encrypts the connection to the proxy with TLS; if the certificate doesn’t match the name in the Server field, the check shows “Couldn’t connect to the proxy: TLS: the proxy’s certificate failed validation”.

Mac and apps

Network extension

A module through which a program can filter and route network connections in macOS. It’s installed as a system extension: separately from the app’s window, and only with the user’s permission. The extension runs on behalf of the system, so it keeps working even when the window is closed.

In Routekeeper: the extension is called Routekeeper Extension (in version 0.2.1, Routekeeper Network Extension), and its status is shown in Settings → Extension. See What Routekeeper is made of.

Child process

A program that another program has launched. Terminal launches git, curl and npm. Browsers and messengers launch helper processes, and almost all of their traffic goes through them.

In Routekeeper: Include Child Processes is on by default: the app’s route applies to its helper processes and to everything it launches. See Apps and services.

Code signature

A digital signature that a developer puts on their program. It shows who released the program (the developer’s Team ID) and which program it is (an identifier like com.example.app). If the program is changed after it was signed, the signature no longer matches.

In Routekeeper: apps are recognized by their signature, not by the file name: a renamed program won’t fall under someone else’s rule, and a rule survives an app update. Programs without a signature are recognized by the path to the file.

localhost (loopback)

The addresses that a Mac uses to reach itself: 127.0.0.1, ::1 and the name localhost. Such connections don’t go out to the network. For example, apps use them to connect to a proxy client running on the same Mac.

In Routekeeper: connections to the Mac itself go direct; the built-in rules and the Settings → Network → Leave localhost alone setting make it so.

Local network

The networks the Mac itself is on: a home or office network over Wi-Fi or a cable, and also networks that a VPN opens, such as a corporate VPN or Tailscale. Their addresses are usually private: 192.168.…, 10.…, 172.16.…–172.31.…, and 100.… for Tailscale. They can’t be reached from the internet, so a remote proxy can’t reach them either.

In Routekeeper: starting with version 0.4.0, an app that goes through a proxy as a whole reaches local networks directly. This is the Settings → Network → Local networks go direct setting, on by default. The exact conditions are in Which rule wins.

Addresses in rules

Subnet (CIDR)

A way to write a range of IP addresses: an address, a slash and the prefix length. 10.0.0.0/8 is all addresses from 10.0.0.0 to 10.255.255.255, and 192.168.1.0/24 is from 192.168.1.0 to 192.168.1.255. The bigger the number after the slash, the narrower the range.

In Routekeeper: you can use a subnet in a rule, and some services already include subnets. See how to write an address in a rule.

Wildcard *.domain

An asterisk in place of any subdomain. Without the asterisk, a rule matches only one name; with it, a rule matches a whole family of names.

In Routekeeper: *.example.com matches both example.com itself and all its subdomains at any depth, for example a.b.example.com; a longer wildcard is more specific, so *.mail.example.com beats *.example.com.

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