NETWORK DIAGNOSTICS
Test whether a TCP port on a public internet host can be reached from the PacketPint server.
A limited number of checks per visitor and target IP is applied. This tool is intended for routine connectivity diagnostics, for example checking whether a port behind a firewall is actually filtered from the public internet, and is not designed to survey open ports on a target.
The checker resolves the submitted host to a public IP address, opens one TCP connection to the selected port and closes it immediately. It is similar to a netcat zero-I/O port test, but it runs from the PacketPint server rather than your own network.
The result shows whether that single TCP connection could be established, the public IP actually tested and the connection-attempt time. It does not send an HTTP request, TLS handshake, login attempt or any other protocol data.
It means the PacketPint server established a TCP connection to the tested public IP address and port. It does not verify the application behind that port or whether the same connection would succeed from your own network.
A firewall, allowlist, geographic rule, rate limit or routing problem can block connections from the PacketPint server. A TCP service can also be available only on another IP address behind the same hostname.
No. It only attempts the TCP connection and closes it if successful. It does not send application data, credentials, protocol commands or a request payload.
Allowing a public tool to connect to private, loopback, link-local or reserved addresses could expose internal services or cloud metadata endpoints. The checker accepts only globally routable public IP addresses.