What is a TCP port check?
Computers expose services on numbered ports — for example, HTTPS on 443 and SSH on 22.
A port check opens a TCP connection to a host and port from SkyPath’s network. Success means open; refuse means closed; timeout often means filtered.
Check port forwarding from outside your LAN
To verify a router rule, run this check against your public IP (filled in on load — or confirm it with What Is My IP).
The service must be listening on the device, the router must forward that TCP port to it, and the ISP must not block the port. Residential ISPs often block inbound 25, 80, or 443.
Open here means the public internet can reach that forward. Closed or filtered usually means the forward, firewall, or ISP path still needs work.
Open vs closed vs filtered
Open: a service accepted the TCP handshake from SkyPath’s edge.
Closed: the host actively refused the connection — nothing is listening on that port from our path.
Filtered: packets were dropped or timed out without a clear refusal. A firewall, security group, or ISP filter may be dropping probes even when the service works for other clients.
If you only need to know whether the host answers at all, try Ping Test. For WireGuard, games, and other datagrams, use the UDP Port Checker.
Dangerous ports when left open
An open port is not always a problem — HTTPS on 443 is expected. Some listeners are high risk if exposed without authentication.
Treat unexpected open RDP (3389), Redis (6379), MongoDB (27017), or Docker API (2375) as urgent: restrict them to VPN or private networks, or shut them down.
Scan profiles and custom ranges
Named profiles group common ports by purpose — web, mail, remote access, databases, and cloud.
Custom mode accepts comma-separated ports (80,443) or ranges (8000-8010), up to 32 ports per scan.
Limitations
Results reflect reachability from SkyPath’s network, not from your home or office connection.
Some hosts rate-limit or block probes from cloud networks, which can look like a filtered port.