About this tool & how to scan it
Port Leak Checker passively records inbound TCP SYN and UDP packets that reach this server. Point a device under test at this server's IP and send traffic (or scan) across the ports and protocols you want to verify — every probe that actually arrives is logged below with its source IP, protocol, destination port and time. Filter by the test device's source IP to isolate your own traffic.
Because packets are captured as they arrive on the wire, anything shown here genuinely traversed the full network path: an intermediary that fakes an “open” port during a scan cannot make a real packet appear here. This is what makes it useful for confirming which outbound ports a restrictive network actually lets through.
This server never replies. It only listens passively, so your scanner will report ports as filtered or closed rather than open — that is expected. The evidence is this log, not the scanner's verdict: if a probe appears here, it reached the server.
Ready-to-run scan scripts (Windows PowerShell, bash and sh) and other scan methods can be found on the scan scripts page.
Scan slowly. Every captured packet is written to disk, so pace your probes or some will be missed. Use a slow Nmap timing template or a scan delay, for example:
nmap -sS -T2 -p- <server-ip> (TCP, all ports)
nmap -sU -T2 --top-ports 100 <server-ip> (UDP)
nmap -sS --scan-delay 100ms -p 1-1024 <server-ip> (fixed delay)
A full-speed blast (-T4/-T5) across all 65,535
ports can outrun capture and drop probes, giving you an incomplete picture.
| No packets captured yet. |