Which ports on your server are actually reachable from the internet?
You opened a firewall port and restarted the service. Portpeek tells you what the outside world actually sees — from outside your network, in real time.
The distinction most tools blur
REFUSED
The host is reachable — something answered and sent a TCP RST. Nothing is listening on that port. The fix: start the service or check your application config.
TIMED OUT
Nothing answered at all. A firewall or network filter is silently dropping the connection. The fix: check your security group, ACL, or iptables rules.
Portpeek always tells you which one it saw — because the right fix depends on knowing the difference.
What Portpeek gives you
Real TCP connections
Opens actual outbound TCP connections from outside your network — not a simulated check. You see exactly what a real client would see.
Per-port timing
Every port gets its own latency measurement down to the millisecond. See how fast each service responds.
Parallel probing
All selected ports are checked simultaneously — scan time depends on network conditions and port count.
No setup, no accounts
Type a hostname, pick the ports you care about, click Scan. No signup, no config, no stored data.
How it works
Enter a target
Type a bare hostname (example.com) or IPv4 address. No protocol prefix, no path.
Pick ports
Select from common service ports (HTTP, HTTPS, SSH, database) or enter a custom port. Up to 10 per scan.
Read the results
Each port shows its state — OPEN, REFUSED, or TIMED OUT — with response time and a plain-English explanation.