Port Scanner

A scan returns three states, not two — and closed tells you something filtered doesn't. Plus why container networking and IPv6 leave ports open you thought were blocked.

Zero Trust networking changes what open internal ports mean — in a perimeter model, internal ports are assumed safe; in Zero Trust, every service must authenticate every connection regardless of network location. Here's how microsegmentation makes port scanning a policy verification tool, why service mesh mTLS decouples open ports from accessible services, and what Kubernetes port exposure looks like from an external scanner.

The entire internet-facing IPv4 space can be scanned in under an hour — Shodan and Censys already have your server's open ports catalogued. Here's what banner grabbing reveals (exact software versions → known CVEs), the difference between open/closed/filtered port states and why "filtered" is the preferred security posture, why SYN scanning doesn't appear in application logs, and what to look for when port scanning your own infrastructure.

A misconfigured open port on an IPv4 server gets found by automated scanners within hours, because the entire IPv4 address space is small enough to scan exhaustively. The same misconfiguration on an IPv6 server might never be found this way — not because it's more secure, but because 2^128 addresses is too large to scan at any practical rate. Here's how IPv6 hosts actually get discovered instead (DNS records, certificate transparency logs, predictable address patterns), and why "too big to scan" is security through obscurity, not security.

Most home network ports show "filtered" from the internet — not because of a configured firewall, but as a side effect of how NAT works: incoming connections without an existing mapping have nowhere to go. Here's the open/closed/filtered distinction, how NAT creates this effect, why port forwarding and UPnP change it, and the CGNAT limitation that can make port forwarding fail entirely.