Portpeek
Which ports on your server are actually reachable from the internet?
Portpeek opens a real TCP connection from outside your network and tells you exactly what happened — connected, refused, or timed out — because the fix is different for each.
| Port | Status | Time | What it means |
|---|---|---|---|
| 80 | open | 42ms | HTTP is listening and reachable |
| 443 | open | 38ms | HTTPS is listening and reachable |
| 22 | refused | 12ms | Host answered but nothing listening there |
| 3306 | timeout | 5000ms | No response — firewall or packet drop |
One port we cannot check: Port 25 (SMTP) is blocked on our platform — outbound SMTP is prohibited. Every other port 1–65535 is fair game. If a host is itself behind Cloudflare, TCP connections to it may appear as timed out rather than refused; this is a platform limitation, not a problem with your network.
- Real TCP connections — every check opens an actual outbound TCP socket, not a ping or heuristics.
- Three distinct answers — open, refused, timed out — each tells you something different.
- Measured timing — every result includes real connection time in milliseconds.
- No accounts, no setup — type a hostname, pick ports, get an answer. Nothing is saved.
Why the distinction matters
- Open
- Your service is running and reachable. You can connect.
- Refused
- Your host is reachable, but nothing is listening on that port. Check whether your application started and bound to the right interface.
- Timed out
- Nothing answered at all. A firewall is silently dropping traffic, or the host is unreachable. Check your security group, iptables, and whether the host is online.