Port mapping validator
Find overlapping listener addresses and port ranges in a supplied service inventory, including dual-stack assumptions.
Compare exclusive listener assignments within the same supplied host or network namespace and transport. Port ranges include both endpoints. A wildcard overlaps all addresses in its family. An IPv6 wildcard also overlaps IPv4 when ipv6Only is false. IPv4-mapped IPv6 addresses use IPv4 identity and require an empty ipv6Only field. Scoped link-local addresses retain their interface identity. Service names remain unchanged. No DNS lookup, real socket probe, NAT translation, socket reuse, multicast or firewall reachability is inferred. More than 5000 conflicting pairs rejects the full report rather than truncating it. Runs locally without uploads. Limit: 500000 combined input characters, 1000 services and 5000 conflicting pairs. Complete JSON and JSON Pointer CSV exports are each capped at 2000000 characters; CSV contains at most 200000 typed values. Preview shows at most 200 rows. Calculations stop after 10 seconds. Downloads retain your source inputs, units, assumptions and complete results. Up to 500,000 characters. Review the settings before running.
Your result
How to use Port mapping validator
- Enter one service binding per CSV row with a name, host or network namespace, protocol, numeric address and inclusive port range.
- For IPv6, set ipv6Only to true or false; leave that field empty for IPv4 and IPv4-mapped addresses.
- Review every conflicting pair and download the complete inventory and results.
Useful next steps
Compare bindings within the same namespace
Two services are compared only when their supplied namespace and transport protocol match. Port ranges include both endpoints. A wildcard IPv4 address overlaps specific IPv4 addresses; an IPv6 wildcard also overlaps IPv4 when ipv6Only is false. Scoped link-local addresses retain their interface identity.
Inventory analysis does not probe a running host
The checker does not resolve hostnames, open sockets or inspect a firewall. It models exclusive listeners, without inferring socket reuse, multicast or NAT translation rules. Different namespaces are treated as separate hosts or network namespaces. More than 5000 conflicts rejects the complete report instead of hiding later pairs.