Skip to content
Get ProGet Pro

Network footprint and the firewall rule

Every connection Guard makes, which ones are optional, how to see them, and a firewall rule that enforces them.

Guard’s runtime connections are listed below. Installation separately downloads and verifies release assets; the relay and telemetry are not enabled runtime features.

ConnectionDirectionWhenDefault
api.hyperliquid.xyz:443 (HTTPS, WebSocket)outan account on mainnet: prices and the account in paper mode, also orders in mainnet modeon for a mainnet account
api.hyperliquid-testnet.xyz:443outan account on testnet: prices and the account in paper mode, also orders in testnet modeon for a testnet account
DNSoutto resolve the aboveon
127.0.0.1:8547in, from your machineyour boton
the relay (WebSocket)outTradingView alerts, browser Guardoff
telemetry heartbeat (version, venue, number of vetoes)outcounting installsoff
zunderlabs.com:443 (/api/licence/renewal)outlicence_auto_update = true: from 14 days before the licence ends, at most every 6 hours, it sends the renewal token and the account address and gets the licence’s newest keyoff

Nothing else. No update check, no crash reporter, no analytics; licence keys are checked offline. The relay and telemetry are not built: guard.toml has no setting for either yet, and when they come they will be off until you switch them on.

Zunder’s own executor already behaves this way on the trading side: it goes to the configured network’s URL only, refuses plain HTTP and follows no redirects (docs/testnet.md).

Terminal window
# Linux
sudo ss -tnp | grep zunder-guard
# macOS
sudo lsof -nP -i -a -c zunder-guard

The installer runs Guard as its own user, zunder-guard. With nftables, that user may reach DNS and port 443, and nothing else:

Terminal window
sudo nft add table inet zunder
sudo nft add chain inet zunder out '{ type filter hook output priority 0; }'
sudo nft add rule inet zunder out meta skuid zunder-guard oif lo accept
sudo nft add rule inet zunder out meta skuid zunder-guard udp dport 53 accept
sudo nft add rule inet zunder out meta skuid zunder-guard tcp dport 53 accept
sudo nft add rule inet zunder out meta skuid zunder-guard tcp dport 443 accept
sudo nft add rule inet zunder out meta skuid zunder-guard counter drop

The counter on the last rule counts every packet Guard tried to send elsewhere. It should stay at zero:

Terminal window
sudo nft list chain inet zunder out

What this does not prove. A port rule cannot tell api.hyperliquid.xyz from any other server on port 443. Hyperliquid’s addresses are not published as fixed, so pinning IPs is fragile. To restrict by hostname, put Guard behind an allow-listing proxy, or use an application firewall (on macOS, for example, LuLu or Little Snitch) with a rule for zunder-guard that allows Hyperliquid’s hostnames. Also allow zunderlabs.com if you enable automatic licence renewal.

Guard opens no port to the outside. If ss -tlnp shows Guard listening on anything but 127.0.0.1 (or the private address you configured), stop it and check guard.toml.

This page as plain Markdown, for people and LLMs: /docs/deploy/network-footprint.md