Proxy tools
TCP port checker
Find out whether a TCP port on a public host accepts connections — useful for proxy ports, game servers and firewall checks.
One TCP connection attempt to one public host and port. Scanning ranges or private networks is not possible.
How it works
What this tool does
Resolve and verify
We resolve the host and confirm every address is public.
One connection attempt
We try a single TCP connection with a short timeout.
Report the state
Open, closed (refused) or filtered/offline (no answer).
How to read the result
“Open” means something accepted the connection. “Closed” means the host answered that nothing listens. “No answer” can mean a firewall drops packets or the host is offline.
Only public addresses are allowed and only one port per request, so this tool cannot be used to scan networks.
In depth
The details that decide the outcome
What a TCP connect attempt can and cannot tell you
A TCP connection begins with a three-way handshake: the client sends SYN, a listening service answers SYN-ACK, and the client confirms with ACK. If the host is reachable but nothing listens on the port, the operating system replies with a reset and the tool reports closed, usually after about one network round trip. If a firewall silently drops the packets, nothing comes back and the tool reports filtered after five seconds. Other network errors are also shown as filtered. The tool closes the socket immediately after connecting and sends no data.
The safeguards shape what you can test. The host name is resolved first and every address must be public; the connection then goes to that verified address, preferring IPv4 when a name has both, so enter an IPv6 literal to test the IPv6 path. Only one host and one port from 1 to 65535 are accepted per request, and the request body is tiny, so the tool cannot scan ranges or reach private networks. The latency shown covers the connection attempt itself, measured after name resolution.
Worked reading: open, closed and filtered on a proxy port
Take a proxy listening on port 3128 (placeholder). Result open in 40 ms: something accepted the connection, which proves reachability but not that it is a proxy, so run the proxy checker next. Result closed in 35 ms: the host is up and rejected the port, so the service is stopped, bound to another port or bound only to localhost. Result filtered at about 5,000 ms: the attempt hit the five-second limit, which points to a firewall drop, an offline host or a routing problem. The timing is a clue: a quick answer means the host replied, while about five seconds means silence.
Two traps are common. First, a firewall that admits only certain source addresses drops this tool’s connection even though the port is open for you, so a service that works from your office shows filtered. Likewise, a service bound only to localhost shows closed from outside, whatever the firewall allows. Second, a TCP result says nothing about UDP: game servers and SOCKS5 UDP relays often use UDP, which this tool never tests. Use the result to find where the path breaks, then confirm with the real client.
| State | Typical time | Meaning | Next step |
|---|---|---|---|
| Open | Tens of milliseconds, depending on distance | A service accepted the TCP connection | Run the proxy or HTTP checker to test the service itself |
| Closed | About one round trip | The host answered that nothing listens there | Check the port number, service status and bind address |
| Filtered | About 5,000 ms | No answer: dropped packets, offline host or routing problem | Check firewalls, security groups and source-address rules |
FAQ
Tool questions
Can I scan a range?
No. One host and one port per request.
Why is my port “filtered”?
A firewall may drop packets silently; check security groups and local firewall rules.
Does it test UDP?
No, only TCP.
Why does the checker say filtered when I can connect from my computer?
The connection comes from this site’s server, not from your device. Source-address rules, geographic filters or provider firewalls that admit only your network make the port look filtered here. Test from a second location and review every rule that mentions source addresses.
Can I check a port on my home PC or router?
Only if it is reachable from the public internet on a public address. Private addresses are blocked, and a home connection behind carrier-grade NAT or without a port-forward rule will not accept inbound connections, so the result will be closed or filtered even if the service runs locally.
Not sure which plan fits?
Describe your use case and target countries and we will recommend a product — or tell you honestly when another type suits you better.