IPSONIC / L4-CHECK
DEVELOP · OPERATE · SECURE

l4-check.

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.

VERSION 0.3.8   /   WINDOWS x64 + LINUX x86_64   /   BINARIES + OPTIONAL SOURCE
Neon-purple cyber unicorn
01 / THE APPROACH

Visibility without complexity.

Operators should not need a privileged daemon, a kernel extension or a monitoring stack just to inspect observed socket destinations.

01 — UNPRIVILEGED

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.

02 — POLLING ONLY

Use native OS data

The Windows IP Helper API provides TCP IPv4 snapshots; Linux procfs also supports TCP/UDP IPv4/IPv6. The interval is configurable in milliseconds.

03 — STANDALONE

Keep dependencies small

Compiled Free Pascal binaries. No Python environment, JavaScript runtime, network service or external CLI tool at runtime.

ON-PREMISE FIRSTCLOUD AGNOSTICOPERATOR FRIENDLYNO TELEMETRYKISS PRINCIPLE
02 / CAPABILITIES

Useful signals. Straight from the CLI.

Filter noise, inspect observed connections, and export structured data for further analysis.

MONITOR

Destination visibility

Protocol, PID, process name, destination IP and port, plus source port and TCP state where available.

TRACK

Socket lifecycle

NEW, CLOSED and STATE changes; observed lifetime for sockets seen in consecutive polls.

FILTER

Focus on what matters

Filter by process, PID, protocol, destination address, port and IPv4 CIDR; exclude known traffic.

EXPORT

Pipeline ready

Human-readable text, JSONL and CSV; one-shot scans and ISO-8601 timestamps for scripting.

ANALYZE

Operational statistics

Periodic counters, process totals and an optional summary for one-shot inspection.

IDENTIFY

Traceable source

One-line version output with a source fingerprint; distributed binaries can be verified using SHA-256 checksums.

03 / INTERNET EGRESS VISIBILITY

What does this Windows client actually connect to?

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.

PUBLIC FIRST

Internet traffic is the starting point

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
PROXY & SWG

Look beyond the gateway logs

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
INCLUDE INTERNAL

Expand the scope when needed

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
Important interpretation: A public destination observed on a client is a reason to investigate, not proof of proxy bypass. Some SWG architectures use endpoint agents, transparent interception or tunnels; and proxy connections can terminate at public addresses. l4-check reports socket endpoints, not routing paths, URLs, TLS content or policy compliance. Correlate with SWG logs, proxy configuration, firewall telemetry and route information. Short-lived sockets may be missed.
04 / COMMAND LINE

From zero to signal in one command.

Readable defaults, composable flags and straightforward integration with existing operator workflows.

Continuous polling./l4-check --interval 100

Scan at a configured minimum interval in milliseconds.

Follow lifecycle events./l4-check --events new,closed,state

Watch new, disappeared and state-changing sockets.

Investigate HTTPS./l4-check --dst-port 443

Limit output to a process and destination port.

Machine-readable snapshot./l4-check --once --format jsonl

Use JSON Lines for pipelines and automated inspection.

Show private destinations./l4-check --all --exclude-port 53

Include non-public destinations and exclude DNS port 53.

Get built-in help./l4-check --help

View the available flags, defaults and examples.

Know what you are seeing. Polling reports socket snapshots, not individual packets or every connection attempt. Short-lived connections may be missed; unavailable process ownership is shown as unknown. A CLOSED event means a socket disappeared from the observed snapshot.
05 / REAL-WORLD USE CASES

Find the destination. Understand the process.

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.

01 / TROUBLESHOOTING

Which internet endpoints does this Windows app use?

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
02 / FIREWALL PLANNING

Identify required egress destinations

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
03 / APPLICATION DEBUGGING

Investigate connection behavior

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
04 / SECURITY TRIAGE

Spot unfamiliar outbound targets

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
05 / SUPPORT & OPERATIONS

Investigate without admin access

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
06 / AUTOMATION

Feed existing operator workflows

Use JSONL or CSV snapshots for incident notes, comparisons and downstream scripts without deploying a dedicated monitoring stack.

l4-check --once --format jsonl
07 / PROXY VALIDATION

Verify proxy routing

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
08 / THIRD-PARTY SERVICES

Discover external service dependencies

Observe network destinations during application startup, authentication and common workflows to identify potential external dependencies.

l4-check --format jsonl --interval 200
09 / SOFTWARE UPDATES

Inspect updater traffic

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
10 / CHANGE VALIDATION

Compare before and after a change

Capture connection snapshots before and after configuration or deployment changes to identify newly observed destination endpoints.

l4-check --once --format csv
11 / VPN & SPLIT TUNNEL

Review destinations during VPN tests

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
12 / WINDOWS ENDPOINT TRIAGE

Investigate Windows endpoint connections

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
13 / INCIDENT HANDOFF

Create portable diagnostic evidence

Capture a machine-readable view of observed sockets for support cases and incident handoffs without requiring elevated access.

l4-check --once --format jsonl
14 / NETWORK MIGRATION

Check dependencies after migration

Review observed destinations when moving a workload to a new network, firewall zone or hosting environment.

l4-check --events new,closed --interval 250
15 / PORT-SPECIFIC ANALYSIS

Focus on a service port

Narrow investigations to one destination port, such as HTTPS, when other application traffic makes the output noisy.

l4-check --dst-port 443 --interval 100
Operational boundary. Polling cannot guarantee complete egress discovery: short-lived connections may fall between scans, and process attribution depends on OS permissions. Use results as observed evidence, not as an exhaustive firewall policy or packet-level audit.
WINDOWS / USER-LEVEL OUTPUT

What a user sees.

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 Windows PowerShell screenshot showing l4-check TCP connection output with process names, destination IPs and ports

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.

06 / BINARY RELEASE

Download. Run. Inspect.

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.

WINDOWS / x64

l4-check 0.3.8 for Windows

Download the Windows executable and start it from PowerShell or Command Prompt.

↓ Download Windows binary

SHA-256: 9532ce152a5aba59eac3a494d3d25ea041371c8316d514094bd27b514247b333

.\l4-check --help
.\l4-check --interval 100
LINUX / x86_64

l4-check 0.3.8 for Linux (also available)

Download the executable and run it as your regular user.

↓ Download Linux binary

SHA-256: 542d899f83bc835be6c9f7be51b0212cbad3374b84e3831047e888080334f4bd

chmod +x ./l4-check
./l4-check --help
./l4-check --interval 100
Verify your downloads. The SHA-256 checksums shown above identify the downloadable binaries in this directory.
07 / OPTIONAL SOURCE

Inspect the code. Build it yourself.

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.

PASCAL SOURCE

l4-check.pas

Single-file application source, provided as-is for review and independent compilation.

↓ Download Pascal source

SHA-256: 2aa84bc64be72c7b0c5a95e4cd11cea303074d0cae6df5cc7a792195130d8925

BUILD ON LINUX

Compile with Free Pascal

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.

Reproducibility note. The standalone Pascal file is useful for inspection; the packaged 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