Network
Check single TCP ports or scan entire service profiles — web, mail, databases, remote access, and cloud — with quick presets, custom port ranges, and security context for exposed services.
Tests from SkyPath's network, not your device
| Port | Service | Status | Time |
|---|---|---|---|
| Waiting to scan… | |||
Open means SkyPath's network reached the host and the port accepted a TCP connection — the service is reachable from the internet on that port.
Closed means the host responded but nothing is listening on that port, or the connection was actively refused.
Filtered usually means a firewall dropped the connection without a clear refusal — common when a port is blocked but not explicitly closed.
Use scan profiles to audit web stacks, mail servers, databases, or remote-access ports in one pass — faster than checking ports one by one.
Open ports on Redis (6379), MongoDB (27017), RDP (3389), or Docker API (2375) include security context — these services are frequently attacked when exposed publicly.
TCP checks are live today. UDP is selectable for context on DNS and WireGuard, but UDP probing is not supported on SkyPath yet.
This test runs from SkyPath's servers, not your browser. Results show what the host exposes to the public internet, which may differ from your local network view.
TCP checks whether a host accepts a connection handshake — useful for web servers, SSH, databases, and most admin services.
UDP checks whether a host responds to datagram traffic — common for DNS, VPN tunnels, and game servers. SkyPath currently supports TCP checks only.
Computers expose services on numbered ports — for example, HTTPS on port 443 and SSH on port 22.
A port check attempts to open a TCP connection to a host and port. If the connection succeeds, the port is open. If it is refused or times out, the port is closed or filtered.
Industry port scanners group checks by purpose — web, mail, remote access, databases, and cloud infrastructure.
SkyPath offers six profiles plus custom input: enter comma-separated ports (80,443) or ranges (8000-8010) for up to 32 ports per scan.
Open: a service is listening and accepted the connection.
Closed: the host is reachable but nothing accepted traffic on that port.
Filtered: packets were dropped or timed out, often because a firewall silently blocked the attempt.
UDP port checks are not available yet.
Results reflect reachability from SkyPath's network, not from your home or office connection.
Some hosts rate-limit or block port probes from cloud networks, which can look like a filtered port even when the service is up.
An open port means a TCP connection to that host and port succeeded from SkyPath's network. A service is listening and reachable on the public internet.
Yes. Switch to Port scan, pick a profile like Common services (32 ports), Web stack, or Databases — or enter custom ports like 80,443 or 8000-8010. Results stream in as each batch completes.
Yes. Use quick-pick chips for SSH, HTTPS, RDP, and more in single-port mode — or run a scan profile to check dozens of ports in one pass.
Closed usually means the host actively refused the connection — nothing is listening on that port. Filtered often means a firewall dropped the packets without a clear refusal, so the check timed out.
Not yet. You can select UDP to see which services typically use it, but SkyPath currently performs TCP connection checks only.
This tool checks remote hosts from SkyPath's servers. Private and local addresses are blocked. To test ports on your own machine, use a local scanner or check from another device on your network.
Firewalls, security groups, ISP filtering, or anti-scan rules can drop probe traffic. The service may be reachable from some networks but not from SkyPath's test origin.
Checking ports you own or have permission to test is generally fine. Scanning systems you do not control may violate terms of service or local law. Use this tool responsibly.
SkyPath VPN
SkyPath VPN is free for Android — one tap to connect, no account, no logs.
Download SkyPath VPN