Free tool · 🚪 Open port checker
Is the port openfrom outside?
Port-forwarding not working? Firewall rule unclear? Test from our server in India and see open, closed or filtered in seconds — with the common service name next to each port.
Only public hosts; private ranges are refused. Up to 12 ports per run, 15 runs per 10 minutes. Exposed database or RDP ports showing “open” are a risk — close them or put them behind a VPN.
What it checks
Everything we would look at first on a client call.
Free, no sign-up, no email gate. If the report shows red, the fix is written next to it — and we are one click away if you would rather we did it.
- Open / closed / filtered with connect time in ms
- Common service names (SSH, RDP, Proxmox, MySQL…)
- Presets for web, admin, mail and database ports
- Security hints for ports that should never be public
FAQ
Common questions
Open vs filtered vs closed?
Open: something answered. Closed: the host replied “nothing here”. Filtered: no reply — a firewall or NAT is dropping packets, or the host is down.
My port shows filtered but the service runs.
Check in order: service bound to 0.0.0.0 (not 127.0.0.1), host firewall (ufw/firewalld/Windows), router port-forward, ISP CGNAT (most home connections) — with CGNAT inbound ports never work; use a VPS/tunnel.
Is this a port scan?
It is a connect test to ports you name on a host you control. Do not test hosts you are not authorised to.