# Discovery advertises every route to a machine `internal/discovery.Plan` adds two optional TXT keys to the `_pipelines._tcp` record: `ts=[,]` lists the host's tailnet addresses (100.64.0.0/10, found on any up interface, including the tunnel interfaces `LANAddresses` skips) and `public=` is the TLS front's origin for the same web proxy, taken from `PIPELINES_WEB_PUBLIC_URL`, which the installer already exports to the server process. `PublicOrigin` accepts only a bare origin: no credentials, path, query or fragment. `Browse` returns `FoundServer.Addresses`, every route to the same machine with `Kind` `lan` (the mDNS A record and advertised port), `tailscale` (same scheme and port on each tailnet IP) or `public` (`wss://` for an https origin, path `/connect`). `Endpoint` stays the LAN route for older clients. The `discover_servers` RPC and `/discovery` (and the proxy's `/api/discovery`, which forwards the body verbatim) carry the same `addresses` array. A Tailscale HTTPS certificate covers only the MagicDNS name, so there is no `wss://` route; the tailnet IP route is `ws://` on the plain web port, encrypted by WireGuard. Tests: `TestPlanAdvertisesTailnetAndPublicRoutes`, `TestBrowseListsEveryRouteToTheSameMachine` (unsafe `ts`/`public` values are dropped). `go test ./internal/discovery ./internal/server ./internal/protocol` passes.