Run as yourself
Run from a standard Windows user session. No Run as Administrator, service installation or elevated PowerShell required. Linux also works without sudo.
TRACE PUBLIC EGRESS. MAP REMOTE ENDPOINTS. SPOT UNEXPECTED DIRECT CONNECTIONS.
Endpoint-side L4 socket visibility for Windows operators. No proxy log required to observe client-side destinations; Linux supported too. Public internet destinations are the default focus; add --all when private destinations matter. Inspect observed remote IPs, ports and process ownership directly from your terminal. No agent. No packet capture. No external runtime dependencies.
Operators should not need a privileged daemon, a kernel extension or a monitoring stack just to inspect observed socket destinations.
Run from a standard Windows user session. No Run as Administrator, service installation or elevated PowerShell required. Linux also works without sudo.
The Windows IP Helper API provides TCP IPv4 snapshots; Linux procfs also supports TCP/UDP IPv4/IPv6. The interval is configurable in milliseconds.
Compiled Free Pascal binaries. No Python environment, JavaScript runtime, network service or external CLI tool at runtime.
Filter noise, inspect observed connections, and export structured data for further analysis.
Protocol, PID, process name, destination IP and port, plus source port and TCP state where available.
NEW, CLOSED and STATE changes; observed lifetime for sockets seen in consecutive polls.
Filter by process, PID, protocol, destination address, port and IPv4 CIDR; exclude known traffic.
Human-readable text, JSONL and CSV; one-shot scans and ISO-8601 timestamps for scripting.
Periodic counters, process totals and an optional summary for one-shot inspection.
One-line version output with a source fingerprint; distributed binaries can be verified using SHA-256 checksums.
Your proxy or Secure Web Gateway (SWG) shows traffic that reaches it. l4-check gives you a complementary endpoint-side view of observed socket destinations — including public connections that may not use your configured proxy.
By default, focus on observed connections to public IP addresses. Reduce internal network noise and identify which Windows applications communicate with external endpoints. Use --all when you also need private or internal destinations.
l4-check --interval 100
A managed proxy or SWG cannot necessarily describe direct connections that never pass through it. Native applications, embedded HTTP clients, updaters or misconfigured software may use a different path. Compare endpoint observations with proxy logs and expected policy.
l4-check --events new --interval 100
Use --all to include private destinations, such as internal servers and proxy IPs. This is useful when investigating the proxy connection itself, split tunneling, internal APIs or other non-public targets.
l4-check --all --interval 100
Readable defaults, composable flags and straightforward integration with existing operator workflows.
./l4-check --interval 100Scan at a configured minimum interval in milliseconds.
./l4-check --events new,closed,stateWatch new, disappeared and state-changing sockets.
./l4-check --dst-port 443Limit output to a process and destination port.
./l4-check --once --format jsonlUse JSON Lines for pipelines and automated inspection.
./l4-check --all --exclude-port 53Include non-public destinations and exclude DNS port 53.
./l4-check --helpView the available flags, defaults and examples.
unknown. A CLOSED event means a socket disappeared from the observed snapshot.Built for Windows administrators who need to understand client internet egress, verify proxy/SWG expectations and troubleshoot applications — without requiring an elevated PowerShell session. Linux is supported too.
Observe public destination IPs and ports while launching a Windows desktop application or reproducing an error. Useful when documentation does not describe all network endpoints.
l4-check --interval 100
Collect observed public destinations before proposing outbound firewall rules. Export the findings for review rather than assuming that the observed set is complete.
l4-check --once --format csv
Inspect new sockets and TCP state changes during Windows application login, API calls, updates or service startup. Compare behavior before and after configuration changes.
l4-check --events new,closed,state
Review processes communicating with unexpected public addresses, including traffic absent from expected SWG logs. Unknown process ownership remains visible instead of silently dropping the socket.
l4-check --interval 250
Run directly from a Windows helpdesk session without installing a service, packet-capture driver or agent. Process names may be unavailable without privileges.
l4-check --all --once
Use JSONL or CSV snapshots for incident notes, comparisons and downstream scripts without deploying a dedicated monitoring stack.
l4-check --once --format jsonl
Investigate public remote endpoints when an application is expected to use your proxy or SWG. Correlate with gateway logs; endpoint socket data alone cannot prove bypass.
l4-check --dst-port 443 --interval 100
Observe network destinations during application startup, authentication and common workflows to identify potential external dependencies.
l4-check --format jsonl --interval 200
Observe where Windows desktop software connects during update checks and downloads. Useful for diagnosing blocked or unexpected update endpoints.
l4-check --interval 100 --events new
Capture connection snapshots before and after configuration or deployment changes to identify newly observed destination endpoints.
l4-check --once --format csv
Observe public remote endpoints while testing Windows VPN or split-tunnel behavior. Socket destinations do not prove which network interface carries the traffic.
l4-check --all --interval 250
Review TCP IPv4 remote endpoints on a Windows workstation, including internal network targets. DNS queries are not captured on Windows.
l4-check --all --dst-port 53
Capture a machine-readable view of observed sockets for support cases and incident handoffs without requiring elevated access.
l4-check --once --format jsonl
Review observed destinations when moving a workload to a new network, firewall zone or hosting environment.
l4-check --events new,closed --interval 250
Narrow investigations to one destination port, such as HTTPS, when other application traffic makes the output noisy.
l4-check --dst-port 443 --interval 100
A representative Windows PowerShell session showing what any user can observe without administrator privileges: TCP connections, owning processes when available, destination IP addresses and ports. Public destinations are the default scope; use --all to include private and reserved addresses.
Illustrative output, not a live capture. Example destinations and process associations are fictional; 1.1.1.1 and 8.8.8.8 are documentation addresses and would not appear in the default public-only view. Proxy or SWG bypass cannot be established from this output alone.
Precompiled standalone executables for Windows x64 and Linux x86_64. No installer or build toolchain required for the binaries. The Pascal source is available separately for inspection and optional local builds.
Download the Windows executable and start it from PowerShell or Command Prompt.
↓ Download Windows binarySHA-256: 9532ce152a5aba59eac3a494d3d25ea041371c8316d514094bd27b514247b333
.\l4-check --help .\l4-check --interval 100
Download the executable and run it as your regular user.
↓ Download Linux binarySHA-256: 542d899f83bc835be6c9f7be51b0212cbad3374b84e3831047e888080334f4bd
chmod +x ./l4-check ./l4-check --help ./l4-check --interval 100
Prefer the ready-to-run Windows binary? Just download it above. If you want to audit or compile l4-check yourself, the original Pascal source is available as a separate download. No GitHub account or external source hosting required.
Single-file application source, provided as-is for review and independent compilation.
↓ Download Pascal sourceSHA-256: 2aa84bc64be72c7b0c5a95e4cd11cea303074d0cae6df5cc7a792195130d8925
Install Free Pascal Compiler (FPC). The build script creates the required build metadata automatically:
./build.sh linux
For Windows x64 cross-compilation, FPC requires matching Win64 RTL units. The complete build script and cross-build setup are included in the source/build package.
build.sh also generates buildinfo.inc with source fingerprint and target metadata required by the program. Use the source/build package and ./build.sh linux, ./build.sh windows64, or ./build.sh all.tar xzf l4-check-source.tar.gz cd l4-check ./build.sh check ./build.sh all
Source/build archive SHA-256: 7c333ffb8c45a40738b3f50fab185bdc930868ddaaf76e4cb51facb7628a7cec